[chef] Re: GitHub workflow for open source cookbooks

[Ringo De Smet < >]

Eric,

On 17 June 2011 16:29, Eric Hauser 
<
 >
 wrote:

> We have a normal chef style cookbooks repository on GitHub with about 30
> cookbooks or so in our site-cookbooks directory.  Since I only want to open
> source a subset of them, I cannot just make our repository public.  I was
> thinking about just setting up a second public repository and using git
> filter-branch to move the cookbooks we want to open into it.  That seems
> like it work well for the initial release, but I wanted to make ongoing
> maintenance easy well.

Have a look at the following:
https://github.com/atriso/chef-repo-pas
https://github.com/atriso/chef-openerp-cookbook

The former link is a Chef repository on Github I am using for one of
my customers, that has the single cookbook repository from the second
link as a Git submodule.

Having the cookbooks I develop in separate Git repositories is easy
for letting other people contribute. It is a repo on it's own, with
tickets, pull requests and alike. Either, people use my repo (or their
own fork) as a Git submodule within their Chef repository, or they use
the knife plugin [1] that allows them to use the vendor branch pattern
similar to "knife cookbook site install".

[1] https://github.com/websterclay/knife-github-cookbooks

In your case, split out the cookbooks you want to share as separate
Git repositories, and then pull them back in in your complete Chef
repository as Git submodules.

Cheers,

Ringo