Add identified maintainers for stapler.

[jeffret-b]

Description

It looks like stapler has been added into the repository permissions updater but doesn't have anyone registered as maintainer. We need people identified to merge and release it. I'm not sure if something additional needs to be done for us to have permissions to merge and deploy.

https://github.com/stapler/stapler/

@jglick, do you want to be added here? As a "recent maintainer" do you approve this PR?

@daniel-beck, confirm you want to be added.

My GH user is "jeffret-b" but on jenkins.io it is "jthompson".

Submitter checklist for changing permissions

Always

• Add link to plugin/component Git repository in description above

For a newly hosted plugin only

• [n/a] Add link to resolved HOSTING issue in description above

For a new permissions file only

• [n/a] Make sure the file is created in permissions/ directory
• [n/a] artifactId (pom.xml) is used for name (permissions YAML file).
• [n/a] groupId / artifactId (pom.xml) are correctly represented in path (permissions YAML file)
• [n/a] Check that the file is named plugin-${artifactId}.yml for plugins

When adding new uploaders (this includes newly created permissions files)

• Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
• Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
• Make sure to @mention the users being added so their GitHub account names are known if they require GitHub merge access (see below).
• All newly added users have logged in to Artifactory at least once

Maintainer checklist (not for requesters!)

• Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
• 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.
  There are IRC Bot commands for it

[jglick]

Note that these files are likely unused, since Stapler is (for now anyway) deployed to OSSRH not Artifactory.

[daniel-beck]

Looks like https://github.com/kohsuke/pom/blob/05af862f5682677cde4d7146affe2d28d2198c97/pom.xml#L84-L94 (hidden in the parent POM) does it, and https://github.com/stapler/stapler/blob/81f51ffa3899dc27b4f400fc928f8c5b85ae6774/pom.xml#L44-L57 is effectively unused. The latter confused me.

Probably safe to close this now.