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

github-management: fix markdown formatting

This commit is contained in:
Nikhita Raghunath 2019-01-02 16:31:46 +05:30
parent 76ecb46f91
commit 60ff4bd4a8
2 changed files with 16 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
github-management/kubernetes-repositories.md
View File

@ -65,7 +65,7 @@ from a central body (e.g. steering committee or sig-architecture)
### Rules for new repositories ### Rules for new repositories
* For now all repos will live in github.com/kubernetes-sigs/\<project-name\>. * For now all repos will live in `github.com/kubernetes-sigs/\<project-name\>`.
* Must contain the topic for the sponsoring SIG - e.g. * Must contain the topic for the sponsoring SIG - e.g.
`k8s-sig-api-machinery`. (Added through the *Manage topics* link on the `k8s-sig-api-machinery`. (Added through the *Manage topics* link on the
repo page.) repo page.)
@ -108,7 +108,9 @@ in official Kubernetes releases. Additionally, the kubernetes.io website, k8s.io
machinery, and other project-wide infrastructure will remain in the kubernetes machinery, and other project-wide infrastructure will remain in the kubernetes
github organization. github organization.
### Goals Create a broader base of repositories than the existing ### Goals
Create a broader base of repositories than the existing
gh/kubernetes/kubernetes so that the project can scale. Present expectations gh/kubernetes/kubernetes so that the project can scale. Present expectations
about the centrality and importance of the repository in the Kubernetes about the centrality and importance of the repository in the Kubernetes
ecosystem. Carries the endorsement of the Kubernetes community. ecosystem. Carries the endorsement of the Kubernetes community.
@ -158,16 +160,16 @@ circumstances (e.g. a code of conduct violation).
When a repository has been deemed eligible for removal, we take the following When a repository has been deemed eligible for removal, we take the following
steps: steps:
* Ownership of the repo is transferred to the [kubernetes-retired] GitHub * Ownership of the repo is transferred to the [kubernetes-retired] GitHub
organization organization
* The repo description is edited to start with the phrase "[EOL]" * The repo description is edited to start with the phrase "[EOL]"
* All open issues and PRs are closed * All open issues and PRs are closed
* All external collaborators are removed * All external collaborators are removed
* All webhooks, apps, integrations or services are removed * All webhooks, apps, integrations or services are removed
* GitHub Pages are disabled * GitHub Pages are disabled
* The repo is marked as archived using [GitHub's archive feature] * The repo is marked as archived using [GitHub's archive feature]
* The removal is announced on the kubernetes-dev mailing list and community * The removal is announced on the kubernetes-dev mailing list and community
meeting meeting
This maintains the complete record of issues, PRs and other contributions, This maintains the complete record of issues, PRs and other contributions,
leaves the repository read-only, and makes it clear that the repository should leaves the repository read-only, and makes it clear that the repository should

5
github-management/permissions.md
View File

@ -29,8 +29,7 @@ Therefore, we are very cautious about giving more people this access than
really need it. really need it.
There are certain actions that require org owner access: There are certain actions that require org owner access:
- Invite or remove members from the organization (in future, will be handled by - Invite or remove members from the organization (handled by [peribolos])
[peribolos])
- Access the organization audit log - Access the organization audit log
- Create new repositories - Create new repositories
- Transfer repositories - Transfer repositories
@ -69,7 +68,7 @@ In most cases, this level of access should not be necessary as the majority of
actions will be able to be implemented by automation. Certain actions like actions will be able to be implemented by automation. Certain actions like
creating a release may still need this level of access. creating a release may still need this level of access.
**// TODO(cblecker):** Define specific roles that need this. <!--- TODO(cblecker): Define specific roles that need this. -->
### Write ### Write