Add timja as a maintainer to commons-lang3-api plugin

[timja]

Description

@nhojpatrick I'd like to help out with this could you approve please?

see some issues:
jenkinsci/commons-lang3-api-plugin#18
jenkinsci/commons-lang3-api-plugin#12

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

[jglick]

(non-voting 👍)

[MarkEWaite]

(non-voting 👍)

[MarkEWaite]

Considering the challenges with https://issues.jenkins.io/browse/JENKINS-69034 and the importance of providing a solution as soon as we can, I recommend that we make an exception for the adoption process and allow that @timja can immediately be added as a plugin maintainer.

[halkeye]

I recommend that we make an exception for the adoption process

I feel like instead of asking the few people on this thread, it should goto dev mailing list for board approval (Since its skipping past the established procedures)

[MarkEWaite]

I recommend that we make an exception for the adoption process

I feel like instead of asking the few people on this thread, it should goto dev mailing list for board approval (Since its skipping past the established procedures)

Request has been posted to the Jenkins developer mailing list.

[daniel-beck]

The easy fix without plugin governance challenges is to remove the ill-advised dependency from configuration-as-code, reverting jenkinsci/configuration-as-code-plugin#1979. It seems unnecessary to go over maintainers' heads while that's an option. While this is the only plugin with the dependency, there's no benefit in conflict prevention anyway, and the PR provides no justification.

[jglick]

FTR that has already been done in jenkinsci/configuration-as-code-plugin#2062 so this can wait for maintainer approval or the standard two-week waiting period.

[timja]

Proceeding