Linux Just Standardized Something We All Use

Añadido: 2026-05-07

[00:00:00]Most of us have some sort of folder for things that we're working on.

[00:00:03]In my case, I have a repos folder for my source code.

[00:00:08]I have things like the model folder for 3D models.

[00:00:11]Maybe you have a folder for CAD stuff or a folder for game development or 3D modeling or artwork or anything else like that.

[00:00:20]Most of us have something.

[00:00:23]If you're doing all your work in a web browser with everything saved in cloud storage, sure, maybe you don't.

[00:00:30]But it's such a standard thing that if I say it, all of you probably have some idea of a thing you use.

[00:00:38]But if everyone has some sort of folder, then maybe that should be standardized.

[00:00:44]Maybe there should be a standard folder for projects, for things that we're working on.

[00:00:51]For instance, desktop icons used to be a far more common thing and this had to be linked to a folder.

[00:00:56]With that, we get the desktop folder.

[00:01:00]Most of us have documents.

[00:01:02]So you have the documents folder, downloads, the downloads folder, music, music, pictures, videos, so on and so forth.

[00:01:09]All of these are standardized folders as part of the free desktop XDG user dirs specification with a few others as well.

[00:01:19]But if you want to know the full list of folders, you can go check that out.

[00:01:23]Since there's already precedent for standardized folders, someone had the idea, let's just add another one.

[00:01:29]But this isn't a recent thing.

[00:01:31]Projects directory created September 15th, 2014 by Bugzilla migration user because this came from the original free desktop Bugzilla.

[00:01:41]And back then, it got literally no attention.

[00:01:45]The only attention it got was in 2018 with the migration over from the Bugzilla.

[00:01:52]Currently, XDG user does not specify a directory for environment of projects.

[00:01:57]Weird way to phrase it, but I'm assuming maybe English is not their first language.

[00:02:02]Anyway, for software projects, these usually include source code, version control, compiled binaries, test artifacts, and downloaded dependencies.

[00:02:12]As they are much more than downloads and usually kept indefinitely, they do not fit in there.

[00:02:17]The benefit of defining a projects folder would be that when writing a readme or install script for a project, one could automatically download the source to the user-defined location, set up the build environment, and install from there.

[00:02:29]About six years later, we got a little bit of feedback.

[00:02:35]I wanted to propose this myself, but found out there's already this old existing issue.

[00:02:39]The projects directory is the only directory besides.files and other XDG users in my home folder and has been for years.

[00:02:46]As the OP describes, I mostly use it for software projects, but I believe it can serve any type of project.

[00:02:53]I used it for school projects that didn't necessarily contain software.

[00:02:56]I imagine it can be used for projects in other professions as well.

[00:02:59]A few months later, someone noted it would also be useful for flat-packed IDEs.

[00:03:03]If it's something that has proper access to the file browser portal, that's not an issue.

[00:03:08]It's going to work totally fine.

[00:03:11]But for a lot of the proprietary applications which support Linux but don't support the flat-packed format, you need somewhere for them to go because they won't just be able to access everything unless you just ignore the sandbox and give them access to the entire system.

[00:03:26]So giving them a dedicated folder where everything can be located, this mostly eliminates that issue.

[00:03:34]But the real attention came with a comment from Raz very, very recently.

[00:03:39]It would in addition be very useful for apps like 3D printers.

[00:03:43]It's basically a catch-all when documents doesn't apply.

[00:03:45]He also went and opened up a merge request to get this actually done.

[00:03:51]I do not know if the original portal was already aware of this, but there was a projects folder already defined in XDG user dirs.

[00:04:02]The issue is they didn't create it.

[00:04:06]They didn't finish that final bit of hookup to actually use the folder.

[00:04:11]If we go to this commit here, this is from February 27th, 2007, initial revision.

[00:04:19]Projects is defined in the translate.c file.

[00:04:24]If we go to PO and go down to sv.po, in this file we have projects right here.

[00:04:32]This already existed in the codebase 19 years ago.

[00:04:43]What I think is likely to have happened here is somebody thought it was a good idea to have a projects folder.

[00:04:49]They were working on a projects folder.

[00:04:51]And then they didn't finish the entire chain of things they needed to do to fully implement the folder.

[00:05:02]So 99% of it was already in the codebase and pretty much all it required was just defining it as a default.

[00:05:15]Now the folder exists.

[00:05:17]This got merged with literally no hassle because it's a single line change.

[00:05:21]All the code was already there.

[00:05:22]It was just using the code that had already been defined.

[00:05:27]And then someone got a little bit impatient when they saw the merge was actually done.

[00:05:32]Flatback still has no idea what XDG projects is if you add it to the file systems override.

