Please keep open source software FREE! I would join if instead of money, developpers will get the shiny red stars or any kinds of "vanity points". ;)
rakesh wrote: > Here is my "personal" opinion. > > Idea is great, but not in best interest of what we call open source > community. One reason for using open source software is that it is > like community work and every one (like me) loves helping others when > ever possible. The motivation to help others is not money but in most > cases is to return the favor. If I have used 1000's of hours of code > produced by 100's of developers then it is my duty to give back my few > hours where ever possible. Your idea is more like expert-exchange > which I hate by the way. > > Apologies if I have hurt your feeling. Again, it is my personal > opinion and your efforts might certainly make sense to some one else. > btw, I did see the the website, good work! > > > > On Nov 1, 10:44�pm, Sjors <[EMAIL PROTECTED]> wrote: > > Hi there, > > > > For those of you who find starring issues not satisfying enough, I've > > created a website that allows you to set a reward for whoever fixes > > your favorite bug:http://jobtorrent.org/ > > > > The problem that I'm trying to solve here is that some bugs are really > > 'popular' amongst users, but - for various reasons - not very > > 'popular' amongst developers. This often results in thousands of > > people starring an issue and - worse - repeating the issue over and > > over again on the mailing list. > > > > This is all very democratic, but wouldn't it be much easier if you > > could just say "I'll pay $10 to the first person who fixes this" and > > get on with life? > > > > Jobtorrent is pretty simple. Go to your favorite bug and copy the URL. > > Then go tohttp://jobtorrent.org/and sign up as an 'employer'. Create > > a new 'job', set a price and paste the URL. > > > > A developer can then accept the job, submit a patch through the usual > > channels, and marks the job as done. If the employer is satisfied with > > the result, the developer gets paid. It's completely up to the > > employer to define 'satisfied': perhaps any patch will do, perhaps he/ > > she will not pay until the patch has actually been incorporated in > > Gears. > > > > In case you're wondering if I'm spamming every single list on Google > > Code, the answer is no. I am a Gears user myself and I've been waiting > > for full 64 bit support for ages. It's working more or less at this > > point, but I would gladly have paid someone to fix it sooner (if I had > > more money to spare). > > > > The converse is also true: I would love to help development of Gears, > > but at the moment I can only do it if somebody pays me for it. > > > > I'm looking forward to hearing your thoughts about this, both from a > > practical point of view and an open-source-ethics point of view. > > > > Kind regards, > > > > Sjors
