Maintenance plans for gradle-helm-plugin
Closed this issue · 4 comments
Hello @tkrullmann 👋
I'd like to understand whether this project will continue to be actively maintained moving forward.
This isn't in the form of any expectation on you, but more so we can best plan whether to submit contributions to this project or move forward with a fork. I saw v2.0.0 published 3 weeks ago, but prior to this, commit activity was around 1-1.5 years ago?
We have various bug fixes and features that we would love to contribute and also want to extend our support, if welcome, to support you on this project if you don't have the time to maintain and respond to community requests.
Most importantly, thank you for all the work you have done on the project to date! 🤝
Hi,
I'm trying to be a bit more active in maintaining this moving forward. That said, my interests have shifted a bit away from Helm, and I'm not using this plugin on any of my active projects. I'm also not keeping up to date on recent k8s or Helm developments as much as I used to. If you'd like to take over, I'll be happy to transfer it to you and/or put up a redirect notice here.
@tkrullmann - thanks for the response, and understood clearly!
- Would you be happy to redirect contributors to our fork?
- Would you archive this repository or simply endorse all future contributions to our fork?
From Gradle's perspective, they won't allow the publication of a plugin if it is a fork, so we'd just need to make it clear to the Gradle Support team, that the new fork is preferred by you?
The fork approach seems better here as there is a little more involved with gaining access to the repository, transferring it, and publishing the plugin under the same Gradle Plugins namespace - thoughts?
I added a closure/redirect notice. Thanks for taking over, and good luck!
Thanks, @tkrullmann 👍