-
Notifications
You must be signed in to change notification settings - Fork 61
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
Charters Meta-issue #31
Comments
For context, this was discussed at the 6/20/18 meeting and the 6/6/18 meeting |
email sent to steering@ with a link to the new template: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-charter-template.md Further reference: https://github.com/kubernetes/community/tree/master/committee-steering/governance |
Re: SIG-VMWare (from the mailing list) - @quinton-hoole wrote: "I added a comment to the kubernetes/community#2300 The relationship between sig-vmware, and the cloud-provider-vsphere subproject of sig-cloud provider is unclear to me. It seems that the two efforts should be collapsed into the latter (at least for now), or the compelling reasons for not doing so should be explicitly documented and approved." |
Discussed 20180718 https://youtu.be/I6BwkOA9dn4?t=8m50s |
I just rolled through the description and edited to the best of my ability, but uh, yeah, that was painful, and I'm pretty sure everything after "issues/recommendations" may be out of date because I didn't touch it. Will be discussing during community meeting update today |
Rolled through and updated again. |
I reconciled a number of merged charters and reviewer assignments with the spreadsheet we used to initially assign SC reviewers. |
For charters that have yet to be reviewed, I swapped @quinton-hoole out for @dims. I did the same with the spreadsheet, but for all SIGs regardless of charter status. |
Updated the issue and spreadhseet based on what I surveyed within kubernetes/community |
We talked during steering today about potentially just not doing the work of writing a charter if a sig plans to fold into sig cloud provider. Also a question of whether sig big data should actually be a wg instead. |
kubernetes/community#2804 is probably ready for SC review given the lack of feedback |
|
This issue is so old and stale, I'd like to propose that we close it and open a new issue with the current work items remaining. |
I will go through existing charters and see what needs to be changed. |
This issue is to help organize the work necessary to move SIG/WG charters forward.
Tracking spreadsheet that was the source for this issue
CHARTERS MERGED:
CHARTERS UNDER SC REVIEW:
CHARTERS MERGED WITHOUT/LIMITED SC REVIEW:
CHARTERS WE ARE HOLDING ON:
CHARTER ISSUES/RECOMMENDATIONS:
TEMPLATE CHANGES REQUESTED:
SIGS TO BE SUNSET:
The text was updated successfully, but these errors were encountered: