permissions/plugin-vsphere-cloud.yml: request maintainership

[jimklimov]

Adding "jimklimov" as co-maintainer: Want to merge a few outstanding pull requests...

Last non-dependency changes cca 2023, some PRs are in review limbo since 2019 (mine since 2024).

In fact, @pjdarton commented in jenkinsci/vsphere-cloud-plugin#137 (comment) that the plugin is up for adoption as there is no deployed platform on his side to test it anymore. At least I have access to one, which is used from Jenkins.

I think @jswager and @jswager1 can be removed from the list, there was no github activity in half a decade, and pom.xml already lists him as "maintainer (retired)".

CD streamlining PRs not proposed yet, so not filling that part of the questionnaire. Hope to enable it later.

Link to GitHub repository

https://github.com/jenkinsci/vsphere-cloud-plugin/

When modifying release permission

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

• @jimklimov

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.

[pjdarton]

I'm happy that someone wants to take it over.