Add markewaite as maintainer of 3 plugins

[MarkEWaite]

Add markewaite as maintainer of 3 plugins

I've included these changes in a single pull request because they can all be approved by @basil. If he doesn't approve them, I'm willing to wait the 2 weeks for the adoption request to be approved.

Add markewaite as a timestamper plugin maintainer

Pull request to be merged:

• Test with Java 25 jenkinsci/timestamper-plugin#394

Current maintainers that can approve my addition:

• @basil
• @StevenGBrown

Add markewaite as a maintainer of throttle-concurrent-builds plugin

Pull request to merge:

• Test with Java 25 jenkinsci/throttle-concurrent-builds-plugin#339

Current maintainers that can approve the addition:

• @abayer
• @basil
• @oleg-nenashev

Add markewaite as a text-finder plugin maintainer

Pull request to be merged:

• Test with Java 25 jenkinsci/text-finder-plugin#295

Current maintainers that can approve the addition:

• @basil
• @jglick

Link to GitHub repository

• https://github.com/jenkinsci/text-finder-plugin
• https://github.com/jenkinsci/throttle-concurrent-builds-plugin
• https://github.com/jenkinsci/timestamper-plugin

When modifying release permission

List the GitHub usernames of the users who should have commit permissions below:

• @MarkEWaite

This is needed in order to cut releases of the plugin or component.

If you are modifying the release permission of your plugin or component, fill out the following checklist:

Release permission checklist (for submitters)

• The usernames of the users added to the "developers" section in the .yml file are the same the users use to log in to accounts.jenkins.io.
• All users added have logged in to Artifactory and Jira once.
• I have mentioned an existing team member of the plugin or component team to approve this request.

When enabling automated releases (cd: true)

Follow the documentation to ensure, your pull request is set up properly. Don't merge it yet.
In case of changes requested by the hosting team, an open PR facilitates future reviews, without derailing work across multiple PRs.

Link to the PR enabling CD in your plugin

CD checklist (for submitters)

• I have provided a link to the pull request in my plugin, which enables CD according to the documentation.

Reviewer checklist

• Check that the $pluginId Developers team has Admin permissions while granting the access.
• In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
• If security contacts are changed (this includes add/remove), ping the security officer (currently @Wadeck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it.

[oleg-nenashev]

Approved

[jglick]

I am not even sure what the text-finder plugin is, or why I might have been marked as a maintainer.

[MarkEWaite]

I am not even sure what the text-finder plugin is, or why I might have been marked as a maintainer.

You became a maintainer of that plugin in 2016 with commit a673619 , the initial upload of permissions.

[jglick]

jenkinsci/text-finder-plugin#12 (comment) and seven years after that I certainly have no idea. Consider it abandoned, whatever it is.