DECISION: Jenkins project to join CDF

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

DECISION: Jenkins project to join CDF

Kohsuke Kawaguchi
Administrator
The two weeks comment period that we set out on Feb 11th has ended. Aside from what’s already publicly discussed in the email thread, the last governance meeting, and past conversations over the year, we didn’t receive any private input during this period, positive or negative.

The board has met, and based on all of those, what we see is a fairly strong consensus among a small number of people who care about this topic. Others seem indifferent, and nobody that we know of are against the move.

So we concluded that we should proceed as the motion proposed in the beginning of the public comment period. This is a big thing, so I’m really happy that we got to this point. I want to thank everyone for making this happen.

We will begin the process of transferring from SPI, and entering into the CDF. In the beginning we are largely going to be working as we have always done, and the work mostly entails invisible formality work — recording decisions, transferring assets, various paperwork, meetings with those foundations, etc. We’ll involve with the relevant team officers, and collectively we’ll provide updates. Once the CDF gets going and we are there, then more evolutions/changes to the governance should follow, such as formalized voting. Such evolution has always been a part of us, and those will be individually discussed, like we’ve always done.

As always, any questions, comments, and/or thoughts are welcome.
--
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/CAN4CQ4z7wjTUz6URD8ETKmAnvuTBD-d-SM-JKC2AL89wLOrRsw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: DECISION: Jenkins project to join CDF

Marky Jackson
I am really happy for this. What can we in the community do to help move this/make the transition easier?

On Mar 1, 2019, at 2:54 PM, Kohsuke Kawaguchi <[hidden email]> wrote:

The two weeks comment period that we set out on Feb 11th has ended. Aside from what’s already publicly discussed in the email thread, the last governance meeting, and past conversations over the year, we didn’t receive any private input during this period, positive or negative.

The board has met, and based on all of those, what we see is a fairly strong consensus among a small number of people who care about this topic. Others seem indifferent, and nobody that we know of are against the move.

So we concluded that we should proceed as the motion proposed in the beginning of the public comment period. This is a big thing, so I’m really happy that we got to this point. I want to thank everyone for making this happen.

We will begin the process of transferring from SPI, and entering into the CDF. In the beginning we are largely going to be working as we have always done, and the work mostly entails invisible formality work — recording decisions, transferring assets, various paperwork, meetings with those foundations, etc. We’ll involve with the relevant team officers, and collectively we’ll provide updates. Once the CDF gets going and we are there, then more evolutions/changes to the governance should follow, such as formalized voting. Such evolution has always been a part of us, and those will be individually discussed, like we’ve always done.

As always, any questions, comments, and/or thoughts are welcome.
--
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/CAN4CQ4z7wjTUz6URD8ETKmAnvuTBD-d-SM-JKC2AL89wLOrRsw%40mail.gmail.com.
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/96E50F9B-F395-420D-9F54-60F35DA1B14F%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: DECISION: Jenkins project to join CDF

Kohsuke Kawaguchi
Administrator
Thanks! Your +1 like that is helping to people to see that this move is positive, and that creates an air cover and motivation for people doing the work.

So I say people can help by bringing more +1s!

On Fri, Mar 1, 2019 at 3:07 PM Marky Jackson <[hidden email]> wrote:
I am really happy for this. What can we in the community do to help move this/make the transition easier?

On Mar 1, 2019, at 2:54 PM, Kohsuke Kawaguchi <[hidden email]> wrote:

The two weeks comment period that we set out on Feb 11th has ended. Aside from what’s already publicly discussed in the email thread, the last governance meeting, and past conversations over the year, we didn’t receive any private input during this period, positive or negative.

The board has met, and based on all of those, what we see is a fairly strong consensus among a small number of people who care about this topic. Others seem indifferent, and nobody that we know of are against the move.

So we concluded that we should proceed as the motion proposed in the beginning of the public comment period. This is a big thing, so I’m really happy that we got to this point. I want to thank everyone for making this happen.

We will begin the process of transferring from SPI, and entering into the CDF. In the beginning we are largely going to be working as we have always done, and the work mostly entails invisible formality work — recording decisions, transferring assets, various paperwork, meetings with those foundations, etc. We’ll involve with the relevant team officers, and collectively we’ll provide updates. Once the CDF gets going and we are there, then more evolutions/changes to the governance should follow, such as formalized voting. Such evolution has always been a part of us, and those will be individually discussed, like we’ve always done.

As always, any questions, comments, and/or thoughts are welcome.
--
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/CAN4CQ4z7wjTUz6URD8ETKmAnvuTBD-d-SM-JKC2AL89wLOrRsw%40mail.gmail.com.
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/96E50F9B-F395-420D-9F54-60F35DA1B14F%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


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

Re: DECISION: Jenkins project to join CDF

Gavin Mogan
I'm also super excited about this. I can't wait to see if this helps other companies get involved.

