On Thu, Oct 18, 2012 at 1:33 PM, Luke Kanies <[email protected]> wrote:
> I agree with all of this. We've done a great job of building a > self-sustaining user community, but we clearly have not delivered that on the > development side. > > There are outside contributors with commit access, but not many, and AFAIK > they aren't able to spend much time on the project. > > I would *love* to have more work on Puppet coming from outside of our > organization. I've always wanted that, and it's always pained me that we > never really figured it out. > > How do we do this? It's not as simple as just giving a bunch of people > commit access, is it? It could be that simple! Especially if it was combined with a move towards developing on master with Puppetlabs merging commits off master into release branches. I think you could easily give an experiment like this a try with the understanding that Puppetlabs can revert commits if they feel they are damaging and can't work with the author to resolve the problem. That and strict control over merging into release branches feels like a solid enough model that it could be tried without an enormous risk. Worst case you could just scrap the idea and revert all the commits that caused the experiment to fail. Thanks, -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
