Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project Status #200

Closed
webratz opened this issue Jun 19, 2020 · 22 comments
Closed

Project Status #200

webratz opened this issue Jun 19, 2020 · 22 comments

Comments

@webratz
Copy link
Contributor

webratz commented Jun 19, 2020

Hey,

this is to give a quick status update on what is up with this plugin and its maintenance:

I've been working on this plugin for a while, mostly due to the fact its used within the setup of my employer and we needed to make some fixes. I'm not having a Java background, so its mostly smaller fixes or getting something just to work.
So most of the time i just try to merge incoming PRs if they don't look horribly wrong.

I'm moving away further from this topic within my company, so the time I can dedicate to this plugin is even less.

In that sense: if there are people that are willing to keep the project healthy and drive it, please reach out to me.

Also see https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/

@webratz webratz pinned this issue Jun 19, 2020
@markjacksonfishing
Copy link
Contributor

I think I also have access to handle and will take over @webratz

@pgarbe
Copy link
Contributor

pgarbe commented Jun 22, 2020

It's probably a good time to officially kick me out too.

@serpentblade
Copy link
Contributor

@webratz,
I'd be interested in taking over support for this plugin. I've reached out to the jenkins dev mailing list, and would be interested in discussing with you further the requirements for the role.

@webratz
Copy link
Contributor Author

webratz commented Oct 22, 2020

@webratz,
I'd be interested in taking over support for this plugin. I've reached out to the jenkins dev mailing list, and would be interested in discussing with you further the requirements for the role.

didn't see anything on the mailing lists. feel free to reach out there to gain access

@jayeshmurli
Copy link

@webratz I would also like to contribute to maintain this plugin. This plugin is extensively being used by my employer and I would like to help it keep up-to-date. Could you please grant me the permissions for it.

@jeremymcgee73
Copy link

@jayeshmurli I believe you need to email the mailing list. Here is the link!

@jayeshmurli
Copy link

@jayeshmurli I believe you need to email the mailing list. Here is the link!

somehow my email to the mailing group is never delivered to the queue. I get a bounce back email stating I dont have permissions to send email to the specified group. Am I missing something here ? 🤔

@jayeshmurli
Copy link

@jeremymcgee73 @webratz I am interested in supporting this plugin. I have tried sending out an email to the Jenkins Dev Email list, but the email delivery does not succeed. Can someone let me know if I am doing something wrong here ?

@webratz
Copy link
Contributor Author

webratz commented Nov 18, 2020

Hey, i think you need to join the mailinglist first. It also works via a web interface at https://groups.google.com/g/jenkinsci-dev

@oleg-nenashev
Copy link
Member

FTR https://groups.google.com/g/jenkinsci-dev/c/z0Ia_aMsrwc/m/zkqWfIDeAgAJ for the adoption request

P.S: Thanks a lot to @webratz for maintaining this plugin, and for properly announcing it adoption! Great to see that others can step up and keep evolving this plugin.

@FnTm
Copy link

FnTm commented Jan 25, 2021

@oleg-nenashev I'm not sure who actually processes the maintainer addition requests, but would you think there'd be any way in moving the process in the aforementioned Google Groups thread along?
The Stalebot in this Repo is closing valid feature requests and PRs left and right. We're depending quite heavily on this plugin for our Jenkins setup and would really have wanted to use some of the additions those PR's would have given us.

@stale
Copy link

stale bot commented May 28, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label May 28, 2021
@webratz
Copy link
Contributor Author

webratz commented May 31, 2021

let's keep this open

@stale stale bot removed the stale label May 31, 2021
@carlosrodf
Copy link
Contributor

I'm also interested in maintaining this plugin but the email i sent to the dev mailing list is not being delivered.
if someone knows please let me know how to proceed 👍

@pgarbe
Copy link
Contributor

pgarbe commented Jun 30, 2021

@carlosrodf as far as I know the permissions are managed here: https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-amazon-ecs.yml
Maybe it helps if you send them a pull request.

@gowthamshankar99
Copy link

I m also interested in maintaining this plugin. not sure how to proceed .

@Stericson
Copy link
Contributor

@webratz Hello, I'm also interested in adopting / helping to maintain this plugin. I've already submitted a request for Maintainer access and will submit a PR to the permissions repository shortly.

@webratz
Copy link
Contributor Author

webratz commented Jan 10, 2022

@webratz Hello, I'm also interested in adopting / helping to maintain this plugin. I've already submitted a request for Maintainer access and will submit a PR to the permissions repository shortly.

i guess all done at jenkins-infra/repository-permissions-updater#2312 or anything missing?

@Stericson
Copy link
Contributor

Stericson commented Jan 10, 2022

Should be once someone approves and merges it. I also assume they'd grant the Github Repo permissions.

Thanks for signing off on the request and for helping to build such a useful plugin 👍

@neirbowj
Copy link

neirbowj commented Mar 1, 2022

Multiple people have expressed interest in adopting this plugin, and reported problems following the published process of engaging on the mailing list. After roughly a year and a half, it seems like maybe the established process needs some attention and adjustment before it will achieve the desired result. I haven't found a way to escalate. Is there a next-step in the process that I am missing?

@Stericson
Copy link
Contributor

@neirbowj I followed this process -- https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/

It was pretty straightforward. I was added as a maintainer and I've done a few releases since then. A number of folks on this issue also went through this process and also became maintainers at some point.

My PR here has quite a bit of information related to my request if it helps.

@ugurkany
Copy link
Contributor

Hey Guys, I would like to remove the adoption status of the plugin if it is okay for you. I will remove it this Saturday if there is no objection. Also, @webratz Thank you for maintaining this plugin. @Stericson is actively maintaining this plugin too. I believe we can take care of this together.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests