Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add explicit steps for cases in rfc-0007-repository-ownership.md #884

Merged
merged 6 commits into from
Jul 2, 2024
Merged

Add explicit steps for cases in rfc-0007-repository-ownership.md #884

Changes from 2 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
079c067
Add explicit steps for cases in rfc-0007-repository-ownership.md
ameowlia Jun 6, 2024
2e075ee
Update toc/rfc/rfc-0007-repository-ownership.md
ameowlia Jun 11, 2024
f232fb1
Update toc/rfc/rfc-0007-repository-ownership.md
ameowlia Jun 18, 2024
67995bd
Update toc/rfc/rfc-0007-repository-ownership.md
ameowlia Jun 18, 2024
2a700b5
Update toc/rfc/rfc-0007-repository-ownership.md
rkoster Jun 25, 2024
3dfee4b
Update toc/rfc/rfc-0007-repository-ownership.md
stephanme Jun 25, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
112 changes: 91 additions & 21 deletions toc/rfc/rfc-0007-repository-ownership.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,24 +55,94 @@ The TOC MUST also approve of any proposal to create a new repository within the

We illustrate several different cases of repository ownership changes and the approvals required for them to proceed:

1. A Working Group wants to create a new repository under their ownership.
* The Working Group MUST approve the addition of the proposed repository to the set of repositories that it owns.
* The TOC MUST approve the creation of the proposed repository.
* The TOC MUST approve the addition of the proposed repository to the Working Group's subset.

1. The TOC wants Working Group A to take ownership of an unclaimed active repository.
* The TOC MUST approve the change in the ownership scope of Working Group A.
* Working Group A MUST approve the change to the set of repositories they own.

1. Working Group A wants to claim ownership of a repository currently owned by Working Group B.
* Both Working Group A and Working Group B MUST approve the change to the sets of repositories they own.
* The TOC MUST also approve the transfer of the repository from Working Group B to Working Group A.

1. A Working Group wants to cease maintaining a repository that it currently owns.
* The Working Group MUST approve the removal of the repository from the set of repositories that it owns.
* The TOC MUST approve the removal of the repository from the Working Group.
* In addition, the TOC MUST decide whether to archive the repository or to arrange for another Working Group to own it instead (possibly a newly formed one, if appropriate and if supported by community contributors).
* **Note:** In this case, it is unlikely that either the TOC or the CFF staff should own this repository, as it was already owned by some Working Group in the CF community.

1. A Working Group wants to rename a repository that it currently owns.
* The Working Group A and the TOC MUST both approve of the new name for the repository.
#### Case 1: A Working Group wants to create a new repository under their ownership.

Approval requirements
* The Working Group MUST approve the addition of the proposed repository to the set of repositories that it owns.
* The TOC MUST approve the creation of the proposed repository.
* The TOC MUST approve the addition of the proposed repository to the Working Group's subset.

Steps
1. Someone opens two PRs. The first PR adds the repo to the [cloudfoundry.yml](../../org/cloudfoundry.yml). The second PR adds the repo to the desired Working Group's yaml. These PRs should link to each other.
ameowlia marked this conversation as resolved.
Show resolved Hide resolved
2. The Working Group and TOC both approve both PRs.
3. The TOC merges the first PR.
4. Wait for automation to run to create the repo.
5. The TOC merges the second PR.
rkoster marked this conversation as resolved.
Show resolved Hide resolved

#### Case 2: The TOC wants Working Group A to take ownership of an unclaimed active repository.

Approval requirements
* The TOC MUST approve the change in the ownership scope of Working Group A.
* Working Group A MUST approve the change to the set of repositories they own.

Steps
1. Someone opens a PRs that adds a repo to the desired Working Group's yaml.
2. The Working Group and TOC both approve the PR.
3. The TOC merges the PR.


#### Case 3: Working Group A wants to claim ownership of a repository currently owned by Working Group B.

Approval requirements
* Both Working Group A and Working Group B MUST approve the change to the sets of repositories they own.
ameowlia marked this conversation as resolved.
Show resolved Hide resolved
* The TOC MUST also approve the transfer of the repository from Working Group B to Working Group A.

Steps
1. Someone opens a PR that moves a repo from Working Group A's yaml to Working Group B's yaml.
2. Working Group A, Working Group B, and TOC approve the PR.
3. The TOC merges the PR.

#### Case 4: A Working Group wants to archive a repository that it currently owns.

Approval requirements
* The Working Group MUST approve the removal of the repository from the set of repositories that it owns.
* The TOC MUST approve the removal of the repository from the Working Group and the archival.

Steps
1. Someone opens a PR that: marks the repo as archived in the [cloudfoundry.yml](../../org/cloudfoundry.yml) and that removes the repo from the Working Group's yaml.
2. The Working Group and TOC both approve the PR.
3. The TOC merges the PR.

#### Case 5: A Working Group wants to delete a repository that it currently owns.

ameowlia marked this conversation as resolved.
Show resolved Hide resolved
ameowlia marked this conversation as resolved.
Show resolved Hide resolved
Approval requirements
* The Working Group MUST approve the removal of the repository from the set of repositories that it owns.
* The TOC MUST approve the removal of the repository from the Working Group and the deletion.

Steps
1. Someone opens a PR that removes the [cloudfoundry.yml](../../org/cloudfoundry.yml) and removes the repo from the Working Group's yaml.
2. The Working Group and TOC both approve the PR.
3. The TOC merges the PR.
4. A github admin deletes the repo.

#### Case 6: A Working Group wants to cease maintaining a repository that it currently owns.

Approval requirements
* The Working Group MUST approve the removal of the repository from the set of repositories that it owns.
* The TOC MUST approve the removal of the repository from the Working Group.
* In addition, the TOC MUST decide whether to archive the repository or to arrange for another Working Group to own it instead (possibly a newly formed one, if appropriate and if supported by community contributors).
* Note: In this case, it is unlikely that either the TOC or the CFF staff should own this repository, as it was already owned by some Working Group in the CF community.


Steps
1. Someone opens a PR that removes the repo from the Working Group's yaml.
2. The TOC reviews and decides what action to take with the repo. Other PRs might be required for this step.
3. The Working Group and TOC both approve the PR.
5. The TOC merges the PR.

#### Case 7: A Working Group wants to rename a repository that it currently owns.

Approval requirements
* The Working Group A and the TOC MUST both approve of the new name for the repository.

Steps
1. Someone two PRs:
ameowlia marked this conversation as resolved.
Show resolved Hide resolved
* PR 1: Add the new repo to the [cloudfoundry.yml](../../org/cloudfoundry.yml).
* PR 2: Rename the repo in the Working Group's yaml. Remove the old repo from the [cloudfoundry.yml](../../org/cloudfoundry.yml).
The second PR adds the repo to the desired Working Group's yaml. These PRs should link to each other.
3. The Working Group and TOC both approve both PRs.
4. The TOC merges the first PR.
5. Wait for automation to run to create the repo.
6. A github admin copies the old repo contents to the new repo.
stephanme marked this conversation as resolved.
Show resolved Hide resolved
7. The TOC merges the second PR.
8. A github admin deletes the old repo.