Core Committers

Core Committers

A core committer is a maintainer on the Mattermost project that has merge access to Mattermost repositories. They are responsible for reviewing pull requests, cultivating the Mattermost developer community, and guiding the technical vision of Mattermost. If you have a question or need some help, these are the people to ask.

Below is the list of core committers working on Mattermost:

Core Developers

Below is the list of core developers working on individual Mattermost repositories:

Community Moderators

Below is the list of community moderators who share feedback and answer questions on Mattermost through forums, GitHub issues and the Mattermost community server:

Product Managers

The core team's Product Managers design, plan, prioritize, and coordinate feature improvements and new features.

Product Designers

The core team's Product Designers design features, user experience, and how the product looks and feels.

Release Managers

The core team's release manager prioritizes and coordinates Cloud and self-managed releases across all the teams.

QA Testers

The core team's QA testers verify the correct functionality of the product from release to release.

Build Engineers

Security Engineers

Technical Writers

The core team's technical writers document product features and functionality from release to release.

How to promote a contributor to core committer

  1. Identify a core committer

    • A core committer is a maintainer on the Mattermost project and has merge access to Mattermost repositories. They are responsible for reviewing pull requests, cultivating the Mattermost developer community, and guiding the technical vision of Mattermost. If you have a question or need some help, these are the people to ask.

    • If you feel someone in the community would be interested in such activities, then they may be a great candidate for being promoted to a core committer!

  2. Nominate a core committer

    • If the nomination is for the Mattermost project, or for a core repository (e.g. mattermost-server, mattermost-webapp), raise the topic in weekly developers meeting.

    • If the nomination is for a repository managed by a specific team (e.g. mattermost-plugin-jira), raise the topic with that team.

  3. Team discussed nomination

    • During the meeting, the nomination is discussed. Meeting participants should feel empowered to raise concerns, if any, on the nomination (e.g. length of involvement in the community, skill sets).

  4. If the nomination is agreed on, the person who nominated the contributor reaches out to them

    • The promotion should be opt-in, and the contributor should feel empowered to decline the promotion if they choose.

  5. If the contributor accepts the nomination, they are

    • Given merge access in the respective GitHub repositories.

    • Added to the Mattermost GitHub organization, which is displayed in their GitHub profile.

    • Able to be added as reviewers to relevant pull requests, to offer technical guidance and reviews.

  6. The promotion is announced (details TBD)

    • The new core committer is added to to the above list of core committers.

    • ...

  7. The new core committer is gifted with lot of :heart: and lot of swag :tada: (details TBD)

    • Core committer mug.

    • ...