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

[Cassiano Leal < >]

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 < " target="_blank"> > 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.