diff options
Diffstat (limited to 'github-management')
| -rw-r--r-- | github-management/README.md | 2 | ||||
| -rw-r--r-- | github-management/kubernetes-repositories.md | 19 | ||||
| -rw-r--r-- | github-management/new-membership-procedure.md | 2 | ||||
| -rw-r--r-- | github-management/org-owners-guide.md | 3 |
4 files changed, 2 insertions, 24 deletions
diff --git a/github-management/README.md b/github-management/README.md index 8ccb566b..ba5024e2 100644 --- a/github-management/README.md +++ b/github-management/README.md @@ -72,7 +72,6 @@ project | [kubernetes](https://github.com/kubernetes) | Core | | [kubernetes-client](https://github.com/kubernetes-client) | API Client Libraries | | [kubernetes-csi](https://github.com/kubernetes-csi) | Container Storage Interface Components | -| [kubernetes-incubator](https://github.com/kubernetes-incubator) | Legacy Incubator Projects | | [kubernetes-retired](https://github.com/kubernetes-retired) | Retired/Archived Projects | | [kubernetes-security](https://github.com/kubernetes-security) | Private Security Fix Mirror | | [kubernetes-sigs](https://github.com/kubernetes-sigs) | SIG-related Projects | @@ -86,6 +85,7 @@ project | [kubernetes-extensions](https://github.com/kubernetes-extensions) | | | [kubernetes-federation](https://github.com/kubernetes-federation) | | | [kubernetes-graveyard](https://github.com/kubernetes-graveyard) | kubernetes-retired should be used instead going forward | +| [kubernetes-incubator](https://github.com/kubernetes-incubator) | Earlier used for legacy incubator projects | | [kubernetes-incubator-retired](https://github.com/kubernetes-incubator-retired) | kubernetes-retired should be used instead going forward | | [kubernetes-providers](https://github.com/kubernetes-providers) | | | [kubernetes-sidecars](https://github.com/kubernetes-sidecars) | | diff --git a/github-management/kubernetes-repositories.md b/github-management/kubernetes-repositories.md index c6b074f4..e326bc11 100644 --- a/github-management/kubernetes-repositories.md +++ b/github-management/kubernetes-repositories.md @@ -164,25 +164,6 @@ circumstances (e.g. a code of conduct violation). ## FAQ -**My project is currently in kubernetes-incubator, what is going to happen to -it?** - -Nothing. We’ll grandfather existing projects and they can stay in the incubator -org for as long as they want to. We expect/hope that most projects will either -move out to ecosystem, or into SIG or Core repositories following the same -approval process described below. - -**My project wants to graduate from incubator, how can it do that?** - -Either approval from a SIG to graduate to a SIG repository, or approval from -SIG-Architecture to graduate into the core repository. - -**My incubator project wants to go GA, how can it do that?** - -For now, the project determines if and when it is GA. For the future, we may -define a cross Kubernetes notion of GA for core and sig repositories, but that’s -not in this proposal. - **My project is currently in core, but doesn’t seem to fit these guidelines, what’s going to happen?** diff --git a/github-management/new-membership-procedure.md b/github-management/new-membership-procedure.md index f48f1df0..ce844d1c 100644 --- a/github-management/new-membership-procedure.md +++ b/github-management/new-membership-procedure.md @@ -47,7 +47,7 @@ required to be eligible to sponsor a new member. These requirements are: - Sponsors must be a member of the org they are attempting to sponsor for. - For example, if the membership being requested is for kubernetes-incubator, + For example, if the membership being requested is for kubernetes-sigs, then the sponsor should be a member of either that org, or main Kubernetes org (as members of the main org have implicit membership in other orgs). diff --git a/github-management/org-owners-guide.md b/github-management/org-owners-guide.md index 272c7cea..ea284b52 100644 --- a/github-management/org-owners-guide.md +++ b/github-management/org-owners-guide.md @@ -75,9 +75,6 @@ for all orgs going forward. Notable discrepancies at the moment: `kubernetes-sig-foo-pr-reviews` teams and are intended mostly as a fallback notification mechanism when requested reviewers are being unresponsive. Ideally OWNERS files can be used in lieu of these teams. -- `admins-foo` and `maintainers-foo` teams as used by the kubernetes-incubator - org. This was a mistake that swapped the usual convention, and we would like - to rename the team ### Structure and Process |