| Age | Commit message (Collapse) | Author |
|
|
|
|
|
Since the kubernetes-incubator org has now been retired, this commit
removes references to the org from our docs.
Note that this commit does NOT remove references in the following docs:
* design proposals
* meeting notes
* docs/notes from old events
|
|
Update who must approve repo creation requests
|
|
The process is only meant for org admins so move to that doc and
decouple the process from the rules and guidelines for repos, which are
meant for everyone.
|
|
Current state of docs:
- https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md#subproject-creation
mentions that repos _may_ be created under k-sigs by a lazy consensus of subproject owners.
- Some charters like https://github.com/kubernetes/community/blob/master/sig-api-machinery/charter.md#deviations-from-sig-governance
have explicit processes setup for who can approve repo creation requests.
- https://github.com/kubernetes/community/blob/master/github-management/kubernetes-repositories.md#rules-for-new-repositories
says that repo creation requests must be approved by lazy consensus of SIG membership.
Current state of how we do things:
- We create repos if the SIG leads have approved the repo creation
request.
- We don't require a lazy consensus thread on the mailing list, just a
publicly linkable written decision.
This commit reconciles the docs with the current state of how we do this.
Note that the wording says "process spelled out in the SIG charter"
because SIG charters _may_ also define a complete process on how they'd
like to handle this, not just the list of people who can approve repo
creation requests.
|
|
|
|
github-management: add suggestions for creating new repos
|
|
|
|
Per comments in review, switching to use shortened URLs to
comply with style guidelines.
Signed-off-by: Steve Winslow <swinslow@gmail.com>
|
|
Signed-off-by: Steve Winslow <swinslow@gmail.com>
|
|
Ref: https://groups.google.com/d/topic/kubernetes-sig-architecture/TjHLgJcDF-I/discussion
|
|
|
|
|
|
doing these changes in a separate PR before doing content changes
in followup PR's
|
|
|
|
|
|
Signed-off-by: Mike Brown <brownwm@us.ibm.com>
|
|
Added a new case I just ran into, and removed SIG Architecture
from having to be involved in the decision to archive (I view
consulting SIG Arch as part of the process for finding new
active maintainers of the project, we could bake this into the
language if it needs to be explicit)
Formatting changes:
- Trimmed whitespace in the FAQ
- Unindented headers
- FAQ questions are now bold rather than italic
- Repo removal is a checklist to follow
|
|
|
|
|
|
|