# Cookbook maintenance problem

**URL:** <https://discourse.chef.io/t/cookbook-maintenance-problem/5492>\
**Category:** Chef Infra (archive)\
**Created:** [June 6, 2014, 5:56pm UTC](https://discourse.chef.io/t/cookbook-maintenance-problem/5492 "2014-06-06T17:56:54Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![brauliobo](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/brauliobo/32/109_2.png) [@brauliobo](https://discourse.chef.io/u/brauliobo)\
**Post date:** [June 6, 2014, 5:56pm UTC](https://discourse.chef.io/t/cookbook-maintenance-problem/5492/1 "2014-06-06T17:56:54Z")

</div>

Hello all,

This subject was already discussed early, but as things really needs  
to get better I’m revamping this.

I see that some authors made a lot of cookbooks. Then they cannot  
handle and maintain them well. For example, the nginx cookbook, misses  
many configuration options and has a long list of pull requests  
([https://github.com/opscode-cookbooks/nginx/pulls](https://github.com/opscode-cookbooks/nginx/pulls)) mostly without any  
comments on them.

So for these cookbooks it is necessary to change the maintainers or  
add new active and experienced developers to them, don’t you think?  
How could that be done?

Cookbooks that matches the exact name are really important, so they  
need to keep up with the users’ needs.

cheers,  
bráulio

---

<div class="post-metadata">

**Author:** ![Sean\_OMeara1](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/sean_omeara1/32/207_2.png) [@Sean\_OMeara1](https://discourse.chef.io/u/Sean_OMeara1)\
**Post date:** [June 10, 2014, 4:40pm UTC](https://discourse.chef.io/t/cookbook-maintenance-problem/5492/2 "2014-06-10T16:40:02Z")

</div>

We found a new maintainer for Nginx. [GitHub - sous-chefs/nginx: Development repository for the nginx cookbook](https://github.com/miketheman/nginx)

Datadog uses and abuses Nginx on an impressive scale, so its in good hands.

> **[Cloud Monitoring as a Service | Datadog](https://www.datadoghq.com/)**
>
> See metrics from all of your apps, tools & services in one place with Datadog's cloud monitoring as a service solution. Try it for free.

-s

On Fri, Jun 6, 2014 at 1:56 PM, Bráulio Bhavamitra [brauliobo@gmail.com](mailto:brauliobo@gmail.com)  
wrote:

> Hello all,
> 
> This subject was already discussed early, but as things really needs  
> to get better I'm revamping this.
> 
> I see that some authors made a lot of cookbooks. Then they cannot  
> handle and maintain them well. For example, the nginx cookbook, misses  
> many configuration options and has a long list of pull requests  
> ([Pull requests · sous-chefs/nginx · GitHub](https://github.com/opscode-cookbooks/nginx/pulls)) mostly without any  
> comments on them.
> 
> So for these cookbooks it is necessary to change the maintainers or  
> add new active and experienced developers to them, don't you think?  
> How could that be done?
> 
> Cookbooks that matches the exact name are really important, so they  
> need to keep up with the users' needs.
> 
> cheers,  
> bráulio

---

<div class="post-metadata">

**Author:** ![brauliobo](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/brauliobo/32/109_2.png) [@brauliobo](https://discourse.chef.io/u/brauliobo)\
**Post date:** [June 24, 2014, 1:02pm UTC](https://discourse.chef.io/t/cookbook-maintenance-problem/5492/3 "2014-06-24T13:02:45Z")

</div>

Nice to hear that Sean!

Thanks,  
Braulio  
Em 10/06/2014 13:40, "Sean OMeara" [someara@opscode.com](mailto:someara@opscode.com) escreveu:

> We found a new maintainer for Nginx. [GitHub - sous-chefs/nginx: Development repository for the nginx cookbook](https://github.com/miketheman/nginx)
> 
> Datadog uses and abuses Nginx on an impressive scale, so its in good  
> hands.  
> [https://www.datadoghq.com/](https://www.datadoghq.com/)
> 
> -s
> 
> On Fri, Jun 6, 2014 at 1:56 PM, Bráulio Bhavamitra [brauliobo@gmail.com](mailto:brauliobo@gmail.com)  
> wrote:
> 
> > Hello all,
> > 
> > This subject was already discussed early, but as things really needs  
> > to get better I'm revamping this.
> > 
> > I see that some authors made a lot of cookbooks. Then they cannot  
> > handle and maintain them well. For example, the nginx cookbook, misses  
> > many configuration options and has a long list of pull requests  
> > ([Pull requests · sous-chefs/nginx · GitHub](https://github.com/opscode-cookbooks/nginx/pulls)) mostly without any  
> > comments on them.
> > 
> > So for these cookbooks it is necessary to change the maintainers or  
> > add new active and experienced developers to them, don't you think?  
> > How could that be done?
> > 
> > Cookbooks that matches the exact name are really important, so they  
> > need to keep up with the users' needs.
> > 
> > cheers,  
> > bráulio

---

<div class="post-metadata">

**Author:** ![brauliobo](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/brauliobo/32/109_2.png) [@brauliobo](https://discourse.chef.io/u/brauliobo)\
**Post date:** [June 29, 2014, 9:08pm UTC](https://discourse.chef.io/t/cookbook-maintenance-problem/5492/4 "2014-06-29T21:08:21Z")

</div>

Made a very simple pull request to support other configurations:

> <https://github.com/sous-chefs/nginx/pull/235>
>
> Support any other configuration the user want to use in a hash. Pretty simple :)

cheers,  
bráulio

On Fri, Jun 6, 2014 at 2:56 PM, Bráulio Bhavamitra [brauliobo@gmail.com](mailto:brauliobo@gmail.com)  
wrote:

> Hello all,
> 
> This subject was already discussed early, but as things really needs  
> to get better I'm revamping this.
> 
> I see that some authors made a lot of cookbooks. Then they cannot  
> handle and maintain them well. For example, the nginx cookbook, misses  
> many configuration options and has a long list of pull requests  
> ([Pull requests · sous-chefs/nginx · GitHub](https://github.com/opscode-cookbooks/nginx/pulls)) mostly without any  
> comments on them.
> 
> So for these cookbooks it is necessary to change the maintainers or  
> add new active and experienced developers to them, don't you think?  
> How could that be done?
> 
> Cookbooks that matches the exact name are really important, so they  
> need to keep up with the users' needs.
> 
> cheers,  
> bráulio

--  
"Lute pela sua ideologia. Seja um com sua ideologia. Viva pela sua  
ideologia. Morra por sua ideologia" P.R. Sarkar

EITA - Educação, Informação e Tecnologias para Autogestão

> **[Bráulio Bhavamitra](https://cirandas.net/brauliobo)**

> **[Cooperativa EITA](https://eita.coop.br/)**
>
> Educação, Informação e Tecnologias para Autogestão

"Paramapurusha é meu pai e Parama Prakriti é minha mãe. O universo é meu  
lar e todos nós somos cidadãos deste cosmo. Este universo é a imaginação da  
Mente Macrocósmica, e todas as entidades estão sendo criadas, preservadas e  
destruídas nas fases de extroversão e introversão do fluxo imaginativo  
cósmico. No âmbito pessoal, quando uma pessoa imagina algo em sua mente,  
naquele momento, essa pessoa é a única proprietária daquilo que ela  
imagina, e ninguém mais. Quando um ser humano criado mentalmente caminha  
por um milharal também imaginado, a pessoa imaginada não é a propriedade  
desse milharal, pois ele pertence ao indivíduo que o está imaginando. Este  
universo foi criado na imaginação de Brahma, a Entidade Suprema, por isso  
a propriedade deste universo é de Brahma, e não dos microcosmos que também  
foram criados pela imaginação de Brahma. Nenhuma propriedade deste mundo,  
mutável ou imutável, pertence a um indivíduo em particular; tudo é o  
patrimônio comum de todos."  
Restante do texto em

> **[A problemática de hoje em dia - Bráulio Bhavamitra](https://cirandas.net/brauliobo/blog/a-problematica-de-hoje-em-dia)**
>
> "Paramapurusha é meu pai e Parama Prakriti é minha mãe. O universo é meu lar e todos nós somos cidadãos deste cosmo. Este universo é a imaginação da Mente Macrocósmica, e todas as entidades estão sendo criadas, preservadas e destruídas nas fases de...

---

<div class="post-metadata">

**Author:** ![Sean\_OMeara1](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/sean_omeara1/32/207_2.png) [@Sean\_OMeara1](https://discourse.chef.io/u/Sean_OMeara1)\
**Post date:** [June 6, 2014, 6:39pm UTC](https://discourse.chef.io/t/cookbook-maintenance-problem/5492/5 "2014-06-06T18:39:12Z")

</div>

Hi Braulio,

Historically, we haven't used Github pull requests to manage contributions  
to cookbooks. Instead, we've tracked issues in our JIRA. This was mainly a  
workflow issue, to ensure that contributions that made it to our review and  
merge queues have has a CLA signed.

After the launch of Supermarket, we'll be able to use Github issues  
directly. It will hel our workflow by adding labels about CLAs to pull  
requests, so we can tell at a glance if we can accept it. That will greatly  
improve our contribution process, so PRs won't languish like this.

During the past 6 months, we've been experimenting with diversifying the  
the Opscode managed cookbooks. This been met with mixed results, but has  
overall been going well. We're not subject matter experts in most things,  
so we've been seeking maintainers where appropriate.

Concerning nginx specifically, its on the list for a complete rewrite to  
address all the issues in one sweep. Because we use it internally, and  
because of the flat namespace on the community site, we're holding on to it  
for now.

We're working hard to get supermarket out the door, so stay tuned.

-s

On Fri, Jun 6, 2014 at 1:56 PM, Bráulio Bhavamitra [brauliobo@gmail.com](mailto:brauliobo@gmail.com)  
wrote:

> Hello all,
> 
> This subject was already discussed early, but as things really needs  
> to get better I'm revamping this.
> 
> I see that some authors made a lot of cookbooks. Then they cannot  
> handle and maintain them well. For example, the nginx cookbook, misses  
> many configuration options and has a long list of pull requests  
> ([Pull requests · sous-chefs/nginx · GitHub](https://github.com/opscode-cookbooks/nginx/pulls)) mostly without any  
> comments on them.
> 
> So for these cookbooks it is necessary to change the maintainers or  
> add new active and experienced developers to them, don't you think?  
> How could that be done?
> 
> Cookbooks that matches the exact name are really important, so they  
> need to keep up with the users' needs.
> 
> cheers,  
> bráulio