Skip to content
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

Closed
jdumars opened this Issue Jun 24, 2018 · 14 comments

Comments

@jdumars
Copy link
Member

jdumars commented Jun 24, 2018

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:

SIG Reviewed by Notes
SIG Auth @jbeda @philips @michelleN subprojects being enumerated (ref: kubernetes/community#2525)
SIG Service Catalog @philips @michelleN followup to use new charter template
SIG Cloud Provider reviewed via thread, needs followup to use new charter template
SIG CLI @pwittrock @bgrant0607 @spiffxp
SIG Instrumentation @derekwaynecarr @spiffxp
SIG Scalability @spiffxp @timothysc tech leads need to be enumerated in sigs.yaml
SIG Cluster Lifecycle @jbeda @bgrant0607
SIG Node @philips @bgrant0607
SIG Storage @philips @quinton-hoole
SIG VMWare @philips @smarterclayton @spiffxp
SIG Scheduling @quinton-hoole @derekwaynecarr
SIG IBMCloud @spiffxp @derekwaynecarr
SIG Testing @brendandburns @dims
SIG Multicluster @timothysc @spiffxp
SIG Apps @bgrant0607 @smarterclayton
SIG Architecture @jbeda @bgrant0607 (also @smarterclayton @brendandburns )
SIG AWS @philips @jbeda @spiffxp under review
SIG Windows @philips @spiffxp needs subprojects / areas of code listed
SIG Release @timothysc @spiffxp
SIG UI @dims @spiffxp
SIG Nework @dims @philips
SIG API Machinery @smarterclayton @bgrant0607
SIG Autoscaling @spiffxp @brendandburns @michelleN
SIG Contributor Experience @spiffxp @sarahnovotny

CHARTERS UNDER SC REVIEW:

SIG Reviewed by Notes
SIG Docs @bgrant0607 @jbeda @spiffxp @pwittrock has picked up 2019-01-15

CHARTERS MERGED WITHOUT/LIMITED SC REVIEW:

SIG SC liasons Notes
SIG PM @sarahnovotny @spiffxp Many differences from the template needing reconciliation, also no SC review AFAICT, see this PR

CHARTERS WE ARE HOLDING ON:

SIG Reviewed by Notes
SIG Azure @brendandburns @sarahnovotny was drafted prior to template, intend to fold into SIG Cloud Provider
SIG Big Data @bgrant0607 @michelleN @spiffxp @timothysc should be a WG
SIG GCP @bgrant0607 @sarahnovotny intend to fold into SIG Cloud Provider
SIG OpenStack @spiffxp @dims intend to fold into SIG Cloud Provider

CHARTER ISSUES/RECOMMENDATIONS:

  • SIG membership standardized
  • Diversity and inclusion statement

TEMPLATE CHANGES REQUESTED:

  • Clear direction on how unresponsive chairs are removed, especially when a low number exists - see this comment
  • Separation of SIG and Sub-project roles - see this PR
  • Something about how leadership lifecycle is managed - see this issue

SIGS TO BE SUNSET:

SIG Assigned to Notes
SIG Cluster Ops @sarahnovotny @michelleN To be decommissioned per kubernetes/community#2031

@jdumars jdumars self-assigned this Jun 24, 2018

@jdumars jdumars added this to Backlog in Steering via automation Jun 24, 2018

@jdumars jdumars moved this from Backlog to In Progress in Steering Jun 24, 2018

@jdumars

This comment has been minimized.

Copy link
Member Author

jdumars commented Jun 26, 2018

For context, this was discussed at the 6/20/18 meeting and the 6/6/18 meeting

@jdumars

This comment has been minimized.

@jdumars

This comment has been minimized.

Copy link
Member Author

jdumars commented Jul 16, 2018

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."

@jdumars

This comment has been minimized.

Copy link
Member Author

jdumars commented Jul 24, 2018

@spiffxp

This comment has been minimized.

Copy link
Member

spiffxp commented Aug 9, 2018

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

@spiffxp

This comment has been minimized.

Copy link
Member

spiffxp commented Aug 29, 2018

Rolled through and updated again.

@spiffxp

This comment has been minimized.

Copy link
Member

spiffxp commented Aug 31, 2018

I reconciled a number of merged charters and reviewer assignments with the spreadsheet we used to initially assign SC reviewers.

@spiffxp

This comment has been minimized.

Copy link
Member

spiffxp commented Oct 5, 2018

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.

@spiffxp

This comment has been minimized.

Copy link
Member

spiffxp commented Oct 11, 2018

Updated the issue and spreadhseet based on what I surveyed within kubernetes/community

@spiffxp

This comment has been minimized.

Copy link
Member

spiffxp commented Oct 24, 2018

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.

@jdumars

This comment has been minimized.

Copy link
Member Author

jdumars commented Oct 29, 2018

kubernetes/community#2804 is probably ready for SC review given the lack of feedback

@justaugustus

This comment has been minimized.

Copy link
Member

justaugustus commented Nov 22, 2018

  • SIG Release charter has merged after review from Aaron and Tim St. Clair - kubernetes/community#2919
  • SIG PM charter - next on the list to revise for me; hopefully before KubeCon, worst case, by EOY
  • SIG Azure charter - I'm not going to bother refactoring this one, as the time would be better spent getting the SIG rolled under SIG Cloud Provider
@timothysc

This comment has been minimized.

Copy link
Member

timothysc commented Mar 5, 2019

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.

@timothysc timothysc added this to the April 2019 milestone Mar 11, 2019

@timothysc

This comment has been minimized.

Copy link
Member

timothysc commented Mar 13, 2019

I will go through existing charters and see what needs to be changed.

@timothysc timothysc closed this Mar 13, 2019

Steering automation moved this from In Progress to Done Mar 13, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.