Hey, I think it totally depends. Bounties are a way to support issues being fixed (in the simplest way), if it happens to be an ownCloud developer either it's a bonus, a ownCloud Inc revenue stream or (as most projects do these give it back to the community team - claiming on behalf of a team is on the roadmap it seems).
Additionally I think it's not just new contributors, but providing an additional income (more coffee/less consultancy etc.) to contributors and perhaps let ownCloud Inc decide on the importance on issues more easily as the bounty could be a measure on importance too. These metrics could be useful and with the idea to let ownCloud Inc employees claim on behalf of the oC community team it goes back into the community. We'll see how ownCloud Inc/Community/Contributors see the best fit. Still new contributors have one more reason to dig into the overhead (read code, read+sign contributor agreement, read contribution workflow etc.) of becoming a contributor. Cheers Michael On Mon, Aug 11, 2014 at 10:16 PM, Bernhard Posselt <[email protected]> wrote: > Bounties are used to get features implemented which main developers wont > implement iirc. I doubt that it will attract more devs. Put yourself in the > role of someone who pays for a bounty: he doesnt want a new contributor, he > wants the issue fixed. > > > On 08/11/2014 08:47 PM, Mark Ziegler wrote: >> >> Hello, >> >> for my understanding bountysource will/should motivate non-main developers >> to solve issues. >> As an employer I want my coders working on issues important for me, >> big bounties make issues (reported by users) more interesting. >> >> I am trying to understand how ownCloud development will work together with >> bountysource. >> >> Cheers, >> Mark >> >> >> Am 11.08.14 20:37, schrieb Bernhard Posselt: >>> >>> Why should it matter who fixes it? >>> >>> On Aug 11, 2014 8:03 PM, Mark Ziegler <[email protected]> wrote: >>>> >>>> Hello, >>>> >>>> one more thought. >>>> Some devs are employed by ownCloud and solving issues. >>>> Which issues should be target on bountysource? Or better which persons? >>>> Will employees give their bounties to the project if they solve them >>>> during work time? >>>> Does that make a difference at all? >>>> >>>> Just some thoughts. >>>> >>>> Cheers, >>>> Mark >>>> >>>> Am 11.08.14 19:41, schrieb Michael Grosser: >>>>> >>>>> Hey, >>>>> >>>>> Small addition: >>>>> Best to say it's mostly handled as a case by case basis as far as I >>>>> know and does try to find the right balance between preventing forks >>>>> (dicussing merging of finished work) and paying for finished work. >>>>> >>>>> Additionally to the 6/12 months option to get refunded if not yet >>>>> started/finished it's possible to let the refund go to the project >>>>> instead of your account. >>>>> >>>>> Cheers >>>>> Michael >>>>> >>>>> On Mon, Aug 11, 2014 at 7:17 PM, Michael Grosser >>>>> <[email protected]> wrote: >>>>>> >>>>>> Hey, >>>>>> >>>>>> If they are closed as won't fix or not merged you get refunded. >>>>>> There is also the option to make bounty contributions time sensitive >>>>>> and let them be automaticly refunded after 6/12 months I think. >>>>>> >>>>>> Cheers >>>>>> mciahel >>>>>> >>>>>> On Mon, Aug 11, 2014 at 5:15 PM, Mark Ziegler >>>>>> <[email protected]> wrote: >>>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> just checked FAQ on Bountysource and still have an open question: >>>>>>> What happens my bounties if issue is never implemented or fixed? >>>>>>> Do I get my money back after some period? >>>>>>> >>>>>>> Cheers, >>>>>>> Mark >>>>>>> _______________________________________________ >>>>>>> Devel mailing list >>>>>>> [email protected] >>>>>>> http://mailman.owncloud.org/mailman/listinfo/devel >>>>> >>>>> _______________________________________________ >>>>> Devel mailing list >>>>> [email protected] >>>>> http://mailman.owncloud.org/mailman/listinfo/devel >>>> >>>> _______________________________________________ >>>> Devel mailing list >>>> [email protected] >>>> http://mailman.owncloud.org/mailman/listinfo/devel >> >> >> _______________________________________________ >> Devel mailing list >> [email protected] >> http://mailman.owncloud.org/mailman/listinfo/devel > > > _______________________________________________ > Devel mailing list > [email protected] > http://mailman.owncloud.org/mailman/listinfo/devel _______________________________________________ Devel mailing list [email protected] http://mailman.owncloud.org/mailman/listinfo/devel
