# Maintainer responsibilities

## Join the team meetings

Participate in the regular team meetings, see [meeting information and protocol] for details.

[meeting information and protocol]: ./README.md#team-meetings

If you can't participate, notify other team members.

## Stay informed

Follow relevant activities on these communication channels:

- GitHub

  Subscribe to issues and pull requests you care about.

- Discourse

  Set the notification level on the [Development > Documentation] Discourse category to "watching".

  [Development > Documentation]: https://discourse.nixos.org/c/dev/documentation/25

- Matrix

  Join the [Nix\* Documentation] Matrix room and enable relevant notifications.

  [Nix\* Documentation]: https://matrix.to/#/#docs:nixos.org

## Take ownership

Maintain your entry in the [`CODEOWNERS`] file in the respective repository.
GitHub will then request reviews for pull requests that change files you own.

[`CODEOWNERS`]: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners

As a maintainer, you are responsible for the code you approve and merge.
Make sure to follow up on bugs and regressions in the code you maintain.

Respond to `@` mentions on GitHub, Discourse, and Matrix within reasonable time.
Notify readers if you cannot deal with the issue due to time constraints or other priorities.

Make sure to reserve time for reviewing pull requests that fall within your area of interest or expertise.

## Provide guidance

Guide potential contributors:

- help answering questions on the [Discourse Help category]
- encourage question authors to raise or upvote issues on GitHub, if needed
- assist them with making pull requests to solve the underlying problems, if possible

[Discourse Help category]: https://discourse.nixos.org/c/learn/9