Hi Alyssa and Liam, Thanks for finalizing it! Commented in the JEP && duplicating it here. Generally it looks good as a draft, but I have concerns about the process. It covers the SUCCESS path well, but taking the target number of ambassadors (20) it's important to take other scenarios into account to make the program more robust.
The election process seems to be bogus by design, because any existing Ambassador may block the election process during his term if he goes rival. There should be a process for overriding votes or terminating membership in the case of such actions . IMHO it should be also explicit that Jenkins Ambassadors are expected to follow Code of Conduct and that their membership may be terminated by Jenkins board in the case of serious violation. Without that the program proposal seems to be unstable. BR, Oleg On Friday, May 4, 2018 at 12:36:29 AM UTC+2, alytong13 wrote: > > Hello, > > A year or so ago I attempted to initiate the Jenkins Ambassador program. > Due to lack of resources the program was put on the backburner. Now, with > additional resources, we are able to give this another try. > > With that said, Liam has kindly written up the pull request and the > initial draft of the JEP. I think it's straightforward however there's > always room for improvement - if you have feedback pls do share. > > PR: https://github.com/jenkinsci/jep/pull/100 > JEP: > https://github.com/bitwiseman/jep/blob/jenkins-ambassador/jep/0000/README.adoc > > Thank you, > Liam and Alyssa > > -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4f99131e-82ac-4c98-b23b-45093f2fff82%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
