kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

SIG Governance: Split Chair & TL roles 

Co-authored-by: Sergey Kanzhelev <skanzhelev@google.com>
This commit is contained in:
Bob Killen 2023-02-27 17:11:02 -06:00
parent 8f33d6a4e2
commit 35cbda0d92
1 changed files with 27 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

46
committee-steering/governance/sig-governance.md
View File

@ -39,9 +39,10 @@ The process for setting up a SIG or Working Group (WG) is listed in the
### Notes on Roles ### Notes on Roles
Within this section "Lead" refers to someone who is a member of the union Within this section "Lead" refers to someone who is a member of the union
of a Chair, Tech Lead or Subproject Owner role. There is no one lead to any of a Chair, Tech Lead, or Subproject Owner role. Leads may, and frequently do
Kubernetes community group. Leads have specific decision making power over some hold more than one role. There is no one lead to any Kubernetes community
part of a group and thus additional accountability. Each role is detailed below. group. Leads have specific decision making power over some part of a group
and thus additional accountability. Each role is detailed below.
- Initial roles are defined at the founding of the SIG or Subproject as part - Initial roles are defined at the founding of the SIG or Subproject as part
of the acceptance of that SIG or Subproject. of the acceptance of that SIG or Subproject.
@ -79,17 +80,17 @@ Subproject contributors (as applicable).
### Chair ### Chair
- Number: 2-3 - Number: 2+
- Membership tracked in [sigs.yaml] - Membership tracked in [sigs.yaml]
- If no tech lead role is present, Chair assumes responsibilities from [#tech-lead] section.
In addition, run operations and processes governing the SIG: In addition, run operations and processes governing the SIG:
- *SHOULD* define how priorities and commitments are managed and delegate to other leads as needed - *SHOULD* define how priorities and commitments are managed and delegate to other leads as needed
- *SHOULD* drive charter changes (including creation) to get community buy-in but *MAY* delegate content creation to SIG contributors - *SHOULD* drive charter changes (including creation) to get community buy-in but *MAY* delegate content creation to SIG contributors
- *SHOULD* identify, track, and maintain the SIGs enhancements for current - *MUST* in conjunction with the Tech Leads identify, track, and maintain the
release and serve as point of contact for the release team, but *MAY* delegate metadata of the SIGs enhancements for the current release and serve as
to another Lead to fulfill these responsibilities point of contact for the release team, but *MAY* delegate to other
contributors to fulfill these responsibilities
- *MAY* delegate the creation of a SIG roadmap to other Leads - *MAY* delegate the creation of a SIG roadmap to other Leads
- *MUST* organize a main group meeting and make sure [sigs.yaml] is up to date - *MUST* organize a main group meeting and make sure [sigs.yaml] is up to date
including subprojects and their meeting information but *SHOULD* delegate the including subprojects and their meeting information but *SHOULD* delegate the
@ -104,8 +105,6 @@ Subproject contributors (as applicable).
staff and approve presented content but *MAY* delegate to other contributors staff and approve presented content but *MAY* delegate to other contributors
to create material and present to create material and present
- *MUST* ensure meetings are recorded and made available - *MUST* ensure meetings are recorded and made available
- *MUST* report activity with the community via k-dev mailing list at least
once a quarter (slides, video from kubecon, etc)
- *MUST* coordinate sponsored working group updates to the SIG and the wider - *MUST* coordinate sponsored working group updates to the SIG and the wider
community community
- *MUST* coordinate communication and be a connector with other community - *MUST* coordinate communication and be a connector with other community
@ -117,13 +116,21 @@ curation from other SIG participants
### Tech Lead ### Tech Lead
- *Optional Role*: SIG Technical Leads - Number: 2+
- Establish new subprojects - Membership tracked in [sigs.yaml]
- Decommission existing subprojects - *MUST* Approve & facilitate the creation of new subprojects
- Resolve X-Subproject technical issues and decisions - *MUST* Approve & facilitate decommissioning of existing subprojects
- Number: 2-3 - *MUST* Resolve cross-Subproject and cross-SIG technical issues and decisions
- Membership tracked in [sigs.yaml] or delegate to another Lead as needed
- Role description in [technical-lead.md] - *MUST* in conjunction with the Chairs identify, track, and maintain the
metadata of the SIGs enhancement proposals for the current release and serve
as point of contact for the release team, but *MAY* delegate to other
contributors to fulfill these responsibilities
- *MUST* Review & Approve SIG Enhancement Proposals, but *MAY* delegate to
other contributors to fulfill these responsibilities for individual proposals
Additional information on the Tech Lead role can be found in
[technical-lead.md]; within the [Chair & TL Contributor Documentation].
### Subproject Owner ### Subproject Owner
@ -274,3 +281,4 @@ Issues impacting multiple subprojects in the SIG should be resolved by either:
[PR Wrangler]: https://kubernetes.io/docs/contribute/participate/pr-wranglers/ [PR Wrangler]: https://kubernetes.io/docs/contribute/participate/pr-wranglers/
[Inclusive Open Source Community Orientation course]: https://training.linuxfoundation.org/training/inclusive-open-source-community-orientation-lfc102/ [Inclusive Open Source Community Orientation course]: https://training.linuxfoundation.org/training/inclusive-open-source-community-orientation-lfc102/
[technical-lead.md]: /contributors/chairs-and-techleads/technical-lead.md [technical-lead.md]: /contributors/chairs-and-techleads/technical-lead.md
[Chair & TL Contributor Documentation]: /contributors/chairs-and-techleads/