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

TLs are approving KEPs

This commit is contained in:
Sergey Kanzhelev 2023-02-08 19:38:27 +00:00
parent 84e98a77f3
commit 0037f98e6a
2 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -88,8 +88,9 @@ Subproject contributors (as applicable).
- *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 - *SHOULD* identify, track, and maintain the SIGs enhancements for current
release and serve as point of contact for the release team, but *MAY* delegate release and serve as point of contact for the release team. If Technical Leads
to another Lead to fulfill these responsibilities are present in a SIG, Technical Leads *MUST* approve the content of the KEP,
while both chairs and TLs *MUST* maintain the KEPs metadata
- *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
@ -121,6 +122,7 @@ curation from other SIG participants
- Establish new subprojects - Establish new subprojects
- Decommission existing subprojects - Decommission existing subprojects
- Resolve X-Subproject technical issues and decisions - Resolve X-Subproject technical issues and decisions
- Review and approve KEPs
- Number: 2-3 - Number: 2-3
- Membership tracked in [sigs.yaml] - Membership tracked in [sigs.yaml]
- Role description in [technical-lead.md] - Role description in [technical-lead.md]

2
contributors/chairs-and-techleads/technical-lead.md
View File

@ -36,6 +36,8 @@ Expectations of Technical Leads are:
right decisions. right decisions.
- They actively identify risk and maintain a high level of trust with other - They actively identify risk and maintain a high level of trust with other
members of the SIG. members of the SIG.
- They are responsible for reviewing and approving KEPs for releases
or rejecting KEPs based on technical vision of a SIG.
Technical Leads have the responsibility to track the technical quality of the Technical Leads have the responsibility to track the technical quality of the
deliverables of the team if a roadmap exists. They are volunteering to provide deliverables of the team if a roadmap exists. They are volunteering to provide