[chef] Re: Defunct Cookbooks on Opscode

[Nathen Harvey < >]

Each cookbook on the community site has a maintainer and may have one or more collaborators  The best course of action, if you'd like to see a change to a given cookbook, is to work with the maintainer and collaborators to see if there's a way to improve the cookbook.

The best way to have one cookbook replace another is to have the maintainers of both cookbooks agree to the change.  Some coordination is likely required and I would be happy to assist in the coordination and actual swap (as would most other Chef employees).

This is a community-driven site and the policies should be largely defined and driven by the community as a whole.   I suspect we'll need to see a number of these transitions happen successfully before we can agree to an "official" policy.  In fact, I'm not sure that we'll need to reach consensus on what should happen; it's likely something best handled on a case-by-case basis.

Daniel - it might be helpful to include links to the cookbooks in question.  Have you reached out to the various maintainers?

Thanks,

Nathen

On Fri, Dec 20, 2013 at 10:33 PM, Daniel Jabbour < " target="_blank"> > wrote:

Hi all-

I’m wondering what the official policy / process is to replace defunct or obsolete cookbooks from the Opscode repository? I see for instance the ‘rvm’ cookbook is totally broken and outdated, and there’s a very nice one on Github. Curious how one can go about replacing it…

Regards,

Daniel

Daniel Jabbour - Founder

(415) 366-9900 x742
" target="_blank">

Amoeba Consulting
http://amoe.ba