Files
carbon-lang/docs/project/groups.md
T
Josh Soref 066b103881 Spelling (#1580)
This PR corrects misspellings identified by the [check-spelling action](https://github.com/marketplace/actions/check-spelling).

The misspellings have been reported at https://github.com/jsoref/carbon-lang/commit/38a1c1640151899fd6da0442a92557f9543b6280#commitcomment-79197316

The action reports that the changes in this PR would make it happy: https://github.com/jsoref/carbon-lang/commit/173c8f9083a68aa61f7cfe94f720f1e5dc7f1ea3

Note: this PR does not include the action. If you're interested in running a spell check on every PR and push, that can be offered separately.

Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
2022-07-22 16:14:21 -07:00

2.3 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
    • 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.

All contributors

Team-specific access

Any team-specific access will typically be managed by a team owner or admin, when somebody joins the respective team.

Admins

Carbon leads

Conduct team

For most purposes, the Core team should be contacted about conduct issues.

Implementation team

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.