Mattermost Handbook
Need help?How to spend company moneyHow to update the HandbookRelease overview
0.2.1
0.2.1
  • Mattermost Handbook
  • Company
    • About Mattermost
      • List of terms
      • Business model
      • Mindsets
    • "How to" guides for staff
      • How to set up a 1-1 channel
      • How to update the handbook
      • How to manage Handbook notifications
      • How to change mobile device
        • How to handle a lost mobile device
      • How to do a mini-retrospective
      • How to autolink keywords in Mattermost
  • Operations
    • Company operations
      • Areas of Responsibility
      • Mattermost Leadership Team (MLT)
        • MLT cadence
      • Company measures
        • Metrics definitions
        • FY23 goals board
        • MLT metrics
      • Company cadence
      • Company policies
        • Community response policy
        • Security policy
      • Company processes
        • Issue/solution process
        • Company agreements
        • Publishing
          • Public web properties
          • Publishing guidelines
            • Brand and visual design guidelines
            • Voice, tone, and writing style guidelines
              • Contribute to documentation
            • Confidentiality guidelines
          • Post-publication quality control process
      • Handbook processes and policies
        • Handbook onboarding
      • Fiscal year planning
    • Research and Development
      • Organization
        • Tech Writing
        • Data engineering
        • Delivery
        • Cloud Platform
        • Site Reliability Engineering
        • GRC
        • Product Security
        • Security Operations
      • Processes
        • Feature Labels
      • Product
        • Product planning
          • Product philosophy and principles
          • Prioritization process
          • Release planning process
          • Roadmap views
          • Release plan
          • Launch plan
          • Feature requests
        • Development process
          • Mobile feature guidelines
          • Deprecation policy
          • Mattermost software requirements process
          • Jira ticket lifecycle
          • Creating new Jira bug tickets
            • Priority levels for tickets
            • Jira fix versions
        • Release process
          • Release overview
          • Feature release process
          • Dot release process
          • Security release process
          • Mobile app release process
          • Desktop app release process
          • Release tips
          • Release scorecard definitions
        • How-to guides for Product
          • How to use productboard
          • How to record a roadmap video
          • How to update integrations directory
          • How to write a feature release announcement
        • Product Management team handbook
          • Product Management Areas of Ownership
          • Product Manager onboarding
          • Product Manager levels
          • Professional development
        • Product Design team handbook
          • Product Design levels
        • Technical Writing team handbook
          • Work with us
          • User interface text guidelines
          • Documentation style guide
          • Our terminology
          • Guidelines for PMs and developers
          • Guidelines for community contributions
          • Technical Writer levels
          • Docathon 2021
            • Getting started with contributing
        • Growth
          • A/B testing methodology
          • PQL definition
        • Analytics
          • Product Analyst Engineer levels
          • Looker
            • Dashboards
            • Explores
          • Telemetry
        • Developer relations
        • Product team hangouts
      • Engineering
        • Infrastructure engineering
          • Cloud infrastructure cost KPIs
          • Cloud data export process
          • Cloud churn process
          • Reliability Manifesto
          • Production Readiness Review
          • Infrastructure Library
        • Integrations team processes
        • Plugin release process
        • Data Engineering
        • Sustained Engineering
          • On call
        • How to go to a conference
        • Public speaking
        • Core contributor expanded access policy
      • Quality Assurance
        • QA workflow
        • QA testing tips and tools
        • Rainforest process
    • Messaging and Math
      • How-to guides for M&M
        • How to create release announcements
        • How to create screenshots and GIFs
        • How to write Mattermost case studies
        • How to write guest blog posts for Mattermost apps and services
        • How to write Mattermost recipes
        • How to compose tweets
        • How to create a split test for web page
        • How to run meetups
        • How to run executive dinners
      • Checklists for M&M
        • Blog post checklist
        • Bio checklist
      • Mattermost websites
      • Demand generation reporting
      • M&M Asana guidelines
      • Content marketing
        • How to use the editorial calendar
        • Content development and distribution
        • Video content guidelines
        • How to contribute content
    • Sales
      • Deal Desk
      • Partner programs
      • Lead management
    • Deployment Engineering
      • Overview
      • Workflows
      • Frequently Asked Questions
      • Playbook for MME Sev 1 Outages
      • Status Update Template
    • Program Management
    • Customer Success
      • Customer Support
    • Legal
      • Contracts
      • Ironclad Basics
        • Company-Wide Workflows
        • Sales Contracts and Workflows
        • Signing a Contract and Contract Repository
    • Finance
      • Budget
      • How to use Airbase
        • Access Airbase
        • Navigate Airbase
        • How to submit a purchase request
        • How to submit a reimbursement request
        • How to review a reimbursement request
        • Vendor portal guide
        • Frequently asked questions
      • Onboarding
        • Vendor onboarding
        • ROW staff onboarding
      • Staff member expenses
        • How to spend company money
        • How to spend company money: Internships
        • Corporate credit card policy
        • How to access Airbase
        • Gifting policy
        • How to book airfare and travel
        • How to reimburse the company
        • How to convert currencies
        • How to get paid
      • Arrange a Bounty Program
      • Naming files and agreements
      • Risk management
        • Mattermost U.S. consulting agreements
      • Operations playbook
    • Security
      • Policies
      • Privacy
        • Data deletion requests
        • Data subject access requests
      • Product Security
        • Product Vulnerability Process
        • Working on security-sensitive pull requests
        • Secure Software Development guide
      • Security Operations
        • User guides
    • Workplace
      • PeopleOps
        • HR cadences
        • HR systems
        • HR Processes
        • Working at Mattermost
          • Onboarding
            • Things everyone must know
            • Staff onboarding
            • Engineer onboarding timeline and expectations
            • Manager onboarding
            • Frequently asked questions
          • Learning and development
          • Mattermost communication best practices
          • Paid time off
            • Out of office email example
          • Travel
            • Business travel insurance
          • Leaves of absence
            • Pregnancy leave
            • Baby bonding parental leave
            • Jury duty
          • Workplace program
          • Relocation
          • Total rewards
        • Performance reviews
          • Formal review process
          • New staff performance review
          • Informal review process
        • Transfers and promotions
        • Offboarding instructions for managers
        • People compliance
      • People policies
      • Groups
        • Staff Resource Groups
      • Approvals and iteration
      • IT
        • IT helpdesk
        • Hardware and software purchases
        • Hardware buy back policy
        • Software systems
  • Contributors
    • Contributors
      • Equity, diversity, and inclusion
      • How to contribute to Mattermost
        • Community Content program
        • Documentation contributions
        • Help Wanted tickets
        • Localization
        • Contribution events
      • Mattermost community
      • Contributor kindness
      • Community systems
      • Guidelines and playbooks
        • Social engagement guidelines
        • Contribution guidelines and code of conduct
        • Mattermost Community playbook
        • How to run a Hackathon
        • Hacktoberfest event organizer guide for Mattermost
    • MatterCon
      • Staff information privacy management
      • Mattermost events code of conduct
      • MatterCon2021
    • Join us
      • Ice-breakers
      • Help Wanted tickets
      • Localization
      • Mattermost GitHub sponsorship
      • Things candidates should know
      • Staff recruiting
      • Recruiting cadences
        • Product Manager hiring process
      • Exec recruiting
        • EA logistics
  • Help and support
    • Contact us
