I'll make this more clear but it's easier if we have projects just put forth a formal project proposal and then request a community presentation slot. The barrier is a bit higher to entry to do so but helps us be more organized imho. We will discuss tomorrow.

On Mon, Jul 1, 2019 at 7:15 PM Erin Boyd <eboyd@...> wrote:

Hello TOC,

I have an additional item to add to the backlog (Strimzi):

https://github.com/cncf/toc/issues/138 

So there was a transition period for Sandbox last Fall where we decided that they didn't need to do a proposal, just the issue & the presentation. I think that is where this poor project got caught in the changes (as well as Keycloak)

Originally, the process was

1) Open an issue to present

2) Open a PR for the project (more formal / exhaustive)

3) Present at the meeting

4) Get sponsorship (hopefully)

Then it changed to:

1) Open an issue to present

2) Present at the meeting

3) Get sponsorship (hopefully)

These steps were updated and published here:

Sandbox Entry Requirements

• Require 2 TOC sponsors to enter the sandbox
• Require presentation to the TOC community twice-a-month meeting
• Require adherence to CNCF IP Policy (including trademark transferred)
• Require sandbox projects to list their sandbox status prominently on website/readme\

It was my understanding that the sandbox projects no longer needed to do the full PR as we weren't going to do a due diligence on Sandbox.

Can anyone please clarify the proper process for me?

Thanks,

Erin

On Mon, Jul 1, 2019 at 3:08 PM Chris Aniszczyk <caniszczyk@...> wrote:

We will be meeting tomorrow:

https://docs.google.com/presentation/d/10quFrj3JWTR3PI32RNblIthSKKPDdUSvmdi8UN2kbbg/edit#slide=id.g25ca91f87f_0_0

https://docs.google.com/document/d/1jpoKT12jf2jTf-2EJSAl4iTdA7Aoj_uiI19qIaECNFc/edit#

We will cover an update on CNCF SIGs (app delivery), community/project backlog, meeting schedule updates and go over the archiving rkt proposal.

--

Chris Aniszczyk (@cra) | +1-512-961-6719

--

Erin A. Boyd

Senior Principal Software Engineer, OCTO

Red Hat

eboyd@...   

--

Chris Aniszczyk (@cra) | +1-512-961-6719