Hi Marky, I have restored the team and granted it Write permissions. Due to whatever reason, the team was just disconnected from the repo. AFAICT, our ChatOps bot also needs update to fix group permission assignments. Now it sets "Read" instead of "Write" upon creation.
As I sent in a few private messages in Gitter, any help is greatly > appreciated > Thanks for pinging people in PM in this case. Usage of mailing lists is highly recommended, but I understand that there is a lack of response here. W.r.t. myself (I also received a ping), I am not available to handle ownership transfer requests on a regular basis. See my message in this thread <https://groups.google.com/d/msg/jenkinsci-dev/uc6NsMoCFQI/AIO4WG1UCwAJ>: "Ownership transfer and adoption requests are still managed via developer mailing list requests, I’ve been handling some of them. Anybody with #jenkins voice permissions can handle such requests (20+ contributors), so I am not a bottleneck here". Although I really want to help Jenkins contributors with the ownership management topics, I have to prioritize. Sorry if it causes any inconvenience. Best regards, Oleg On Sunday, January 20, 2019 at 11:41:11 PM UTC+1, [email protected] wrote: > > :-( man I am so frustrated. > As I sent in a few private messages in Gitter, any help is greatly > appreciated > I pay in beer, burritos or other San Francisco funs during the next > Jenkins World. > I am just trying to chop wood and carry water > > On Sunday, January 20, 2019 at 12:44:05 PM UTC-8, Marky Jackson wrote: >> >> It appears the admin team has disappeared >> >> { >> "regards" : { >> "name" : “marky”, >> "phone" : "+1 (408) 464 2965”, >> "email" : “[email protected] <javascript:>", >> "team" : "jackson5“ >> } >> } >> >> On Jan 20, 2019, at 12:05 PM, Baptiste Mathus <[email protected] >> <javascript:>> wrote: >> >> Done! You should have received an invitation. Welcome aboard! >> >> [21:03] <+ batmat> | jenkins-admin: make jequals5 committer of >> groovy-events-listener-plugin >> [21:03] <@jenkins-adm> | Failed to add user to team: {"message":"Not >> Found","documentation_url":" >> https://developer.github.com/v3/users/#get-a-single-user"} >> [21:04] <+ batmat> | jenkins-admin: make markyjackson-taulia >> committer of groovy-events-listener-plugin >> [21:04] <@jenkins-adm> | Added markyjackson-taulia as a GitHub committer >> for repository groovy-events-listener-plugin >> [21:05] <+ batmat> | jenkins-admin: make jequals5 the lead of >> groovy-events-listener-plugin >> [21:05] <@jenkins-adm> | Changing default assignee of subcomponent >> groovy-events-listener-plugin to jequals5 >> [21:05] <@jenkins-adm> | Default assignee set to jequals5 >> >> Le dim. 20 janv. 2019 à 21:03, Baptiste Mathus <[email protected] >> <javascript:>> a écrit : >> >>> Sorry for the lack of answers here. >>> >>> I'm going to proceed here, because of the latency, despite you missed a >>> critical step AFAICT in our process >>> https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess >>> >>> : >>> putting the previous maintainer(s) in CC... >>> >>> >>> >>> Le dim. 20 janv. 2019 à 02:44, <[email protected] <javascript:>> a >>> écrit : >>> >>>> Are we not working on adoption of plugins any longer? I know there are >>>> some upcoming changes and that could be the reason but in any case, a >>>> reply >>>> to some effect would really be a good thing. >>>> As we work to get wider outreach I feel it would be good to not let >>>> things sit for long periods of time unanswered and I know this is open >>>> source and there is no SLA but is there something I can help with to >>>> address these type of items in a more timely manner? >>>> Looking to help in any way possible. Not only with adopting this plugin >>>> but also in the wider way to help the team. >>>> Thanks kindly in advance. >>>> >>>> On Tuesday, January 15, 2019 at 8:39:36 PM UTC-8, [email protected] >>>> wrote: >>>>> >>>>> I wanted to circle back on this request. >>>>> >>>> -- >>>> 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 [email protected] <javascript:>. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/4a100fe4-4ef0-4745-9a1f-d95a735a74ff%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/4a100fe4-4ef0-4745-9a1f-d95a735a74ff%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >> 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 [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS78ExCAbC0o3FYr1_z6BZD5XSKrqjQHX-4V1kRxeaQEPw%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS78ExCAbC0o3FYr1_z6BZD5XSKrqjQHX-4V1kRxeaQEPw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> >> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/02f77e78-2e55-47c9-ad0b-2abf14f4f15f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
