Re: CNCF SIG Contributor Experience Proposal
On the call today you suggested pairing down the scope of the SIG because there is so much proposed. It occured to me that contributing to the CNCF can mean a lot of things. To large areas are contributions to SIGs and to projects. In your opinion, should the SIG initially be limited to one area of focus (and if so which one) or to focus on both?
For those not familiar... CNCF SIGs are a little different from Kubernetes SIGs. Kubernetes SIGs own and are responsible for code within Kubernetes. CNCF SIGs are an extension of the TOC:
Each project has their own governance model and contribution process. Where Kubernetes SIGs have a solid line or ownership to Kubernetes code, CNCF TOC SIGs have a dotted line relationship to CNCF Projects who own the code and governance. The dotted line relationship means that projects do work with and connect to a SIG but the ownership model is different.
On Tue, Jan 21, 2020, at 12:09 PM, Paris Pittman via Lists.Cncf.Io wrote: