search

camaraproject / Governance

Telco network capabilities exposed through APIs provide a large benefit for customers. By simplifying telco network complexity with APIs and making the APIs available across telco networks and countries, CAMARA enables easy and seamless access.
53 stars 44 forks source link

Create CAMARA teams for Codeowners & Maintainers - apply to all sub projects #134

Open hdamker opened 1 month ago

hdamker commented 1 month ago

Problem description

As discussed and confirmed within TSC 2024-05-02 we introduce teams for the Maintainers and Codeowners within all Sub Projects of CAMARA to ensure an easy and consistent administration of access rights within the repositories. By this all Maintainers and Codeowners will be invited as members into the GitHub Organization.

  1. For each Sub Project there will be a team <sub-project>_maintainers - the members of this team shall be consistent with the MAINTAINER.mdfile within the Sub Project
  2. For each Sub Project there will be a team <sub-project>_codeowners - the members of this team shall be consistent with the CODEOWNERS file within the Sub Project
  3. All MAINTAINERS.md files shall have a new column "GitHub Username" which must be filled
  4. All <*>_maintainers teams have as parent a team maintainers
  5. All <*>_codeownersteams have as parent a team codeowners
  6. The following teams will added to the "Collaborators and teams" of a Sub Project
    • <sub-project>_codeowners with write access
    • <sub-project>_maintainers with triage access
    • camaraproject/admins with maintain access
    • (camaaraproject/maintainers with read access) postponed, see below.
  7. At each CODEOWNERS file the following three lines will be added in the end, making the CAMARA admin owners of the CODEOWNERS and MAINTAINERS.md files:
# Owners of the CODEOWNER and Maintainer.md files are the admins of CAMARA (to allow them to keep the teams within the CAMARA organization in sync in case of changes)
/CODEOWNERS @camaraproject/admins
/MAINTAINERS.MD @camaraproject/admins

Expected action

The above described will be setup for all existing Sub Projects.

Additional context

The TSC asked to use this issue, especially point 3 above to request a review of the current Maintainer lists in each Sub Projects.

hdamker commented 1 month ago

In addition to the issue description we might need a "root" of all members within the CAMARA organisation which we can use to grant explicit read access within all public repositories.

This "team" should include all Maintainers, Codeowners, TSC Members, but going forward potential further teams beside these ones.

Until this is discussed within the Admin team I have removed the addition of read access for the maintainer team to each Sub Project.

hdamker commented 1 month ago

Status regarding the points

  1. Done by @eharrison24 ... some invites are still pending (they expire after 7 days, might need retries). For some Maintainers no GitHub username could be identified - to be resolved during PRs for point 3.
  2. Done by @hdamker ... some invites are still pending (they expire after 7 days, might need retries)
  3. To be done except for the following Sub Projects which already have the right format: for QualityOnDemand, ReleaseManagement, SimpleEdgeDiscovery, NetworkAccessManagement, LocationInsights
  4. Done with 1.
  5. Done with 2.
  6. Done by @hdamker
  7. To be done, in same PRs then for 3. (done for the ones listed in 3.)
hdamker commented 1 month ago

3./7. done for SimSwap and SiteToCloud