# Defunct Cookbooks on Opscode

**URL:** <https://discourse.chef.io/t/defunct-cookbooks-on-opscode/4826>\
**Category:** Chef Infra (archive)\
**Created:** [December 21, 2013, 3:33am UTC](https://discourse.chef.io/t/defunct-cookbooks-on-opscode/4826 "2013-12-21T03:33:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Daniel\_Jabbour](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/daniel_jabbour/32/413_2.png) [@Daniel\_Jabbour](https://discourse.chef.io/u/Daniel_Jabbour)\
**Post date:** [December 21, 2013, 3:33am UTC](https://discourse.chef.io/t/defunct-cookbooks-on-opscode/4826/1 "2013-12-21T03:33:13Z")

</div>

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  
[daniel@amoe.ba](mailto:daniel@amoe.ba)

Amoeba Consulting  
[http://amoe.ba](http://amoe.ba)

---

<div class="post-metadata">

**Author:** ![Mike](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/mike/32/18_2.png) [@Mike](https://discourse.chef.io/u/Mike)\
**Post date:** [December 21, 2013, 3:37am UTC](https://discourse.chef.io/t/defunct-cookbooks-on-opscode/4826/2 "2013-12-21T03:37:32Z")

</div>

This is a long-standing question, and has yet to be fully detailed as to  
how this would happen.

I'll defer answering to Chef Community leaders, such as Nathen Hervey?  
-Mike

On Fri, Dec 20, 2013 at 10:33 PM, Daniel Jabbour [daniel@amoe.ba](mailto:daniel@amoe.ba) 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
> 
> [image: Amoeba Consulting] [http://amoe.ba/](http://amoe.ba/)  
> _Daniel Jabbour_ - Founder  
> (415) 366-9900 x742  
> daniel@amoe.ba
> 
> _Amoeba Consulting_  
> [http://amoe.ba](http://amoe.ba)
> 
> [image: Facebook] [http://facebook.com/AmoebaConsulting](http://facebook.com/AmoebaConsulting) [image:  
> Twitter] [http://twitter.com/AmoebaSoft](http://twitter.com/AmoebaSoft) [image: LinkedIn][http://linkedin.com/company/amoeba-consulting-llc](http://linkedin.com/company/amoeba-consulting-llc) [image:  
> GitHub] [https://github.com/AmoebaConsulting](https://github.com/AmoebaConsulting) [image: Google Plus][http://plus.google.com/107440881665995164447/](http://plus.google.com/107440881665995164447/)

---

<div class="post-metadata">

**Author:** ![scottmlikens](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/scottmlikens/32/126_2.png) [@scottmlikens](https://discourse.chef.io/u/scottmlikens)\
**Post date:** [December 22, 2013, 9:02pm UTC](https://discourse.chef.io/t/defunct-cookbooks-on-opscode/4826/3 "2013-12-22T21:02:26Z")

</div>

Generally if a cookbook needs to be replaced; the author of the cookbook  
can release his cookbook from [community.opscode.com](http://community.opscode.com) and have someone  
else upload their cookbook to replace it. Completely voluntary it has  
transpired previously and likely could again. 🙂

Also Supermarket I believe will help this problem to a degree. (See  
Forward)

-------- Original Message --------  
Subject: [chef] Announcing Supermarket  
Date: Fri, 15 Nov 2013 17:51:48 -0800  
From: Seth Vargo [sethvargo@opscode.com](mailto:sethvargo@opscode.com)  
Reply-To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)

Ohai Chefs,

This year at the Chef Summit, we announced and open sourced Supermarket  
[https://github.com/opscode/supermarket](https://github.com/opscode/supermarket) and we are inviting you to  
hack! Supermarket is Opscode's new ICLA site and the framework for the  
new community and cookbook sharing application.

We built and demoed the ICLA functionality at Summit and are working  
closely to integrate supermarket into our systems to automate the  
existing contribution process. We are going to build the CCLA components  
next and then move on to developing the cookbook API. We are encouraging  
everyone in the community to start discussions and ideas about what the  
top features in the new community site should (or should not) be. Here  
are some ideas to get you started:

- Suggest a feature and get buy-in from community members
- Develop an algorithm or system for objective cookbook quality measures
- Propose a process for subjective cookbook measurements
- Request API endpoints you think should exist and why

Unfortunately you cannot yet use this site to sign the CLA that we  
require for you to contribute to this site, but your existing Opscode  
CLA does suffice (can you feel the irony?). BUT, we are not using JIRA,  
so everything (Pull Requests, Issues, Suggestions, and Code) is done  
through GitHub! And that’s just a sneak peek of some of the awesomeness  
you can expect soon :).  
It looks like Supermarket will replace the Community site

On 12/20/13 7:37 PM, Mike wrote:

> This is a long-standing question, and has yet to be fully detailed as  
> to how this would happen.
> 
> I'll defer answering to Chef Community leaders, such as Nathen Hervey?  
> -Mike
> 
> On Fri, Dec 20, 2013 at 10:33 PM, Daniel Jabbour \<daniel@amoe.ba  
> [mailto:daniel@amoe.ba](mailto:daniel@amoe.ba)\> 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
> 
> Amoeba Consulting <http://amoe.ba/>
> *Daniel Jabbour* - Founder
> (415) 366-9900 x742 <tel:%28415%29%20366-9900%20x742>
> daniel@amoe.ba <mailto:daniel@amoe.ba>
> 
> *Amoeba Consulting*
> http://amoe.ba <http://amoe.ba/>
> 
> Facebook <http://facebook.com/AmoebaConsulting> Twitter
> <http://twitter.com/AmoebaSoft> LinkedIn
> <http://linkedin.com/company/amoeba-consulting-llc> GitHub
> <https://github.com/AmoebaConsulting> Google Plus
> <http://plus.google.com/107440881665995164447/>
> 
> ```
> 
> !DSPAM:52b50d1a211701804284693!

---

<div class="post-metadata">

**Author:** ![Nathen\_Harvey2](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/nathen_harvey2/32/179_2.png) [@Nathen\_Harvey2](https://discourse.chef.io/u/Nathen_Harvey2)\
**Post date:** [December 22, 2013, 10:56pm UTC](https://discourse.chef.io/t/defunct-cookbooks-on-opscode/4826/4 "2013-12-22T22:56:14Z")

</div>

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 [daniel@amoe.ba](mailto:daniel@amoe.ba) 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
> 
> [image: Amoeba Consulting] [http://amoe.ba/](http://amoe.ba/)  
> _Daniel Jabbour_ - Founder  
> (415) 366-9900 x742  
> daniel@amoe.ba
> 
> _Amoeba Consulting_  
> [http://amoe.ba](http://amoe.ba)
> 
> [image: Facebook] [http://facebook.com/AmoebaConsulting](http://facebook.com/AmoebaConsulting) [image:  
> Twitter] [http://twitter.com/AmoebaSoft](http://twitter.com/AmoebaSoft) [image: LinkedIn][http://linkedin.com/company/amoeba-consulting-llc](http://linkedin.com/company/amoeba-consulting-llc) [image:  
> GitHub] [https://github.com/AmoebaConsulting](https://github.com/AmoebaConsulting) [image: Google Plus][http://plus.google.com/107440881665995164447/](http://plus.google.com/107440881665995164447/)

---

<div class="post-metadata">

**Author:** ![Seth\_Vargo2](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@Seth\_Vargo2](https://discourse.chef.io/u/Seth_Vargo2)\
**Post date:** [December 28, 2013, 2:51am UTC](https://discourse.chef.io/t/defunct-cookbooks-on-opscode/4826/5 "2013-12-28T02:51:48Z")

</div>

It’s also worth noting, specifically for the RVM cookbook, Fletcher and Aaron are now maintainers and the next release of RVM will use [https://github.com/fnichol/chef-rvm](https://github.com/fnichol/chef-rvm). The maintainer we very kind in giving up the namespace.

Happy cooking, Seth

Seth Vargo  
Release Engineer, Opscode  
@sethvargo  
From: Nathen Harvey Nathen Harvey  
Reply: [nharvey@getchef.com](mailto:nharvey@getchef.com) [nharvey@getchef.com](mailto:nharvey@getchef.com)  
Date: December 22, 2013 at 5:56:29 PM  
To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com) [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
Subject: [chef] Re: Defunct Cookbooks on Opscode  
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 [daniel@amoe.ba](mailto:daniel@amoe.ba) 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  
[daniel@amoe.ba](mailto:daniel@amoe.ba)

Amoeba Consulting  
[http://amoe.ba](http://amoe.ba)