General discussion about Chef

[chef] GitHub workflow for open source cookbooks


Chronological Thread 
  • From: Eric Hauser < >
  • To:
  • Subject: [chef] GitHub workflow for open source cookbooks
  • Date: Fri, 17 Jun 2011 10:29:02 -0400
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=DWxnGs9VydHQLOAjW+6/P8l+XjcfzhWUbHWVw8BgnESGrGc5VwgDvl472yWXAXxesH T1OcOUIya2GQEFT2NLJaF2qKFUvHvo/g86Tz8YaFqaRjtdelDY6wfo6gGP5ZBBoUtpwn hkqAIWNjGfnasGBcz9iZFGmAVq43FiJ9Y5ixQ=
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.

Archive powered by MHonArc 2.6.16.

§