Boundaries

Some of us don't want to work for free. We explain what to expect when interacting in the issue queue.

Priorities

Some of us set the roadmap. We explain how to make your issues a priority for us.

Co-maintenance

Some of us need help. We explain how to become a co-maintainer.

Sponsorships

Some of us can only work on the project when sponsored. We explain how to sponsor general development or specific features.

Process

Some of us don't enjoy certain tasks. We explain how to help to produce better release notes, documentation, etc.

Support

Some of us don't provide a support SLA. We explain how to obtain paid enterprise grade support.

A MAINTENANCE_MANIFESTO.md is a collection of Statements.

Statements can be written by the maintainer or chosen from a list of existing statements.

Maintenance Manifesto

This project adheres to the manifesto:
https://maintenance-manifesto.github.io/manifestos/sponsored-free-time.md

John Doe
Maintainer

Pre-made manifestos

This is an example of a re-used manifesto. In this cas the maintainer chose to adhere to the _Sponsored Free Time_ manifesto.

There are pre-made manifestos and pre-made statements. A maintainer may choose to have a MAINTENANCE_MANIFESTO.md like the on in the example. Even if a maintainer chooses to use an existing manifesto, as many amends, clarifications, and emphasis can be added as needed.

Find the manifesto that suits your needs in this list.

Statement #9: Priority

The maintainer of this module chooses the priority of any given task or issue arbitrarily based on personal preference or need.

If a user wants to increase priority on a certain issue they can do so by:

  • Writing documentation for issues marked as Needs docs.
  • Writing tests for issues marked as Needs tests.
  • Doing manual QA for existing patches.

The maintainer will appreciate the collaboration effort by increasing the priority of the requested issue.

John Doe
Maintainer

Pre-made and free-form statements

This is an example of a statement in a maintainer manifesto. A manifesto is a list of statements that the maintainer chooses to govern a particular project.

It is possible that a maintainer doesn't feel represented by any of the pre-made manifestos. In that case the maintainer can create a MAINTENANCE_MANIFESTO.md using pre-made statements. 

This project it governed by the following statements:
  * https://maintenance-manifesto.github.io/statements/9-priority.md
  * https://maintenance-manifesto.github.io/statements/2-sponsored-time.md
  * Environment donations (see below)
  * https://maintenance-manifesto.github.io/statements/3-positive-language.md

  Environment donations:
  If a user requires that the maintainer donates time for them (fixing a bug for them, giving them support, etc.), then the request should be accompanied by a proof of payment of a donation ($1 minimum) in the name of the project to any of the following environment focused non-profits:
https://www.gobmallorca.com/que-pots-fer/fes-un-donatiu.

In the example above the maintainer uses a set of pre-made statements as well a particularity (Environment donations) that the maintainer feels is important for that project.

Choose from the list of statements or write your own.

Users of the project now have the background

The point of the manifesto is to let users know about the boundaries set by the maintainer.

Promote the Manifesto

Help us make open source more sustainable. Share this project with your contacts and encourage them to add a MAINTENANCE_MANIFESTO.md in their open source repositories.

Share in Twitter or Contact us to help