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

[Alex Soto < >]

I agree on the hurdle to contribute.  My hurdle is how can I maintain a 'dev' 
environment and a clean gem installed environment for 'normal' work.  Like 
John, I'm short on time, so the hurdle to 'easy' contributions just keeps me 
pigeon-holed working on my own stuff.

Another thing is I'd publish my chef repo on github, but it's problematic 
because I have some stuff in there I don't want published, keys, passwords, 
etc.

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.

Alex

On Jul 15, 2010, at 12:47 PM, John Merrells wrote:

> 
> On Jul 15, 2010, at 11:58 AM, Daniel DeLeo wrote:
> 
>> This is awesome. Any plans to publish the gem?
> 
> 
> I don't think it really warrants being a gem. I think it should be added to 
> the 'chef::client' 
> cookbook recipe... then the user could select the notifier(s) they want 
> enabled via the
> cookbook attributes.
> 
> On a related topic... I still don't quite grok how one can contribute back 
> to the cookbooks...
> there are multiple repos of cookbooks... and multiple repos of single 
> cookbooks... so its
> kinda hard to contribute.
> 
> So far I've found the existing cookbooks to be a very useful crib for 
> writing my own... often
> I copy one, hack away the stuff I'm not interested in (apache, etc) and 
> then add the few 
> small twiddles I need (e.g. nginx). 
> 
> Also, I tend to work on a recipe until it works for me.... and then stop 
> working on it... and
> I don't bother making it generic enough for anybody to use..... me being 
> lazy but I think
> the contributing back hurdle is too high. 
> 
> John
> 
> -- 
> John Merrells
> http://johnmerrells.com
> +1.415.244.5808
> 
> 
> 
> 
> 
>