New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add charter for CNCF Storage SIG. #234
Add charter for CNCF Storage SIG. #234
Conversation
|
||
# Areas Considered In Scope | ||
|
||
Storage systems and approaches suitable for and commonly used in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like there is a verb or two missing here - doing what with storage systems and approaches? Given the next paragraph maybe it is as simple as "understanding", but maybe also "documenting"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed, will add a verb.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry to be picky @quinton-hoole I would feel more comfortable with casting my vote if we had something to resolve this comment (especially as it could be used as a model charter for other SIGs).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lizrice No problem. I've added a verb to make it a proper sentence. The verbless phrase also grated my grammar education sensibilities :-)
To avoid duplicating what's already in the next paragraph, and the mission statement section, I just added "are considered in scope".
|
||
# Interfaces With Other Related Groups | ||
|
||
* **Kubernetes Storage SIG** - is focussed towards |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: would be nice to have links to the other groups here to help avoid confusion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed, will add.
Projects. | ||
|
||
# Current CNCF Storage Projects | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we expect this list of projects to be updated over time, or is this a snapshot? I am worrying about the maintainability of this list, plus also the list here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed. We need to decide where the canonical mapping from CNCF projects to
CNCF SIGs lives. I'll leave it here for now, but we can move it to a
consolidated location once that has been decided.
@lizrice @quinton-hoole SIG Security created its own repo and put the charter and other stuff there. https://github.com/cncf/sig-security Should we do the same thing here? |
Agreed. Will move.
…On Tue, May 7, 2019, 08:10 Xiang Li ***@***.***> wrote:
@lizrice <https://github.com/lizrice> @quinton-hoole
<https://github.com/quinton-hoole> SIG Security created its own repo and
put the charter and other stuff there.
https://github.com/cncf/sig-security Should we do the same thing here?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#234 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AKNAA6CI3YRZJGTPQP2XJQTPUGLYFANCNFSM4HLCOZYQ>
.
|
Given the shortage of time, I suggest we get the final charter into this repo, and move it to the new one as soon as that's been set up properly. |
@caniszczyk It seems that @quinton-hoole has addressed all comments. How shall we get this Charter approved? Start a vote process? |
|
||
**[Proposed] Co-Chairs:** Alex Chircop, Quinton Hoole, “One Other TBD” | ||
|
||
**[Proposed] Tech Leads:** Saad Ali, Xing Yang, “One Other TBD” |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add Sugu Sougoumarane as Tech Lead
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you please remove [Proposed] -- when merged, that will ratify the co-chairs, right? unless you plan on separate process for finalizing chairs :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes - once the vote is complete, we will remove the [Proposed]
TOC vote kicked off for CNCF Storage SIG: https://lists.cncf.io/g/cncf-toc/message/3247 |
The CNCF Storage SIG has been approved! +1 binding TOC votes (6/9): |
cc @xiang90 @caniszczyk
On Tue, 30 Apr 2019, 13:07 "Li, Xiang, x.li@alibaba-inc.com wrote:
I worked with the Storage WG to create the initial SIG Storage Charter. We now have a draft. We hope to form the SIG before May 20 so that we can announce it at Kubecon.