[chef] Re: [chef-dev] Ownership Changes of Chef Cookbooks Revisited

["Julian C. Dunn" < >]

Hey Ryan,

I'm actually gonna shift this thread to chef@ so that it gets broader
visibility.

I've been meaning to address some of the points here since we had the
Cookbook Governance BoF at ChefConf (and I have been remiss in not
posting a summary from that). I have a short deck that summarized how
I set up the conversation at the BoF:
http://www.slideshare.net/JulianDunn/chef-cookbook-governance-bof-at-chefconf

What we heard from folks there is that the community wants Chef
(Software, Inc.) to be more prescriptive about managing the namespaces
on the community site. In other words, folks who were at the BoF
wouldn't mind if we set some standards for evicting unresponsive
maintainers from those namespaces, and/or transferring ownership to
others who want to take over cookbooks -- provided, of course, that we
have made a good faith effort to contact maintainers & encourage them
to do their duty.

I'd like to hear from others who weren't at the BoF if they also feel
this way. If you do, then I think we (Chef Software, Inc.) should work
with the community to develop some of these rules, and then enforce
them, to the extent that 'enforce' means 'be the broker of last resort
in case of dispute or cookbook abandonment'.

I've also asked Chris Webber, our community software developer, to
weigh in on this thread. He has some thoughts that may be pertinent.

- Julian

On Fri, May 23, 2014 at 4:58 PM, Ryan Hass 
<
 >
 wrote:
> A little over six months have gone by since many of the cookbooks were
> handed off to various community maintainers. Now seems like a good time
> to continue this discussion with wisdom at hand; I am sure many others,
> like myself may have questions and surely have ideas on how to improve.
>
> Many of the cookbook maintainers have done an outstanding job of working
> with the community, resolving issues, and accepting and mentoring
> changes. Unfortunately, there are a few which have not met the quality
> standards which preceded their maintainer-ship. Having said this, I
> would like to discuss the Chef governance policy with regards to
> maintainers whom have been unable to fulfill their duties, and the
> process of ensuring these cookbooks continue to have high quality going
> forward.
>
> Some questions I have are:
>
> * What is the current governance of cookbooks which were previously
> maintained by Chef (Opscode)?
>
> * How can the community get involved in this governance process to
> ensure high quality standards persist for said cookbooks?
>
> Please do not hesitate to share your questions or thoughts on the
> subject of the cookbooks which were handed off. As mentioned, I am sure
> there are many others with related questions and ideas on the topic.
>
> -Ryan H.
> This electronic message contains information which may be confidential or 
> privileged. The information is intended for the use of the individual or 
> entity named above. If you are not the intended recipient, be aware that 
> any disclosure, copying, distribution or use of the contents of this 
> information is prohibited. If you have received this electronic 
> transmission in error, please notify us by e-mail at 
> (
 )
>  immediately.
>



-- 
[ Julian C. Dunn 
<
 >
          * Sorry, I'm    ]
[ WWW: http://www.aquezada.com/staff/julian    * only Web 1.0  ;]
[ gopher://sdf.org/1/users/keymaker/           * compliant!    ;]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9       ]