Re: 2 weeks comment period (was: Re: A new home for Jenkins)

[R. Tyler Croy]

(replies inline)

On Fri, 08 Feb 2019, Kohsuke Kawaguchi wrote:

> In FOSDEM, we organized a BOF session in which we talked a bit more about
> the CDF among 20-40 people who gathered. The response was good.
> 
> Attached is the charter of the CDF
> .
> This is the terms in which the Jenkins project is considering to move under
> the CDF. From the page 7 and onward, there's a bunch of details that
> describe the structure of the CDF.


This charter looks pretty much the same as what I originally looked at for a
"JSF" at the beginning of this process, so looks good to me! :)


> 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. Again, if anyone has questions, concerns, and/or opinions, I'd
> love to hear those.


THis is important, thanks for highlighting it Kohsuke. This also reflects my
understanding of the world under the CDF. I will add that the "oversight body
of each TOC project", will also need to be in conversation with the CDF to help
set our budget to appropriately meet our needs.

Fortunately, with the CDF structure, this means we'll finally have a _real_ and
dependable annual budget, I couldn't be more excited :D


> Now, putting my board hat on, I talked with the other board members (aka
> Tyler), and 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.


Looks great to me, please do comment and weight in!



Toodles

--
GitHub:  https://github.com/rtyler

GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2

-- 
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/20190211144148.GV23906%40grape.brokenco.de.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

2 weeks comment period (was: Re: A new home for Jenkins)

[Kohsuke Kawaguchi]

In FOSDEM, we organized a BOF session in which we talked a bit more about
the CDF among 20-40 people who gathered. The response was good.

Attached is the charter of the CDF
.
This is the terms in which the Jenkins project is considering to move under
the CDF. From the page 7 and onward, there's a bunch of details that
describe the structure of the CDF.

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. Again, if anyone has questions, concerns, and/or opinions, I'd
love to hear those.

Now, putting my board hat on, I talked with the other board members (aka
Tyler), and 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.

Please keep the conversation going.

2019年1月24日(木) 9:40 Kohsuke Kawaguchi :

> Thanks everyone who came to the Q The slides are available here
> 
> & the recording is available here.
> 
>
> If you are coming to FOSDEM, be sure to let us hear your thoughts.
>
> 2019年1月22日(火) 11:29 Liam Newman :
>
>> Hello everyone!
>>
>> We'll be doing an online Q on this tomorrow:
>> January 23rd, 2019 - 10am PST (6pm UTC)
>> Zoom: https://zoom.us/j/165732888
>> Here's a link to the Google calendar event
>> 
>>
>> Please join us and bring any questions you might have.
>>
>>
>>
>>
>> On Thursday, January 17, 2019 at 3:02:09 PM UTC-8, Kohsuke Kawaguchi
>> wrote:
>>>
>>>
>>> On Thu, Jan 17, 2019 at 12:26 AM nicolas de loof 
>>> wrote:
>>>
 That's a great new imho. This is not just about getting Jenkins
 community find a legal status. This is about building a full ecosystem and
 get collaboration with many other tools and vendor in this area. I remember
 the CNCF announcement, which was a tiny thing, and became a fantastic
 ecosystem. I hope CDF will bring the same dynamic.

>>>
>>> Right, that's the goal. My hope is that the broad term that is
>>> "Continuous Delivery" creates a big enough umbrella for enough projects and
>>> the communities to work together. Also, these OSS projects working better
>>> together is beneficial for user organizations, and that's how we hope to
>>> drive more participations.
>>>
>>>
>>>
 Le jeu. 17 janv. 2019 à 07:49, Rick  a écrit :

> This would be huge good news for Jenkins community I think. Especially
> for Jenkins China Community. I'm very looking forward to it. I think the
> CDF could provide us with a great opportunity to host more events or
> activities. I can image that CDF will help to bring more contributors and
> sponsors into the community.
>
> Second, I need to thank KK for giving me the support and delegation to
> running Jenkins Subscription WeChat Account. Now we almost have 1K
> subscribers. One article will be published per week. And I'm willing to
> take the initiative to help build an activity Jenkins Community in China.
> I'd love to the contact person in China for CDF or Jenkins if we need some
> kind that people. I've serval Jenkins related talks at some conference or
> meetup last year. I hope I could speak more topics to my forks this year.
> My company (alauda.io) and other companies or communities
> (DevOpsDays) are very supportive. I hope I could show up in the KubeCon in
> China this year.
>
> If I understand correctly, we don't discuss the details in this
> thread. But if everything is going well, then we might need to create a 
> new
> 

Re: A new home for Jenkins

[Kohsuke Kawaguchi]

Thanks everyone who came to the Q The slides are available here

& the recording is available here.


If you are coming to FOSDEM, be sure to let us hear your thoughts.

2019年1月22日(火) 11:29 Liam Newman :

> Hello everyone!
>
> We'll be doing an online Q on this tomorrow:
> January 23rd, 2019 - 10am PST (6pm UTC)
> Zoom: https://zoom.us/j/165732888
> Here's a link to the Google calendar event
> 
>
> Please join us and bring any questions you might have.
>
>
>
>
> On Thursday, January 17, 2019 at 3:02:09 PM UTC-8, Kohsuke Kawaguchi wrote:
>>
>>
>> On Thu, Jan 17, 2019 at 12:26 AM nicolas de loof 
>> wrote:
>>
>>> That's a great new imho. This is not just about getting Jenkins
>>> community find a legal status. This is about building a full ecosystem and
>>> get collaboration with many other tools and vendor in this area. I remember
>>> the CNCF announcement, which was a tiny thing, and became a fantastic
>>> ecosystem. I hope CDF will bring the same dynamic.
>>>
>>
>> Right, that's the goal. My hope is that the broad term that is
>> "Continuous Delivery" creates a big enough umbrella for enough projects and
>> the communities to work together. Also, these OSS projects working better
>> together is beneficial for user organizations, and that's how we hope to
>> drive more participations.
>>
>>
>>
>>> Le jeu. 17 janv. 2019 à 07:49, Rick  a écrit :
>>>
 This would be huge good news for Jenkins community I think. Especially
 for Jenkins China Community. I'm very looking forward to it. I think the
 CDF could provide us with a great opportunity to host more events or
 activities. I can image that CDF will help to bring more contributors and
 sponsors into the community.

 Second, I need to thank KK for giving me the support and delegation to
 running Jenkins Subscription WeChat Account. Now we almost have 1K
 subscribers. One article will be published per week. And I'm willing to
 take the initiative to help build an activity Jenkins Community in China.
 I'd love to the contact person in China for CDF or Jenkins if we need some
 kind that people. I've serval Jenkins related talks at some conference or
 meetup last year. I hope I could speak more topics to my forks this year.
 My company (alauda.io) and other companies or communities (DevOpsDays)
 are very supportive. I hope I could show up in the KubeCon in China this
 year.

 If I understand correctly, we don't discuss the details in this thread.
 But if everything is going well, then we might need to create a new
 organization which named like CDF. An official website might be necessary
 too. So, in my opinion, it will have lots of works are waiting for us.
 Right?

 Anyway, I expect more and more good news about Jenkins. If there's
 anything I can do for the Jenkins community. Just say it.

 Best regards,
 Rick (Zhao Xiaojie)

 On Thu, Jan 17, 2019 at 4:32 AM Oliver Gondža  wrote:

