-
Notifications
You must be signed in to change notification settings - Fork 64
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
ansible-xml needs new care takers #16
Comments
@cmprescott, I understand from your comment in issue #12 that you're definitely interested in taking ownership of this project. No contest from me; I can't commit at this time to any regular maintenance. |
I'd love to take it over with the ultimate goal of getting it merged into ansible-modules-extras. I'm in a position where I'd have a few hours a week to devote to the project. I'd be happy to share the responsibilities with anyone else who would like it though. Thanks, |
Well that was easy @cmprescott I'm going to transfer ownership over to you now. |
GitHub told me I can only transfer from an org to myself at this time. I am doing that now.
Once that is complete I'll try transferring to @cmprescott again. You will receive an email from GitHub allowing you to accept to decline the transfer. Additional information about transfers is available on this page: https://help.github.com/articles/transferring-a-repository/ |
@cmprescott done
|
I see that the move was successful. Nice. |
Ping to relevant contributors:
Thanks to everyone for showing their interest in this module! The response we've gotten since we first published the (very rough and very incomplete) first version has been more than I ever anticipated.
Sadly, the original maintainers no longer have the time required to give this project the attention it now requires. The time has come for this module to find new care takers who can give it the care it requires. Therefore @RHInception has decided that we are officially end-of-life'ing this project.
From reviewing the most recent comments on the issue tracker, it seems that @Lx and @cmprescott have expressed the most interest in taking over this project. I do not want to personally dictate the future of this module, rather I'd like to create a proper venue (this issue) for arranging a clean hand-over of the project.
Open Pull Requests
All PR's which were open this morning have been merged, de-conflicted, and pushed.
Open Issues
After merging all open PR's I manually closed issue #13 (tilde-expansion in file paths)
The remaining open issues will not be addressed by myself or the rest of the RH Inception team and are left as an exercise to the new future maintainers
Next Steps
I'd love to see a contributor step up and state their intention to officially take over ownership of the project. We want to leave the future of this module in the hands of those who still have the energy required to do the needful.
Once consensus has been reached I'll be happy to arrange to transfer ownership of the project to the new maintainer(s). We will not interfere if a consensus cannot be reached, rather the project will go into read-only mode and refer new users to the forks chart.
?
Any takers? (thoughts?)
The text was updated successfully, but these errors were encountered: