On Sunday, March 5, 2023 at 9:00:20 AM UTC-7 iamagui wrote:
Hi all, I am very new to Jenkins and came across that ' https://plugins.jenkins.io/cvs/' is up for adoption. If possible, could you please let me know the duties and responsibility of a plugin maintainer to see whether l can able to perform the tasks and able to adopt it. Pardon me if asking this already disqualify me for being a maintainer. Thanks in advance. Thanks for your interest and thanks for a great question. I think that our documented answer(s) are missing key information. I'll point to the documentation that I've found and then offer my opinions as a plugin maintainer. *Documentation that I've found:* https://www.jenkins.io/project/governance/#helping-and-taking-over-dormant-plugins provides a few sentence overview that encourages plugin adoption, but it does not outline specific duties of a plugin maintainer. https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/#faq includes text that says: Once you’ve chosen a plugin, review the documentation on plugin maintainership in the Jenkins project. This is especially important if you’re not currently a plugin developer. Unfortunately, the "documentation on plugin maintainership" phrase is not a link and I don't find a specific single document that I would call the "documentation on plugin maintainership". I think we should create that page and I will attempt to make this post be a rough draft of the things that I think should be described there. *My opinions as a plugin maintainer:* I believe there are multiple levels of involvement and a plugin maintainer helps users if they engage in *any* of those levels. They may not be able to engage in all of them, but *any* of them are already a help to Jenkins users 1. Test and release new versions of the plugin (either manually <https://www.jenkins.io/doc/developer/publishing/releasing-manually/> or automatically <https://www.jenkins.io/doc/developer/publishing/releasing-cd/>) when valuable and relevant changes have been made to the plugin 2. Modernize the plugin (see the "Improve a plugin" tutorial <https://www.jenkins.io/doc/developer/tutorial-improve/> for guidance and the "Contributing to open source" document <https://docs.google.com/document/d/1PKYIpPlRVGsBqrz0Ob1Cv3cefOZ5j2xtGZdWs27kLuw/edit?usp=sharing> for other ideas) and release a version with the modernizations 3. Review, approve, and merge dependency update pull requests (usually from Dependabot), releasing new versions when those updates include important changes 4. Respond to plugin security issues when the security team shares issues (see the security guide for maintainers <https://www.jenkins.io/security/for-maintainers/>) 5. Respond to new issue reports 6. Review existing <https://issues.jenkins.io/issues/?jql=resolution%20is%20EMPTY%20and%20component%3D15486>(CVS plugin) <https://issues.jenkins.io/issues/?jql=resolution%20is%20EMPTY%20and%20component%3D15486>issue reports 7. Fix issues 8. Review existing (CVS plugin) pull requests <https://github.com/jenkinsci/cvs-plugin/pulls> and provide feedback to the submitters on those pull requests 9. Implement enhancements If all a new maintainer can do is test and release new versions of the plugin, they've helped users by delivering updates. If they can also modernize the plugin and release a new version, they've also helped users and reduced their future work as a maintainer. If they can also review existing issue reports, that's even more that they have helped users. Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/696ea726-438c-4095-ad00-8fb3e7d65768n%40googlegroups.com.
