[chef-dev] Re: Community contribution check-in

[Alex Soto < >]

Cookbook publishing/collaboration is most important to me.  

Community Site:
Just ran into this today.  I happened to look at the cookbook community site 
and noticed someone posted a comment offering patches 5 months ago!  It would 
have been great if there were some sort of alert to comments.  Who knows if 
he will notice I posted a comment reply to him.


Cookbook Publishing:
Also, I haven't been actively doing any chef work for the last few months so 
I might have missed any new developments, but I don't see a good way to 
publish a single cookbook and easily collaborate on it with someone (pull in 
patches) and still easily pull it into production chef repositories.

The cookbooks I've published to the community site have all been extracted 
from my employer's cookbook repository.  I haven't had the time to extract 
the cookbooks out into public repo's and don't see a simple way to do that 
without a bit of extra work on my part.  Maybe that's the price I pay for 
publishing the cookbook, but I'm short on time (like everyone else), but 
maybe the smoother the process can be, the more the community can contribute?


Alex


On Aug 18, 2011, at 6:56 PM, Bryan McLellan wrote:

> Hey folks,
> 
> I'd like to take a minute to check-in with everyone on how the
> contribution process is working. We've made great strides in some
> areas, here is where we've been focusing:
> 
> * Weekly triage to ensure patches get marked for merging
> * More discussion on this list where everyone can participate
> * Move toward more regular releases of projects
> * Increased focus on packaging for releases
> 
> Here are a couple issues we're looking at tackling next:
> 
> * Github 'issues' is still enabled for some projects, causing confusion
> * Pull requests aren't triaged to ensure they have a corresponding ticket
> * Some projects still need more regular merging and releases
> * We don't have an automated infrastructure to test releases and cookbooks
> 
> What is most important to you?
> Was the contribution process [1] too difficult to pick up?
> Are there tools we should be utilizing to make it much easier?
> Any other ways we could improve the experience?
> 
> Let me know, you can email me directly at 
> <
 >
>  if you
> have any thoughts or concerns that you would be uncomfortable
> publishing to the list.
> 
> -- 
> Bryan McLellan | opscode | senior systems administrator
> (c) 206.607.7108 | (t) @btmspox | (b) http://blog.loftninjas.org
> 
> [1] http://wiki.opscode.com/display/chef/How+to+Contribute