[00:05:38]It needs some time to get shipped by distros.

[00:05:40]Definitely more than being in Git for 10 minutes.

[00:05:43]It was in Git for about 24 minutes at this point.

[00:05:47]I understand you want to use it, but it's not going to ship out that quickly.

[00:05:54]And very shortly after this, a change also opened up in GLib.

[00:05:57]This currently still sits open.

[00:05:58]I assume there's still some code changes they need to do to make that work.

[00:06:02]And that'll probably happen with the next major release of GNOME, I would assume.

[00:06:08]Especially so if this is going to happen.

[00:06:11]What will happen to the folder's design in Nautilus slash files?

[00:06:15]Will it get a custom icon like the other folders?

[00:06:19]Doing icon design, doing any sort of design does take a bit of time.

[00:06:24]You have to go through design review and make sure it fits the styling guidelines, things like that.

[00:06:28]So it will probably get merged, I would assume in a couple of weeks, maybe a couple of months.

[00:06:35]However, it turns out the discussion was being had back in 2022.

[00:06:40]They thought it was a default folder.

[00:06:43]It actually wasn't.

[00:06:44]So this was probably being created by their distro because some distros did go and create it and it was generally a good idea to have.

[00:06:52]But now that this is the default, the discussion here has been reopened.

[00:06:58]And again, something is probably going to happen here.

[00:07:02]But if you want to use this today, if you're on a rolling release distro like I am, you likely already have a projects folder that exists.

[00:07:10]I don't know if any of the print releases have it yet.

[00:07:14]I think the change was probably made a little bit too close to when they came out for that to actually be merged in.

[00:07:21]But do check for yourself.

[00:07:22]Maybe you already have it.

[00:07:23]At the end of the day, why does this even matter to begin with?

[00:07:27]If you have your own folder, can't you just keep using the folder?

[00:07:32]Yes.

[00:07:33]Yes, you can keep doing exactly that.

[00:07:35]You don't have to use the projects folder.

[00:07:39]But by defining a standard, by defining a default, it encourages application developers to actually go and use the default.

[00:07:49]Not just dump things in your home directory, dump things in the specific default directory that projects go into.

[00:07:58]Because quite a few projects, one of those being Android Studio, like to go and make folders in your home directory, just for themselves.

[00:08:07]Here's your Android Studio projects.

[00:08:10]Here are your other various projects.

[00:08:12]Here's your other projects.

[00:08:13]Here's your other ones.

[00:08:14]And that gets really, really messy.

[00:08:17]Now, one of these is fine.

[00:08:18]And you can obviously always go and just move the files elsewhere and then access them like that.

[00:08:24]But there are some applications which expect their default folder to exist.

[00:08:29]And if it doesn't exist, they will remake it every time you open the app.

[00:08:34]But wouldn't it be nice if that didn't happen?

[00:08:36]You open up an app for the first time and it goes and makes its subdirectory inside the projects folder.

[00:08:42]That is totally fine.

[00:08:43]Keep the work segregated from the rest of the work.

[00:08:45]But it does it in the projects folder.

[00:08:48]However, okay, I do live in reality and I understand that even though config has been defined in XDG user DERS probably since the very start of the project and has existed and a lot of applications do make use of it, there are still apps which spam their configs in the home directory.

[00:09:11]or they spam their data files in the home directory even though there is a defined data directory.

[00:09:20]Assuming apps are actually using it correctly and not just hard coding the project path which some of them do for config, you also get control.

[00:09:29]The power of XDG user DERS is you can go and redefine the directory into a new location.

[00:09:37]So if you don't want these in your home directory, you can put them into their own subdirectory.

[00:09:43]You can put them anywhere you want on your system that they're going to have read and write access to.

[00:09:50]Again, like config though, there are applications which use config but they don't actually use the XDG setting.

[00:09:59]All they do is hard code the path.

[00:10:03]So you change it and all they do is just make their own config folder again.

[00:10:08]But even though there are apps that are not going to use it, it's still a good change because it sets the pathway for things to improve, for things to get better.

[00:10:21]If you don't set that path, then nothing is going to change.

[00:10:25]So let me know your thoughts.

[00:10:27]Do you care about the existence of a projects directory?

[00:10:32]Is this something you're going to use?

[00:10:34]Is this something you were already using?

[00:10:36]Or do you already have a workflow set around your own custom folders?

[00:10:40]And that's just what you're going to keep doing.

[00:10:43]I would love to know.

[00:10:44]So if you like the video, go like the video.

[00:10:47]If you really like the video and you want to become one of these amazing people over here, check out the Patreon, SubcribeStar, Liberpay, linked in the description down below.

[00:10:57]That's going to be it for me.

[00:10:58]And defaults.