I'm moving to accept JEP-201 <https://github.com/jenkinsci/jep/pull/40>. >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 <[email protected]> wrote: > Time to select Delegate > <https://github.com/jenkinsci/jep/tree/master/jep/1#bdfl-delegate> for > the first wave of JEPs! > > JEP-200 <https://github.com/jenkinsci/jep/tree/master/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 <https://github.com/jenkinsci/jep/tree/master/jep/201> is the > mission statement for the new configuration-as-code project. As the person > who filed JENKINS-31094 > <https://issues.jenkins-ci.org/browse/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 [email protected]. 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.
