[chef] Re: RE: Re: Splitting Chef::Client and Chef::Server into their own cookbooks

[Adam Jacob < >]

On Wed, Oct 13, 2010 at 10:05 AM, Paul Choi 
<
 >
 wrote:
> Wow, I did not know about this command. Much more convenient than manually 
> downloading the tarballs from the cookbooks website. Good to know!
>
> "knife cookbook site vendor", by the way.
>
> Also, when you mean edit the cookbooks to your liking, do you mean making a 
> copy in site-cookbooks and modifying it there?

Nope - if you use the knife cookbook site vendor command, you can make
your edits directly to the cookbook from the upstream, and it will
keep track of the differences.  When a new cookbook version is
released upstream, you can just run it again, and let source control
work it's magic.

> Sorry if this seems a little basic... I started using 0.8.16 on CentOS, and 
> since the community cookbooks are more Ubuntu-friendly, I rolled out my own 
> cookbooks for internal use. I wouldn't mind contributing CentOS/RHEL/VMware 
> related-stuff, when I start rolling out a new environment and depend on 
> community cookbooks. It's been a bit intimidating trying to figure out the 
> whole contribution process since I have no background in contributing to 
> open-source projects.

We would love to have the contributions - we'll be improving this
process.  In the meantime, can you hop on #chef on irc.freenode.net
and hit up one of the opscode folks to walk you through it?

Best,
Adam

-- 
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: