Open Source Projects For Beginners
itwbennett writes "Whoever said 'everyone has to start somewhere' has clearly never tried contributing to an open source project — the Linux Kernel development team in particular is known for its savagery. But if you're determined to donate your time and talents, there are some things you can do to get off on the right foot. Of course you should pick something you're interested in and that you use. Check, and double check. You should also research the project, learn about the process for contributing, and do your utmost to avoid asking questions that you can find the answers to. But beyond that there are some hallmarks of beginner-friendly open source projects like Drupal, Python, and LibreOffice — namely, a friendly and active community, training and mentorship programs, and a low barrier to entry."
Beginners and non programmers can even help. 99.99786% of all OSS projects desperately need help with documentation. IF you want to start somewhere, start there.
Do not look at laser with remaining good eye.
the Linux Kernel development team in particular is known for its savagery
I've found that the "It's my party and no one else is invited" syndrome permeates all too many OSS projects. Finally stopped offering to help after encountering one too many projects that act like the snobby fraternity from a bad 80's movie. Now I do my own stuff and forgo the projects that have already started.
The cow says "Moo." The dog says "Woof." The Timothy says "Thanks, valued customer. We appreciate your input."
How about contribute to something you can add value to? like, not treating it like contributing just something to just any project has absolute value that you can then put on your CV.
So look at software you use - fix some bugs that annoy you and contribute fixes or create new features that you would find useful in the software. that's how almost all successful small open source projects operate. which is pretty much how the example guy on the article went about it. contributing to software you don't use is going to be a mess.
if you have a truly novel fix or improvement to the linux kernel, you could always present it at as well. that's contributing even if you don't get your commit in, if it's a good solution to some known problem then people will take notice. because if you feel like that your changes wouldn't be appreciated, you could always just release a fork.
just answering questions on stackoverflow etc can greatly help some projects too.
world was created 5 seconds before this post as it is.
My fist ever contribution to an open source project was a silly little patch for the Kernel. While there was some initial indifference on the mailing list, I received actionable feedback. I iterated a couple of times, times, fixed issues that were called out and got my pulled in. All without any 'savage' name calling, flaming or . True, there are more than a few grumpy Kernel hackers, just are also loads of folks willing to help out newbies. You know, like in ANY opensource project. Hell, there's a website and a mailing list just for newbies! I really don't understand why Linux gets so much hate. Especially considering that it is the LARGEST, most successful open source project ever?
1) Get a github account.
2a) Submit a bug.
2b) Request a new feature.
2c) Fix a bug.
2d) Research and comment on an open issue.
2e) Add a new feature.
2f) Fix typos in documentation.
2g) Add documentation.
2h) Add a translation for your own language.
2i) Add a new theme/template.
2j) Make the project page nicer to look at.
2k) Thank the authors.
2l) ???
3) Profit!
Getting involved starts simply with making "first contact".
Any half-decent project team will gracefully accept anything you have to offer and pretty soon you'll find you have quite a lot to offer.
Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
Try Oolite. A free, cross-platform space game based on the classic Elite. Dead easy to get into and a great community behind it.
Smivs on the intertubes!
Everyone will post their 2 cents worth, recreating the article in a hodge-podge way.
Don't complain about syntax, grammar, or spelling. There is no.hell like input on android.
I heard that FreeRCT is in need for both programmers and graphic artists. Their goal is to create an open game in the spirit of Rollercoaster Tycoon 1 & 2.
OpenHatch is a non-profit dedicated to matching prospective free software contributors with communities, tools, and education.
http://openhatch.org/
Very useful for beginners.
http://openhatch.org/search/?q=&toughness=bitesize
http://openhatch.org/search/?q=&contribution_type=documentation&toughness=bitesize
Uh, this one is really simple.
Don't start at the kernel, idiot.
Don't start at a compiler or programming language or other system part, fool.
Start with an application. In fact, if you need to get that explained, you should start with a good book.
The kernel and compiler, etc. people ought to be hostile to newbies. Their goal is not to teach newbies, it's to deliver reliable code. You don't start learning to fly with a Boing 747 full of passengers, you start with a simulator or a Cessna.
Your first contributions shouldn't be in anything that other (applications) rely on. It should be in an application. Something where if it fails only that thing fails and not everything that depends on it. You'll find that the maintainers of these applications are more forgiving, simply because the burden on them is a lot less.
And yes, I say that as someone who has contributed to bunches of projects.
Assorted stuff I do sometimes: Lemuria.org
The BRL-CAD project defines two levels of tasks geared towards new contributors. "Deuces" are small tasks expected to take less than 2 hours. "Quickies" take around 2 days:
http://brlcad.org/wiki/Deuces
http://brlcad.org/wiki/Quickies
The project even provides a virtual machine disk image that has everything set up and ready to go.
Cheers!
Sean