Defunct Cookbooks on Opscode


#1

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

Amoeba Consulting
http://amoe.ba


#2

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 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/
Daniel Jabbour - Founder
(415) 366-9900 x742
daniel@amoe.ba

Amoeba Consulting
http://amoe.ba

[image: Facebook] http://facebook.com/AmoebaConsulting [image:
Twitter] http://twitter.com/AmoebaSoft [image: LinkedIn]http://linkedin.com/company/amoeba-consulting-llc [image:
GitHub] https://github.com/AmoebaConsulting [image: Google Plus]http://plus.google.com/107440881665995164447/


#3

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

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
Reply-To: chef@lists.opscode.com
To: chef@lists.opscode.com

Ohai Chefs,

This year at the Chef Summit, we announced and open sourced 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> 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!


#4

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 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/
Daniel Jabbour - Founder
(415) 366-9900 x742
daniel@amoe.ba

Amoeba Consulting
http://amoe.ba

[image: Facebook] http://facebook.com/AmoebaConsulting [image:
Twitter] http://twitter.com/AmoebaSoft [image: LinkedIn]http://linkedin.com/company/amoeba-consulting-llc [image:
GitHub] https://github.com/AmoebaConsulting [image: Google Plus]http://plus.google.com/107440881665995164447/


#5

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. 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 nharvey@getchef.com
Date: December 22, 2013 at 5:56:29 PM
To: chef@lists.opscode.com 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 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

Amoeba Consulting
http://amoe.ba