> > Eric F Crist wrote: > >> Restricting bounty development to the small handful of developers >> who've already done work on OpenVPN is a bad idea. It doesn't >> entice new, talented, developers to participate. >> > > This is a really tough issue. > > Having a new developer join the team to create some significant > amount of work as the very first interaction will create a lot of > problems when that person isn't already familiar with the exact modus > operandi of the project. Worst case it will simply lead to code that > bitrots. Imagine you not being able to review and give immediate > feedback on a wave of patches that are coming in, the author hears > nothing and continues working, and in the end there's a huge pile of > commits that just don't make sense, even though the final product > works kinda ok.. Nightmare. > Requiring bounty developers to use our "standard" development process and handing out the bounty in phases helps a lot in solving these issues. I agree with Eric that we should not intentionally exclude people from claiming the bounties. However, I think for the bounty system to be successful the people claiming the bounties have to be able to
- get the job done (technically) - work with other developers to make sure they don't dig a hole for themselves an drop a crappy patch to the mailinglist in the end I don't think the developer has to be an OpenVPN developer to qualify. If he/she has worked on other projects (and can prove it), there's no reason to exclude him/her from claiming a bounty task. -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock
