Request to be made a maintainer for https://github.com/jenkinsci/fortify-on-demand-uploader-plugin

[Konstantin Voin]

Hello,

Need help with adding a new maintainer for https://github.com/jenkinsci/fortify-on-demand-uploader-plugin. Unfortunately, current 3 maintainers are no longer with our company. We can get help from one of them but he doesn't remember the password. The work email associated with the account is no longer active to be able to reset the password.

·         Link to a plugin  - https://github.com/jenkinsci/fortify-on-demand-uploader-plugin

·         Link(s) to pull requests you want to deliver, if applicable -  Not Applicable

·         Your GitHub username/id  – makropod for https://github.com/makropod

Please help.

Thanks!

Konstantin Voin

[Mark Waite]

On Fri, Nov 19, 2021 at 2:00 PM Konstantin Voin wrote:

Hello,

Need help with adding a new maintainer for https://github.com/jenkinsci/fortify-on-demand-uploader-plugin. Unfortunately, current 3 maintainers are no longer with our company. We can get help from one of them but he doesn't remember the password. The work email associated with the account is no longer active to be able to reset the password.

One of the three maintainers has a non-microfocus email address. I've included that maintainer on a blind carbon copy of this email message in hopes they will reply with "approved to add a maintainer".

I've also blind carbon copied the microfocus addresses of the other two maintainers in case one of them is still available to receive email at that address.

If that doesn't work, then we'll need to follow the "adopt a plugin" process of allowing a timeout period before you're allowed to adopt the plugin.

Mark Waite

·         Link to a plugin  - https://github.com/jenkinsci/fortify-on-demand-uploader-plugin

·         Link(s) to pull requests you want to deliver, if applicable -  Not Applicable

·         Your GitHub username/id  – makropod for https://github.com/makropod

Please help.

Thanks!

Konstantin Voin

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c3e04f2e-c279-477d-8652-1bbde2a11632n%40googlegroups.com.

[Konstantin Voin]

Hello Mark,

Following up after 2+ weeks. Have you heard back from any maintainers? If not, can you start a process to transition the ownership to me?

Thanks!

[Mark Waite]

On Monday, December 6, 2021 at 7:36:36 AM UTC-7 Konstantin Voin wrote:

Hello Mark,

Following up after 2+ weeks. Have you heard back from any maintainers? If not, can you start a process to transition the ownership to me?

No reply from any of the maintainers.  The "Adopt a plugin" process  indicates that you should request commit access (done in this thread), then wait the two weeks (done), and you can be granted commit privileges on the repository.  To release a new version of the plugin, you need to submit a pull request to the repository pernissions updater repository configuration file to add your jenkins.io account as one of the maintainers.

I believe that the hosting team (Gavin Mogan, currently a team of 1) and others have permission to grant commit access.

Mark Waite

[Konstantin Voin]

Hello Mark,

I created a PR but as it turned out I needed to have a JIRA access in order for PR to complete. Can someone kick the build again, since I don't have access to do that?

Thanks!

[Mark Waite]

On Tuesday, December 7, 2021 at 4:05:01 PM UTC-7 Konstantin Voin wrote:

Hello Mark,

I created a PR but as it turned out I needed to have a JIRA access in order for PR to complete. Can someone kick the build again, since I don't have access to do that?

I've restarted the CI job but it reports that you need still need to login to:

• https://issues.jenkins.io 
• https://repo.jenkins-ci.org 

Those systems use a "lazy" process to create user accounts only after the user has been authenticated.  It avoids creating 100 000+ artifact repository accounts when a much, much smaller number of users need artifact repository accounts.

Could you login to each of those locations?

Mark Waite

[Jean-Marc Meessen]

Just adding a little detail to Mark's observation: once successfully logged into the various systems (in particular Artifactory), you need to wait for about an hour so that the hourly batch processes can update the needed information. I got bitten by that during my first plugin adoption.

/- Jmm

--

You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/cb377c49-a836-4437-a35e-c374f6beb807n%40googlegroups.com.

[Konstantin Voin]

Looks like I'm in. What do I need to request in order to maintain members of the plugin team ?

[Gavin Mogan]

Teams can only have org members in it. So for now you'll have to request one of us (usually timja or myself) to add people to the team. Tim added the list of users you specified, so once they accept the org invite they'll be in the team.

if you want to add any existing org members (like myself) you already have maintainer access.

I do want to eventually come back to my proposal to have team membership in RPU, but its been put on hold for a bit while I fix other things.

Gavin

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/36ff3fae-5943-41fc-bc87-62aaad5956a7n%40googlegroups.com.

[Konstantin Voin]

Thanks Gavin. How about removing users? Ask one of you?

[Gavin Mogan]

your marked as maintainer of the team so you should be able to remove whomever you want. I can't remember what gives admin access to the repo, but I think you have access to outside contributors section too, but I personally recommend team over that.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/af688312-6d17-4646-8010-4ec7565ad705n%40googlegroups.com.

[Daniel Beck]

Repo admins (the default for maintainers now) can add/remove external collaborators (a reason we have so many).

Team maintainers can add/remove team members.

[Jean-Marc Meessen]

Hello Konstantin,

Thank you for adopting this plugin.

I am working with Mark Waites and a couple of others on various initiatives to improve the contributors and maintainers experience (especially newcomers).

It is in that context that I believe that it would be great if we could we discuss your experience by mail of even is a short call (if time zones are favorable). I'd like to know things, among others, like:

• was the adoption successful?
• what were the friction points? 
• Did you get (or needed) help? In what form? 
• what were your motives for adoption?
• what is your previous experience as Jenkins/OSS contributor and in java dev?
• ....

If interested to share your experience, you can contact me at jean...@meessen-web.org.

/- Jmm

Jean-Marc Meessen

Brussels, Belgium

[Alberto Bec]

Hi all, I was part of this request to be added to the repo. Konstantin doesn't see me in the org to give me permissions, turns out I missed the GitHub invitation email to accept being added to the org. Can that be resent?

Thanks

[Daniel Beck]

On Thu, Jan 20, 2022 at 4:51 AM Alberto Bec <qba...@gmail.com> wrote:

Hi all, I was part of this request to be added to the repo. Konstantin doesn't see me in the org to give me permissions, turns out I missed the GitHub invitation email to accept being added to the org. Can that be resent?

 

Done

[Alberto Bec]

Got it. Thank you very much