-
Notifications
You must be signed in to change notification settings - Fork 228
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
Comments
I think I also have access to handle and will take over @webratz |
It's probably a good time to officially kick me out too. |
@webratz, |
didn't see anything on the mailing lists. feel free to reach out there to gain access |
@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. |
@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 ? 🤔 |
@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 ? |
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 |
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. |
@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? |
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. |
let's keep this open |
I'm also interested in maintaining this plugin but the email i sent to the dev mailing list is not being delivered. |
@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 |
I m also interested in maintaining this plugin. not sure how to proceed . |
@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? |
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 👍 |
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? |
@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. |
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. |
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/
The text was updated successfully, but these errors were encountered: