Missing adopt-this-plugin topic on maintainer-less plugins repository

[alecharp]

Hello,

I've been looking at the plugins marked as to be adopted and found that we are missing some. Let me explain, some plugins don't have any developers listed in their permission files and their repository doesn't have the adopt-this-plugin topic. For those, I believe that we should add the adopt-this-plugin topic on the repository, to be fair with users and potentially find new person to maintain the plugin.

Here is the list of plugins I gathered:

• accelerated-build-now-plugin: https://github.com/jenkinsci/accelerated-build-now-plugin
• any-buildstep: https://github.com/jenkinsci/any-buildstep-plugin
• anything-goes-formatter: https://github.com/jenkinsci/anything-goes-formatter-plugin
• backup-interrupt-plugin: https://github.com/jenkinsci/backup-jobs-plugin
• batch-task: https://github.com/jenkinsci/batch-task-plugin
• build-cause-run-condition: https://github.com/jenkinsci/build-cause-run-condition-plugin
• build-keeper-plugin: https://github.com/jenkinsci/build-keeper-plugin
• campfire: https://github.com/jenkinsci/campfire-plugin
• console-tail: https://github.com/jenkinsci/console-tail-plugin
• copy-project-link: https://github.com/jenkinsci/copy-project-link-plugin
• create-fingerprint: https://github.com/jenkinsci/create-fingerprint-plugin
• downstream-buildview: https://github.com/jenkinsci/downstream-buildview-plugin
• downstream-ext: https://github.com/jenkinsci/downstream-ext-plugin
• envfile: https://github.com/jenkinsci/envfile-plugin
• extension-filter: https://github.com/jenkinsci/extension-filter-plugin
• fail-the-build-plugin: https://github.com/jenkinsci/fail-the-build-plugin
• favorite-view: https://github.com/jenkinsci/favorite-view-plugin
• gnat: https://github.com/jenkinsci/gnat-plugin
• hsts-filter-plugin: https://github.com/jenkinsci/hsts-filter-plugin
• javancss: https://github.com/jenkinsci/javancss-plugin
• jqs-monitoring: https://github.com/jenkinsci/jqs-monitoring-plugin
• kpp-management-plugin: https://github.com/jenkinsci/kpp-management-plugin
• mailmap-resolver: https://github.com/jenkinsci/mailmap-resolver-plugin
• nant: https://github.com/jenkinsci/nant-plugin
• openid4java: https://github.com/jenkinsci/openid4java-plugin
• port-allocator: https://github.com/jenkinsci/port-allocator-plugin
• progress-bar-column-plugin: https://github.com/jenkinsci/progress-bar-column-plugin
• project-stats-plugin: https://github.com/jenkinsci/project-stats-plugin
• sbt: https://github.com/jenkinsci/sbt-plugin
• scons: https://github.com/jenkinsci/scons-plugin
• scoring-load-balancer: https://github.com/jenkinsci/scoring-load-balancer-plugin
• script-realm: https://github.com/jenkinsci/script-realm-plugin
• shared-objects: https://github.com/jenkinsci/shared-objects-plugin
• slave-status: https://github.com/jenkinsci/slave-status-plugin
• statusmonitor: https://github.com/jenkinsci/statusmonitor-plugin
• svn-revert-plugin: https://github.com/jenkinsci/svn-revert-plugin
• tattletale-plugin: https://github.com/jenkinsci/tattletale-plugin
• tcl: https://github.com/jenkinsci/tcl-plugin
• template-workflows: https://github.com/jenkinsci/template-workflows-plugin
• testopia: https://github.com/jenkinsci/testopia-plugin
• text-finder-run-condition: https://github.com/jenkinsci/text-finder-run-condition-plugin
• vault-scm-plugin: https://github.com/jenkinsci/vault-scm-plugin
• windows-exe-runner: https://github.com/jenkinsci/windows-exe-runner-plugin

[NotMyFault]

For those, I believe that we should add the adopt-this-plugin topic on the repository, to be fair with users and potentially find new person to maintain the plugin.

If visibility is a concern, the plugin site should display the adoption banner, if the developer list is empty.
Manually (and retrospectively) adding the topic to every repository may address the issue for now, but isn't future-proof.

[alecharp]

Good point.
The banner is coming from the fact that the topic appears in the update-center.

I guess we could tweak the update-center to use the fact that the list is empty to assume the plugin is up for adoption.

[MarkEWaite]

I really like the idea of having the plugins site display the adoption banner if the list of developers is empty. If the update center can be extended to automatically declare that a plugin is up for adoption if its developer list is empty, that sounds great to me.

[alecharp]

If I'm not mistaken, the plugin site uses the labels value of the update-center entry, which are the topics of the GH repository.

Also, the plugin-health-scoring is currently using that labels list to specify of a plugin is up for adoption or not. Having the 'empty developers list means up for adoption' logic on the update center directly would solve the problem everywhere.

[alecharp]

To be fair, I think having the topic on the repository would also be a good addition, as if someone wants to adopt a plugin, that person might browse the adopt-this-plugin filtered list (https://github.com/search?q=topic%3Aadopt-this-plugin+org%3Ajenkinsci+fork%3Atrue&type=repositories) which is on the root page of the jenkinsci organization.

Adding the label on the repositories I listed is not future proof, but this can also be a one time thing as we can update the pull request template on the RPU repository to specify that when removing the last entry of the developers list, that person must add the topic on the repository before we merge the pull request.

[daniel-beck]

I don't think Daniel favors that approach ;)

Fine with me (see jenkins-infra/update-center2#654), but blocked by jenkins-infra/repository-permissions-updater#2911.