@@ -20,18 +20,23 @@ GHC is an open source project, and we would love you to contribute to it. For e
If you want to become part of the core group that develops and maintains GHC, you can
join the **GHC Team**. Anyone can join the team!
Being a member of the GHC Team carries power and responsibility:
*You do not need to be a member of the GHC Team to contribute to GHC*!
You can do all the things described in Section 1, and more, without being a signed-up
member of the team.
But being a member of the GHC Team carries extra power, as well as extra responsibility:
**Power**
* Ability to merge patches into GHC's main trunk, subject to GHC’s code review policies. See GHC's [Contributing a Patch](https://gitlab.haskell.org/ghc/ghc/-/wikis/Contributing-a-Patch) documentation for more information about this process.
* Standing invitation to the GHC weekly meeting.
**Responsibilities**
**Responsibilies**
* Actively contribute to GHC, through patches, code review, design discussions, infrastructure. "Actively contribute" means at least with a tempo of every month or two. e.g. making a small intervention once a year is not really enough to be a member of the team.
* Monitor, and when appropriate contribute to, the [`ghc-devs` mailing list](https://mail.haskell.org/mailman/listinfo/ghc-devs).
* Willingness to review merge requests, when the expertise fits.
* Willingness to proactively review merge requests, when the expertise fits.
* Willingness to undertake some specific obligations, to take responsibility for some specific part of GHC
### 2.1 Membership
* We keep the GHC Team membership on [a page in this repository](team.mkd).
