On Wed, Oct 17, 2012 at 10:14 PM, Miguel Di Ciurcio Filho <[email protected]> wrote:
> b) Make Puppet a real community project, where the "Puppet Community > Project" (maybe a different name) is the upstream of Puppet Enterprise > or other PuppetLabs projects. Like Citrix did to Xen and CloudStack, > Red Hat does with many other projects KVM, Linux, oVirt, OpenStack is > the upstream for many companies, Samba, Apache HTTP server is part of > many proprietary solutions. The list could go on and on. I think this is probably the only way to stop things from collapsing under the weight of the community expectations at this point. I think opening up commit access to outside developers would be an enormously dangerous, but potentially extremely rewarding, way to go. I know that I've gotten discouraged from my attempts to fix things in facter from the difficulty of getting them merged in and reviewed for large scale changes. Obviously I think if this is the route things go then the addition of developers would have to be carefully controlled at the beginning in order to not have chaos and a blob of code that Puppetlabs themselves can no longer use productively, but it's clear that Puppetlabs simply cannot hire enough developers internally to improve things at the rate that the community wishes for. 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.
