Thank you! :) I will do my best to keep cookbook as clean and functional as possible. If anyone else want to help me, I'm really open. Last thing you can do for Ceph cookbook is to enable travis ( https://travis-ci.org/profile/ceph ) for this repository. Guilhem Lettron On Tue, Feb 18, 2014 at 2:45 PM, Sage Weil <sage@xxxxxxxxxxx> wrote: > On Tue, 18 Feb 2014, Guilhem Lettron wrote: >> Hi Sage, >> Sorry I didn't see this thread until tomorrow (Loic ping me this discussion >> during Paris meetup). >> >> I already do a lot of work on Ceph coobook last years, when I see the >> inactivity on repository, I review PR, merge and add tests on my own. >> Here is my repo: https://github.com/guilhem/ceph-cookbook >> >> I also have registered ceph on chef community >> repository: http://community.opscode.com/cookbooks/ceph >> >> I will be happy to merge it back on official repository and commit new >> version on chef community site. > > Thank you! This is great news. Let me know if there's anything I can > help with. > > sage > >> >> Guilhem Lettron >> >> >> On Mon, Feb 3, 2014 at 8:36 PM, Sage Weil <sage@xxxxxxxxxxx> wrote: >> Hi everyone, >> >> We have a huge backlog of pull requests on ceph-cookbooks.git on >> github. >> At the moment Inktank doesn't have a lot of spare cycles to >> review and >> test these changes. Are there any chef+ceph users that are >> interested in >> helping maintain these cookbooks? >> >> sage >> -- >> To unsubscribe from this list: send the line "unsubscribe >> ceph-devel" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at >> http://vger.kernel.org/majordomo-info.html >> >> >> >> -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
