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

78 lines
2.9 KiB
Markdown

# Groups
<!--
Part of the Carbon Language project, under the Apache License v2.0 with LLVM
Exceptions. See /LICENSE for license information.
SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
-->
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](https://github.com/orgs/carbon-language/people)
- [GitHub team: Contributors with label access](https://github.com/orgs/carbon-language/teams/contributors-with-label-access):
Mirrors the GitHub organization for write access.
[Manually updated](/github/update_label_access.py).
- [Discourse Forums account](https://forums.carbon-lang.dev)
- [Discord Chat access](https://discord.com/app)
- [Google group](https://groups.google.com/g/carbon-lang-contributors): 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](https://github.com/orgs/carbon-language/people?query=role%3Aowner)
- [Discourse Forums group](https://forums.carbon-lang.dev/g/admins)
- Discord Chat role: admin
### Conduct team
For most purposes, the Core team should be contacted about conduct issues.
- [Google group](https://groups.google.com/g/carbon-lang-conduct-team):
Primarily a contact list.
### Core team
- [GitHub team](https://github.com/orgs/carbon-language/teams/core-team)
- [Discourse Forums group](https://forums.carbon-lang.dev/g/core_team)
- Discord Chat role: core-team
### Review managers
- [GitHub team](https://github.com/orgs/carbon-language/teams/review-managers)
- [Discourse Forums group](https://forums.carbon-lang.dev/g/review_managers)
- Discord Chat role: review-managers
- [Google group](https://groups.google.com/g/carbon-lang-review-managers):
Grants Google Drive access.
### 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](#admins) -- any issue can be resolved by
escalating to the [core team](#core-team). Notably, this team is _not_
responsible for the _design_ of the language itself, only for its
implementation.
- [Github team](https://github.com/orgs/carbon-language/teams/implementation-team)
- [Discourse Forum group](https://forums.carbon-lang.dev/g/implementation-team)
- Discord Chat role: implementation-team