> Those are interesting news. Are we expecting to partner with existing
> communities around existing CD projects as a part of CDF? Are some of
> them on board with this vision or do we expect they will join us
> provided this turns out to be the right way to go? My concern is the
> “Continuous Delivery Foundation” feels pretty general and while
> getting
> under the wings of Linux Foundation is an impressive recognition of
> what
> we have achieved, it would be unfortunate to make an impression of
> claiming the whole field without wider consensus.
>
> On 16/01/2019 20.01, Marky Jackson wrote:
> > This is very exciting and welcoming!!!
> >
> >> On Jan 16, 2019, at 10:57 AM, Kohsuke Kawaguchi  >> > wrote:
> >>
> >> Ever since our project got our present ‘Jenkins’ name in 2011,
> we’ve
> >> always been conscious about the governance of this project. It’s a
> key
> >> part of ensuring the well-being of the project. We’ve not only
> talked
> >> the talk, but done some walking the walk too, such as team
> >> , JEP
> >> , and SIG <
> https://jenkins.io/sigs/>.
> >>
> >> One idea in this space that we’ve discussed in and out is software
> >> foundation around Jenkins. Those of you who came to Jenkins World
> >> Contributor Summit in 2017 might remember Tyler presenting this
> idea
> >> under the name “Jenkins Software Foundation” (see slides
> >> <
> 

Re: A new home for Jenkins

[Liam Newman]

Hello everyone!

We'll be doing an online Q on this tomorrow:
January 23rd, 2019 - 10am PST (6pm UTC)
Zoom: https://zoom.us/j/165732888 
Here's a link to the Google calendar event 


Please join us and bring any questions you might have. 




On Thursday, January 17, 2019 at 3:02:09 PM UTC-8, Kohsuke Kawaguchi wrote:
>
>
> On Thu, Jan 17, 2019 at 12:26 AM nicolas de loof  > wrote:
>
>> That's a great new imho. This is not just about getting Jenkins community 
>> find a legal status. This is about building a full ecosystem and get 
>> collaboration with many other tools and vendor in this area. I remember the 
>> CNCF announcement, which was a tiny thing, and became a fantastic 
>> ecosystem. I hope CDF will bring the same dynamic.
>>
>
> Right, that's the goal. My hope is that the broad term that is "Continuous 
> Delivery" creates a big enough umbrella for enough projects and the 
> communities to work together. Also, these OSS projects working better 
> together is beneficial for user organizations, and that's how we hope to 
> drive more participations.
>
>  
>
>> Le jeu. 17 janv. 2019 à 07:49, Rick > a 
>> écrit :
>>
>>> This would be huge good news for Jenkins community I think. Especially 
>>> for Jenkins China Community. I'm very looking forward to it. I think the 
>>> CDF could provide us with a great opportunity to host more events or 
>>> activities. I can image that CDF will help to bring more contributors and 
>>> sponsors into the community.
>>>
>>> Second, I need to thank KK for giving me the support and delegation to 
>>> running Jenkins Subscription WeChat Account. Now we almost have 1K 
>>> subscribers. One article will be published per week. And I'm willing to 
>>> take the initiative to help build an activity Jenkins Community in China. 
>>> I'd love to the contact person in China for CDF or Jenkins if we need some 
>>> kind that people. I've serval Jenkins related talks at some conference or 
>>> meetup last year. I hope I could speak more topics to my forks this year. 
>>> My company (alauda.io) and other companies or communities (DevOpsDays) 
>>> are very supportive. I hope I could show up in the KubeCon in China this 
>>> year.
>>>
>>> If I understand correctly, we don't discuss the details in this thread. 
>>> But if everything is going well, then we might need to create a new 
>>> organization which named like CDF. An official website might be necessary 
>>> too. So, in my opinion, it will have lots of works are waiting for us. 
>>> Right?
>>>
>>> Anyway, I expect more and more good news about Jenkins. If there's 
>>> anything I can do for the Jenkins community. Just say it.
>>>
>>> Best regards,
>>> Rick (Zhao Xiaojie)
>>>
>>> On Thu, Jan 17, 2019 at 4:32 AM Oliver Gondža >> > wrote:
>>>
 Those are interesting news. Are we expecting to partner with existing 
 communities around existing CD projects as a part of CDF? Are some of 
 them on board with this vision or do we expect they will join us 
 provided this turns out to be the right way to go? My concern is the 
 “Continuous Delivery Foundation” feels pretty general and while getting 
 under the wings of Linux Foundation is an impressive recognition of 
 what 
 we have achieved, it would be unfortunate to make an impression of 
 claiming the whole field without wider consensus.

 On 16/01/2019 20.01, Marky Jackson wrote:
 > This is very exciting and welcoming!!!
 > 
 >> On Jan 16, 2019, at 10:57 AM, Kohsuke Kawaguchi >>>  
 >> > wrote:
 >>
 >> Ever since our project got our present ‘Jenkins’ name in 2011, we’ve 
 >> always been conscious about the governance of this project. It’s a 
 key 
 >> part of ensuring the well-being of the project. We’ve not only 
 talked 
 >> the talk, but done some walking the walk too, such as team 
 >> , JEP 
 >> , and SIG <
 https://jenkins.io/sigs/>.
 >>
 >> One idea in this space that we’ve discussed in and out is software 
 >> foundation around Jenkins. Those of you who came to Jenkins World 
 >> Contributor Summit in 2017 might remember Tyler presenting this idea 
 >> under the name “Jenkins Software Foundation” (see slides 
 >> <
 https://docs.google.com/presentation/d/1E3sUlRnfG-Dpmj-Lwrse56S0aUY3PBoGlenU5QwYCXg/edit#slide=id.g16abb2ffe7_0_242>
  

 >> and notes 
 >> <
 https://docs.google.com/document/d/1JSxYNI_RuA8ITlxVmxBdFg1A-sOKz-w7a9tzuPfWmr4/edit#heading=h.hc79wlk2cwzn>),
  

 >> at the DevOps World | Jenkins World Contributor Summit in 2018 and 
 >> afterwards, Tracy has helped continue this conversation (see slides 
 >> <
 

Re: A new home for Jenkins

[Kohsuke Kawaguchi]

On Thu, Jan 17, 2019 at 12:26 AM nicolas de loof 
wrote:

> That's a great new imho. This is not just about getting Jenkins community
> find a legal status. This is about building a full ecosystem and get
> collaboration with many other tools and vendor in this area. I remember the
> CNCF announcement, which was a tiny thing, and became a fantastic
> ecosystem. I hope CDF will bring the same dynamic.
>

Right, that's the goal. My hope is that the broad term that is "Continuous
Delivery" creates a big enough umbrella for enough projects and the
communities to work together. Also, these OSS projects working better
together is beneficial for user organizations, and that's how we hope to
drive more participations.



> Le jeu. 17 janv. 2019 à 07:49, Rick  a écrit :
>
>> This would be huge good news for Jenkins community I think. Especially
>> for Jenkins China Community. I'm very looking forward to it. I think the
>> CDF could provide us with a great opportunity to host more events or
>> activities. I can image that CDF will help to bring more contributors and
>> sponsors into the community.
>>
>> Second, I need to thank KK for giving me the support and delegation to
>> running Jenkins Subscription WeChat Account. Now we almost have 1K
>> subscribers. One article will be published per week. And I'm willing to
>> take the initiative to help build an activity Jenkins Community in China.
>> I'd love to the contact person in China for CDF or Jenkins if we need some
>> kind that people. I've serval Jenkins related talks at some conference or
>> meetup last year. I hope I could speak more topics to my forks this year.
>> My company (alauda.io) and other companies or communities (DevOpsDays)
>> are very supportive. I hope I could show up in the KubeCon in China this
>> year.
>>
>> If I understand correctly, we don't discuss the details in this thread.
>> But if everything is going well, then we might need to create a new
>> organization which named like CDF. An official website might be necessary
>> too. So, in my opinion, it will have lots of works are waiting for us.
>> Right?
>>
>> Anyway, I expect more and more good news about Jenkins. If there's
>> anything I can do for the Jenkins community. Just say it.
>>
>> Best regards,
>> Rick (Zhao Xiaojie)
>>
>> On Thu, Jan 17, 2019 at 4:32 AM Oliver Gondža  wrote:
>>
>>> Those are interesting news. Are we expecting to partner with existing
>>> communities around existing CD projects as a part of CDF? Are some of
>>> them on board with this vision or do we expect they will join us
>>> provided this turns out to be the right way to go? My concern is the
>>> “Continuous Delivery Foundation” feels pretty general and while getting
>>> under the wings of Linux Foundation is an impressive recognition of what
>>> we have achieved, it would be unfortunate to make an impression of
>>> claiming the whole field without wider consensus.
>>>
>>> On 16/01/2019 20.01, Marky Jackson wrote:
>>> > This is very exciting and welcoming!!!
>>> >
>>> >> On Jan 16, 2019, at 10:57 AM, Kohsuke Kawaguchi >> >> > wrote:
>>> >>
>>> >> Ever since our project got our present ‘Jenkins’ name in 2011, we’ve
>>> >> always been conscious about the governance of this project. It’s a
>>> key
>>> >> part of ensuring the well-being of the project. We’ve not only talked
>>> >> the talk, but done some walking the walk too, such as team
>>> >> , JEP
>>> >> , and SIG >> >.
>>> >>
>>> >> One idea in this space that we’ve discussed in and out is software
>>> >> foundation around Jenkins. Those of you who came to Jenkins World
>>> >> Contributor Summit in 2017 might remember Tyler presenting this idea
>>> >> under the name “Jenkins Software Foundation” (see slides
>>> >> <
>>> https://docs.google.com/presentation/d/1E3sUlRnfG-Dpmj-Lwrse56S0aUY3PBoGlenU5QwYCXg/edit#slide=id.g16abb2ffe7_0_242>
>>>
>>> >> and notes
>>> >> <
>>> https://docs.google.com/document/d/1JSxYNI_RuA8ITlxVmxBdFg1A-sOKz-w7a9tzuPfWmr4/edit#heading=h.hc79wlk2cwzn>),
>>>
>>> >> at the DevOps World | Jenkins World Contributor Summit in 2018 and
>>> >> afterwards, Tracy has helped continue this conversation (see slides
>>> >> <
>>> https://docs.google.com/presentation/d/1Q-BGZV4H9x0Vo7QsEg-UfT04jQSJ6zuAQXahl9m3iuY/edit?usp=sharing
>>> >).
>>> >>
>>> >> *Why?
>>> >> *
>>> >> In a nutshell, the “problems” we are trying to solve here are:
>>> >>
>>> >>   * *Limits to current support and services* - Software in the Public
>>> >> Interest , which currently hosts Jenkins, is
>>> >> a fairly modest “limited service” non-profit organization. I love
>>> >> what they do, but we could use more help; entering into legal
>>> >> contracts, setting up recurring payment that doesn’t go through my
>>> >> own personal credit card. These inabilities hamper the growth of
>>> >> the project.

Re: A new home for Jenkins

[Kohsuke Kawaguchi]

On Wed, Jan 16, 2019 at 10:49 PM Rick  wrote:

> This would be huge good news for Jenkins community I think. Especially for
> Jenkins China Community. I'm very looking forward to it. I think the CDF
> could provide us with a great opportunity to host more events or
> activities. I can image that CDF will help to bring more contributors and
> sponsors into the community.
>

Yeah, exactly, that's precisely one of the goals.


> Second, I need to thank KK for giving me the support and delegation to
> running Jenkins Subscription WeChat Account. Now we almost have 1K
> subscribers. One article will be published per week. And I'm willing to
> take the initiative to help build an activity Jenkins Community in China.
> I'd love to the contact person in China for CDF or Jenkins if we need some
> kind that people. I've serval Jenkins related talks at some conference or
> meetup last year. I hope I could speak more topics to my forks this year.
> My company (alauda.io) and other companies or communities (DevOpsDays)
> are very supportive. I hope I could show up in the KubeCon in China this
> year.
>

Thank you for all that you've been doing with the Jenkins project. The CDF,
especially as more projects will join, create more platform and message
that we can speak.

If I understand correctly, we don't discuss the details in this thread. But
> if everything is going well, then we might need to create a new
> organization which named like CDF. An official website might be necessary
> too. So, in my opinion, it will have lots of works are waiting for us.
> Right?
>

Yes, as it gets closer to the reality a lot of work will happen through the
Linux Foundation, who runs the CDF.


Anyway, I expect more and more good news about Jenkins. If there's anything
> I can do for the Jenkins community. Just say it.
>
> Best regards,
> Rick (Zhao Xiaojie)
>
> On Thu, Jan 17, 2019 at 4:32 AM Oliver Gondža  wrote:
>
>> Those are interesting news. Are we expecting to partner with existing
>> communities around existing CD projects as a part of CDF? Are some of
>> them on board with this vision or do we expect they will join us
>> provided this turns out to be the right way to go? My concern is the
>> “Continuous Delivery Foundation” feels pretty general and while getting
>> under the wings of Linux Foundation is an impressive recognition of what
>> we have achieved, it would be unfortunate to make an impression of
>> claiming the whole field without wider consensus.
>>
>> On 16/01/2019 20.01, Marky Jackson wrote:
>> > This is very exciting and welcoming!!!
>> >
>> >> On Jan 16, 2019, at 10:57 AM, Kohsuke Kawaguchi > >> > wrote:
>> >>
>> >> Ever since our project got our present ‘Jenkins’ name in 2011, we’ve
>> >> always been conscious about the governance of this project. It’s a key
>> >> part of ensuring the well-being of the project. We’ve not only talked
>> >> the talk, but done some walking the walk too, such as team
>> >> , JEP
>> >> , and SIG > >.
>> >>
>> >> One idea in this space that we’ve discussed in and out is software
>> >> foundation around Jenkins. Those of you who came to Jenkins World
>> >> Contributor Summit in 2017 might remember Tyler presenting this idea
>> >> under the name “Jenkins Software Foundation” (see slides
>> >> <
>> https://docs.google.com/presentation/d/1E3sUlRnfG-Dpmj-Lwrse56S0aUY3PBoGlenU5QwYCXg/edit#slide=id.g16abb2ffe7_0_242>
>>
>> >> and notes
>> >> <
>> https://docs.google.com/document/d/1JSxYNI_RuA8ITlxVmxBdFg1A-sOKz-w7a9tzuPfWmr4/edit#heading=h.hc79wlk2cwzn>),
>>
>> >> at the DevOps World | Jenkins World Contributor Summit in 2018 and
>> >> afterwards, Tracy has helped continue this conversation (see slides
>> >> <
>> https://docs.google.com/presentation/d/1Q-BGZV4H9x0Vo7QsEg-UfT04jQSJ6zuAQXahl9m3iuY/edit?usp=sharing
>> >).
>> >>
>> >> *Why?
>> >> *
>> >> In a nutshell, the “problems” we are trying to solve here are:
>> >>
>> >>   * *Limits to current support and services* - Software in the Public
>> >> Interest , which currently hosts Jenkins, is
>> >> a fairly modest “limited service” non-profit organization. I love
>> >> what they do, but we could use more help; entering into legal
>> >> contracts, setting up recurring payment that doesn’t go through my
>> >> own personal credit card. These inabilities hamper the growth of
>> >> the project.
>> >>
>> >>   * *High barrier to participation by corporate contributors* - Our
>> >> unique governance structure makes it unnecessarily hard for
>> >> corporate contributors to come in and feel at home. We aren’t an
>> >> Apache project, an Eclipse project, nor a company-owned project
>> >> like Chef or Spring. We are just a little too unique to be
>> >> understood by corporate open-source offices, lawyers, and
>> >> pointy-haired bosses. The net 

Re: A new home for Jenkins

[R. Tyler Croy]

(replies inline)

On Wed, 16 Jan 2019, Oliver Gond??a wrote:

> Those are interesting news. Are we expecting to partner with existing
> communities around existing CD projects as a part of CDF? Are some of them
> on board with this vision or do we expect they will join us provided this
> turns out to be the right way to go? My concern is the ???Continuous
> Delivery Foundation??? feels pretty general and while getting under the
> wings of Linux Foundation is an impressive recognition of what we have
> achieved, it would be unfortunate to make an impression of claiming the
> whole field without wider consensus.


Hiya Oliver! I'll answer this since I've also been working a bit behind the
scenes with Tracy and the Linux Foundation (LF) to move this forward.

LF has been reaching out to some other projects which are what I would consider
our brothers and sisters in the Continuous Delivery space. A few of them are
projects which many Jenkins users are already very familiar with, but since a
couple of those projects are waiting for Jenkins to take the lead here, they
have not publicly discussed or committed to the idea of the CDF.


I'll have to write a blog post at some point about our path thus far, but I
originally wanted a Jenkins Software Foundation, but it was actually others
outside of the Jenkins project that _suggested_ and wanted a more broad
umbrella to support this entire space.

Suffice it to say, Jenkins is leading the way here, but we will not be the only
ones at the party! :)



Cheers
--
GitHub:  https://github.com/rtyler

GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2

-- 
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/20190117191625.zdajjrl5lkg2jx4w%40grape.brokenco.de.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

Re: A new home for Jenkins

[夏润泽]

Good News. As a user in China, I also hope that more and more Chinese users 
can use Jenkins and participate in the contribution.

On Thursday, January 17, 2019 at 2:57:51 AM UTC+8, Kohsuke Kawaguchi wrote:
>
> Ever since our project got our present ‘Jenkins’ name in 2011, we’ve 
> always been conscious about the governance of this project. It’s a key part 
> of ensuring the well-being of the project. We’ve not only talked the talk, 
> but done some walking the walk too, such as team 
> , JEP 
> , and SIG .
>
> One idea in this space that we’ve discussed in and out is software 
> foundation around Jenkins. Those of you who came to Jenkins World 
> Contributor Summit in 2017 might remember Tyler presenting this idea under 
> the name “Jenkins Software Foundation” (see slides 
> 
>  
> and notes 
> ),
>  
> at the DevOps World | Jenkins World Contributor Summit in 2018 and 
> afterwards, Tracy has helped continue this conversation (see slides 
> 
> ).
>
>
> *Why?*
> In a nutshell, the “problems” we are trying to solve here are:
>
>
>- *Limits to current support and services* - Software in the Public 
>Interest , which currently hosts Jenkins, is a 
>fairly modest “limited service” non-profit organization. I love what they 
>do, but we could use more help; entering into legal contracts, setting up 
>recurring payment that doesn’t go through my own personal credit card. 
>These inabilities hamper the growth of the project.
>
>- *High barrier to participation by corporate contributors* - Our 
>unique governance structure makes it unnecessarily hard for corporate 
>contributors to come in and feel at home. We aren’t an Apache project, an 
>Eclipse project, nor a company-owned project like Chef or Spring. We are 
>just a little too unique to be understood by corporate open-source 
> offices, 
>lawyers, and pointy-haired bosses. The net result is that we lose out on 
>their participation and contributions — money and people. I’ve been on the 
>phone with some of those companies myself, and so has Tracy.
>
>- *Misperception that Jenkins is owned by CloudBees* - A common 
>perception error is that Jenkins is a CloudBees project, when it really 
>isn’t. But this perception is self-perpetuating. We want a long-term 
>structure to keep Jenkins alive and thriving, and not being tied to the 
>fate of any single entity is a key requirement. We want more companies to 
>participate in Jenkins, feel a co-ownership, and push Jenkins forward 
>together.
>
>- *Need to coordinated broader community of contributors* - On the 
>people front, it used to be that the bulk of the forward motion in this 
>project came from individual plugin developers. Today, where we need to 
>move forward requires more organized contributors and skills other than 
>coding. Blue Ocean was a good example. So was Config as Code, where it 
> took 
>the persistence of two corporate contributors. Pipeline Authoring SIG 
> to me is another young 
>example where if you look at the key participants, it really represents 
>organizations and what they are concerned about.
>
>- *Raising and using money well* - On the money front, we are not 
>tapping our ability to raise money, and we lack the ability to use it 
>effectively. On the few 
> 
>occasions 
> 
>that we did a donation drive, we have shown incredible ability to raise 
>money, but I know we can do a few orders of magnitude more. Plus, this 
> kind 
>of irregular income is difficult to make the most of, because it’s hard to 
>enter into recurring expenses. Also, without our own legal entity, we lack 
>the ability to turn the money into what’s most precious — people!
>
> Given all this, the Jenkins board, CloudBees (as the biggest contributor), 
> and the Linux Foundation kept exploring this foundation idea beyond those 
> contributor summits. We have floated some ideas with some of the companies 
> participating in the ecosystem. Thoughts have evolved, ideas turned into 
> more concrete plans, and I think it has developed to a point where this is 
> beginning to look real, and really makes a lot of sense for the project.
>
>
> *What?*
> So here are the key ideas/features of the foundation:
>
>
>- We 

Re: A new home for Jenkins

[Carlos Sanchez]

Great news for the community!
Thanks KK

On Wed, Jan 16, 2019 at 7:58 PM Kohsuke Kawaguchi  wrote:

> Ever since our project got our present ‘Jenkins’ name in 2011, we’ve
> always been conscious about the governance of this project. It’s a key part
> of ensuring the well-being of the project. We’ve not only talked the talk,
> but done some walking the walk too, such as team
> , JEP
> , and SIG .
>
> One idea in this space that we’ve discussed in and out is software
> foundation around Jenkins. Those of you who came to Jenkins World
> Contributor Summit in 2017 might remember Tyler presenting this idea under
> the name “Jenkins Software Foundation” (see slides
> 
> and notes
> ),
> at the DevOps World | Jenkins World Contributor Summit in 2018 and
> afterwards, Tracy has helped continue this conversation (see slides
> 
> ).
>
>
> *Why?*
> In a nutshell, the “problems” we are trying to solve here are:
>
>
>- *Limits to current support and services* - Software in the Public
>Interest , which currently hosts Jenkins, is a
>fairly modest “limited service” non-profit organization. I love what they
>do, but we could use more help; entering into legal contracts, setting up
>recurring payment that doesn’t go through my own personal credit card.
>These inabilities hamper the growth of the project.
>
>- *High barrier to participation by corporate contributors* - Our
>unique governance structure makes it unnecessarily hard for corporate
>contributors to come in and feel at home. We aren’t an Apache project, an
>Eclipse project, nor a company-owned project like Chef or Spring. We are
>just a little too unique to be understood by corporate open-source offices,
>lawyers, and pointy-haired bosses. The net result is that we lose out on
>their participation and contributions — money and people. I’ve been on the
>phone with some of those companies myself, and so has Tracy.
>
>- *Misperception that Jenkins is owned by CloudBees* - A common
>perception error is that Jenkins is a CloudBees project, when it really
>isn’t. But this perception is self-perpetuating. We want a long-term
>structure to keep Jenkins alive and thriving, and not being tied to the
>fate of any single entity is a key requirement. We want more companies to
>participate in Jenkins, feel a co-ownership, and push Jenkins forward
>together.
>
>- *Need to coordinated broader community of contributors* - On the
>people front, it used to be that the bulk of the forward motion in this
>project came from individual plugin developers. Today, where we need to
>move forward requires more organized contributors and skills other than
>coding. Blue Ocean was a good example. So was Config as Code, where it took
>the persistence of two corporate contributors. Pipeline Authoring SIG
> to me is another young
>example where if you look at the key participants, it really represents
>organizations and what they are concerned about.
>
>- *Raising and using money well* - On the money front, we are not
>tapping our ability to raise money, and we lack the ability to use it
>effectively. On the few
>
>occasions
>
>that we did a donation drive, we have shown incredible ability to raise
>money, but I know we can do a few orders of magnitude more. Plus, this kind
>of irregular income is difficult to make the most of, because it’s hard to
>enter into recurring expenses. Also, without our own legal entity, we lack
>the ability to turn the money into what’s most precious — people!
>
> Given all this, the Jenkins board, CloudBees (as the biggest contributor),
> and the Linux Foundation kept exploring this foundation idea beyond those
> contributor summits. We have floated some ideas with some of the companies
> participating in the ecosystem. Thoughts have evolved, ideas turned into
> more concrete plans, and I think it has developed to a point where this is
> beginning to look real, and really makes a lot of sense for the project.
>
>
> *What?*
> So here are the key ideas/features of the foundation:
>
>
>- We are calling it “Continuous Delivery Foundation” (CDF), and it
>will have a broader charter. It will house not just Jenkins but other
>open-source projects in this space. Through the CDF, 

Re: A new home for Jenkins

[nicolas de loof]

That's a great new imho. This is not just about getting Jenkins community
find a legal status. This is about building a full ecosystem and get
collaboration with many other tools and vendor in this area. I remember the
CNCF announcement, which was a tiny thing, and became a fantastic
ecosystem. I hope CDF will bring the same dynamic.

Le jeu. 17 janv. 2019 à 07:49, Rick  a écrit :

> This would be huge good news for Jenkins community I think. Especially for
> Jenkins China Community. I'm very looking forward to it. I think the CDF
> could provide us with a great opportunity to host more events or
> activities. I can image that CDF will help to bring more contributors and
> sponsors into the community.
>
> Second, I need to thank KK for giving me the support and delegation to
> running Jenkins Subscription WeChat Account. Now we almost have 1K
> subscribers. One article will be published per week. And I'm willing to
> take the initiative to help build an activity Jenkins Community in China.
> I'd love to the contact person in China for CDF or Jenkins if we need some
> kind that people. I've serval Jenkins related talks at some conference or
> meetup last year. I hope I could speak more topics to my forks this year.
> My company (alauda.io) and other companies or communities (DevOpsDays)
> are very supportive. I hope I could show up in the KubeCon in China this
> year.
>
> If I understand correctly, we don't discuss the details in this thread.
> But if everything is going well, then we might need to create a new
> organization which named like CDF. An official website might be necessary
> too. So, in my opinion, it will have lots of works are waiting for us.
> Right?
>
> Anyway, I expect more and more good news about Jenkins. If there's
> anything I can do for the Jenkins community. Just say it.
>
> Best regards,
> Rick (Zhao Xiaojie)
>
> On Thu, Jan 17, 2019 at 4:32 AM Oliver Gondža  wrote:
>
>> Those are interesting news. Are we expecting to partner with existing
>> communities around existing CD projects as a part of CDF? Are some of
>> them on board with this vision or do we expect they will join us
>> provided this turns out to be the right way to go? My concern is the
>> “Continuous Delivery Foundation” feels pretty general and while getting
>> under the wings of Linux Foundation is an impressive recognition of what
>> we have achieved, it would be unfortunate to make an impression of
>> claiming the whole field without wider consensus.
>>
>> On 16/01/2019 20.01, Marky Jackson wrote:
>> > This is very exciting and welcoming!!!
>> >
>> >> On Jan 16, 2019, at 10:57 AM, Kohsuke Kawaguchi > >> > wrote:
>> >>
>> >> Ever since our project got our present ‘Jenkins’ name in 2011, we’ve
>> >> always been conscious about the governance of this project. It’s a key
>> >> part of ensuring the well-being of the project. We’ve not only talked
>> >> the talk, but done some walking the walk too, such as team
>> >> , JEP
>> >> , and SIG > >.
>> >>
>> >> One idea in this space that we’ve discussed in and out is software
>> >> foundation around Jenkins. Those of you who came to Jenkins World
>> >> Contributor Summit in 2017 might remember Tyler presenting this idea
>> >> under the name “Jenkins Software Foundation” (see slides
>> >> <
>> https://docs.google.com/presentation/d/1E3sUlRnfG-Dpmj-Lwrse56S0aUY3PBoGlenU5QwYCXg/edit#slide=id.g16abb2ffe7_0_242>
>>
>> >> and notes
>> >> <
>> https://docs.google.com/document/d/1JSxYNI_RuA8ITlxVmxBdFg1A-sOKz-w7a9tzuPfWmr4/edit#heading=h.hc79wlk2cwzn>),
>>
>> >> at the DevOps World | Jenkins World Contributor Summit in 2018 and
>> >> afterwards, Tracy has helped continue this conversation (see slides
>> >> <
>> https://docs.google.com/presentation/d/1Q-BGZV4H9x0Vo7QsEg-UfT04jQSJ6zuAQXahl9m3iuY/edit?usp=sharing
>> >).
>> >>
>> >> *Why?
>> >> *
>> >> In a nutshell, the “problems” we are trying to solve here are:
>> >>
>> >>   * *Limits to current support and services* - Software in the Public
>> >> Interest , which currently hosts Jenkins, is
>> >> a fairly modest “limited service” non-profit organization. I love
>> >> what they do, but we could use more help; entering into legal
>> >> contracts, setting up recurring payment that doesn’t go through my
>> >> own personal credit card. These inabilities hamper the growth of
>> >> the project.
>> >>
>> >>   * *High barrier to participation by corporate contributors* - Our
>> >> unique governance structure makes it unnecessarily hard for
>> >> corporate contributors to come in and feel at home. We aren’t an
>> >> Apache project, an Eclipse project, nor a company-owned project
>> >> like Chef or Spring. We are just a little too unique to be
>> >> understood by corporate open-source offices, lawyers, and
>> >> pointy-haired bosses. The net 

Re: A new home for Jenkins

[Rick]

This would be huge good news for Jenkins community I think. Especially for
Jenkins China Community. I'm very looking forward to it. I think the CDF
could provide us with a great opportunity to host more events or
activities. I can image that CDF will help to bring more contributors and
sponsors into the community.

Second, I need to thank KK for giving me the support and delegation to
running Jenkins Subscription WeChat Account. Now we almost have 1K
subscribers. One article will be published per week. And I'm willing to
take the initiative to help build an activity Jenkins Community in China.
I'd love to the contact person in China for CDF or Jenkins if we need some
kind that people. I've serval Jenkins related talks at some conference or
meetup last year. I hope I could speak more topics to my forks this year.
My company (alauda.io) and other companies or communities (DevOpsDays) are
very supportive. I hope I could show up in the KubeCon in China this year.

If I understand correctly, we don't discuss the details in this thread. But
if everything is going well, then we might need to create a new
organization which named like CDF. An official website might be necessary
too. So, in my opinion, it will have lots of works are waiting for us.
Right?

Anyway, I expect more and more good news about Jenkins. If there's anything
I can do for the Jenkins community. Just say it.

Best regards,
Rick (Zhao Xiaojie)

On Thu, Jan 17, 2019 at 4:32 AM Oliver Gondža  wrote:

> Those are interesting news. Are we expecting to partner with existing
> communities around existing CD projects as a part of CDF? Are some of
> them on board with this vision or do we expect they will join us
> provided this turns out to be the right way to go? My concern is the
> “Continuous Delivery Foundation” feels pretty general and while getting
> under the wings of Linux Foundation is an impressive recognition of what
> we have achieved, it would be unfortunate to make an impression of
> claiming the whole field without wider consensus.
>
> On 16/01/2019 20.01, Marky Jackson wrote:
> > This is very exciting and welcoming!!!
> >
> >> On Jan 16, 2019, at 10:57 AM, Kohsuke Kawaguchi  >> > wrote:
> >>
> >> Ever since our project got our present ‘Jenkins’ name in 2011, we’ve
> >> always been conscious about the governance of this project. It’s a key
> >> part of ensuring the well-being of the project. We’ve not only talked
> >> the talk, but done some walking the walk too, such as team
> >> , JEP
> >> , and SIG .
> >>
> >> One idea in this space that we’ve discussed in and out is software
> >> foundation around Jenkins. Those of you who came to Jenkins World
> >> Contributor Summit in 2017 might remember Tyler presenting this idea
> >> under the name “Jenkins Software Foundation” (see slides
> >> <
> https://docs.google.com/presentation/d/1E3sUlRnfG-Dpmj-Lwrse56S0aUY3PBoGlenU5QwYCXg/edit#slide=id.g16abb2ffe7_0_242>
>
> >> and notes
> >> <
> https://docs.google.com/document/d/1JSxYNI_RuA8ITlxVmxBdFg1A-sOKz-w7a9tzuPfWmr4/edit#heading=h.hc79wlk2cwzn>),
>
> >> at the DevOps World | Jenkins World Contributor Summit in 2018 and
> >> afterwards, Tracy has helped continue this conversation (see slides
> >> <
> https://docs.google.com/presentation/d/1Q-BGZV4H9x0Vo7QsEg-UfT04jQSJ6zuAQXahl9m3iuY/edit?usp=sharing
> >).
> >>
> >> *Why?
> >> *
> >> In a nutshell, the “problems” we are trying to solve here are:
> >>
> >>   * *Limits to current support and services* - Software in the Public
> >> Interest , which currently hosts Jenkins, is
> >> a fairly modest “limited service” non-profit organization. I love
> >> what they do, but we could use more help; entering into legal
> >> contracts, setting up recurring payment that doesn’t go through my
> >> own personal credit card. These inabilities hamper the growth of
> >> the project.
> >>
> >>   * *High barrier to participation by corporate contributors* - Our
> >> unique governance structure makes it unnecessarily hard for
> >> corporate contributors to come in and feel at home. We aren’t an
> >> Apache project, an Eclipse project, nor a company-owned project
> >> like Chef or Spring. We are just a little too unique to be
> >> understood by corporate open-source offices, lawyers, and
> >> pointy-haired bosses. The net result is that we lose out on their
> >> participation and contributions — money and people. I’ve been on
> >> the phone with some of those companies myself, and so has Tracy.
> >>
> >>   * *Misperception that Jenkins is owned by CloudBees* - A common
> >> perception error is that Jenkins is a CloudBees project, when it
> >> really isn’t. But this perception is self-perpetuating. We want a
> >> long-term structure to keep Jenkins alive and thriving, and not
> >> being tied 

Re: A new home for Jenkins

[Oliver Gondža]

Those are interesting news. Are we expecting to partner with existing 
communities around existing CD projects as a part of CDF? Are some of 
them on board with this vision or do we expect they will join us 
provided this turns out to be the right way to go? My concern is the 
“Continuous Delivery Foundation” feels pretty general and while getting 
under the wings of Linux Foundation is an impressive recognition of what 
we have achieved, it would be unfortunate to make an impression of 
claiming the whole field without wider consensus.


On 16/01/2019 20.01, Marky Jackson wrote:

This is very exciting and welcoming!!!

On Jan 16, 2019, at 10:57 AM, Kohsuke Kawaguchi > wrote:


Ever since our project got our present ‘Jenkins’ name in 2011, we’ve 
always been conscious about the governance of this project. It’s a key 
part of ensuring the well-being of the project. We’ve not only talked 
the talk, but done some walking the walk too, such as team 
, JEP 
, and SIG .


One idea in this space that we’ve discussed in and out is software 
foundation around Jenkins. Those of you who came to Jenkins World 
Contributor Summit in 2017 might remember Tyler presenting this idea 
under the name “Jenkins Software Foundation” (see slides 
 
and notes 
), 
at the DevOps World | Jenkins World Contributor Summit in 2018 and 
afterwards, Tracy has helped continue this conversation (see slides 
).


*Why?
*
In a nutshell, the “problems” we are trying to solve here are:

  * *Limits to current support and services* - Software in the Public
Interest , which currently hosts Jenkins, is
a fairly modest “limited service” non-profit organization. I love
what they do, but we could use more help; entering into legal
contracts, setting up recurring payment that doesn’t go through my
own personal credit card. These inabilities hamper the growth of
the project.

  * *High barrier to participation by corporate contributors* - Our
unique governance structure makes it unnecessarily hard for
corporate contributors to come in and feel at home. We aren’t an
Apache project, an Eclipse project, nor a company-owned project
like Chef or Spring. We are just a little too unique to be
understood by corporate open-source offices, lawyers, and
pointy-haired bosses. The net result is that we lose out on their
participation and contributions — money and people. I’ve been on
the phone with some of those companies myself, and so has Tracy.

  * *Misperception that Jenkins is owned by CloudBees* - A common
perception error is that Jenkins is a CloudBees project, when it
really isn’t. But this perception is self-perpetuating. We want a
long-term structure to keep Jenkins alive and thriving, and not
being tied to the fate of any single entity is a key requirement.
We want more companies to participate in Jenkins, feel a
co-ownership, and push Jenkins forward together.

  * *Need to coordinated broader community of contributors* - On the
people front, it used to be that the bulk of the forward motion in
this project came from individual plugin developers. Today, where
we need to move forward requires more organized contributors and
skills other than coding. Blue Ocean was a good example. So was
Config as Code, where it took the persistence of two corporate
contributors. Pipeline Authoring SIG
 to me is another
young example where if you look at the key participants, it really
represents organizations and what they are concerned about.

  * *Raising and using money well* - On the money front, we are not
tapping our ability to raise money, and we lack the ability to use
it effectively. On the few

occasions

that we did a donation drive, we have shown incredible ability to
raise money, but I know we can do a few orders of magnitude more.
Plus, this kind of irregular income is difficult to make the most
of, because it’s hard to enter into recurring expenses. Also,
without our own legal entity, we lack the ability to turn the
money into what’s most precious — people!

Given all this, the Jenkins board, CloudBees (as the biggest 
contributor), and the Linux Foundation kept exploring this foundation 
idea beyond those contributor summits. We have floated some 

Re: A new home for Jenkins

[Marky Jackson]

This is very exciting and welcoming!!!

> On Jan 16, 2019, at 10:57 AM, Kohsuke Kawaguchi  wrote:
> 
> Ever since our project got our present ‘Jenkins’ name in 2011, we’ve always 
> been conscious about the governance of this project. It’s a key part of 
> ensuring the well-being of the project. We’ve not only talked the talk, but 
> done some walking the walk too, such as team 
> , JEP 
> , and SIG .
> 
> One idea in this space that we’ve discussed in and out is software foundation 
> around Jenkins. Those of you who came to Jenkins World Contributor Summit in 
> 2017 might remember Tyler presenting this idea under the name “Jenkins 
> Software Foundation” (see slides 
> 
>  and notes 
> ),
>  at the DevOps World | Jenkins World Contributor Summit in 2018 and 
> afterwards, Tracy has helped continue this conversation (see slides 
> ).
> 
> Why?
> 
> In a nutshell, the “problems” we are trying to solve here are:
> 
> Limits to current support and services - Software in the Public Interest 
> , which currently hosts Jenkins, is a fairly modest 
> “limited service” non-profit organization. I love what they do, but we could 
> use more help; entering into legal contracts, setting up recurring payment 
> that doesn’t go through my own personal credit card. These inabilities hamper 
> the growth of the project.
> 
> High barrier to participation by corporate contributors - Our unique 
> governance structure makes it unnecessarily hard for corporate contributors 
> to come in and feel at home. We aren’t an Apache project, an Eclipse project, 
> nor a company-owned project like Chef or Spring. We are just a little too 
> unique to be understood by corporate open-source offices, lawyers, and 
> pointy-haired bosses. The net result is that we lose out on their 
> participation and contributions — money and people. I’ve been on the phone 
> with some of those companies myself, and so has Tracy.
> 
> Misperception that Jenkins is owned by CloudBees - A common perception error 
> is that Jenkins is a CloudBees project, when it really isn’t. But this 
> perception is self-perpetuating. We want a long-term structure to keep 
> Jenkins alive and thriving, and not being tied to the fate of any single 
> entity is a key requirement. We want more companies to participate in 
> Jenkins, feel a co-ownership, and push Jenkins forward together.
> 
> Need to coordinated broader community of contributors - On the people front, 
> it used to be that the bulk of the forward motion in this project came from 
> individual plugin developers. Today, where we need to move forward requires 
> more organized contributors and skills other than coding. Blue Ocean was a 
> good example. So was Config as Code, where it took the persistence of two 
> corporate contributors. Pipeline Authoring SIG 
>  to me is another young example 
> where if you look at the key participants, it really represents organizations 
> and what they are concerned about.
> 
> Raising and using money well - On the money front, we are not tapping our 
> ability to raise money, and we lack the ability to use it effectively. On the 
> few  occasions 
>  that we 
> did a donation drive, we have shown incredible ability to raise money, but I 
> know we can do a few orders of magnitude more. Plus, this kind of irregular 
> income is difficult to make the most of, because it’s hard to enter into 
> recurring expenses. Also, without our own legal entity, we lack the ability 
> to turn the money into what’s most precious — people!
> Given all this, the Jenkins board, CloudBees (as the biggest contributor), 
> and the Linux Foundation kept exploring this foundation idea beyond those 
> contributor summits. We have floated some ideas with some of the companies 
> participating in the ecosystem. Thoughts have evolved, ideas turned into more 
> concrete plans, and I think it has developed to a point where this is 
> beginning to look real, and really makes a lot of sense for the project.
> 
> What?
> 
> So here are the key ideas/features of the foundation:
> 
> We are calling it “Continuous Delivery Foundation” (CDF), and it will have a 
> broader charter. It will house not just Jenkins but other open-source 
> projects in this space. Through the CDF, we want to create open-source 
> solutions collectively addressing the whole software development 

A new home for Jenkins

[Kohsuke Kawaguchi]

Ever since our project got our present ‘Jenkins’ name in 2011, we’ve always
been conscious about the governance of this project. It’s a key part of
ensuring the well-being of the project. We’ve not only talked the talk, but
done some walking the walk too, such as team
, JEP
, and SIG .

One idea in this space that we’ve discussed in and out is software
foundation around Jenkins. Those of you who came to Jenkins World
Contributor Summit in 2017 might remember Tyler presenting this idea under
the name “Jenkins Software Foundation” (see slides

and notes
),
at the DevOps World | Jenkins World Contributor Summit in 2018 and
afterwards, Tracy has helped continue this conversation (see slides

).


*Why?*
In a nutshell, the “problems” we are trying to solve here are:


   - *Limits to current support and services* - Software in the Public
   Interest , which currently hosts Jenkins, is a
   fairly modest “limited service” non-profit organization. I love what they
   do, but we could use more help; entering into legal contracts, setting up
   recurring payment that doesn’t go through my own personal credit card.
   These inabilities hamper the growth of the project.

   - *High barrier to participation by corporate contributors* - Our unique
   governance structure makes it unnecessarily hard for corporate contributors
   to come in and feel at home. We aren’t an Apache project, an Eclipse
   project, nor a company-owned project like Chef or Spring. We are just a
   little too unique to be understood by corporate open-source offices,
   lawyers, and pointy-haired bosses. The net result is that we lose out on
   their participation and contributions — money and people. I’ve been on the
   phone with some of those companies myself, and so has Tracy.

   - *Misperception that Jenkins is owned by CloudBees* - A common
   perception error is that Jenkins is a CloudBees project, when it really
   isn’t. But this perception is self-perpetuating. We want a long-term
   structure to keep Jenkins alive and thriving, and not being tied to the
   fate of any single entity is a key requirement. We want more companies to
   participate in Jenkins, feel a co-ownership, and push Jenkins forward
   together.

   - *Need to coordinated broader community of contributors* - On the
   people front, it used to be that the bulk of the forward motion in this
   project came from individual plugin developers. Today, where we need to
   move forward requires more organized contributors and skills other than
   coding. Blue Ocean was a good example. So was Config as Code, where it took
   the persistence of two corporate contributors. Pipeline Authoring SIG
    to me is another young
   example where if you look at the key participants, it really represents
   organizations and what they are concerned about.

   - *Raising and using money well* - On the money front, we are not
   tapping our ability to raise money, and we lack the ability to use it
   effectively. On the few
    occasions
    that
   we did a donation drive, we have shown incredible ability to raise money,
   but I know we can do a few orders of magnitude more. Plus, this kind of
   irregular income is difficult to make the most of, because it’s hard to
   enter into recurring expenses. Also, without our own legal entity, we lack
   the ability to turn the money into what’s most precious — people!

Given all this, the Jenkins board, CloudBees (as the biggest contributor),
and the Linux Foundation kept exploring this foundation idea beyond those
contributor summits. We have floated some ideas with some of the companies
participating in the ecosystem. Thoughts have evolved, ideas turned into
more concrete plans, and I think it has developed to a point where this is
beginning to look real, and really makes a lot of sense for the project.


*What?*
So here are the key ideas/features of the foundation:


   - We are calling it “Continuous Delivery Foundation” (CDF), and it will
   have a broader charter. It will house not just Jenkins but other
   open-source projects in this space. Through the CDF, we want to create
   open-source solutions collectively addressing the whole software
   development lifecycle, to foster and sustain the ecosystem of open-source,
   vendor-neutral projects through collaborations and interoperability, then
   finally to