[chef] Re: [[chef-dev]] Re: [[chef-dev]] Re: Re: Re: Contributing to Cookbooks (was chef & hoptoad)

[Adam Jacob < >]

On Fri, Jul 16, 2010 at 9:28 PM, Chad Woolley 
<
 >
 wrote:
> Yes, that's exactly what I would like to see- a parallel mode for
> knife which works with a plain git repo, or even just github.  This
> would allow people who don't use chef-server to still fork and
> participate in the opscode cookbook community.

Patches welcome!

There is nothing stopping you from contributing to the cookbook
community, though - all you need to do is package up your cookbook and
publish it.  It's not specific to the Chef server.  At the same time,
not every cookbook is going to work with chef-solo - things like
Search and Data Bags are always going to be a bummer there.

> When I first started with chef, I tried briefly to be a good citizen
> and do this manually fork opscodes' cookbooks using git topic branches
> and do pull requests, tickets, etc.  However, it's just too much work
> (i.e. much easier to just write all my cookbooks from scratch using
> opscode's cookbooks as an example, and not fork opscode's cookbooks or
> contribute anything back).

There is nothing wrong with writing your own cookbooks - you're not
being a bad citizen.  What you might want to do after the fact is
publish *yours*, because others might prefer the way you do it to the
way we do.  TIMTOWTDI is the rule here.

> Since my from-scratch cookbooks were so much simpler, focused, and
> non-buggy; I'm not sure I would fork opscode's again even if it were
> easy to contribute back, but that's a discussion for another day ;)
> chef-solo and ohai are the bomb in any case, thanks a lot for them.

Right, that's the point - if you like what you're doing, and it's
awesome, don't stop doing it.  But consider sharing it, so that other
people who *also* like what you are doing can do it your way instead.

Adam

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