-
Notifications
You must be signed in to change notification settings - Fork 202
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
Offering to help maintain this repo #209
Comments
👍 Hopefully the maintainers will see this soon and be appreciative of the help. Paging @fnichol |
Thanks @stuartpreston :) |
Paging @tyler-ball as he was the last one to merge code on this repo... :) |
We are working on putting some more regular triage and maintenance on these projects. I definitely appreciate the offer to help and as we look to widen the ability for people to take a more active role in some of these projects I'll keep you informed. I'm mobile at the moment so I'll revisit the sum total of your first post when I'm at a terminal more suited to a real response. Thanks! |
Thanks @smurawski, I'll look forward to hearing from you. |
Thanks 👍 |
Thanks for the offer @proffalken! I've sent this to my manager to see what he thinks. We're happy and grateful for open source contributions and maintenance. I think the time investment would be in determining a process for granting/removing maintainers and documenting the release process, code quality standards, etc. |
IMO this should get moved to chef/kitchen-ec2, all the rest of the typical chef devs should get added (i.e. i don't have merge button here), and then we should add @proffalken as an external maintainer. We also need to keep the bureaucracy of adding external maintainers to a minimum. The answer here should probably just be 'yes, here's a commit bit'. Documentation should not block it, and you can just point @proffalken at the way that contributions happen on chef/chef for examples (which mostly boils down to getting 2 +1's from maintainers other than the PR author and keeping the changelog updated). If we think we've got some kind of documentation process that blocks simply saying 'yes' to new external maintainers then that process needs to get burned in a fire since its doing more harm than good. |
Glad to see so much positive attitude around this having worked previously on projects where offers of help were rejected! :) I'll wait to hear back from you about progress, if you have any questions in the mean-time, send me a message and we'll arrange a time to talk. |
Sounds positive! @smurawski when are you back in London next for another steak dinner? :-) Allow some time to come down to Cardiff and you can meet @proffalken F2F with the rest of the DevOpsGuys :-) |
@proffalken if you're still interested in maintenance I can make this happen. Cheers! |
@cheeseplus that would be awesome, thanks. If you can add me, then I'll let the others here at DevOpsGuys know and we'll start to schedule in some time to make this happen :) /cc @TheOpsMgr |
@proffalken you're added as a maintainer - we use the chef RFC contributing guidelines which mostly means 2 x +1 votes from maintainers for merges assuming a lieutenant doesn't veto. @TheOpsMgr I accidentally invited you initially and you're welcome to help maintain if you desire - just didn't want to sign you up unwillingly |
Awesome, thanks @cheeseplus. I was an OpenStack developer in a previous life so I'm happy with the chef way of working :) Closing this bug now. |
💯 👍 |
Hi all,
I've noticed that a number of the issues and pull requests on here (including mine, and yes, this is reasonably selfish!) are waiting for some time before they are addressed by the maintainers.
I'm assuming that this is due to workload elsewhere, so I'd like to offer our services to help out.
DevOps Guys are a consultancy based in South Wales, UK, and we're willing to take on some of the responsibility for testing/merging kitchen-ec2 if the community is happy for us to do so.
We would look to start with triage work and prioritising some of the simpler PRs and Issues such as the following:
Once these are out of the way, we would then look to address other issues on the backlog with the help of the community to ensure that we can continue to use AWS as one of our testing platforms of choice.
If you are happy for us to take part, please let me know and (if at all possible!) please flag this issue up to the package maintainers.
Thanks in advance,
Matt
Matthew Macdonald-Wallace
matthew@devopsguys.com
http://www.devopsguys.com/
http://doics.co/
Twitter: @proffalken
github.com/proffalken
The text was updated successfully, but these errors were encountered: