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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Considering for adoption #20
Comments
Timing this out. It's been a while. |
I will sync-up with Jesse next week and ask him |
Seems like this isn't going anywhere. If you guys could do with any additional dev help, please feel free to reach out. |
Please see https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin for the official adoption process. The Jenkins project mostly uses Jira and mailing lists, so issues reported here will most likely fall through the cracks (especially for busy people like Jesse Glick) |
@TobiX thanks for your comment. The process was followed, I tried to get their attention this way, then gave up. As you said, people are busy and there is not a lot of traction in this plugin. |
Yes, https://groups.google.com/forum/#!searchin/jenkinsci-dev/junit-attachments-plugin%7Csort:date/jenkinsci-dev/YJTPj904ueg/bAxlY_nhDQAJ definitely fell through the cracks. I see some kind of consensus in the thread, but nobody really followed up on the permission transfer. It is somewhat my bad, because I was usually processing transfer requests at that time. We have around 30 active people who can do it (including @jglick), but uh oh. My apologies for it. @pjhampton if you are still interested to take ownership, I can transfer it |
Sounds good @oleg-nenashev |
So, should I transfer it? |
You want to transfer it to my username? Would it not make more sense to keep it in the Jenkins org and give me commit access to the repo? That way I can shepherd it with the help of the Jenkins community. |
No, I think @oleg-nenashev just meant to grant you write & deploy access. |
In that case, yes, please :) |
Done. This is the case when later than never. |
Hey @jglick 馃憢
I'm interesting in adopting this plugin for maintainership as I use it on a hobby project and in a legacy work project. Just a couple of q's before I bring it to the maintainer list:
Does maintainership mean I can choose the direction of the plugin given that it maintains backward compatibility?
Is there an ETA target when fixing bugs?
Why are you putting this up for adoption?
Thanks
p
The text was updated successfully, but these errors were encountered: