Oh, now I understand where the confusion arose.  There is a link in the intro of the main document to a description of the differences between Kubernetes SIGs and CNCF SIGS. That’s where the following wording is:

“CNCF SIGS: Created by the TOC”

https://docs.google.com/document/d/1oSGhx5Hw7Hs_qawYB46BvRSPh0ZvFoxvHx-NWaf5Nsc/edit

But I agree with you Diane – I should add it to the body of the doc too, to clarify.

Q

From: Quinton Hoole <quinton.hoole@...>
Date: Thursday, January 31, 2019 at 07:29
To: Diane Mueller-Klingspor <dmueller@...>
Cc: "cncf-toc@..." <cncf-toc@...>, Erin Boyd <eboyd@...>, Sarah Allen <sarahallen@...>, Bryan Cantrill <bryan@...>, Chris Aniszczyk <caniszczyk@...>, Matt Farina <matt.farina@...>, Alex Chircop <alex.chircop@...>, Alexis Richardson <alexis@...>
Subject: Re: [cncf-toc] CNCF SIGs Proposal

My apologies Diane – I just reread the Operating Model section and you’re right - it’s not sufficiently clear on the point you raised.  I will add some wording to the effect of my email reply below.

Regards

Q

From: <cncf-toc@...> on behalf of Diane Mueller-Klingspor <dmueller@...>
Date: Thursday, January 31, 2019 at 06:54
To: Quinton Hoole <quinton.hoole@...>
Cc: "cncf-toc@..." <cncf-toc@...>, Erin Boyd <eboyd@...>, Sarah Allen <sarahallen@...>, Bryan Cantrill <bryan@...>, Chris Aniszczyk <caniszczyk@...>, Matt Farina <matt.farina@...>, Alex Chircop <alex.chircop@...>, Alexis Richardson <alexis@...>
Subject: Re: [cncf-toc] CNCF SIGs Proposal

Quinton, 

If you are referring to this one sentence:

"The TOC makes use of this input to act as an informed and effective executive board to select and promote appropriate CNCF projects and practices, and to disseminate high quality information to end users and the cloud-native community in general." as the section discussion the creation/instantiation/proposal process for new SIGs"

I'd like a bit more clarity. If someone from the community (outside of the TOC) wishes to propose a SIG, what it the process? Or is it just the purview of the TOC on know when a new SIG should be created - then that would be nice to have clarified further.

If there's another section of the document, that you feel clarifies this SIG instantiation/proposal process, please point me in the right direction. I'm just not finding it.

Thanks for your help,

Diane Mueller
@openshiftcommon

On Thu, Jan 31, 2019 at 6:16 AM Quinton Hoole <quinton.hoole@...> wrote:

Thanks Diane

I think that’s adequately covered in the doc - the TOC creates and approves SIG’s.  If anyone believes we need to create more SIG’s, they should, by implication, ask the TOC to do that.  The current intention is to keep the number of SIGs relatively small, at least initially, and make sure they’re all highly effective before expanding the number of SIG's.

Q

From: <cncf-toc@...> on behalf of Diane Mueller-Klingspor <dmueller@...>
Date: Thursday, January 31, 2019 at 05:27
To: Quinton Hoole <quinton.hoole@...>
Cc: "cncf-toc@..." <cncf-toc@...>, Erin Boyd <eboyd@...>, Sarah Allen <sarahallen@...>, Bryan Cantrill <bryan@...>, Chris Aniszczyk <caniszczyk@...>, Matt Farina <matt.farina@...>, Alex Chircop <alex.chircop@...>, Alexis Richardson <alexis@...>
Subject: Re: [cncf-toc] CNCF SIGs Proposal

Quinton et al,

Would it be possible to ask for a section in the Operator Model on how one goes about proposing a new SIG and the process for getting it approved?

(or if there is documentation on this topic elsewhere, reference/link to it in an appendix)?

Kind Regards,

Diane Mueller

Director, Community Development

Red Hat 

@openshiftcommon

On Wed, Jan 30, 2019 at 10:47 PM Quinton Hoole <quinton.hoole@...> wrote:

Greetings to the new TOC

