On Thu, Oct 28, 2010 at 11:02 AM, Nigel Kersten <[email protected]> wrote: > On Thu, Oct 28, 2010 at 7:52 AM, Markus Roberts <[email protected]> wrote: >> So do we have any characterization of who didn't want to see code on >> puppet-dev? Are there any individuals that would like to come forward and >> speak for that side, or does anyone know who (in a general, demographic >> sense) was pushing for this change? > > I think we have a selection bias in responses here. I've had a number > of conversations with people who have talked about how they like to be > involved in design decisions and keep up with the RFC style emails, > but end up ignoring this list because of all the patches flying past, > or feel intimidated into not getting involved due to all the code > discussion.
Right, and I think everyone who's chimed in is more concerned about a single public list both puppet labs employees and community members submit patches to and code reviews to. I think the good middle ground is to create puppet-patches or use puppet-bugs or something for the code review discussions, leave puppet-dev for more general discussions about developing puppet, and puppet-users for more general discussions about using puppet. We just absolutely should not have two patch review lists, one for community patches and one for puppet labs employee patches. -Jeff -- 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.
