Linux

In ~/src Mostly because I'm too lazy to type "source".

Putting one directly under the home directory feels like a psychopathic move, so I stay by XDG and put them under a subdirectory of xdg-documents

~/git, for projects I cloned from the web because I don't know how to code :(

~/src

I NEED TO LEARN HOW TO GIT.

https://media.tenor.com/Te4dsU13mkMAAAAM/bernie-mac-smh.gif

~/.projects

${HOME}/repos

~/workspace/git

That way I can also keep other stuff in the same "workspace" directory and keep everything else clean

I have a Code, simulations, ECAD, and FreeCAD folder in the workspace folder where projects or 1-offs are stored and when I want to bring them to git, I copy them over, play around in the project folders again, then copy changes over when I am ready to commit.

I could better use branching and checking out in git, but large mechanical assemblies work badly on git.

~/src/${reponame}

~/code/$LANGUAGE/$REPONAME

~/git

I used to use ~/devbut for years now I use ~/Workspace becaue Eclipse made me do it

~/code for everything I want to change/look at the source code.

~/.local/src for stuff I want to install locally from source.

~/dev/, with project/org subdirectories

~/src/

Simple, effective, doesn't make my home folder any more of a mess than I already left it as.

C:\repos or ~/repos

All over the place...

~/dev

/dev/null

~/repo for code I write and ~/src for code I didnt.

~/Projects

XDG Documents folder

For a project called "Potato Peeler", I'll put it into a structure like this:

~/Projects/Tools/Potato-Peeler/potato-peeler/

Tools/ is just a rough category. Other categories are, for example, Games/ and Music/, because I also do gamedev and composing occasionally.

Then the capitalized Potato-Peeler/ folder, that's for me to drop in all kinds of project-related files, which I don't want to check into the repo.

And the lower-case potato-peeler/ folder is the repo then. Seeing other people's structures, maybe I'll rename that folder to repo/, and if I have multiple relevant repos for the Project, then make it repo-something.

I also have a folder like ~/Projects/Tools/zzz/ where I'll move dormant projects. The "zzz" sorts nicely to the bottom of the list.

Same, but by language, e.g. Development/Python.

Like others, I have a folder in my home directory called "Code." Most operating systems encourage you to organize digital files by category (documents, photos, music, videos). Anything that doesn't fit into those categories gets its own new directory. This is especially important for me, as all my folders except Code are synced to NextCloud.

~/git/vendor/<gitUser>/<repo>

and

~/git/<myName>/<forge>/<user>/<repo>

Examples:

~/git/vendor/EnigmaCurry/d.rymcg.tech
~/git/mike/forgejo/mikew/myproject
~/git/mike/github/johndoe/otherProject

Most of my code and some non-code is under ~/src, but I have repos scattered all around for other things.

Any naming convention is fine as long as it's meaningful to you. But it's a good idea to keep your own repos separate from the random ones you clone from the internet.

~/repos

~/git/AUR|dev|whatever/$(git clone) is where mine usually reside.

~/source

~/Projects/$TOPIC_OR_LANGUAGE/$PROJECT_NAME

ie.

• ~/Projects/Web/passport.ink for a web dev project
• ~/Projects/Minecraft/synthetic_ascension for a Minecraft mod
• ~/Projects/C++/journalpp for a C++ library

~/projects for things I made

~/git for things other people made

I tend to follow this structure:

Projects
├── personal
│   └── project-name
│       ├── code
│       ├── designs
│       └── wiki
└── work
    └── project-name
        ├── code
        ├── designs
        └── wiki

~/gits

Documentation is usually a doc folder inside the repo or just a README.md for small projects.