Skip to contents

Purpose

sceptre is maintained by a small team with shared responsibility for its scientific validity, software quality, and long-term usefulness. This document records who maintains the project, how decisions are made, and how repository responsibilities are assigned.

Maintainers

The current maintainers are:

  • Eugene Katsevich — Lead Maintainer.
  • Timothy Barry — Maintainer.
  • Louis Deutsch — Maintainer.

Decision making

Routine implementation and maintenance decisions may be made by the maintainer doing the work, subject to code review.

The maintainer group discusses material decisions and seeks consensus. Material decisions include:

  • changes to statistical methodology;
  • additions, removals, or breaking changes to the public API;
  • release timing and supported-platform policy;
  • roadmap changes; and
  • changes to licensing, governance, or the Code of Conduct.

If maintainers cannot reach consensus on a technical, release, or roadmap decision, the decision is made by majority vote, with the Lead Maintainer casting the tie-breaking vote if necessary. Changes to licensing, governance, the Code of Conduct, or maintainer membership require agreement of the maintainer group.

Code review

The Lead Maintainer coordinates code review and releases. Changes are ordinarily made through pull requests. Pull requests from non-maintainers require approval from a maintainer before merging. Pull requests authored by maintainers should, whenever practical, be reviewed by another maintainer before merging. Maintainers review contributions for consistency with the project’s goals and scientific and technical standards.

Joining and leaving the maintainer group

New maintainers are added by agreement of the existing maintainers after a sustained record of constructive contributions and demonstrated ability to uphold the project’s scientific, technical, and community standards.

A maintainer may step down at any time. Maintainer status and repository access may also be reconsidered when responsibilities change or a maintainer is inactive for an extended period. Any removal not requested by the maintainer requires agreement of the other maintainers and a reasonable opportunity for the affected maintainer to respond.

Changes to this document

Changes to this governance document are proposed through a pull request and require agreement of the maintainer group. The governance model may evolve as the project and its contributor community grow.