Since basically everyone, Opscode included, stopped shipping cookbooks as giant monolithic git repos this account hasn't really had much of a purpose. Currently it just serves as a repeater for most part. Both librarian and berkshelf are quite capable of installing directly from git which makes it all even more moot. Is there a big cohort out there still using this for any reason other than "it hasn't broken, not fixing it"?
--Noah
On Nov 13, 2012, at 8:13 PM, < "> > wrote:
> On behalf of TAQTIQA LLC (www.taqtiqa.com) I'll be a public face for the
> management and running of the cookbooks account on Github. Other volunteers are
> always welcomed.
>
> Initial TODO is (essentially based on the roadmap stated in cookbooks/about):
> - extract tar.gz and zip archives of each repo's tags to www.cookbooks.io
> (delivered by the AWS ClouFront CDN)
> - write a source for librarian-chef to retrieve archives from www.cookbooks.io
> - expand the list of individual and organization/enterprise cookbooks that are
> tracked.
> - regularize updating of github.com/cookbooks
>
> Hopefully the Librarian-chef integration should make it more attractive to use
> any of these cookbooks in production settings.
>
> Any thoughts or suggestions appreciated.
> Please make suggestions/requests in the issues section of
> github.com/cookbooks/about
>
> Regards
> Mark
Archive powered by MHonArc 2.6.16.