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
We are starting a list of “tested” and “approved” community cookbooks and
was wondering if anyone had done this.
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 brian@akins.org 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.
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?
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 <brian@akins.org (mailto:brian@akins.org)> 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.
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 cassianoleal@gmail.com 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 brian@akins.org 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.
+1
On Fri, Apr 5, 2013 at 10:35 AM, Mike miketheman@gmail.com 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 cassianoleal@gmail.com
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 brian@akins.org 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.
Ohai,
On 4/5/13 8:35 AM, "Mike" miketheman@gmail.com 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.
This is correct. We don't want to be an impediment to people publishing
cookbooks on the community site. We also aren't adding new cookbooks to
support and maintain except under special circumstances. For information
about this see:
http://wiki.opscode.com/display/chef/Cookbook+Support
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.
The namespacing issue on the community site essentially requires a rewrite
of the application, which is planned. I can't speak to the time frame
of that yet other than that it will be after 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.
Totally. We had a discussion about this at the summit. Again, this is
something that we will revisit after ChefConf. Notes from the summit are
posted here.
http://wiki.opscode.com/display/chef/Cookbook+Curation+and+Contribution
Cheers,
Joshua
On Apr 8, 2013, at 6:42 PM, Joshua Timberman joshua@opscode.com wrote:
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.Totally. We had a discussion about this at the summit. Again, this is
something that we will revisit after ChefConf. Notes from the summit are
posted here.
The thought occurs to me that one additional thing we need here is a community manager for this kind of stuff. I wonder if Opscode has anyone on staff with previous experience in this kind of role? 
--
Brad Knowles brad@shub-internet.org
LinkedIn Profile: http://tinyurl.com/y8kpxu
On Apr 8, 2013, at 21:14, "Brad Knowles" brad@shub-internet.org wrote:
The thought occurs to me that one additional thing we need here is a community manager for this kind of stuff. I wonder if Opscode has anyone on staff with previous experience in this kind of role?
Indeed, we do :).
And we are currently focused on making ChefConf as awesome as possible. 
Cheers,
Joshua
On Apr 8, 2013, at 11:15 PM, Joshua Timberman joshua@opscode.com wrote:
And we are currently focused on making ChefConf as awesome as possible.
Please do. I won't be able to be there, due to schedule conflicts with me working at a customer site. But I will be keeping an eye on the stuff that comes out, and I'll definitely be checking out any slides, videos, or anything else that gets posted from ChefConf.
That's right after my birthday, so I would consider it to be a great birthday present to have lots of good stuff to come out of ChefConf.
Thanks again!
--
Brad Knowles brad@shub-internet.org
LinkedIn Profile: http://tinyurl.com/y8kpxu