Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Call for Maintainers #143

Open
fgrehm opened this issue May 8, 2015 · 24 comments
Open

Call for Maintainers #143

fgrehm opened this issue May 8, 2015 · 24 comments

Comments

@fgrehm
Copy link
Owner

@fgrehm fgrehm commented May 8, 2015

Hey guys!

Life, as it tends to do, has progressed for me in such a way that I am no longer able to devote time to maintaining this plugin, especially as I no longer use it on a daily basis.

As such, this project has been neglected and I apologize for that. I am hoping there is someone who would be willing to step up and take over maintaining this project so it gets the attention it deserves. If you would like to do so, please respond with a comment explaining a bit about what you would like to do as a maintainer of this project. I'll then add one or more of those users as collaborators.

Thanks everyone!

@aneeshusa
Copy link

@aneeshusa aneeshusa commented May 11, 2015

I just started using vagrant-cachier a few days ago, but I'd be willing to maintain this project. It definitely solves one of my pain points and I see myself using it for a long time. I'd want to start with triaging the existing issue list and shoring up the test suite, then look at adding new bucket types. FYI, I'm in the middle of finals right now so I'll be busy for another week and a half, but after that I'll be able to pick up the pace. Also, huge shoutout for making this plugin - it saves me a ton of time, and I really appreciate the effort you've put in.

@fgrehm
Copy link
Owner Author

@fgrehm fgrehm commented May 13, 2015

@aneeshusa Awesome! I went ahead and added you as a collaborator on the project, enjoy your superpowers 💃

LMK when you are ready to cut a release and I'll look into setting things up on the RubyGems side of things. If you need any feedback or help feel free to ping me on the appropriate issue / PR, I wont be able to help out testing / writing code but I'm always available to answer questions you and other collaborators might have.

Cheers! 🍻

@rogeriopradoj
Copy link

@rogeriopradoj rogeriopradoj commented May 19, 2015

👍 good luck!

@cromulus
Copy link

@cromulus cromulus commented May 20, 2015

Congrats!

This is an important project and I'm happy to see someone step up!
On May 19, 2015 12:28 AM, "Rogerio Prado de Jesus" notifications@github.com
wrote:

[image: 👍] good luck!


Reply to this email directly or view it on GitHub
#143 (comment)
.

@aneeshusa
Copy link

@aneeshusa aneeshusa commented May 20, 2015

Thanks for the kind words everyone! Pushing through finals right now but looking forward to getting started on maintaining next week.

@jalcine
Copy link

@jalcine jalcine commented Jun 17, 2015

Is there a label to look into for helping out?

@schlueter
Copy link

@schlueter schlueter commented Jul 7, 2015

I'd be willing to assist as well if you'd like help @aneeshusa .

@fgrehm
Copy link
Owner Author

@fgrehm fgrehm commented Jul 7, 2015

@jalcine @schlueter any kind of help would be greatly appreciated, be it triaging issues, fixing bugs, testing PRs.... I'm up for providing commit access to the repository but given the current project activity and the amount of collaborators we have from the time I put together the PR Hack I'd like to see some action first.

For now I'm going to start fresh and will clean up the write access we have around besides @patcon's since he helped out with the latest release

Sorry @mindreframer @cromulus @fh @laggyluke @tmatilai @gimler @aneeshusa, I can get you write access again in case you guys are interested, feel free to unwatch this issue and avoid getting additional noise on your inboxes and thanks for the help you provided!

@joelhandwell
Copy link

@joelhandwell joelhandwell commented Mar 11, 2016

@aneeshusa Is there any updates?

@lwh
Copy link

@lwh lwh commented Jun 23, 2016

Do you still need people?

@fgrehm
Copy link
Owner Author

@fgrehm fgrehm commented Jun 23, 2016

Yes!

@rmohr
Copy link
Collaborator

@rmohr rmohr commented Sep 26, 2016

Hi @fgrehm ,

I would also be very interested in helping out. As a start I would want to merge #180 to make the plugin work properly on newer Fedora guests.

@fgrehm
Copy link
Owner Author

@fgrehm fgrehm commented Nov 22, 2016

Damn, I'm really sorry @rmohr, your email got "lost" in my inbox. You should receive an invite for collaborating on the project any time soon so you got the power now!

LMK when you are ready to cut a release and shoot me you rubygems account.

@amontalban
Copy link

@amontalban amontalban commented Jan 18, 2017

Hi @fgrehm,

Do you need more help? I want #168 to be merged but nobody took it in almost a year.

Thanks!

@rmohr
Copy link
Collaborator

@rmohr rmohr commented Jan 18, 2017

@amontalban will look at it tomorrow, @fgrehm since my time is also very limited I would be happy to have @amontalban as maintainer too.

@deiga
Copy link

@deiga deiga commented Dec 19, 2017

@rmohr @fgrehm What is the status here currently? Can I help with stuff? :)

@patcon
Copy link
Collaborator

@patcon patcon commented Dec 20, 2017

Having recently gone through a successful effort in transferring maintainership, I'd say that creating a gitter.im chat room and submitting a PR for the README badge is a great way to start. It makes it easy to invite in potential maintainers, have some lightweight convos about style and process and triage, and get a repo moving again :)

@tarcinil
Copy link

@tarcinil tarcinil commented Feb 8, 2018

I would be interested in helping with this effort. I would look at adding Travis testing as well as DCO for all pull requests.

@davividal
Copy link

@davividal davividal commented Aug 22, 2018

@rmohr @patcon @fgrehm @amontalban what is the current status?
How can I help?
I noticed that the gitter.im/fgrehm/vagrant-cachier is pretty much dead.

@Dispader
Copy link

@Dispader Dispader commented Dec 3, 2018

I'll also say-hey, here: the Cachier plugin is important enough to our CI efforts, and I've run an open source project or two over the years. We might-could form a team: I'm wagering the work is pretty light, here.

@patcon
Copy link
Collaborator

@patcon patcon commented Dec 3, 2018

Sorry, never did get push access myself to pass along. But I support these offers! So long as you're not overzealous about blockchain tech... ;)

(See also: event-stream)

@davividal
Copy link

@davividal davividal commented Dec 4, 2018

@Dispader and @patcon : I forked this repo and gave you both access to it.
Let's get it moving :)

@patcon
Copy link
Collaborator

@patcon patcon commented Dec 4, 2018

Thanks! I'm not using this anymore, but I'll ping Fabio on the Twitters about delegating push to y'all (and me if I can help in situations like this in future)

@fgrehm
Copy link
Owner Author

@fgrehm fgrehm commented Dec 10, 2018

hey peeps! sorry for the silence here. if you guys are able to create a github org and give me enough 💪 I can transfer ownership to the org right away. I can also give away rubygems push permissions to people but I'd rather give it to just one person that is capable of setting up gem releases from CI

Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
You can’t perform that action at this time.