Re: Incubation discussion

alexis richardson


Yes that would be implied: so full transfer isn't obligatory on entering Incubation. At least for now.

In my view no project would exit Incubation if the project leads were opposed to continuing. So this rule is arguably an explicit version of a hidden assumption.


On Wed, 13 Apr 2016 20:22 Mark Peek, <markpeek@...> wrote:
One thing this implies to me is we will not be transferring any project assets to the CNCF until the project exits incubation. Otherwise it would be harder to disentangle the project should either side decide not to join. Is this the right assumption? If so, are we ok with having incubation projects in the CNCF but without asset ownership?


From: <cncf-toc-bounces@...> on behalf of Robert Lalonde via cncf-toc <cncf-toc@...>
Reply-To: Robert Lalonde <rlalonde@...>
Date: Wednesday, April 13, 2016 at 12:00 PM
To: Alexis Richardson <alexis@...>
Cc: "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] Incubation discussion

seems very reasonable.


On Apr 13, 2016, at 2:58 PM, Alexis Richardson via cncf-toc <cncf-toc@...> wrote:

Today we had some verbal +1s for the following suggestion:

1. The time when becoming a CNCF Project is irrevocable is when a project is promoted from Incubation 
2. Prior to this a project may choose to leave, or be asked to leave.

The TOC might change this rule in the future but for now it has a clear rationale: it enables new projects to have a safety valve.  Before the TOC has finalised its modus operandi and how we help CNCF projects, we want projects to join CNCF and help us shape our model. So we are asking projects to join despite this uncertainty. In return we provide a safety valve. 

In effect we are saying to projects "tell us when you are ready to leave Incubation".

Comments please. Feel free to rewrite this. Indication of support will not be taken as a formal vote.  This email thread is for discussion only & towards creating language that we can put to a vote in the future. 

cncf-toc mailing list

Join to automatically receive all group messages.