mirror of
https://github.com/carbon-language/carbon-lang.git
synced 2026-09-24 22:02:23 +01:00
We're using labels for proposals... https://github.com/carbon-language/carbon-lang/settings/access allows granting triage access for specific teams. https://github.com/organizations/carbon-language/settings/member_privileges doesn't appear to allow doing the same at the org-level. So I've decided to create a team that mirrors the org, and grants triage access. `¯\_(ツ)_/¯` I don't know that this is the right solution long-term, but for now I think it's right. Manually updating this group is slow and error-prone, so the script automates it.
2.2 KiB
2.2 KiB
Groups
These are groups used by the Carbon Language project, listed here for central tracking.
We use a mix of:
- Groups to assist contacting key contributors on appropriate systems:
- GitHub teams
- Discourse Forums groups
- Discord Chat roles
- Google groups, usually as Google Drive ACLs. We generally won't use these as contact lists, unless specifically mentioned. Please prefer Discourse Forums.
All contributors
- GitHub organization
- GitHub team: Contributors with label access: Mirrors the GitHub organization for write access. Manually updated.
- Discourse Forums account
- Discord Chat access
- Google group: Grants Google Drive access.
Team-specific access
Any team-specific access will typically be managed by a team owner or admin, when somebody joins the respective team.
Admins
- GitHub owners
- Discourse Forums group
- Discord Chat role: admin
Conduct team
For most purposes, the Core team should be contacted about conduct issues.
- Google group: Primarily a contact list.
Core team
- GitHub team
- Discourse Forums group
- Discord Chat role: core-team
Review managers
- GitHub team
- Discourse Forums group
- Discord Chat role: review-managers
- Google group: Grants Google Drive access.