forked from kubernetes/community
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Copy sig-charter-template to sig-auth
- Loading branch information
Showing
1 changed file
with
66 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,66 @@ | ||
# SIG YOURSIG Charter | ||
|
||
This charter adheres to the conventions described in the [Kubernetes Charter README] and uses | ||
the Roles and Organization Management outlined in [sig-governance]. | ||
|
||
## Scope | ||
|
||
Include a 2-3 sentence summary of what work SIG TODO does. Imagine trying to | ||
explain your work to a colleague who is familiar with Kubernetes but not | ||
necessarily all of the internals. | ||
|
||
### In scope | ||
|
||
Link to SIG section in [sigs.yaml] | ||
|
||
#### Code, Binaries and Services | ||
|
||
- list of what qualifies a piece of code, binary or service | ||
- as falling into the scope of this SIG | ||
- e.g. *clis for working with Kubernetes APIs*, | ||
- *CI for kubernetes repos*, etc | ||
- **This is NOT** a list of specific code locations, | ||
- or projects those go in [sigs.yaml] | ||
|
||
#### Cross-cutting and Externally Facing Processes | ||
|
||
- list of the non-internal processes | ||
- that are owned by this SIG | ||
- e.g. qualifying and cutting a Kubernetes release, | ||
- organizing mentorship programs, etc | ||
|
||
### Out of scope | ||
|
||
Outline of things that could be confused as falling into this SIG but don't or don't right now. | ||
|
||
## Roles and Organization Management | ||
|
||
This sig follows adheres to the Roles and Organization Management outlined in [sig-governance] | ||
and opts-in to updates and modifications to [sig-governance]. | ||
|
||
### Additional responsibilities of Chairs | ||
|
||
- list of any additional responsibilities | ||
- of Chairs | ||
|
||
### Additional responsibilities of Tech Leads | ||
|
||
- list of any additional responsibilities | ||
- of Tech Leads | ||
|
||
### Deviations from [sig-governance] | ||
|
||
- list of other ways this SIG's roles and governance differ from | ||
- the outline | ||
- **If the SIG doesn't have either Chairs or Tech Leads specify that here.** | ||
|
||
### Subproject Creation | ||
|
||
Pick one: | ||
|
||
1. SIG Technical Leads | ||
2. Federation of Subprojects | ||
|
||
[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md | ||
[sigs.yaml]: https://github.com/kubernetes/community/blob/master/sigs.yaml#L1454 | ||
[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md |