- From: Joshua Timberman <
>
- To: "
" <
>
- Subject: [chef] Re: Re: Re: Re: "recommended" cookbooks list?
- Date: Tue, 9 Apr 2013 00:42:22 +0000
- Accept-language: en-US
Ohai,
On 4/5/13 8:35 AM, "Mike"
<
>
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
Archive powered by MHonArc 2.6.16.