[chef] Re: Re: Re: Re: chef & hoptoad

[Joshua Timberman < >]

Ohai!

On Jul 15, 2010, at 2:40 PM, Alex Soto wrote:

> I'd love to read how some of the opscode guys are doing chef dev work AND 
> working on maintaining systems with chef, what their workflow is, etc.

We have a number of repositories. First, the two open source ones we start 
with:

1. Cookbooks http://github.com/opscode/cookbooks
2. Chef Repository http://github.com/opscode/chef-repo

I actually maintain both of these repositories for Opscode, and they are 
separate from my own testing repositories.

I work with a number of Chef Servers for testing cookbooks, doing development 
workflow and building our training material, etc. Each of these servers has a 
corresponding chef-repo, and each one has a different Opscode Platform 
organization as the Chef Server (except the case of my local OSS Chef Server 
for testing installation).

I first clone the chef-repo, then I use the vendor branch workflow described 
on our help site[0]. Most of these repos are private or throwaway. If they 
were something I wanted to publish to a central repo, then that would have 
either the apprpriate github repository (private or public depending on the 
use), or a private internal Git server.

I hope this helps clarify, along with the contributing email I sent to the 
list a few minutes ago. If not, let me know if you have further questions.

[0]: http://help.opscode.com/faqs/start/working-with-cookbooks

-- 
Opscode, Inc
Joshua Timberman, Senior Solutions Engineer
C: 720.334.RUBY E: