Skip to content

GOVERNANCE_NOTES.md

Fontshow — Governance and Decision Records

Current version: v0.28.7.post14 Applies to: Project planning, technical decisions, and contributions

Purpose

This document defines the governance model for the Fontshow project.

It explains:

  • how decisions are made and recorded,
  • how scope changes are approved,
  • how planning artifacts evolve over time.

The goal is to provide clarity and continuity, not bureaucracy.

Governance Principles

  • Explicit decisions Important decisions must be recorded and discoverable.

  • Traceability Decisions should be traceable to context, rationale, and consequences.

  • Minimal process Governance should support development, not obstruct it.

Decision Types

Planning Decisions

Examples:

  • Roadmap changes
  • Milestone redefinitions
  • Timeline adjustments

Requirements:

  • Document the decision.
  • State what is being replaced or superseded.
  • Record the rationale.

Technical Decisions

Examples:

  • API contracts
  • Testing strategy changes
  • CLI behavior guarantees

Requirements:

  • Explain alternatives considered.
  • Record constraints and trade-offs.
  • State whether the decision is reversible.

Scope Decisions

Examples:

  • Deferring features
  • Rejecting proposed changes
  • Splitting or merging milestones

Requirements:

  • Explicit justification.
  • Clear impact assessment.

Decision Records

Decisions SHOULD be recorded as lightweight notes containing:

  • Title
  • Context
  • Decision
  • Rationale
  • Consequences

Decision records MAY live in:

  • a dedicated documentation file,
  • or clearly labeled sections in relevant documents.

Change Management

  • Changes to governance documents MUST be explicit.
  • Silent changes are not acceptable.
  • Superseded decisions MUST remain accessible for historical reference.

Authority and Responsibility

  • The project maintainer has final authority.
  • Contributors are encouraged to propose changes.
  • Proposals should be clearly marked and justified.

Relationship to Other Documents

  • Governance notes complement:
  • ROADMAP.md
  • MILESTONES_DEFINITION.md
  • ISSUE_MODEL.md

They do not replace technical specifications or contracts.

Status

This governance model is active and applies to all planning and decision-making from v0.28.7.post14 onward.