Late last year Alexis kicked off a public discussion regarding forming CNCF SIG’s (initially referred to as Categories).  Since then a few of us have collaborated on soliciting further input, addressing all the comments, and producing a finalish proposal for consideration by the TOC.

Please give it a read and we can decide how to proceed at the next meeting this Tue, Feb 5

https://docs.google.com/document/d/1mt1LH1QJgwA91A6x-DEdjg4ZOXrOnxxc1d2xhq4Hq3I/edit?usp=sharing

Q

From: Alexis Richardson <alexis@...>
Date: Tuesday, January 15, 2019 at 07:58
To: Alex Chircop <alex.chircop@...>
Cc: Erin Boyd <eboyd@...>, Sarah Allen <sarahallen@...>, Bryan Cantrill <bryan@...>, Chris Aniszczyk <caniszczyk@...>, Quinton Hoole <quinton.hoole@...>, Matt Farina <matt.farina@...>
Subject: Re: CNCF TOC SIGs Doc

can you put this link into the main doc as a comment?

On Tue, Jan 15, 2019 at 3:57 PM Alex Chircop <alex.chircop@...> wrote:

Hi Alexis,

Following our initial discussion in Seattle, Quinton and I had a discussion on this.   I captured the notes and applied them to the operating model.   I decided to make a copy of the doc and apply the changes to operating model section only - the current doc is hard to process due to the number of comments.

Here is the amended operating model content: https://docs.google.com/document/d/1ySri5jVrPaJjTJ_tZnDzcc4Xmcm4uKoUrHT6lVO6Pcw/edit#heading=h.6cl6hmsbz9fv

Kind Regards,

Alex

---

From: Alexis Richardson <alexis@...>
Sent: 09 January 2019 19:36
To: Erin Boyd; Sarah Allen
Cc: Bryan Cantrill; Chris Aniszczyk; Quinton Hoole; Alex Chircop; Matt Farina
Subject: CNCF TOC SIGs Doc

 

hi all

happy 2019!

how's this doc looking?  I daren't look.  can we show the toc an update next week?

a

On Mon, Dec 10, 2018 at 5:35 AM Alexis Richardson <alexis@...> wrote:

+sarah

On Fri, 7 Dec 2018, 13:35 Erin Boyd, <eboyd@...> wrote:

Sounds good.

Please feel free to catch me on Slack.

Erin

On Wed, Dec 5, 2018 at 11:18 PM Alexis Richardson <alexis@...> wrote:

Thank you Erin.  Let's try and sync 1-1 during the week 

On Thu, 6 Dec 2018, 00:42 Erin Boyd, <eboyd@...> wrote:

HI Alexis,

I think I am speaking on a panel at this time.

I can collaborate in the document.

Sorry about that.

Thanks,

Erin

On Tue, Dec 4, 2018 at 11:46 AM Alexis Richardson <alexis@...> wrote:

more details » CNCF TOC meeting re SIGs Doc meeting to discuss the Categories and SIGs doc identify and divide up work tasks to clean up draft doc. eg: we agree a new section plan and each take one section? or something When Mon Dec 10, 2018 3:30pm – 4:10pm Mountain Time - Denver Where lobby of the Sheraton Grand Seattle (map) Joining info meet.google.com/hud-jxti-yvh Or dial: +1 929-299-3513  PIN: 706587657# Calendar eboyd@... Who • Alexis Richardson - organizer • bryan@... • Matt Farina • eboyd@... • alex.chircop@... • quinton.hoole@... • Chris Aniszczyk Going (eboyd@...)?   Yes - Maybe - No    more options »

Invitation from Google Calendar You are receiving this email at the account eboyd@... because you are subscribed for invitations on calendar eboyd@.... To stop receiving these emails, please log in to https://www.google.com/calendar/ and change your notification settings for this calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn More.

--

Kind Regards,

Diane Mueller

Director, Community Development

Red Hat OpenShift

@openshiftcommons

We have more in Common than you know, learn more at http://commons.openshift.org

--

Kind Regards,

Diane Mueller

Director, Community Development

Red Hat OpenShift

@openshiftcommons

We have more in Common than you know, learn more at http://commons.openshift.org