I'm interested in real experience and personal answers not just those standard worn out "benefits of contributing to open source" that we all memorized by heart by now.

I've met many people who contribute to open source project and almost never did this topic come up: why did they contribute to this open source project. So, if you've contributed to an open source project before in any way, can you please pause for a second and try to remember what really made you decide to contribute to that particular project.

Was it a random decision, was it because you were bored, was it because the company you worked for was already using it and you contributed as part of your job, was it because the project was too big you wanted to get contracts, or the project was too small you wanted to build it, or because your prof or co-worker asked you to help with his open source project, or.....

closed as not constructive by Mark Trapp Nov 27 '11 at 1:06

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
If this question can be reworded to fit the rules in the help center, please edit the question.

I thought I was pretty clear in my answer, I do it because I like to achieve things and be useful, and a little bit for the social & status aspect of the thing. Do you need more details ?
–
user2567Oct 12 '10 at 13:27

Oh I misunderstood you then. All these reasons are yours. I thought you were talking in general because you started each bullet point with "some people".
–
ErminOct 12 '10 at 13:31

No, I wanted to describe all top reasons before, as it's a subject I like very much (psychology)
–
user2567Oct 12 '10 at 13:37

I contributed to an open source project that would have faded away had I not contributed. I'm happy to say that because I did contribute it's still around and has flourished a little more than anyone expected.

When I switched from Windows to a Mac, my favourite IM client wasn't available. There was a small project started to create one.

It got into early alpha stages, was very buggy and crashy and eventually the author abandoned it. There were quite a few people using it at the time, and each time the IM service updated it's protocol, the client would get worse.

I started writing some fixes for it and before I knew it I had become it's developer. As it turned out, a couple of forks turned up, and the original project died back a little, yet I helped contribute to some of the forks too. The joys of open source!

Right now, an iPhone app I am actively working on is based on one of the forks that popped up for the IM protocol library. It's amazing how open source products can evolve and come full circle sometimes :)

We frequently do small contributions to various open source projects. This is primarily done because a particular piece of code done to achieve some functionality "logically" belongs to the projects and not our own code, and by contributing them back upstream they get part of the official distribution instead of us having to keep close track of new updates ensuring the code still works.

This is a good thing, as it lowers the risk of things breaking when deciding to upgrade to the newest version of libraries.