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
  • Who is eligible?
  • Eligible contribution areas
  • What types of contributions aren't eligible?
  • Process outline
  • Quarterly check-ins
  • Process for contributors to exit the program
  • Notes

Was this helpful?

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

Mattermost GitHub sponsorship

PreviousHelp Wanted ticketsNextThings candidates should know

Last updated 10 months ago

Was this helpful?

Mattermost participates in the GitHub sponsorship program to help empower our key contributors and sponsor them for 1 year. The goal of the program is to recognize exceptional community contributions that go above and beyond.

allows the developer community to financially support the people and organizations who design, build, and maintain the open source projects they depend on, directly on GitHub.

Who is eligible?

Mattermost GitHub sponsorship is considered for -like contributors ("Most Valued Professional") in any of the supported by GitHub.

MVP-like contributors:

  • Focus on contributions that have a wider impact that many can benefit from.

  • Have proven success working asynchronously in a self-serve, autonomous way that doesn’t require many direct touch points with Mattermost teams to develop, test, or document their contribution.

  • Give extra effort in a way that exceeds what’s expected.

  • Has, shares, and delivers on a clear vision.

  • Steps forward to assist when opportunities present themselves.

  • Has demonstrated empathy and understanding for the software development process.

Eligible contribution areas

  • Technical peer help on demand via public forums, including but not limited to: Mattermost Community server, Mattermost User Forum, and the Mattermost subreddit on Reddit.

  • Product localization via string translation (known also as l10n and i18n).

  • Lead monthly product localization delivery (cherry-pick L10N PRs, weekly community communication, data analytics/reporting, develop and deliver nurture campaigns to increase translation quality).

  • Product evangelism for technical communities.

  • Fix product issues and add new product functionality to improve the user experience.

  • Address user journey gaps such as migration tooling.

  • Customer-requested product integrations.

What types of contributions aren't eligible?

  • Code changes to features that Mattermost charges money to use. This includes features available only to Professional or Enterprise customers that aren't open-sourced, and code within the /enterprise GitHub repository where the majority of paid Enterprise features are maintained.

Process outline

  1. A Mattermost staff member recommends a contributor for sponsorship and writes a short motivation to support their recommendation. The nomination should include a description of what the contributor does for us and/or takes ownership for that we'd like to compensate them for. The nomination should be addressed to their direct manager as well as the program lead.

  2. Program lead sends a request to ap@mattermost.com to approve the sponsorship.

  3. Program lead informs the contributor of the nomination. Once the contributor has accepted it (by simply replying to the notice), the sponsorship is processed and appears in the contributor's GitHub profile.

  4. The staff member who recommended the contributor acts as an internal mentor to provide product guidance.

Quarterly check-ins

All sponsorship participants are expected to participate in quarterly check-ins with the program lead. Check-ins can occur asychronously on the Mattermost Community Server, or scheduled as a live meeting using Zoom. The goal of quarterly check-ins is to ensure organizational and program alignment, contributor satisfaction, support, empowerment, as well as participant retention. Continued sponsorship will be reviewed quarterly, and align with the end of Mattermost fiscal year quarters: April, July, October, and January. Sponsorship will be paused following 3 consecutive months of inactivity, disengagement, or failing to respond to check-in requests.

During quarterly check-ins:

  • Participants meet with the program lead to share their program feedback on what’s going well, what’s not going well, and any blockers encountered.

  • Internal team members working closely with participants share contextual performance feedback with the program lead.

Process for contributors to exit the program

  1. The sponsored contributor informs the program lead, by email, of their intention to leave the program.

  2. The program lead sends a request to IT to remove any applicable core contributor privileges as well as the sponsorship itself. Accounts Payable and the staff member who nominated the contributor are included for visibility.

Notes

  • The current program lead is Carrie Warner.

Mattermost product and development documentation contributions. Documentation isn’t currently eligible because of the range of effort complexity involved (from typo fixes to new content development) which doesn’t directly map to the .

An senior leader approves the recommendation and notifies the program lead.

GitHub Sponsors
MVP
available regions
existing reimbursement structure
MLT