Selecting Delegates for the first wave of JEPs

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Selecting Delegates for the first wave of JEPs

Kohsuke Kawaguchi
Administrator
Time to select Delegate for the first wave of JEPs!

JEP-200 is in the area of remoting, which has been primarily maintained by Oleg for years now. As such, I think it makes the natural sense that he continues to act as Delegate in this space. I think JEP-200 is a great change that eliminates not just one vulnerability but a whole class of vulnerability, which is something we'd like to see more of.

JEP-201 is the mission statement for the new configuration-as-code project. As the person who filed JENKINS-31094 and did a few prototypes in this space, I'm really really excited about this. I think this is a much awaited feature by many Jenkins admins, so hats off to Nicolas and Ewelina for pushing this forward. As this is the new area we are opening up, I will be the reviewer of JEP-201 myself. Once it gets accepted, my intention is to have future JEPs in this area presided by Ewelina. 
--
Kohsuke Kawaguchi

--
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/CAN4CQ4wrx6R6J4vbkUWn7NJpsg-UTzdz%3Dy32jY4ZmK1J7AjuTQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Selecting Delegates for the first wave of JEPs

Ewelina Wilkosz
I won't object :)

On Tuesday, December 5, 2017 at 9:01:08 AM UTC+1, Kohsuke Kawaguchi wrote:
Time to select <a href="https://github.com/jenkinsci/jep/tree/master/jep/1#bdfl-delegate" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjep%2Ftree%2Fmaster%2Fjep%2F1%23bdfl-delegate\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHiotq55DdZouP2EjrD7n15wHpu8w&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjep%2Ftree%2Fmaster%2Fjep%2F1%23bdfl-delegate\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHiotq55DdZouP2EjrD7n15wHpu8w&#39;;return true;">Delegate for the first wave of JEPs!

<a href="https://github.com/jenkinsci/jep/tree/master/jep/200" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjep%2Ftree%2Fmaster%2Fjep%2F200\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHsbigIQTmH9tf1dMGrYHGe-YzYiA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjep%2Ftree%2Fmaster%2Fjep%2F200\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHsbigIQTmH9tf1dMGrYHGe-YzYiA&#39;;return true;">JEP-200 is in the area of remoting, which has been primarily maintained by Oleg for years now. As such, I think it makes the natural sense that he continues to act as Delegate in this space. I think JEP-200 is a great change that eliminates not just one vulnerability but a whole class of vulnerability, which is something we'd like to see more of.

<a href="https://github.com/jenkinsci/jep/tree/master/jep/201" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjep%2Ftree%2Fmaster%2Fjep%2F201\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGY4SXfzH1AC5NrtZFCNzdWI_JTlA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjep%2Ftree%2Fmaster%2Fjep%2F201\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGY4SXfzH1AC5NrtZFCNzdWI_JTlA&#39;;return true;">JEP-201 is the mission statement for the new configuration-as-code project. As the person who filed <a href="https://issues.jenkins-ci.org/browse/JENKINS-31094" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FJENKINS-31094\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGaWCa4mTX22h-IIze59Hut8tuoLA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FJENKINS-31094\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGaWCa4mTX22h-IIze59Hut8tuoLA&#39;;return true;">JENKINS-31094 and did a few prototypes in this space, I'm really really excited about this. I think this is a much awaited feature by many Jenkins admins, so hats off to Nicolas and Ewelina for pushing this forward. As this is the new area we are opening up, I will be the reviewer of JEP-201 myself. Once it gets accepted, my intention is to have future JEPs in this area presided by Ewelina. 
--
Kohsuke Kawaguchi

--
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/ccd08bb4-bb2c-47f7-91fa-88a34d9b67bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Selecting Delegates for the first wave of JEPs

R. Tyler Croy
In reply to this post by Kohsuke Kawaguchi
(replies inline)

On Tue, 05 Dec 2017, Kohsuke Kawaguchi wrote:

> Time to select Delegate
> <https://github.com/jenkinsci/jep/tree/master/jep/1#bdfl-delegate> for the
> first wave of JEPs!



wunderbar



- R. Tyler Croy

------------------------------------------------------
     Code: <https://github.com/rtyler>
  Chatter: <https://twitter.com/agentdero>
     xmpp: [hidden email]

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
------------------------------------------------------

--
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/20171205172659.kvaxtttfkdncxkxp%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.

signature.asc (201 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Selecting Delegates for the first wave of JEPs

Joseph P
In reply to this post by Ewelina Wilkosz
Nicolas and Ewelina, please keep up the good work. Looking forward to it 😊

--
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/9ee6ee90-bdd7-485a-b924-f86ebbab4b6f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Selecting Delegates for the first wave of JEPs

Oleg Nenashev
As JEP delegates we do not have strict review SLAs IIRC.
In the case of Remoting it may take a while to find time for a review.

среда, 6 декабря 2017 г., 8:12:31 UTC+1 пользователь Joseph P написал:
Nicolas and Ewelina, please keep up the good work. Looking forward to it 😊

--
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/23fdafcc-fdf5-40a0-95a9-9ad67d0a7424%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Selecting Delegates for the first wave of JEPs

Kohsuke Kawaguchi
Administrator
In reply to this post by Kohsuke Kawaguchi
I'm moving to accept JEP-201. From what I can tell, everyone involved in this area are happy to see this move forward. I've heard from Ewelina and Nicolas that when they showed it to people they got great reaction.

As I wrote before, I'm really excited to see this happen.

On Tue, Dec 5, 2017 at 12:00 AM Kohsuke Kawaguchi <[hidden email]> wrote:
Time to select Delegate for the first wave of JEPs!

JEP-200 is in the area of remoting, which has been primarily maintained by Oleg for years now. As such, I think it makes the natural sense that he continues to act as Delegate in this space. I think JEP-200 is a great change that eliminates not just one vulnerability but a whole class of vulnerability, which is something we'd like to see more of.

JEP-201 is the mission statement for the new configuration-as-code project. As the person who filed JENKINS-31094 and did a few prototypes in this space, I'm really really excited about this. I think this is a much awaited feature by many Jenkins admins, so hats off to Nicolas and Ewelina for pushing this forward. As this is the new area we are opening up, I will be the reviewer of JEP-201 myself. Once it gets accepted, my intention is to have future JEPs in this area presided by Ewelina. 
--
Kohsuke Kawaguchi
--
Kohsuke Kawaguchi

--
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/CAN4CQ4yoUrBkyr5-cJEn8n2hNaYjmutS9DR%2BH6uzMAREHEFZTA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.