Draft JEP: Jenkins Ambassador Program

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Draft JEP: Jenkins Ambassador Program

Alyssa Tong-2
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.


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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAC9wNawtidk2tN24fxdYf%3DZoi3wO-8wz6VM%2BorhuFyR05sS5JA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Draft JEP: Jenkins Ambassador Program

Oleg Nenashev
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: <a rel="nofollow" href="https://github.com/jenkinsci/jep/pull/100" style="color:rgb(53,114,176);text-decoration:none;font-family:&quot;Helvetica Neue&quot;,Helvetica,Arial,sans-serif;font-size:14px" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjep%2Fpull%2F100\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNELRHAGZd2HgJNnbmBa45nRaGpssQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjep%2Fpull%2F100\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNELRHAGZd2HgJNnbmBa45nRaGpssQ&#39;;return true;">https://github.com/jenkinsci/jep/pull/100
JEP:  <a rel="nofollow" href="https://github.com/bitwiseman/jep/blob/jenkins-ambassador/jep/0000/README.adoc" style="color:rgb(53,114,176);text-decoration:none;font-family:&quot;Helvetica Neue&quot;,Helvetica,Arial,sans-serif;font-size:14px" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fbitwiseman%2Fjep%2Fblob%2Fjenkins-ambassador%2Fjep%2F0000%2FREADME.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFYAsKRxsePWOwXRFp2g3_tus2_Yg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fbitwiseman%2Fjep%2Fblob%2Fjenkins-ambassador%2Fjep%2F0000%2FREADME.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFYAsKRxsePWOwXRFp2g3_tus2_Yg&#39;;return true;">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 [hidden email].
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.
Reply | Threaded
Open this post in threaded view
|

Re: Draft JEP: Jenkins Ambassador Program

Alyssa Tong-2
great point Oleg, we'll be sure to include appropriate verbiage 

On Sat, May 5, 2018 at 5:22 AM, Oleg Nenashev <[hidden email]> wrote:
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.


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 [hidden email].
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.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAC9wNaxWYfcUZuYyypD4OukKs-Mg-%2BQ2WY%3DJW78_UNBEN1x1aQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Draft JEP: Jenkins Ambassador Program

Oleg Nenashev
Hi all,

Just to provide an update, JEP has been accepted **as a draft**, and now it is known as JEP-5.

In addition to the major concern above, I am reposting my other comments here:
  • comment - JEP Proposal mentions people who may cast votes in addition to Jenkins Ambassadors. Since "Jenkins Ambassador" is proposed as a sponsored community program, IMHO the proposal should mention community roles instead of people. E.g. "Board members and Jenkins officers" or so.
    • Since the project grows and changes, people may move to different roles or leave the project. It would render JEP obsolete.
    • On the other hand, having more explicit benefits to Officers/Board members may encourage contributors to apply to these positions so that we could do some rotation in roles and make the community more diversified
  • comment - "Staff Ask the Expert booth @ Jenkins World" is mentioned as a Benefit. IMHO it should be rather a kind of responsibility and cover other events. Actually, "responsibilities" is the section I would propose to add, because I would also expect Ambassadors to contribute to blog-posts and/or to other community events
  • comment - It is not clear which certifications are offered is benefits

Liam has listed these topics in Open Questions section in the JEP, and IMHO it worth discussing them.


Best regards,
Oleg

On Monday, May 7, 2018 at 4:25:51 PM UTC+2, alytong13 wrote:
great point Oleg, we'll be sure to include appropriate verbiage 

On Sat, May 5, 2018 at 5:22 AM, Oleg Nenashev <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="7PeYADlZBgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">o.v.ne...@...> wrote:
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: <a rel="nofollow" href="https://github.com/jenkinsci/jep/pull/100" style="color:rgb(53,114,176);text-decoration:none;font-family:&quot;Helvetica Neue&quot;,Helvetica,Arial,sans-serif;font-size:14px" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjep%2Fpull%2F100\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNELRHAGZd2HgJNnbmBa45nRaGpssQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjep%2Fpull%2F100\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNELRHAGZd2HgJNnbmBa45nRaGpssQ&#39;;return true;">https://github.com/jenkinsci/jep/pull/100
JEP:  <a rel="nofollow" href="https://github.com/bitwiseman/jep/blob/jenkins-ambassador/jep/0000/README.adoc" style="color:rgb(53,114,176);text-decoration:none;font-family:&quot;Helvetica Neue&quot;,Helvetica,Arial,sans-serif;font-size:14px" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fbitwiseman%2Fjep%2Fblob%2Fjenkins-ambassador%2Fjep%2F0000%2FREADME.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFYAsKRxsePWOwXRFp2g3_tus2_Yg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fbitwiseman%2Fjep%2Fblob%2Fjenkins-ambassador%2Fjep%2F0000%2FREADME.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFYAsKRxsePWOwXRFp2g3_tus2_Yg&#39;;return true;">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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="7PeYADlZBgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/4f99131e-82ac-4c98-b23b-45093f2fff82%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/4f99131e-82ac-4c98-b23b-45093f2fff82%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/4f99131e-82ac-4c98-b23b-45093f2fff82%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/4f99131e-82ac-4c98-b23b-45093f2fff82%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b9fff225-d4b3-4a02-a872-09a53ab56045%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.