create README, so when merged this won't be a "proposal"#3
create README, so when merged this won't be a "proposal"#3ultrasaurus wants to merge 4 commits intoquinton-hoole:2019-02-05-cncf-sigsfrom
Conversation
|
fixed PR so it goes to 2019-02-05-cncf-sigs (which was my original intent) -- note that there are some unintended whitespace diffs (which Github diff UI can ignore if you check the box) |
|
@quinton-hoole @caniszczyk should I rebase this on master and submit PR there? please feedback, if there's anything in here that is problematic in any way... happy to learn more about TOC process and abandon this if it's not what y'all want :) |
| ## Responsibilities & Empowerment of SIGs | ||
|
|
||
| It is the desire of the TOC that the CNCF SIGs, under guidance from the TOC, provide high-quality technical expertise, unbiased information and proactive leadership within their category. 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. SIGs explicitly have no direct authority over CNCF projects. In particular, the creation of CNCF SIG’s does not change the existing, successfully practiced [charter](https://github.com/cncf/foundation/blob/master/charter.md) goal that "Projects.. will be ‘lightly’ subject to the Technical Oversight Committee". | ||
| It is the desire of the TOC that the CNCF SIGs, under guidance from the TOC, provide high-quality technical expertise, unbiased information and proactive leadership within their category. 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. SIGs explicitly have no direct authority over CNCF projects. In particular, the creation of CNCF SIG’s does not change the existing, successfully practiced [charter](https://github.com/cncf/foundation/blob/master/charter.md) goal that "Projects.. will be ‘lightly’ subject to the Technical Oversight Committee". |
There was a problem hiding this comment.
It's not clear that anything changed in this chunk?
There was a problem hiding this comment.
only whitespace -- can change my editor settings to not remove trailing whitespace when resubmitting
| @@ -0,0 +1,14 @@ | |||
| ## Initial SIGS | |||
There was a problem hiding this comment.
Why is this removed from the main doc, and not linked from anywhere?
This is the list of SIGs that was approved by the TOC. I think it should:
- remain the canonical list of SIGs, clearly indicated as such,
- be updated to indicate the TOC liaisons that have been appointed to each by the TOC.
- be updated to link to the details of each SIG as those get formulated (or indicate that the SIG is still nascent).
- be updated if and when SIG's are renamed, split, merged etc.
I would suggest splitting out the formatting-only changes into a separate PR, and then we can do the other restructuring/updates separately.
2 participants
refactored for readability post merging (this include prior formatting PRs)