Hi KK, Thanks for giving more details about the CDF. This is all good from my perspective. Just one question I want to ask.
I know the main structure will remain. But how the relationship is going between SIG and Committee? Another similar question is about the ambassador. The CDF and Jenkins will both have the ambassador or just one of them. Best regards, Rick On Tue, Feb 12, 2019 at 12:35 AM Kohsuke Kawaguchi <k...@kohsuke.org> wrote: > This is the formal call for input for the decision to move the Jenkins > project to the newly forming Continuous Delivery Foundation. (I was told > that my earlier attempt > <https://groups.google.com/d/msg/jenkinsci-dev/1w57jl3K4S4/G1LvRwZEFgAJ> > to just change the subject didn't create a wholly new thread, hence this > email) > > Speaking as the board, if we are to pull the trigger and formalize this > new home, given the magnitude of the proposal, we need to make a binding > decision and record it as such. Given that this seems to be a topic that > relatively small number of people care about, and that those reactions so > far have been overwhelmingly positive, the board would like to set 2 weeks > comment period ending on Feb 22nd, where we solicit anyone's organized > thoughts on why you think we should or shouldn't move the Jenkins project > under the proposed CDF. You can write it here, or if need be, send the > board a private email at jenkinsci-bo...@googlegroups.com. We'll consider > and respond to them, and provided that there still remains a significant > consensus (like the one that we are seeing so far), then the board will > make the binding decision. > > Not much of the existing structure of the Jenkins project will change. > Committers, contributors, officers, teams, the board, and all that will > still remain (including all the "normalization" work like voting.) The idea > is that the board and officers of the Jenkins project will be the > "oversight body of each TOC Project" (charter 7-b-i) and this links the > chain of authority of the CDF and the Jenkins project. Our existing > technical decision making process of JEP, SIG, PR, etc remain under our > control. The whole of the draft charter can be seen here > <https://drive.google.com/file/d/1QwpyOLRh4o41Hh5GA0FvTB8iNEEW-I9_/view?usp=sharing>. > Again, if anyone has questions, concerns, and/or opinions, I'd love to hear > those. > > Please keep the discussion going. Organized thoughts are always better, > but if you just want to pile on your +1, that'd be appreciated, too :-) > > -- > 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 jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4z7Q9jXL4PqfqVbBvmjsNy5B6uzEP%2BgnMFu0%2BnGQ6sLXw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4z7Q9jXL4PqfqVbBvmjsNy5B6uzEP%2BgnMFu0%2BnGQ6sLXw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- https://github.com/LinuxSuRen -- 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/CAMM7nTGx5c2LPacrKSCZQ6-ASjRftvJLm2%2BS8iynyCDbeQigQA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
