[chef] Re: Re: Re: Re: "recommended" cookbooks list?

[Sean OMeara < >]

+1 

On Fri, Apr 5, 2013 at 10:35 AM, Mike < " target="_blank"> > wrote:

> Ideally, once a community cookbook is mature enough, it should probably move
> to the root namespace and be "adopted" by opscode. Thoughts?

Opscode has more than once mentioned that the community should be able
to develop and maintain cookbooks, and that their "adoption" is in
limited capacity - it takes a lot of work.

As to namespacing, that's been discussed for quite a long time, and I
am hoping to bring up the discussion once again at the upcoming
ChefConf.

Consider how other open source communities deal with it - in many
others, there are clear "abandonment" guidelines, as well as "if
someone wants to own this and I'm no longer able to dedicate time to
it, take it" attitude.

I am hoping we can learn form them and apply such behaviors in the
Chef community, since we're all so awesome.

-M

On Fri, Apr 5, 2013 at 9:37 AM, Cassiano Leal < "> > wrote:
> I believe that namespacing would be a good beginning, something like
> "username-apache2", while keeping opscode-maintained cookbooks in the root
> namespace e.g. "apache2".
>
> Ideally, once a community cookbook is mature enough, it should probably move
> to the root namespace and be "adopted" by opscode. Thoughts?
>
> - cassiano
>
> On Friday, April 5, 2013 at 10:24, Ranjib Dey wrote:
>
> we need some sort of namespace or quality check for the community cookbooks.
> Some of them dont event converge (from very beginning ), they also block the
> name, hence if some only actually writes a working cookbook for the same ,
> it has to be uploaded with a different name.
>
> i hope to see test  kitchen run status shown against individual cookbooks,
> that would fix a lot of stuff.
>
>
>
>
>
> On Fri, Apr 5, 2013 at 3:50 AM, Brian Akins < "> > wrote:
>
> Is anyone keeping a list of "recommended" cookbooks? The community site is
> great when the "good" cookbook matches the name of the product/service you
> are deploying, however this is not always the case. A good example is redis
> - you have to know to search for a different name and/or look at github.
>
> We are starting a list of "tested" and "approved" community cookbooks and
> was wondering if anyone had done this.
>
>
>