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
- Discord roles
- Google groups, usually as Google Drive ACLs. We generally won't use these as contact lists, unless specifically mentioned. Please prefer other community forums.
TODO: Update this information, it's out of date.
- GitHub organization
- GitHub team: Contributors with label access: Mirrors the GitHub organization for write access.
- Discord access
- Google group: Grants Google Drive access.
Any team-specific access will typically be managed by a team owner or admin, when somebody joins the respective team.
- GitHub owners
- Discord role: admin
- GitHub team
- Discord role: carbon-leads
For most purposes, the Core team should be contacted about conduct issues.
- Google group: Primarily a contact list.
This team is responsible for development of Carbon's primary, reference implementation and toolchain. It also oversees other related implementation work within the Carbon project, from tooling of the language spec to test suites. There may be some overlap with admins -- any issue can be resolved by escalating to the Carbon leads. Notably, this team is not responsible for the design of the language itself, only for its implementation.
- GitHub team
- Discord role: implementation-team