Hi,
On Fri, Apr 13, 2012 at 7:15 PM, Denis Barishev
< >
wrote:
This is a concern I also have. I have several cookbooks that have theThe "ospcode-cookbooks" organization on GitHub contains only cookbooksThanks that exactly what I thought. This cookbook is heavily outdated. Could
that we directly publish, maintain and support, all under the
"opscode" user on the community site. Everyone is free to share their
own cookbooks on the community site (and host the code repository
wherever they like).
http://community.opscode.com/users/opscode
we publish the new cookbook in the opscode repository? I think it would be
problematic to contact the author, the cookbook is dated to 2010 and it's
too old. Though I haven't try to contact the author... I mean the author
doesn't support the cookbook, so this may just turn into a waste of time.
It also concerns all other cookbooks that are forgot by their authors. They
don't have any life in their repositories.
same name as those on the community site so I never bothered to look
into what would be required to release them there. If we could somehow
add a "name" field to the metadata that the download tool could use to
name the directory downloaded into (or perhaps rework the way recipes
are named to be based on names rather than directory names) that would
solve a lot of these issues.
Actually I have also created theI would be very interested in these - we already have custom
new graylog2 cookbook which uses elasticsearch.
mongo/graylog cookbooks that were derived from somewhere in the wild
at one stage. I am a week or two away from upgrading from 0.9.5p1 to
the latest and would like to share the effort if possible. Are these
stored in a github repository anywhere?
Archive powered by MHonArc 2.6.16.