6 ms·

If there is an open source project out there that you want to be involved in, you just start contributing. Either find an open issue you want to fix, or identif

If there is an open source project out there that you want to be involved in, you just start contributing. Either find an open issue you want to fix, or identify some feature or improvement that you would like to see and implement it. This sounds simplistic, but this is really how you can get your start. Starting a new project and getting mind share and traction is a lot of work, so it is often a better use of your time to get involved in an existing project that aligns with your interests. Good luck!

matheusmoreira 4y ago
> you just start contributing Before doing anything I think it's wise to look at how other contributors were treated. Sometimes maintainers just aren't very open to contribution. Gotta pick one's battles, otherwise it can lead to a lot of wasted effort. Spending time exploring a complex codebase and formulating a patch set only to end up being ignored can be a very negative experience.
digisign 4y ago
Hmm, wasn't getting at that aspect, not yet anyway. Rather, I'm looking for information on what languages/libraries are required, setting up a build environment, getting familiar with the GUI libraries, etc. Where are the config files? Glibs? I think that's a thing. Dbus? Styling has completely changed a few times, for example. Basically an up-to-date tutorial. I used to do GUI programming about twenty+ years ago, so wouldn't be a complete newbie. Once done with that, I'll think about focusing on the maintenance or greenfield work I'd like to do.