Re: SIG scopes
Joe Beda <jbeda@...>
One other angle/comment: We have a model right now a SIG owning some level over oversight over a project. But the mapping may not be that clean. A project may be primarily in a specific space but there may be aspects of that that cross all the lines. (example is security, but there are others, I’m sure). We need to find the right way to involve the right SIGs at the right times.
From: <cncf-toc@...> on behalf of Alex Chircop <alex.chircop@...>
Having gone through some of the debates when we first put the SIG charters together, there are a few other considerations I'd like to add to the debate :-)
In general I think SIGs should bias towards having a broader rather than a narrower scope:
This was part of the original governance/operating model for the SIGs: Each SIG was to have a number of co-chairs - specifically to allow load sharing and continuity over time. The focus for specific projects/initiatives is then applied to the tech lead role - of which there can be as many as needed based on the workload/diversity of topics in the SIG scope. This allows the tech leads to be focused on a specific area, whilst the co-chairs help manage & co-ordinate.
Of course, nothing is static and ideas & orgs evolve over time, so there are always changes that can be applied.
Also, agree with the points about getting content around SIGs on the website (which will help participation), better (and more explicit) management of SIG priorities (which I guess should also reflect the TOC priorities).
From: cncf-toc@... <cncf-toc@...> on behalf of Quinton Hoole via Lists.Cncf.Io <quinton=hoole.biz@...>
Sent: 07 November 2019 22:01
To: Liz Rice <liz@...>
Cc: cncf-toc@... <cncf-toc@...>
Subject: Re: [cncf-toc] SIG scopes
This is exactly the discussion I hoped to spark, so I definitely don't mind your debate :-)
Michelle and I happened to have a chat about this today, as she mentioned, and will discuss further with the TOC.
In summary, my personal opinion is that we need to:
1. Agree what the scope of the CNCF is.
2. Partition that scope into bite-sized chunks that cover the entire scope (these were the original 7 proposed SIGs).
3. Make sure that each of the chunks is appropriately taken care of. Over time the details of "appropriately taken care of" will clearly change, as hot spots come and go (FaaS, Service Mesh, Secure Containers, Edge, ..... ), projects come and go, etc. In the extreme, a chunk may be completely dormant for a period of time, or temporarily focussed on one specific subset. But it's still a chunk of the logical total CNCF scope.
There are many different ways to execute on the above. The 7 originally proposed SIG's and their scopes are one way.
Other ways are fine, as long as they achieve the overall goal over time.
There are several possible ways to implement the above strategy.
On Thu, Nov 7, 2019 at 11:01 AM Liz Rice <liz@...> wrote: