added stefan_spieker as developer

[StefanSpieker]

Description

I would like to adopt the thin-backup-plugin. Which is up for adoption. The maintainer seems to be @tofuatjava since he merged an old PR of mine a few weeks ago.
https://github.com/jenkinsci/thin-backup-plugin

I logged in to Jira sucessfully, but got an error for artifactory:

Login has failed. Due to Incorrect username/password or locked user.

Submitter checklist for adding or changing permissions

Always

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

For a newly hosted plugin only

• Add link to resolved HOSTING issue in description above

For a new permissions file only

• Make sure the file is created in permissions/ directory
• artifactId (pom.xml) is used for name (permissions YAML file).
• groupId / artifactId (pom.xml) are correctly represented in path (permissions YAML file)
• 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

Reviewer 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.
• 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

[timja]

cc @tofuatjava do you approve this?

[tofuatjava]

I always welcome work power and fresh ideas, but as always I want to ensure that the basic idea of Matthias and my - building a efficient backup tool which only backups what needed and not more - will be also be the vision for all new ideas. I started a "remake" on a branch several years ago. To be honest I do not have the time to do it alone...

[timja]

to be clear do you approve this or not?

[StefanSpieker]

I do not intend to change the plugin purpose. I think it is a quite useful plugin, which just needs some refreshing.

[tofuatjava]

YES, I approve. Sorry if I was not clear in my last statement.

[timja]

@StefanSpieker it won't work unless you manage to login to Artifactory.

If you are able to login to Jira with the same username and password but not artifactory can you please raise a helpdesk ticket at: https://github.com/jenkins-infra/helpdesk/issues/new/choose

[StefanSpieker]

@timja Ok, finally logged into artifactory. Used the wrong password. So now I successfully signed in.