[chef] RE: Re: Re: Re: Re: Re: [RFC] github.com/cookbooks

[Matt Ray < >]

I think if we (Opscode) and all other producers of Community cookbooks were to tag every uploaded version this would be a moot point but it hasn't happened. I'm sure we're open to suggestions for how to enforce this, especially in the case where Community cookbooks might not be originating from GitHub or even git repos (gasp). Can we somehow make the Community site support this without creating yet another place to find cookbooks?

Thanks,

Matt Ray

Senior Technical Evangelist | Opscode Inc.

| (512) 731-2218

Twitter, IRC, GitHub: mattray

---

From: Jesse Campbell
Sent: Wednesday, November 14, 2012 9:26 PM
To:
Subject: [chef] Re: Re: Re: Re: Re: [RFC] github.com/cookbooks

Biggest problem I run into with the opscode community cookbook site is that it isn't a git repo, so i have to download files, so if i make changes, i can't easily merge in upstream changes.
The opscode cookbooks are also in https://github.com/opscode-cookbooks, but those are dev versions, not the released versions, so i can't use them without possibly running into untested/broken code.

Basically what i want is for the opscode community cookbook site to allow running a git clone of everything it holds, instead of being a repository of zip files.

-jesse

On Wed, Nov 14, 2012 at 6:22 PM, AJ Christensen < " target="_blank"> > wrote:

Are there overwhelming issues with the Opscode Community cookbook site