I’m just referring to the natural fate of most open source software: it can go unmaintained when the original author has less time and interest. If it’s not handed off to someone who cares, even great patches can go unmerged, easy questions go unanswered. This is often why forks come about, even the venerable Apache httpd whose name is in part a pun on this issue: https://www.apache.org/foundation/faq.html#name
So the goal here is to get enough people able to hand off ownership that we can avoid this. If it also means we improve the quality of the cookbooks, I won’t object.
On May 8, 2015, at 3:02 PM, Michael D Mosier email@example.com wrote:
This seems like an awesome idea. Im not sure what you mean by abandoned or what type of problems you have with your cookbooks? Sorry i am fairly new to Chef so Im looking at this as a problem I will encounter some day.
Michael D Mosier
University Of Texas, Austin
Sent from my iPad
On May 8, 2015, at 4:03 PM, Mike <firstname.lastname@example.org mailto:email@example.com> wrote:
I had done this 2 years ago with virtually zero response over here: https://github.com/chef-community/about https://github.com/chef-community/about
Maybe we should combine out powers?
On Fri, May 8, 2015 at 5:02 PM, Joseph Holsten <firstname.lastname@example.org mailto:email@example.com> wrote:
Anyone who’s been in the chef community for a while has felt the pain of abandoned cookbooks. And in fact, I’ve found myself unable to maintain the ones I care about.
So I’ve created a github organization to own my repos. I’ve already invited a number of people, and would love to invite /you/.
For now, this community is low ceremony. If there’s anything you’d like the chef brigade to do, please let me know!