FWIW, +1 all for it obviously, we've already had the opportunity to discuss this at Jenkins World.
And thanks again for that move Ozan, Emmanuel & your company LesFurets. IMO the next step is to file a JIRA into the HOSTING <https://issues.jenkins-ci.org/projects/HOSTING> project, linking to this thread here (also to essentially remind that a standard fork is not desirable for the typical reasons). 2017-09-27 11:50 GMT+02:00 Daniel Beck <m...@beckweb.net>: > > > On 27. Sep 2017, at 11:45, Oleg Nenashev <o.v.nenas...@gmail.com> wrote: > > > > discussion at the Governance meeting today so that anybody can provide > feedback > > Nobody bothered to speak up in this thread for the past week, so I don't > think this is necessary. > > -- > 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/ms > gid/jenkinsci-dev/06DAAE82-4B84-4CE9-84D7-7720990D0B00%40beckweb.net. > 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5HaUs1D%3DWnNwJDNCiKuKYkW-r9rp9e74Sf-TwFt61p7g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.