Cheering vs. Getting Involved in an Open Source Project
Wednesday, 21. May 2008, 07:16:00
This is at best paradoxical. How comes that people who are such believers and supporters of open source are only users and cheerleaders instead of getting involved?
Maybe it's because we are Romanian, and we are used with such paradoxical behaviors. Or because the difference between cheering and doing is very very large. Or because programming actually is hard. Or because we like the idea in principle, but we don't have the courage to start living it. And I can think of a couple of other reasons.
Regarding myself, I tried to choose an open source project to participate in. First I tried Mozilla then Open Office and I found out that they are really complex projects and that the time to enter such a project is quite high (incidentally, Open Office recently became much more contributor-friendly, with its new website). Then I looked at smaller projects that I was using: ArgoUML and PostSharp. Still no luck - they didn't manage to capture my attention, although both are great pieces of work. I even tried to open my own open source project, something I think would have been a cool application - a "send to"-like tool allowing not only to send data to an application, but also a "send as" option allowing to transform the data into something else before sending it (e.g. "send to thunderbird as attachment", "send to thunderbird as zipped attachment" etc.). I didn't even find the time to add the document describing the mechanism and the prototype code to its sourceforge account.
There are many reasons why this happens. First, I wasn't very familiar with Linux until recently, and Linux is the best open source development tool because all the libraries you need for development and their documentation are a command line away (be it tar, apt-get, slapt-get or any other command). I very much miss the installation super-powers when I work on Windows.
Second, my time is fragmented, no matter how much I try to organize it. I have development tasks to finish, then I work on some training materials, then I think about my website, then I think about my blog, then I work with my wife on projects coming through her company and so on. And I find that many times the learning curve for an open source project is too steep, and I don't have the time to invest in it.
Third, I got used with giving my time on demand, instead of donating my time. If somebody asks me to help at a project, I would jump in the bandwagon as soon as I think it's interesting. But that's not the open source way. Rather, it's me who should find a project that interests me and to invest in it.
Maybe that's just me, but I think times have changed since The cathedral and the bazaar. The number of open source projects has exploded, and the large majority of them fail. There's nothing wrong with it; it's only the selection of the fittest, but who likes to jump in a probable failure? And, even more difficult, who has the time to look at all new open source projects and choose one that's interesting?
I'm not saying it can't be done. I'm just saying that I don't know how to do it, and that I'd very much love to participate to an open source project that fits my knowledge, my skills, and who can capture my attention. So, if you work on an open source project, please let me know how you solve those problems.
Personal advertisement: I am PassionIT and I help teams develop high quality software. I train, I help improving and I work hands-on, depending on the needs. Contact me if you need help. Alexandru Bolboaca-Diaconu
