From a2d842fb3761b723955eab7c669c7af424dda400 Mon Sep 17 00:00:00 2001 From: Jon Church Date: Sat, 24 Feb 2024 18:03:26 -0500 Subject: [PATCH 1/4] add Github Access Structure Overview section --- Contributing.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/Contributing.md b/Contributing.md index dfe5f13833..7badca501b 100644 --- a/Contributing.md +++ b/Contributing.md @@ -87,6 +87,18 @@ the organizations requested. They will then close the issue. Happy triaging! +## GitHub Access Structure Overview + +We're implementing a structured approach to GitHub permissions across our projects, ensuring clarity, security, and efficient collaboration. Each level of access is a superset of the permissions available to the level(s) below it in the hierarchy. Here’s an overview of the structure, permissions, and associated teams: + +* Technical Committee – admin permissions across all Express orgs (Expressjs, jshttp, pillarjs). Highest level of access, owner permissions on repos and orgs. TC members will be added to a github team in each org, and permissions will be granted to the team. + +* Project Captain – admin permissions on a specific repo. Permissions similar to TC, but scoped to a specific repo not an entire org. Permissions must be applied manually to a Project Captain user as a result. Creating a github team for this is optional, as the permissions are not applied at the team level. + +* Committer – commit bit on a given repo or repos. Permissions must be applied manually. Github team here is optional, but recommended. All members of the org who have a commit bit for one or more repos can be members. + +* Triager – can close/tag/manage issues/discussions across all orgs. See the Triager Guide for more information. Triagers will be added to a github team in each org, and permissions will be granted to the team. + ## Becoming a Committer All contributors who land a non-trivial contribution should be on-boarded in a timely manner, From 97f8406fe84d2c181f350179bc545909f85657e5 Mon Sep 17 00:00:00 2001 From: Jon Church Date: Sat, 24 Feb 2024 18:12:44 -0500 Subject: [PATCH 2/4] add links to orgs and triager guide --- Contributing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Contributing.md b/Contributing.md index 7badca501b..f720345422 100644 --- a/Contributing.md +++ b/Contributing.md @@ -91,13 +91,13 @@ Happy triaging! We're implementing a structured approach to GitHub permissions across our projects, ensuring clarity, security, and efficient collaboration. Each level of access is a superset of the permissions available to the level(s) below it in the hierarchy. Here’s an overview of the structure, permissions, and associated teams: -* Technical Committee – admin permissions across all Express orgs (Expressjs, jshttp, pillarjs). Highest level of access, owner permissions on repos and orgs. TC members will be added to a github team in each org, and permissions will be granted to the team. +* Technical Committee – admin permissions across all Express orgs ([expressjs](https://github.com/expressjs), [jshttp](https://github.com/jshttp), [pillarjs](https://github.com/pillarjs)). Highest level of access, owner permissions on repos and orgs. TC members will be added to a github team in each org, and permissions will be granted to the team. * Project Captain – admin permissions on a specific repo. Permissions similar to TC, but scoped to a specific repo not an entire org. Permissions must be applied manually to a Project Captain user as a result. Creating a github team for this is optional, as the permissions are not applied at the team level. * Committer – commit bit on a given repo or repos. Permissions must be applied manually. Github team here is optional, but recommended. All members of the org who have a commit bit for one or more repos can be members. -* Triager – can close/tag/manage issues/discussions across all orgs. See the Triager Guide for more information. Triagers will be added to a github team in each org, and permissions will be granted to the team. +* Triager – can close/tag/manage issues/discussions across all orgs. See the [Triager Guide](Triager-Guide.md) for more information. Triagers will be added to a github team in each org, and permissions will be granted to the team. ## Becoming a Committer From 88465071f8a315ee83aae7344c7b530dc75565d2 Mon Sep 17 00:00:00 2001 From: Jon Church Date: Mon, 26 Feb 2024 16:08:11 -0500 Subject: [PATCH 3/4] remove line about TC member group Co-authored-by: Wes Todd --- Contributing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Contributing.md b/Contributing.md index f720345422..ed161aa6d0 100644 --- a/Contributing.md +++ b/Contributing.md @@ -91,7 +91,7 @@ Happy triaging! We're implementing a structured approach to GitHub permissions across our projects, ensuring clarity, security, and efficient collaboration. Each level of access is a superset of the permissions available to the level(s) below it in the hierarchy. Here’s an overview of the structure, permissions, and associated teams: -* Technical Committee – admin permissions across all Express orgs ([expressjs](https://github.com/expressjs), [jshttp](https://github.com/jshttp), [pillarjs](https://github.com/pillarjs)). Highest level of access, owner permissions on repos and orgs. TC members will be added to a github team in each org, and permissions will be granted to the team. +* Technical Committee – admin permissions across all Express orgs ([expressjs](https://github.com/expressjs), [jshttp](https://github.com/jshttp), [pillarjs](https://github.com/pillarjs)). Highest level of access, owner permissions on repos and orgs. * Project Captain – admin permissions on a specific repo. Permissions similar to TC, but scoped to a specific repo not an entire org. Permissions must be applied manually to a Project Captain user as a result. Creating a github team for this is optional, as the permissions are not applied at the team level. From f5b6eaa29096e23969dece5d69ddd585bae9ca0c Mon Sep 17 00:00:00 2001 From: Jon Church Date: Mon, 26 Feb 2024 16:45:21 -0500 Subject: [PATCH 4/4] switch use of manually to individually --- Contributing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Contributing.md b/Contributing.md index ed161aa6d0..1895066011 100644 --- a/Contributing.md +++ b/Contributing.md @@ -93,9 +93,9 @@ We're implementing a structured approach to GitHub permissions across our projec * Technical Committee – admin permissions across all Express orgs ([expressjs](https://github.com/expressjs), [jshttp](https://github.com/jshttp), [pillarjs](https://github.com/pillarjs)). Highest level of access, owner permissions on repos and orgs. -* Project Captain – admin permissions on a specific repo. Permissions similar to TC, but scoped to a specific repo not an entire org. Permissions must be applied manually to a Project Captain user as a result. Creating a github team for this is optional, as the permissions are not applied at the team level. +* Project Captain – admin permissions on a specific repo. Permissions similar to TC, but scoped to a specific repo not an entire org. Permissions must be applied individually to a Project Captain user as a result. Creating a github team for this is optional, as the permissions are not applied at the team level. -* Committer – commit bit on a given repo or repos. Permissions must be applied manually. Github team here is optional, but recommended. All members of the org who have a commit bit for one or more repos can be members. +* Committer – commit bit on a given repo or repos. Permissions must be applied individually to the user. Github team here is optional, but recommended. All members of the org who have a commit bit for one or more repos can be members. * Triager – can close/tag/manage issues/discussions across all orgs. See the [Triager Guide](Triager-Guide.md) for more information. Triagers will be added to a github team in each org, and permissions will be granted to the team.