Skip to content
The first pages of the Maintainer Handbook template

Maintainer Handbook

Document template for Google Docs and Word

Make a copy in Google Docs
Price
Free
Difficulty
Beginner
Updated
November 12, 2026

Every page (7)

Overview

Open source projects stall when maintainers answer the same questions, make decisions in private and burn out before the next release. This handbook writes those rules down: how issues are triaged, when releases ship, who decides what, how the project is funded, and how maintainers keep their time. Each section names an owner and a time limit, so a newcomer knows what to expect.

The sample handbook is for Cinderfield Cloud, a fictional project with a six-weekly release cycle, two to five maintainers and a £662,000 income line. Replace the roles, response times and budget first, then run the set-up steps on a fresh machine. Every name, figure and contact in the file is fictional sample data.

Useful for

  • A new maintainer who needs to know how to triage the issue queue on day one
  • A release manager planning a six-weekly cycle with a security patch in between
  • A company asking for the licence, funding and governance rules before adopting

What's included

  • Cover page with the handbook title and prepared-for details
  • Triage architecture diagram with labels, owners and the issue flow
  • Release timeline with dates and a calendar of the busiest month
  • Governance team cards and a RACI table of key deliverables
  • Funding statement with income, costs, reserves and a budget target
  • Wellbeing article and a make-it-yours guide for the project

How to use it

  1. 1

    Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.

  2. 2

    Replace the project name, licence and repository links on the first page with your own.

  3. 3

    Run the set-up steps on a fresh machine, and correct any step that fails.

  4. 4

    Label real good first issues, add a code of conduct enforcement contact, and name the decision makers.

  5. 5

    Delete the guide page, then share the handbook in the repository or present it to contributors.

What you need

Requirements

  • A Google account with access to Google Drive

Works with

  • Google Docs
  • Microsoft Word (download the .docx)

Questions

Does this replace a licence or contributor agreement?

No. The handbook explains how people contribute and who decides, but your licence and any contributor agreement still need their own text, checked by a lawyer if companies use the project.

Are the project and people real?

No. Cinderfield Cloud, Idris Okafor, Nell Brandt, the funding figures and the contact details are all fictional sample data. Every email address ends in .example, so replace them before publishing.

How long should the triage rules be?

As short as they can be while still answering the question a newcomer asks. A reply within three working days and one labelled owner per issue is usually enough to start with.

  • #contributing-guide
  • #maintainer-handbook
  • #open-source-governance
  • #triage-process
  • #release-process
  • #code-of-conduct-template
  • #open-source-contribution

More contributing guide templates

See all 8

Also in Developer workflows

All developer workflows templates
Get this template

Preparing your template…