Is this project still maintained?
thomas-riccardi opened this issue · 27 comments
There has been no commit since dc58363 (2014-11-11), although important issues have been reported (like ubuntu completely broken by default), and many PR proposed, but not answered.
So...
Is there still a maintainer for this project?
I am going to assume it is not. I have had an open issue for ~20 days without so much as a response.
Hopefully I can be pleasantly surprised with some feedback or at least the owners get in contact to add a few contributors who are open to maintaining this cookbook. I wouldn't mind lending a hand.
Otherwise is the next step we all get behind a fork?
the staggering amount of unmerged PRs and lack of issue resolution makes it kind of clear no one is maintaining this project.. sad because it appears no one has a mongodb cookbook to replace it?
I haven't had time to contribute in half a year, mostly because I don't work with chef in my current role.
I'd be happy to help get the project out from under this burden, but I need at least one other person to help maintain. @zarry, @nukepuppy, @triccardi-systran do you have time to help stay on top of incoming tickets if I handle the backlog?
@josephholsten Honestly I think we would have the most success with a few active contributors. I don't mind being one of those but I wouldn't feel comfortable being the only active contributor as my available time to work on these sorts of things can vary greatly week to week.
That being said, I have no problem being one of those active contributors and helping you churn through some of this backlog.
@josephholsten I would also be willing to help. We are starting to use Mongo more and need Chef support. I would much prefer to help here than maintain my own clone.
@zarry @geerzo OK, I'll help get this to a stable place with you. The first thing I'm going to do is put together a status update like #41 (comment)
There's two kinds of things I want knocked out quickly: ready-to-merge changes and bug reports that are no longer valid. After that, I want bug triage and follow up on all open tickets.
Sound good?
@josephholsten That sounds like a great start to me. Let me know what you need from me.
@josephholsten I can try to write a PR for my issues (like #376), but I would need some guidance (and some time) as I'm not familiar with chef recipes, especially this one.
@josephholsten Let me know how I can help. Is there a way to fix the Travis CI issue (#374) and then rerun all the PRs to see which ones really fail?
@josephholsten I'm a little late to this party but I'd like to offer my help to resolve issues and bring things up to speed.
I think this repo is a victim of its own success. Unfortunately, however, as the single most downloaded MongoDB repo in the supermarket the maintainers of this repo have (likely involuntarily) assumed a responsibility to maintain it. I know it's a lot of work and that's why I'm tossing my name in the hat.
Let me know!
Also willing to help, at least for ubuntu-specific issues/PRs.
It looks that most of the members of the edelight group have a pretty low activity on github … I guess the most wise is to fork this to a new organization and add some members to contribute or may be the owners will transfer this repo if they don't want to maintain it anymore.
Glad to help as well
I'm willing to pitch in, too
@luishdez I fully support a new home for this cookbook.
@luishdez @josephholsten We would need access to publish on supermarket in place of the current mongodb cookbook up there in addition to a new github home.
Consider me available to help on this when we do find a new home. Anyone out there feel strongly enough to take ownership?
@josephholsten I am to lend a hand. I don't have many public commits to back up my experience, however I am very capable of getting involved.
ok, you all should be added to github.com/chef-brigade. If I screwed up your invitation, please let me know.
@josephholsten Great!!
If we intend to fork this repo to become a primary repo for mongo, I'll recommend to fork the repo in a new repo ( not the github way ) to avoid the ( sub-link form info ) and add a Readme note about the fork. Because this gives the sensation that it's not a primary repo and people will go to the original repo.
@josephholsten I think we can pull all the existing pull requests as those are just branches. Then push the unmerged branches and convert them to Pull requests. It will be like having the original PR though we'll loose the comments and the original title of the PR…
1: clone the original repo
2: Add fetch = +refs/pull/*/head:refs/remotes/origin/pr/*to remote origin in .git/config
3: git fetch origin
4: change the origin remote to the new repo
5: checkout and pull the remote/prs you want and push them
6: from github click those branches and convert to pull request , I think as soon you push a new branch github will tell you if you want to create a PR
We can create a new clean repo under chef-brigade/mongodb-cookbook or some…
@luishdez you should have the perms to create a repo under @chef-brigade, yes? Go ahead and create the repo, push up to it and I'll delete the fork one.
I'm happy to assist as well if necessary. I don't have a lot of free cycles for active cookbook development, but can help with PR reviews/merges if extra hands are requested.
Perhaps it would be a good idea to leave a warning in this project's README.md for people that end up here and skip the issues section, or pointing at the @chef-brigade repository.
ok, we're fully up to speed at https://github.com/chef-brigade/mongodb-cookbook, and got the readme update in #399
@josephholsten Can you update the readme and update the supermarket page for this module? I had to stumble on this issue before noticing that work had been transitioned away.
nope, I don't have write access