1. Create a source control repository containing all your code, and publish it to an online code forge. GitHub’s docs might help with this: https://docs.github.com/en/get-started/start-your-journey
2. Choose an open-source license and add it to the repository as a LICENSE file. If you want to require any projects that build upon yours to be open-source too, the GNU GPL is a good choice. If you want to allow proprietary programs to include your library without releasing any source code other than that which is directly based on yours, the GNU LGPL is good for that. If you want to allow people to do whatever they want, even use all your code as the basis of a proprietary program without credit, the Unlicense is a good choice. There are a lot of licenses with different degrees of “copyleft” and attribution requirements in between. Technically publishing with a license file is all you need to do, but there are more things you should do.
3. Create a README text file describing what your program does, and instructing users on how to compile and run it. Consider including more detailed documentation on how to use it, as well.
4. Clean up your code and file layout so that it’s as easy as is feasible for other programmers to understand.
5. Promote your project to whoever you think might find it useful!

Unfortunately, the state of Android music players is not great. Currently I have two FOSS music players installed: Metro Music Player (the F-Droid version of Retro Music Player) and mucke. mucke has a ton of really cool features that improve the shuffle experience but it’s actually worse than most apps at pulling album art. Retro/Metro has beautiful UI, and has pretty good features for customization, but lacks the cool features mucke has and is less stable. Both have more than one annoying bug, but it took me a while to find music players that had this few dealbreakers.

I suspect Plasma 6 will remove it. Though I’m liking this desktop setup so much I might just keep it for the rest of Debian Bookworm’s lifespan.

this is my “gaming” Plasma activity, so in theory everything I play regularly is there :)

i’m personally fine with the windows being slightly brighter, but i think an almost-black theme would look good too… might experiment with that, thanks for the suggestion!

Me too, but I also think it just looks cool. Sci-fi vibes.

deleted by creator

Details:

• OS is Debian bookworm, DE is Plasma 5.27.
• Plasma theme is Oxygen.
• Icon theme is a slightly modified version of Oxylite, only changes are that it follows my system color scheme, the “inherits” list is different, and the start-here and preferences-system icons have been changed.
• Wallpaper is Haenau.
• I’m using Oxygen for Qt widgets and decorations, with the Obsidian Coast color scheme, and standard Breeze Dark for GTK2.
• Layout is entirely my own. I’m showing my Games activity because the main one contains a folder view that might expose info I don’t want to expose here.

Hopefully this is original enough? I’m not sure. I’ve gotten away with posting desktops with mostly existing themes before, but on other occasions I’ve had posts removed for it. At least I mixed and matched some icons this time.

bonus screenshot with apps:

I know Okular can do at least most of that. Don’t think it’s available for Mac OS X, though.

Depends on a few factors, AFAIK as a non-lawyer. If the license allows closed-source derivatives (i.e. is permissive rather than copyleft), then anyone can create a closed-source version with all of the contributors’ changes, including the original maintainer. And anyone can choose to keep it open-source. The community contributions still to some extent belong to the contributors, though the license waives most of their rights.

Some projects are copyleft, but contributors are required to sign a license agreement (a CLA) which allows a single entity to change the license as they desire, including to closed-source - this is a good reason to avoid such projects. The contributors don’t own their work in such a case, but they can still fork the old project as it was before being taken closed source.

In a copyleft (e.g. GPL) project with no CLA, it’s illegal for anyone to make a closed-source version, and a major contributor could sue even the maintainer for doing so.

In all such cases, the change to a closed-source model does not erase the existence of the open-source code with community contributions. A fork is always possible.