Hi folks, The vsphere-cloud plugin has a number of outstanding PRs, some of them from early this year. The only plugin owner with commit access (Jason) no longer has the time/resources to continue working on the plugin (or access to the resources required to test it) and is on record saying that he would like someone else to take over (https://groups.google.com/d/msg/jenkinsci-dev/gowLQQXBUec/CgGZ-hQvBQAJ). I was discussing a takeover with the other plugin maintainer (Eric, who does not have commit access at present) when Jason said he was trying to hand over commit-access to us (https://github.com/jenkinsci/vsphere-cloud-plugin/pull/76#issuecomment-313497218) ... but as there's no sign of further activity on that front it would appear that this process has stalled. I would like to get that process (re?)started so we can get this sorted.
I understand (from https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin) that you need github and jenkins-infrastructure IDs to grant people commit access... - My github ID is "pjdarton", and my Jenkins-infrastructure ID is also "pjdarton". - Eric's github ID is "elordahl" and I believe that his Jenkins-infrastructure ID is the same (https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=elordahl). Please can you grant us both commit-access to the vsphere-cloud plugin? We could then work on clearing the backlog of PRs... Regards, Peter -- 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/4a861d07-741d-4d0e-9667-f4583ec919b7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
