[chef] Re: Community cookbook maintenance (was: Re: Reprepro cookbook)

[Roland Moriz < >]

> Am 22.06.2015 um 22:52 schrieb Julian C. Dunn 
> <
 >:
> 
> On Mon, Jun 22, 2015 at 12:33 PM, Adam Jacob 
> <
 >
>  wrote:
> 
>> To speak for Chef Software directly, we have always had people on staff
>> whose role was assisting the creation and maintenance of cookbooks. That
>> number has fluctuated up and down over time, with the skill sets of people
>> we hire, and the normal day-to-day ebb and flow of trying to figure out how
>> to build a business that is successful. We have people on staff today who 
>> do
>> the same. What is clear is that the energy around cookbooks in the 
>> community
>> is far greater than the energy we can muster as an organization (regardless
>> of how much capital we do or do not have - y'all outnumber us) - and so our
>> focus today is on trying to build and support the best community we can,
>> through development of the supermarket, better tooling, and providing a few
>> key examples of how best to build a community cookbook (see Sean's work on
>> the httpd cookbook.)
>> 
>> Perhaps we need to organize a PR/merge festival brigade?
> 
> Hey Adam,
> 
> Would we consider transferring some of those cookbooks our of
> {opscode,chef}-cookbooks to a community-organized org like
> chef-brigade (https://github.com/chef-brigade) or redguide
> (https://github.com/redguide) for better maintenance? What would be
> the preconditions to doing that?
> 
> Personally I would like the chef-brigade and redguide to be merged,
> but I do not remember all the players involved -- if they are on this
> list perhaps they can speak up.


How would this prevent the problems that happend with the last migration of 
former opscode-cookbooks to community maintainers? 

Why should community maintainers care about the cookbooks in the future? 
It can be a time consuming burden and people need to pay their rent and do 
their regular jobs…

I know, this will be very provoking, but:

If Chef, inc. doesn't want to maintain even critical cookbooks anymore, is 
there still a valid reason for running a public Supermarket site? 
If you go the "libertarian way" there is no reason for a supermarket site to 
protect/block names of cookbooks anymore that prevents users to pick other, 
maybe better community resources over legacy-cookbooks that are mentioned in 
guides and examples. 

Either you (Chef, Inc.) control the market (e.g. maintain critical things 
yourself) or you should allow the free market (=community) to compete against 
each other based on equal opportunity (= namespaces or no supermarket). 
Everything else/in between will just end in chaos and anarchy.

regards
Roland

Attachment: smime.p7s
Description: S/MIME cryptographic signature