[chef] Re: GitHub workflow for open source cookbooks

[Charles Duffy < >]

I don't try to sync cookbooks in our public repository back to the private one -- once it's moved to public, it's public, and that's the *only* place it lives.

On Fri, Jun 17, 2011 at 9:29 AM, Eric Hauser < "> > wrote:

Hi,

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.  Assuming I don't change the directory names, I believe I might be able to cherry-pick from the private repository to keep the public cookbooks up to date.  The other alternative I thought was filter-branch'ing a new public repository, forking it and making the fork private.  This requires more coordination with the other guys using our repository and I'm not sure if you can send a pull request to a public repository from a private one.

Anyone have a good suggestion? Thanks.