[[chef-dev]] Re: [chef] Re: Re: Contributing to Cookbooks (was chef & hoptoad)

[Alex Soto < >]

On Jul 15, 2010, at 7:05 PM, Joshua Timberman wrote:

> On Jul 15, 2010, at 4:31 PM, Alex Soto wrote:
> 
>> First I mainly spend my time with chef developing cookbooks, so how would 
>> I 'contribute' a cookbook while not incurring a lot of overhead ?  For 
>> example, I create a cookbook that I haven't seen in the wild, I'd like to 
>> publish it for others to use and enhance, but since it's in my private 
>> repo, how would I do that?
> 
> If you would like to simply publish a new cookbook that doesn't "exist" in 
> the wild yet, the best place to put that is the Opscode cookbooks site.
> 
> Then other people can discover and use your cookbook by downloading it with 
> the 'vendor branch' workflow.

Great news.  I was under the impression that the cookbooks site was just a 
distribution method for the cookbooks in the opscode cookbooks repo. I wasn't 
aware I could just push things up there.  What happens to a cookbook I push 
up there?  Does it get reviewed, or does it go right up on the site?  
> 
>> One idea would be that I have another cookbooks repo where I publish the 
>> cookbook and be able to import it using the existing vendor stuff knife 
>> provides but use it against other repo's than just the cookbooks site.
> 
> Currently knife only supports the Opscode cookbooks site, since it provides 
> an API that we can use directly. I do not knife if the dev team has plans 
> to implement support for other sites or methods by which to 'vendor' 
> cookbooks. The advantage of the Opscode site vs say GitHub is that it 
> integrates well with the Platform, and its a better known quantity for the 
> API usage. But I'll let Adam or Dan speak up about potential roadmap topics 
> in that regard.
I looked at the code, and I see what you mean, but it seems like it's just 
pulling down a tarball.  By pointing to another repo and using git archive, 
you can mimic that behavior.  Unfortunately, it doesn't seem that github 
allows using that command to pull a single cookbook as a tarball so it may 
not be useful for github, but private github repo's work that way.