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
  • What is the Mattermost community server?
  • Contributors team
  • Staff team
  • Key channels for staff
  • Channel naming conventions
  • Email distribution lists
  • Workplace FAQs

Was this helpful?

Edit on Git
Export as PDF
  1. Operations

Workplace

Description of norms on Mattermost Community server

PreviousUser guidesNextPeopleOps

Last updated 11 months ago

Was this helpful?

What is the Mattermost community server?

The Mattermost community server runs the latest stable build of Mattermost's software, including all open source code for Mattermost Team Edition as well as commercial code for Mattermost Enterprise Edition.

It has two objectives:

  • Provide a workplace for Mattermost staff.

  • Engage with our , including users, contributors and partners.

The Mattermost community server is not a production server and has occasional downtime.

You can reach the server at:

The server is also available via the following URLs, primarily used to test pre-release features:

The server has two teams:

Contributors team

Staff team

Staff usernames on the Mattermost server

All Mattermost staff members hired after Jan 1, 2020 should have a username in the form of @[FIRST_NAME]_[LAST_NAME] for example "Alice Evans" should be alice.evans.

If there are duplicate first name and last names, the new person added should add a middle initial in the form of @[FIRST_NAME].[MIDDLE_INITIAL].[LAST_NAME] for example, "Alice Janice Evans" who joined after the first Alice Evans would be @alice.j.evans.

There are some user accounts that for legacy issues cannot use this format, for all other Mattermost staff--even those who joined before Jan 1 2020--should use the format that creates the most clarity.

Not mentioning staff while referring to them

By default, people's user names and first names trigger mention notifications in Mattermost. This can be distracting if people have the same first names, for example there are multiple people named "Chris" at Mattermost. If you want to mention someone without triggering a notification consider using their three letter initials, for example, "Alice Emily Evans" would be AEE.

Key channels for staff

The following table lists popular channels for Staff:

Purpose
Name
Description

ANNOUNCE Asynchronous Announcements

Public channel in STAFF team for making staff-wide announcements.

ANNOUNCE Synchronous Announcements

Public channel in STAFF team for weekly all-staff meeting (see link in header for more info on "COM", past recordings and materials, etc.

ANNOUNCE New Staff Announcements

Public channel in STAFF team for announcing and welcoming new staff members.

Channel naming conventions

Any Mattermost staff member can create, rename and archive channels on the pre-release server. When channels don't contain sensitive information they should default to Public channel in CONTRIBUTORS team and welcome participation by contributors.

We trust our staff to use names that are fast, obvious, forgiving, and also to help our colleagues with constructive suggestions when names could be improved through iteration.

The following conventions are in place for channels with common purposes:

Purpose
Naming Convention
Explanation

BUILD Translation Discussion

i18n: [LANGUAGE]

Public channel in CONTRIBUTORS team for collaborating on translations in different languages

EE: [FEATURE]

Public channel in CONTRIBUTORS team for openly discussing Enterprise Edition features with the public

SOCIALIZE Discuss geographic locations

Loc: [CITY OR AREA NAME]

Public channel in CONTRIBUTORS team for socializing with contributors including staff, partners and technical contributors in specific geographies.

Use cases: Organize social and professional meet-ups

SUPPORT Support PS customers

PS: [Customer Name]

Private channel in CONTRIBUTORS team Channel for Premier Support customers engaging with senior Support Engineer

COLLABORATE

Work with partners

Partner: [Partner Name]

Private channel in CONTRIBUTORS team for discussions with close partners and Mattermost staff

OPERATE Plan, review and iterate on company operations with MLT

MLT [TOPIC]

OPERATE Plan, review and iterate on company operations with MLX

MLX [TOPIC]

Email distribution lists

Workplace messaging solutions like Mattermost are excellent for real-time and topic-based communications.

When it comes to long-form cascaded communications (announced information to be forwarded to groups with context from different leaders), then email and email distribution lists are best, and we do use them at Mattermost.

Workplace FAQs

, which runs our upcoming stable release. This server includes work-in-progress features, and can contain bugs and have occasional downtime. This server receives regular pushes of features and/or bug fixes of the next release for testing purposes.

, which runs latest builds of Mattermost's software, including all pre-release features of our core products. It is the most unstable version of the Mattermost community server. Bugs and occasional downtime is expected as this server receives daily pushes of features and/or bug fixes for testing purposes.

URL:

Available to anyone who'd like to join the server using either an email and password account () or a Mattermost staff account, which is set up via Okta and requires MFA either through Okta or Google Authenticator.

URL:

A confidential space for requiring a Mattermost Okta account and MFA.

As an alternative to saying @alice.evans using AEE lets you refer to the person in passing without pushing an alert to them. For staff members that want to be alerted to even passing mentions of their name, they can opt in to that model by creating a on their three letter initials.

For example, the channel can be joined any contributor, partner or staff member to socialize with our .

BUILD Build EE with

Private channel in STAFF team for topic-specific channels for members of to work on , E.g. MLT Daily, MLT R&D, etc.

Private channel in STAFF team for topic-specific channels for members of . E.g. MLX Recruiting, MLT HR, etc.

We have a (you need to be a staff member subscribed to our Announcements channel for access).

This section provides staff with quick access to common questions and answers related to workplace policies, procedures, and general information. You can find a list of the frequently asked questions .

https://community-release.mattermost.com
https://community-daily.mattermost.com
https://community.mattermost.com/core
you can sign-up for a free account online
https://community.mattermost.com/private-core
keyword notification
Loc: Seattle
community
Mattermost Board summarizing email distributions lists at Mattermost
here
Announcements
Customer Obsession Meeting
Welcome
community
communities
Mattermost cadence
https://community.mattermost.comcommunity.mattermost.com
Mattermost Leadership Team
Mattermost Leadership Extended Team
Mattermost staff