Ruby hacker proposes to quit his job and work only on OSS while living on donation money
1–10 of 13 posts
Re: Ruby hacker proposes to quit his job and work only on OSS while living on donation money
#2I'd throw in some cash the second he decides to try this. Working full-time on something is much more productive than working evenings.
Re: Ruby hacker proposes to quit his job and work only on OSS while living on donation money
#3Something similar happened before with the Haiku OS project back in 2005 when Axel Dörflel worked on it full time for a few months using donated funds. (Link: http://haikunews.org/print/1125)
Re: Ruby hacker proposes to quit his job and work only on OSS while living on donation money
#4I'd throw in some cash the second he decides to try this. Working full-time on something is much more productive than working evenings.
is he working on something you need, or would you just support him for the sake of idealism?
if you do need the end product, then it seems reasonable enough. but if it's idealism you seek, how many hackers should set up donation bins before you stop donating to each new one?
Re: Ruby hacker proposes to quit his job and work only on OSS while living on donation money
#5The Perl Foundation (http://foundation.perl.org/) has done this quite a bit. There's a good model to follow.
Hacker News' own benhoyt has http://micropledge.com/ which seems well suited to the task.
Re: Ruby hacker proposes to quit his job and work only on OSS while living on donation money
#6I think this model would work better if he wanted to take time off to start up and develop a new OSS project.
I can see a lot of people donating to get 'Some really cool project' built.
But I doubt that faster bug fixes and improved documentation in open source reporting software is worth 60$ to too many people if you take away the feel good factor of donating to open source
Re: Ruby hacker proposes to quit his job and work only on OSS while living on donation money
#7I find it hard to convince a corporation to donate money for an OSS. It would need approval from people not familiar with OSS.
May be the model is to do it, thru consulting. For example, start working in Ruport, then advertise your self as a Ruport consultant, find some customers that are willing to pay for support or consulting, as you are able to charge for it, you can spend more time working in the project. I think several people have been able to do it. Companies are used to pay for support or consulting, they are not used to pay for something that is already free.
Some companies have been able to do it with great success. SpringOne, JBoss, JGoodies come to my mind.
Re: Ruby hacker proposes to quit his job and work only on OSS while living on donation money
#8Bram Cohen (who supports his family off of grateful BitTorrent users) is the exception. A lot of programmers are paid to work on open source (however, they are mostly employed by large Open Source advocates like IBM).
Re: Ruby hacker proposes to quit his job and work only on OSS while living on donation money
#9Bram Cohen (who supports his family off of grateful BitTorrent users) is the exception. A lot of programmers are paid to work on open source (however, they are mostly employed by large Open Source advocates like IBM).
I'm not so sure he supported his family on donations for very long. BitTorrent turned into a pretty well funded venture (of which he is chief scientist) a while ago.
Re: Ruby hacker proposes to quit his job and work only on OSS while living on donation money
#10I think this model would work better if he wanted to take time off to start up and develop a new OSS project. I can see a lot of people donating to get 'Some really cool project' built. But I doubt that faster bug fixes and improved documentation in open source reporting software is worth 60$ to too many people if you take away the feel good factor of donating to open source
On the other hand, i certainly know of businesses using open source projects that would happily pay someone external to fix a bug or add a feature to a given project. Why they wouldn't just assign one of their own developers is a mystery, but that's the way it is.