On Sat, Dec 10, 2011 at 3:37 PM, Bryan McLellan email@example.com wrote:
On Fri, Dec 9, 2011 at 1:33 AM, Hedge Hog firstname.lastname@example.org wrote:
On Fri, Dec 9, 2011 at 9:36 AM, Matt Ray email@example.com wrote:
Is there an associated ticket with this?
On Fri, Dec 9, 2011 at 11:14 AM, Sebastian Boehm
Only a GitHub ticket for now:
For the sake of clarity for those new to the list, this is a pull
request and github issue in the ‘cookbooks’ GitHub account, which is
completely separate from the Opscode Cookbooks at
http://github.com/opscode/cookbooks and our ticketing at
It would be great if the Website/Blog link for that repository pointed
at a static page somewhere that outlined its purpose, how to
contribute to it, and how it differs from the Opscode cookbook
repository regarding content, source and contribution.
Bryan is right we should have an about repo that is a github-pages site.
Essentially one description of the the problems tackled by
github.com/cookbooks is described in the following exchange (rberger
not assoc with any cookbooks teams as far as I am aware, he just
describes an issue many have identified for some time):
This also makes clear why Opscode won’t, can’t and arguably shouldn’t
advocate for use of one of:
They have SLAs to deliver on and they can only do that if they have
the fully control that people paying for the SLA are demanding by,
well, paying for a SLA
It’s not personal - just business.
Of course anybody can fork:
make their changes on top and offer whatever SLA they feel they can.
πόλλ’ οἶδ ἀλώπηξ, ἀλλ’ ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)