# Github.com/cookbooks

**URL:** <https://discourse.chef.io/t/github-com-cookbooks/1728>\
**Category:** Chef Infra (archive)\
**Created:** [February 10, 2011, 1:41am UTC](https://discourse.chef.io/t/github-com-cookbooks/1728 "2011-02-10T01:41:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![hedgehog](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/hedgehog/32/620_2.png) [@hedgehog](https://discourse.chef.io/u/hedgehog)\
**Post date:** [February 10, 2011, 1:41am UTC](https://discourse.chef.io/t/github-com-cookbooks/1728/1 "2011-02-10T01:41:47Z")

</div>

Hi,  
I’m getting to the point where I think I can take down the “(WIP don’t  
fork)” caveat.  
It is not yet clear to me if the Chef community would use this (one  
application mentioned below).

How do people want to see this work:

- If someone (group), reputable (as defined by the community), wants  
to take over the cookbooks account… I’m more than happy to hand over  
🙂
- Cookbook specific collaborators: Allow? Criteria people would like  
to see applied?
- Keep github issues page for each cookbook?
- Comments on default branch names (live, master, qa, 37s) and tags?  
These are generated for the opscode cookbooks. 37Signals cookbooks  
have the 37s branch/tags

Use case:

- A Chef Cookbook Library web site ala [0].  
Downloads don’t seem relevant, but some metric as a  
f(watching,fork,issues) might be of use. One can also imagine parsing  
the metadata file and indicating platforms, etc. etc.

HTH

[0] [http://www.ruby-toolbox.com/categories/continuous\_integration.html](http://www.ruby-toolbox.com/categories/continuous_integration.html)

–  
πόλλ’ οἶδ ἀλώπηξ, ἀλλ’ ἐχῖνος ἓν μέγα  
[The fox knows many things, but the hedgehog knows one big thing.]  
Archilochus, Greek poet (c. 680 BC – c. 645 BC)  
[http://wiki.hedgehogshiatus.com](http://wiki.hedgehogshiatus.com)