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

Merge pull request #3728 from Disper/patch-1 

Removes a dead link to the sig-short-template
This commit is contained in:
Kubernetes Prow Robot 2019-07-22 07:08:52 -07:00 committed by GitHub
parent 2c01ad69f7 a23a9cb895
commit ae5218eb55
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
governance.md
View File

@ -69,13 +69,10 @@ Each SIG must have a charter that specifies its scope (topics,
subsystems, code repos and directories), responsibilities, areas of subsystems, code repos and directories), responsibilities, areas of
authority, how members and roles of authority/leadership are authority, how members and roles of authority/leadership are
selected/granted, how decisions are made, and how conflicts are selected/granted, how decisions are made, and how conflicts are
resolved. See the [SIG charter process] for details on how charters are managed. resolved. See the [SIG charter process] for details on how charters are managed.
A [short template] for intra-SIG governance has been SIGs should be relatively free to customize or change how they operate,
developed in order to simplify SIG creation, and additional templates within some broad guidelines and constraints imposed by cross-SIG processes
are being developed, but SIGs should be relatively free to customize (e.g., the release process) and assets (e.g., the kubernetes repo).
or change how they operate, within some broad guidelines and
constraints imposed by cross-SIG processes (e.g., the release process)
and assets (e.g., the kubernetes repo).
A primary reason that SIGs exist is as forums for collaboration. A primary reason that SIGs exist is as forums for collaboration.
Much work in a SIG should stay local within that SIG. However, SIGs Much work in a SIG should stay local within that SIG. However, SIGs
@ -213,7 +210,6 @@ All contributors must sign the CNCF CLA, as described [here](CLA.md).
[sig governance]: /committee-steering/governance/sig-governance.md [sig governance]: /committee-steering/governance/sig-governance.md
[owners]: /community-membership.md#subproject-owner [owners]: /community-membership.md#subproject-owner
[sig charter process]: /committee-steering/governance/README.md [sig charter process]: /committee-steering/governance/README.md
[short template]: /committee-steering/governance/sig-governance-template-short.md
[kubernetes repository guidelines]: /github-management/kubernetes-repositories.md [kubernetes repository guidelines]: /github-management/kubernetes-repositories.md
[working group governance]: /committee-steering/governance/wg-governance.md [working group governance]: /committee-steering/governance/wg-governance.md
[user group governance]: /committee-steering/governance/ug-governance.md [user group governance]: /committee-steering/governance/ug-governance.md