-
Notifications
You must be signed in to change notification settings - Fork 22
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Jian Qiu <[email protected]>
- Loading branch information
Showing
1 changed file
with
39 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,39 @@ | ||
# Open Cluster Management Repositories Guidelines | ||
|
||
This document attempts to outline a structure for creating GitHub repositories with the Open-Cluster-Management project. It also describes how and when repositories are removed. | ||
|
||
# Rules for New Repositories | ||
|
||
* All repos will live in github.com/open-cluster-management-io/\<project-name\>. | ||
* Must contain the topic for the sponsoring sub projects - e.g. application. (Added through the Manage topics link on the repo page.) | ||
* Must adopt the Open-Cluster-Management Code of Conduct | ||
* All code projects use the Apache License version 2.0. | ||
* All OWNERS of the project must also be active Open-Cluster-Management members. | ||
* Must be approved by the following process. | ||
1. It has been discussed and recognized in the community meeting with a | ||
publicly linkable written decision. | ||
2. It must have two sponsors, each of whom must be the maintainer of a sub project. | ||
3. An repository onboarding issue is created in the community repo. | ||
|
||
## Removing Repositories | ||
|
||
As important as it is to add new repositories, it is equally important to prune | ||
old repositories that are no longer relevant or useful. | ||
|
||
It is in the best interests of everyone involved in the Open-Cluster-Management community | ||
that our various projects and repositories are active and healthy. This | ||
ensures a rapid response to potential required fixes (e.g. critical security | ||
problems) and (most importantly) it ensures that contributors and users receive | ||
quick feedback on their issues and contributions. | ||
|
||
### Grounds for removal | ||
|
||
Repositories may be removed from the project if they | ||
are deemed _inactive_. Inactive repositories are those that meet any of the | ||
following criteria: | ||
|
||
* There are no longer any active maintainers for the project and no | ||
replacements can be found. | ||
* All PRs or Issues have gone un-addressed for longer than six months. | ||
* There have been no new commits or other changes in more than a year. | ||
* The contents have been folded into another actively maintained project. |