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

(steering/governance): add subproject lead section to SIG governance 

Signed-off-by: Nabarun Pal <pal.nabarun95@gmail.com>
This commit is contained in:
Nabarun Pal 2023-08-10 17:11:01 +05:30
parent 4e77953f54
commit 9cf733b121
No known key found for this signature in database
GPG Key ID: E71158161DF2A2CB
1 changed files with 31 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -136,15 +136,39 @@ the acceptance of that SIG or Subproject.
Additional information on the Tech Lead role can be found in Additional information on the Tech Lead role can be found in
[technical-lead.md]; within the [Chair & TL Contributor Documentation]. [technical-lead.md]; within the [Chair & TL Contributor Documentation].
#### Subproject Owner #### Subproject Lead
**Note:** This is a generalized high-level description of the role, and the
specifics of the subproject lead role's responsibilities and related
processes *MUST* be defined for individual SIGs or subprojects. The process
for becoming an Subproject Lead should be defined in the SIG charter of the
SIG owning the subproject.
Subproject Leads are the technical authority for a subproject in the Kubernetes
project. They *MUST* have demonstrated both good judgement and responsibility
towards the health of that subproject.
- Number: 2+ - Number: 2+
- Scoped to a subproject defined in [sigs.yaml] - Membership tracked in [sigs.yaml] via *subproject.leads* entry and scoped to a subproject
- Seed leads and contributors established at subproject founding - *MUST* set technical direction and make or approve design decisions for their subproject - either directly or through delegation
- *SHOULD* be an escalation point for technical discussions and decisions in - *MUST* mentor and guide approvers, reviewers, and contributors to the subproject.
the subproject - *MUST* maintain components, review, shepherd and approve proposals for enhancing areas owned by the subproject
- *MUST* actively participate in triaging issues and reviewing PRs
- *SHOULD* be an escalation point for technical discussions and decisions in the subproject
- *SHOULD* set milestone priorities or delegate this responsibility - *SHOULD* set milestone priorities or delegate this responsibility
- Membership tracked in [sigs.yaml] via links to OWNERS files - *SHOULD* ensure a healthy process for discussion and decision making is in place.
- *MAY* make decisions to resolve conflicts
#### Subproject Owner
- *Optional if and only if Subproject Leads are defined for the subproject*
- Number: 2+
- Membership tracked in [sigs.yaml] via links to OWNERS files
- Scoped to a subproject defined in [sigs.yaml]
- *MUST* actively participate in triaging issues and reviewing PRs
- *SHOULD* mentor and guide contributors of the subproject
- *SHOULD* help the subproject leads (if defined) in their responsibilities
#### All Leads #### All Leads
@ -175,7 +199,7 @@ governance requirements, including defining more roles to sustain the group. If
a SIG needs to change the Chair and Tech Lead position to include or remove a SIG needs to change the Chair and Tech Lead position to include or remove
duties, this needs to be approved by the Steering Committee. Newly created roles duties, this needs to be approved by the Steering Committee. Newly created roles
that don't assume any responsibility of Chair and/or Tech Lead should follow that don't assume any responsibility of Chair and/or Tech Lead should follow
the governing processes in the SIGs charter. the governing processes in the SIGs charter.
Example of SIG roles created to help operations: Example of SIG roles created to help operations: