Hi,
There is now an about/how-to-contribute page for the
github.com/cookbooks organization:
https://github.com/cookbooks/about
I’ve also just made the first pass at tracking individual cookbook
repositories.
This is still only some of the Heavywater cookbooks that are not in
the Opscode collection.
Notwithstanding the beta status:
Now that it is possible to track individual repos do people have any
best-of-breed cookbooks they think are worth tracking. At the moment
I’m inclined to add these cookbooks from Silversky Solutions (aka
fnichol on github):
nichol/chef-rbenv
nichol/chef-ruby_build
I imagine there could be others from Silversky Solutions, but the
above are all that I have used…
Finally, the Heavywater cookbooks that were tracked when in their
cookbooks repository collection, had been broken out into separate
repos. I now track those separate repos.
This provides an opportunity to decide on a deprecation/change-over
policy/workflow, if there should be any, when a cookbook is not
dropped, but just changes repository name - inconvenient but not
there-is-no-code-anymore bad.
Ideally, once out of the Beta phase, a cookbook repo would never
disappear completely from github.com/cookbooks, but they can change
upstream (think of this in terms of a massive commit changing the old
upstream code into the new upstream code).
I think this case of heavywater is unique since they were the first
non-opscode upstream group whose cookbooks collection was tracked, and
now they are the first whose individual repos are tracked.
So now we workout how to handle these situations going forward 
Thoughts?
–
πόλλ’ οἶδ ἀλώπηξ, ἀλλ’ ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://hedgehogshiatus.com