(I am excited enough that i logged into groups.google with my personal account, that's how excited i am)

On Friday, March 1, 2019 at 3:28:27 PM UTC-8, Kohsuke Kawaguchi wrote:
Thanks! Your +1 like that is helping to people to see that this move is positive, and that creates an air cover and motivation for people doing the work.

So I say people can help by bringing more +1s!

On Fri, Mar 1, 2019 at 3:07 PM Marky Jackson <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="1ODyyWFeBwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">marky.r...@...> wrote:
I am really happy for this. What can we in the community do to help move this/make the transition easier?

On Mar 1, 2019, at 2:54 PM, Kohsuke Kawaguchi <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="1ODyyWFeBwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">k...@...> wrote:

The two weeks comment period that we set out on Feb 11th has ended. Aside from what’s already publicly discussed in <a href="https://groups.google.com/d/topic/jenkinsci-dev/5D8PzawL998/discussion" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/5D8PzawL998/discussion&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/5D8PzawL998/discussion&#39;;return true;">the email thread, <a href="http://meetings.jenkins-ci.org/jenkins-meeting/2019/jenkins-meeting.2019-02-27-18.01.html" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmeetings.jenkins-ci.org%2Fjenkins-meeting%2F2019%2Fjenkins-meeting.2019-02-27-18.01.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEJISE3UcsPxGyVQnv5quv-HOoEgg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmeetings.jenkins-ci.org%2Fjenkins-meeting%2F2019%2Fjenkins-meeting.2019-02-27-18.01.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEJISE3UcsPxGyVQnv5quv-HOoEgg&#39;;return true;">the last governance meeting, and past conversations over the year, we didn’t receive any private input during this period, positive or negative.

The board has met, and based on all of those, what we see is a fairly strong consensus among a small number of people who care about this topic. Others seem indifferent, and nobody that we know of are against the move.

So we concluded that we should proceed as <a href="https://groups.google.com/d/msg/jenkinsci-dev/5D8PzawL998/Hhr_ZdG-AAAJ" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msg/jenkinsci-dev/5D8PzawL998/Hhr_ZdG-AAAJ&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msg/jenkinsci-dev/5D8PzawL998/Hhr_ZdG-AAAJ&#39;;return true;">the motion proposed in the beginning of the public comment period. This is a big thing, so I’m really happy that we got to this point. I want to thank everyone for making this happen.

We will begin the process of transferring from SPI, and entering into the CDF. In the beginning we are largely going to be working as we have always done, and the work mostly entails invisible formality work — recording decisions, transferring assets, various paperwork, meetings with those foundations, etc. We’ll involve with the relevant team officers, and collectively we’ll provide updates. Once the CDF gets going and we are there, then more evolutions/changes to the governance should follow, such as formalized voting. Such evolution has always been a part of us, and those will be individually discussed, like we’ve always done.

As always, any questions, comments, and/or thoughts are welcome.
--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="1ODyyWFeBwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4z7wjTUz6URD8ETKmAnvuTBD-d-SM-JKC2AL89wLOrRsw%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4z7wjTUz6URD8ETKmAnvuTBD-d-SM-JKC2AL89wLOrRsw%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4z7wjTUz6URD8ETKmAnvuTBD-d-SM-JKC2AL89wLOrRsw%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4z7wjTUz6URD8ETKmAnvuTBD-d-SM-JKC2AL89wLOrRsw%40mail.gmail.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="1ODyyWFeBwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/96E50F9B-F395-420D-9F54-60F35DA1B14F%40gmail.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/96E50F9B-F395-420D-9F54-60F35DA1B14F%40gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/96E50F9B-F395-420D-9F54-60F35DA1B14F%40gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/96E50F9B-F395-420D-9F54-60F35DA1B14F%40gmail.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.


--
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/f1d0bacd-bb75-4212-8fa7-a248913918eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: DECISION: Jenkins project to join CDF

Rick
I am looking forward to this. Which reminds me, if we will provide the Chinese version for the CDF website. I asked this in the cdf mail list. But got nothing.

On Sat, Mar 2, 2019, 07:30 'Gavin Mogan' via Jenkins Developers <[hidden email]> wrote:
I'm also super excited about this. I can't wait to see if this helps other companies get involved.

(I am excited enough that i logged into groups.google with my personal account, that's how excited i am)

On Friday, March 1, 2019 at 3:28:27 PM UTC-8, Kohsuke Kawaguchi wrote:
Thanks! Your +1 like that is helping to people to see that this move is positive, and that creates an air cover and motivation for people doing the work.

So I say people can help by bringing more +1s!

On Fri, Mar 1, 2019 at 3:07 PM Marky Jackson <[hidden email]> wrote:
I am really happy for this. What can we in the community do to help move this/make the transition easier?

On Mar 1, 2019, at 2:54 PM, Kohsuke Kawaguchi <[hidden email]> wrote:

The two weeks comment period that we set out on Feb 11th has ended. Aside from what’s already publicly discussed in the email thread, the last governance meeting, and past conversations over the year, we didn’t receive any private input during this period, positive or negative.

The board has met, and based on all of those, what we see is a fairly strong consensus among a small number of people who care about this topic. Others seem indifferent, and nobody that we know of are against the move.

So we concluded that we should proceed as the motion proposed in the beginning of the public comment period. This is a big thing, so I’m really happy that we got to this point. I want to thank everyone for making this happen.

We will begin the process of transferring from SPI, and entering into the CDF. In the beginning we are largely going to be working as we have always done, and the work mostly entails invisible formality work — recording decisions, transferring assets, various paperwork, meetings with those foundations, etc. We’ll involve with the relevant team officers, and collectively we’ll provide updates. Once the CDF gets going and we are there, then more evolutions/changes to the governance should follow, such as formalized voting. Such evolution has always been a part of us, and those will be individually discussed, like we’ve always done.

As always, any questions, comments, and/or thoughts are welcome.
--
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/CAN4CQ4z7wjTUz6URD8ETKmAnvuTBD-d-SM-JKC2AL89wLOrRsw%40mail.gmail.com.
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/96E50F9B-F395-420D-9F54-60F35DA1B14F%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


--
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/f1d0bacd-bb75-4212-8fa7-a248913918eb%40googlegroups.com.
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTEbTmFLXEJeKZyswdpeWSLyt5m2AsiYA0HwzNyw1C2HBg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.