11–20 of 85 posts
I have an online friend who contributes to firefox. They are fairly beginner-friendly, though you probably need to have some C++ skills. https://www.mozilla.org/en-US/contribute/
But if you are used to Github/PRs their Bugzilla/Hg-Patches workflow feels like going back in time... way back to the old days.
I have an online friend who contributes to firefox. They are fairly beginner-friendly, though you probably need to have some C++ skills. https://www.mozilla.org/en-US/contribute/
http://www.freesbd.org/ A fun open source operating system. Some C knowledge required.
Look into it.
ESR wrote "Every good work of software starts by scratching a developer's personal itch." You'll be much more effective working on a program that you use and want to make better, compared to a beginner-friendly project that you have no interest in.
Instead of looking externally for projects, look inwards. Think about the software you already use, and how it could be better: that stupid annoying behavior, or that obvious improvement, or your idea for a cool feature. And then set your sights on that!
An example: I was a big fan of the game Angband, which I played on Mac OS 9. When OS X came out, I wanted to play Angband again. So I "carbonized" it, so I (and others) could play it on OS X. I had never carbonized a program before, and that's how I learned.
I apologize for not really answering the question, but I have known aspiring programmers give up because they got bored. "Not being bored" is really important, more important than "not being frustrated."
If anyone has a better workflow for fixing ad hoc bugs you discover while integrating an open source library into your project, I would love to hear it.
You can filter by language and see open issues.
There is so much low hanging fruit building a new browser engine, that there is plenty of stuff to work on even if you aren't yet an expert on browser engines.
Also, you get to use a new programming language :)