@@ -8,7 +8,7 @@ It is a description of how things currently work, but should be seen as a starti
GHC is an open source project, and we would love you to contribute to it. For example
* You can file a bug report.
* You can help charactise or minimise a bug, so there is a small repro case.
* You can help characterise or minimise a bug, so there is a small repro case.
* You can offer a patch that fixes a bug, or improves documentation
* You can review a merge request
* You can improve the user manual or documentation in the code.
...
...
@@ -29,7 +29,7 @@ But being a member of the GHC Team carries extra power, as well as extra respons
* 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.
**Responsibilies**
**Responsibilities**
* 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 proactively review merge requests, when the expertise fits.
