Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Clarify that one of two ways mark a plugin for adoption #7555

Merged
merged 1 commit into from
Sep 28, 2024
Merged

Clarify that one of two ways mark a plugin for adoption #7555

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions content/doc/developer/plugin-governance/adopt-a-plugin.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,10 +124,13 @@ Before marking a plugin for adoption,
we recommend to announce the incoming change in the link:https://groups.google.com/g/jenkinsci-dev[Jenkins Developer Mailing list] or in other appropriate channels.
It may help you find new maintainers and, ideally, to establish a transition and knowledge transfer process.

. Add the `+adopt-this-plugin+` label to the plugin. It can be done in 2 ways:
. Add the `+adopt-this-plugin+` label to the plugin. A plugin is marked for adoption in one of two ways:
** Put an `+adopt-this-plugin+` topic in the plugin's GitHub repository.
If you have multiple plugins inside a single repository, it will apply to all of them
If multiple plugins are maintained inside a single repository, the repository topic marks all of them for adoption.
This is the preferred method because the maintainer directly controls the topics assigned to the plugin repository
** Add an `+adopt-this-plugin+` label to the plugin entry in the Update Center's link:https://github.com/jenkins-infra/update-center2/blob/master/resources/label-definitions.properties[label-definitions.properties] file
If multiple plugins are maintained inside a single repository, an update center entry can mark a subset of the plugins for adoption.
This is not the preferred method because the maintainer does not directly control the Update Center file
. Optional: If you want to explain why you're marking that plugin as up for adoption,
add a section to the plugin's documentation.
You can also document your vision for the plugin there so that new maintainers can take it into account.
Expand Down