Powered by GitBook
On this page
  • Users
  • End users
  • IT administrators
  • System integrators
  • Contributors
  • Solution contributors
  • Platform contributors
  • Translation contributors
  • Documentation contributors
  • Quality Assurance contributors
  • Knowledge Base contributors
  • Deployment solution contributors
  • UX Design contributors
  • Coordination contributors
  • Mattermost staff

Was this helpful?

Edit on Git
Export as PDF
  1. Contributors
  2. Contributors

Mattermost community

PreviousContribution eventsNextContributor kindness

Last updated 3 years ago

Was this helpful?

At Mattermost, we be believe workplace messaging will become a leading platform for workflow and business process. We believe building such a platform on open source infrastructure has powerful advantages.

We consider people who share these beliefs, and who seek to benefit from or influence the Mattermost open source project, to be part of the “Mattermost Community”.

The success of Mattermost as an open source platform for messaging-based workflow and business process depends on empowering our community to build with us towards a shared vision.

The Mattermost community has two parts, Users and Contributors, detailed below.

Interested in contributing to Mattermost? .

Users

In general, all members of the Mattermost community are users of the open source project. They can range from end users and system administrators, to developers on the Mattermost platform in some way. The common bond we all share is that we benefit from the project’s continued and growing success.

The user community has a number of segments:

