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 RFC to remove non-standard Github teams #262

Merged
merged 3 commits into from
Aug 9, 2022
Merged

Add RFC to remove non-standard Github teams #262

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
46e7f90
Add RFC to remove non-standard Github teams
Gerg Apr 28, 2022
9ef6d01
Fill in PR link
Gerg Apr 28, 2022
a0f17ef
Incorporate feedback to non-standard teams RFC
Gerg Aug 1, 2022
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
37 changes: 37 additions & 0 deletions toc/rfc/rfc-draft-remove-nonstandard-github-teams.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
# Meta
[meta]: #meta
- Name: Remove Non-Standard GitHub Teams
- Start Date: 2022-04-28
- Author(s): @gerg
- Status: Draft <!-- Acceptable values: Draft, Approved, On Hold, Superseded -->
- RFC Pull Request: [https://github.com/cloudfoundry/community/pull/262](https://github.com/cloudfoundry/community/pull/262)


## Summary

Remove GitHub teams (and associated access) that are outside of the CFF
governance model.

## Problem

There are currently many GitHub teams in the `cloudfoundry` GitHub organization
that do not correlate with a CFF-recognized entity (working group, TOC, etc).
These teams grant access to CFF-governed repositories, but are not beholden to
the CFF's roles and other processes for governing access. In addition, the
volume of GitHub teams makes it more difficult to manage team access via the
GitHub UI and intermediary tools like
[`cloudfoundry.yml`](https://github.com/cloudfoundry/community/blob/main/org/cloudfoundry.yml).

Gerg marked this conversation as resolved.
Show resolved Hide resolved
Nevertheless, controlling access to Cloud Foundry repositories only by teams defined by CFF technical governance is a substantial change from the previous system of access and team management and in the short term will cause unexpected loss of access to repositories for some contributors and automated development and release processes.

As per [RFC 0007](https://github.com/cloudfoundry/community/blob/main/toc/rfc/rfc-0007-repository-ownership.md), CFF staff also require access to many repositories in the Cloud Foundry GitHub organization that are outside the scope of project technical operation, such as those for CFF websites or the Cloud Foundry Certified Developer examinations.
## Proposal

Delete all GitHub teams in the `cloudfoundry` organization that do not conform
to
[rfc-0005-github-teams-and-access](https://github.com/cloudfoundry/community/blob/main/toc/rfc/rfc-0005-github-teams-and-access.md)
or another CFF-recognized entity, such as CFF staff members.

To allow the CF community to function while the Working Groups adjust their scope and membership, the TOC will permit the formation of exceptional teams on a case-by-case basis. These exceptional teams must be identified as such clearly in their names with phrases such as "temporary" and "delete me", and these teams should be related to unofficial teams that were previously deleted. The TOC and Working Groups will review these exceptional teams regularly for deletion, with the goal of removing all exceptional teams by the end of 2022.

CFF staff may create teams as needed to administer repositories outside the scope of technical project operation. The names for any such teams should clearly indicate their relation to CFF staff responsibilities.