Hi notmyfault, I'm about to run the "Adopt a Plugin" process as described here: Adopt a Plugin (jenkins.io).

diabol_jenkins, mrfatstrat, patbos, tommysdk - I'm "pinging" you in GitHub right now. Is it correct that you kind of abandoned the plugin? Please mark it "for adoption" by adding the "adopt-this-plugin" label, at least.

Yes - that’s my intention.

Do you mind linking the GitHub url the repository is currently located at?

Hi notmyfault, the link can be found in the other issue I opened because of the promoted builds plugin (JENKINS-72527) - here again for the sake of completeness: https://github.com/Diabol/delivery-pipeline-plugin

Thanks, do you have permission to transfer the original repository? I'll send you an invitation, just let me know the GitHub handle.

Or are you not related to diabol at all?

Hi notmyfault, unfortunately I’m not related to Diabol at all, so I need to wait for their approval, according to the guidelines of how to adopt a plugin. 

Oh, I wasn't aware of that, but no worries. The plugin has had no release in ~4 years. We will consider it abandoned.

For abandoned plugins, you don't need the existing/original maintainer's approval.

I will take care of the onboarding in the jenkinsci organization, if you file a PR modifying https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-delivery-pipeline-plugin.yml adding the username(s) of the account(s) created on https://accounts.jenkins.io/, which should have release permission. E.g. "rzanner" (and others) in your case. Make sure everyone logged into Jira and https://repo.jenkins-ci.org/.

Ensure to fill out the PR template too, so I can invite the people you wish to grant commit permission to.

Don't hesitate to throw me a ping on GH too

Hi notmyfault, I modified the plugin-delivery-pipeline-plugin.yml file in my fork of the RPU, adding my (rzanner) and gsoffredini's (gsoffredini) handles. I left the others untouched - or should I remove them?

I'm about to file a PR - what "PR template" you're talking about should I use?

Another question: does it make sense to also change the "groupId" of the plugin to "org/jenkins-ci/plugins" (and path in the permissions YAML file?), since it will be hosted in the jenkinsci github?

The versioning scheme will change anyway, as I understand it.

Also, I need to send a mail to the jenkinsci-dev mailing list, correct?

> or should I remove them?

Feel free to remove them. We generally don't keep maintainers listed who moved on. If they choose to return, they can add themselves again, of course.

> I'm about to file a PR - what "PR template" you're talking about should I use?

If you create a PR, it contains a default template where you are supposed to list the GH handles, which is needed in order to invite you to the org.

> does it make sense to also change the "groupId"

No, groupId and artifactId are considered "internal" identifiers for the update center to know about a plugin and serve no purpose outside.

> Also, I need to send a mail to the jenkinsci-dev mailing list, correct?

Yes, please.

I'll go ahead and close the issue, further discussion happens in the RPU PR: https://github.com/jenkins-infra/repository-permissions-updater/pull/3792