Skip to content

Commit 405eec2

Browse files
authored
Merge pull request #1799 from spiffxp/org-team-guidance
Add team guidance section to org-owners-guide
2 parents d853d7d + 270cacf commit 405eec2

File tree

1 file changed

+30
-1
lines changed

1 file changed

+30
-1
lines changed

Diff for: org-owners-guide.md

+30-1
Original file line numberDiff line numberDiff line change
@@ -47,8 +47,37 @@ Note, this list is subject to change.
4747
There are more organization names that we are squatting on with possible future
4848
intentions. [For more details please see community issue #1407](https://github.com/kubernetes/community/issues/1407).
4949

50+
## Team Guidance
51+
52+
Each organization should have the following teams:
53+
54+
- teams for each repo `foo`
55+
- `foo-admins`: granted admin access to the `foo` repo
56+
- `foo-maintainers`: granted write access to the `foo` repo
57+
- `foo-reviewers`: granted read access to the `foo` repo; intended to be used as
58+
a notification mechanism for interested/active contributors for the `foo` repo
59+
- a `bots` team
60+
- should contain bots such as @k8s-ci-robot and @linuxfoundation that are
61+
neccessary for org and repo automation
62+
- an `owners` team
63+
- should be populated by everyone who has `owner` privileges to the org
64+
- gives users the opportunity to ping owners as a group rather than having to
65+
search for individuals
66+
67+
**NB**: Not all organizations in use today currently follow this team guidance.
68+
We are looking to coalesce existing teams towards this model, and use this model
69+
for all orgs going forward. Notable discrepancies at the moment:
70+
71+
- `foo-reviewers` teams are considered a historical subset of
72+
`kubernetes-sig-foo-pr-reviews` teams and are intended mostly as a fallback
73+
notification mechanism when requested reviewers are being unresponsive. Ideally
74+
OWNERS files can be used in lieu of these teams.
75+
- `admins-foo` and `maintainers-foo` teams as used by the kubernetes-incubator
76+
org. This was a mistake that swapped the usual convention, and we would like
77+
to rename the team
78+
5079
## Repository Guidance
5180

5281
Repositories have additional guidelines and requirements, such as the use of
5382
CLA checking on all contributions. For more details on those please see the
54-
[Kubernetes Template Project](https://github.com/kubernetes/kubernetes-template-project).
83+
[Kubernetes Template Project](https://github.com/kubernetes/kubernetes-template-project).

0 commit comments

Comments
 (0)