End users

People using Mattermost to communicate and achieve their organization’s top priorities.

IT administrators

People deploying Mattermost and supporting end users.

System integrators

People who extend and customize Mattermost privately but who do not share back their work with the open source community (for a range of reasons, often related to confidentiality) are considered “users”. When users are able to share their work with others in the community they are recognized as “contributors”.

Customers

Organizations that purchase Mattermost Enterprise Edition as an extension of the Mattermost open source project for advanced features are known as "customers". While the Mattermost roadmap is focused on benefiting the broad community, large customers may accelerate certain parts of the roadmap they find most valuable through purchasing large numbers of Enterprise Edition licenses.

Contributors

Contributors are a subset of the Mattermost community who help increase the overall benefits of Mattermost for others. This may be as simple as offering feature ideas, reporting bugs, or offering professional installation and deployment services. Or it can be as complex as building whole new products based on Mattermost, or contributing code to the underlying software.

The work of all contributors is valued, appreciated, and recognized as a driving force behind the project’s growth.

There are many ways to contribute.

Solution contributors

  • Self-hosted integration solutions: Includes connectivity and integration with third-party applications such as Jira, Confluence, GitLab, Jenkins, and other tools.

  • SaaS-based integration solutions: Includes connectivity and integration with services like Twitter, Zendesk, Salesforce, and hundreds of other extensions with services like Zapier.

  • Programming solutions: Includes language-specific drivers and connectors to simplify the work of other developers.

  • Mattermost user experience plugins: Includes server and client-side plug-ins that enhance the native capabilities of a Mattermost server, such as voice, video, and screensharing with Zoom’s self-hosted or vendor-hosted solutions.

  • Federated experiences: Includes bridges with IRC, Slack, and other messaging applications through solutions like Matterbridge.

  • Custom user experiences: Includes integrations into Terminal and Pidgin built off the same core APIs as Mattermost’s Web, Desktop, iOS, and Android experiences.

Community Coordinator: Jason Blais

LinkedIn recognition

You are welcome to document your contributions to the Mattermost open source project in your resume or on LinkedIn in any matter you feel is accurate. Below is an example of an entry:

  • Title: Open Source Solution Contributor

  • Organization/Company: Mattermost

  • Location: [Where you did your work]

  • From: [Date started]

  • I currently work here: Check "Yes" if you continue to maintain your work

  • Headline: Solution contributor for Mattermost open source project

  • Description: [Description of your solution, its benefit to end users, and link to project. Example: "Maintainer of Mattermost-Zoom plugin which offers voice, video and screensharing for Mattermost end users through Zoom integration, either through a self-hosted private cloud deployment or a vendor-hosted SaaS service from Zoom. See the project at https://github.com/mattermost/mattermost-plugin-zoom."]

Other contributor types beyond solution contributors are also welcome to use and modify this LinkedIn template to document their contributions.

Platform contributors

  • Level 2: Corrections or improvements to on-screen text, documentation, or help text. Cosmetic improvements to code base.

  • Level 3: Corrections of minor bugs in code base other than on-screen text, documentation, or help text either through spontaneous contribution or by volunteering for and being assigned a ticket by a core committer.

  • Level 4: Corrections to major bugs, or the implementation of minor feature either through spontaneous contribution or by volunteering for and being assigned a ticket by a core committer. Alternatively, requesting and being assigned a ticket of 2 mana or higher by core committer and completing the project.

  • Level 5: Requesting and being assigned a ticket of 8 mana or higher by core committer and completing the project.

  • Core Committer: Highly skilled developer who becomes a maintainer and regular contributor to core Mattermost open source projects.

