Files
carbon-lang/docs/project/groups.md
T
5db229afc6 Create an implementation team. (#179)
Create a team to oversee the implementation of Carbon. This team is
responsible for code reviews as well as handling any implementation-specific
decisions.

Originally, it was suggested to call this a "toolchain" team. During
discussion, it became clear that the scope wasn't easily limited to
implementation efforts that were necessarily part of the toolchain. There are
many different aspects of implementation, and we anticipate code sharing
between them that make it unhelpful to try to separate these. Instead, this
team is chartered with broadly covering all of the implementation concerns in
Carbon. If someone is concerned that an issue is larger than that, perhaps
impacting the design of the language, the project, or the community, the
standard process already provides for easy escalation to the core team.

Co-authored-by: Jon Meow <46229924+jonmeow@users.noreply.github.com>
Co-authored-by: austern <austern@google.com>
Co-authored-by: Geoff Romer <gromer@google.com>
2021-01-16 16:06:39 -08:00

2.9 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

Team-specific access

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

Admins

Conduct team

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

Core team

Review managers

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 core team. Notably, this team is not responsible for the design of the language itself, only for its implementation.