While this thread is quiet, between the previous rounds of discussions in Jenkins World contributor summit and the recent mailing list discussion, I think there's a consensus of the general problem space. I intend to accept this JEP here <https://github.com/jenkinsci/jep/pull/55> within several days. So please roll in your +1s!
Tyler will be working on this area, and he has been championing the education/arming of users as well as making Jenkins accessible to the broader users, on top of all the other things he has worked on over the past decade. I think he's well qualified to drive this effort, and as such I intend to delegate subsequent JEPs in this space to Tyler. On Thu, Feb 8, 2018 at 11:05 AM Kohsuke Kawaguchi <[email protected]> wrote: > Yay! I think this is an important step for the Jenkins project. I'm really > excited. > > We started talking about this in some of the events adjacent to FOSDEM. I > think people generally grok the idea and they are happy that we are > attacking these challenges. > > > On Tue, Feb 6, 2018 at 8:03 AM R. Tyler Croy <[email protected]> wrote: > >> >> After pounding my head against my whiteboard for a couple months, I'm >> finally >> ready to talk about this idea which was first discussed at Jenkins World >> 2017 >> in San Francisco. >> >> At the Contributor Summit we held, Kohsuke challenged us to make Jenkins >> easy >> enough for an end-user to go from "zero" (downloading Jenkins) to >> continuously >> delivering a project in under 5 clicks and under 5 minutes. >> >> Jenkins Essentials has this goal in mind, with an additional goal of >> making >> Jenkins development more efficient. >> >> I have proposed a draft of JEP-300 which outlines the problem domain and >> overview of Jenkins Essentials more thoroughly >> >> rendered: >> https://github.com/rtyler/jep/tree/essentials-overview-300/jep/300 >> pull request to jenkinsci/jep: https://github.com/jenkinsci/jep/pull/48 >> >> >> To be successful with Jenkins Essentials, I'm endeavouring to improve >> pre-release verification as well as post-release monitoring. Some of the >> initial tasks that my colleague Raul and I are tackling can be found on >> this >> board: https://issues.jenkins-ci.org/secure/RapidBoard.jspa?rapidView=396 >> >> >> I'm still sketching out the Developer Experience aspects of this in >> another >> thread once I have some thoughts written down. >> >> >> Please take a look at the document and let me know what you think on this >> thread :) >> >> >> >> Cheers >> - R. Tyler Croy >> >> ------------------------------------------------------ >> Code: <https://github.com/rtyler> >> Chatter: <https://twitter.com/agentdero> >> xmpp: [email protected] >> >> % 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/20180206160253.dkz7whf7h74bda64%40blackberry.coupleofllamas.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > 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/CAN4CQ4z0jxf0toO3x7DNXscBtQ4mpVD%2BvsCz136vgiKOm_ossw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