Community Coordinator: Jason Blais and Ben Schumacher

Translation contributors

Community Coordinator: Jason Blais

Documentation contributors

Community Coordinator: Carrie Warner and Justine Geffen

Quality Assurance contributors

Community Coordinator: TBD

Knowledge Base contributors

Community Coordinator: Amy Blais

Deployment solution contributors

Community Coordinator: Jason Blais and Amy Blais

UX Design contributors

Community Coordinator: Andrew Brown

Coordination contributors

Coordination Contributors help organize and align contributors from all the different roles above. When coordinating and leading a contributor community, key principles to keep in mind include:

  • Make it easy and realistic for contributors to get started.

Have clear instructions and realistic expectations. Remember there are thousands of open source projects in the world so the more difficult it is to contribute the fewer contributions there will be.

  • Recognize, retain, and recruit

Recognizing people’s contributions is vital to keeping them engaged. Leverage the existing programs to acknowledge the impact people are having. Retaining active contributors is hugely impactful because they’re trained and ready to go on future projects, and both acknowledgement for jobs done well and new, interesting projects are key to keeping momentum going. The next more important is recruiting new contributors and being able to showcase a vibrant and active existing community to offer a model for new contributions.

  • Focus on high impact, skill appropriate contributions

When possible, influence contributors to apply themselves to the highest impact tickets and projects appropriate for their skill level. Meaningful contributions early in the contributor journey are a powerful way to draw people into the community.

Mattermost staff

Mattermost staff are paid by Mattermost, Inc. to take on any of the contributor roles mentioned above, as well as to develop and support Mattermost Enterprise Edition as a commercial extension of the Mattermost open source project for large and sophisticated organizations.

As of May 2020, . Solution Contributors create a host of technologies to empower Mattermost software to solve real world problems. Technologies include:

Platform contributors provide improvements to the core Mattermost open source projects under . Contributions may be made at different levels of skill and impact:

Level 1: Stated intention to contribute by completing which adds contributor’s name to .

All contributors Level 2 and above are eligible for a acknowledging their role in the open source project.

Translation contributors can create and update translations to existing or new Mattermost languages at . In addition, community members can become “Language owners” and help review, coordinate and supervise the translation of Mattermost into languages they speak.

Documentation Contributors update, edit, and create new documentation, help text, training, and other materials to help the community get the most out of Mattermost software. Core documentation is found at and contributions can be made via the open source repository at .

Quality Assurance contributors help find, confirm and report product defects via our process at . Anyone who encounters a verifiable defect is welcome to file a bug on the system.

Bonus: When a QA contributor finds and reports a bug on a release candidate build of Mattermost prior to the final release of the system, they can be awarded a for their contribution.

Knowledge Base contributors share feedback, questions, and answers on Mattermost through forums for , , GitHub issues, and on the .

Deployment solutions contributors create packaging and automation for making it easier to deploy Mattermost, using tools such as Docker, Kubernetes, and other leading virtualization and orchestration solutions. See for guidance on how to build to common Mattermost standards.

UX Design contributors influence the design of the Mattermost user experience through discussion in the ux-design channel on the Mattermost continous integration server at and through contributions to the on .

Learn about all the ways to get involved with our community
over 1,900 open source projects on GitHub reference Mattermost
https://github.com/mattermost/
Mattermost Contributor Agreement
Mattermost Approved Contributor’s list
custom-printed Mattermost Mug
https://translate.mattermost.com
https://docs.mattermost.com
https://github.com/mattermost/docs/
https://www.mattermost.org/filing-issues/
Mattermost Bug Hunter Award
troubleshooting
feature proposals
Mattermost community server
Deployment Solutions Programs
https://community.mattermost.com/core/channels/ux-design
Mattermost User Experience Guidelines
GitHub