Skip to content

GOVERNANCE.adoc

Latest commit

 

History

History
162 lines (105 loc) · 4.24 KB

GOVERNANCE.adoc

File metadata and controls

162 lines (105 loc) · 4.24 KB
Raw

Governance Model

This document describes the governance model for this repository.

Table of Contents

Overview

This repository follows a Sole Maintainer Governance Model:

  • Single maintainer (@hyperpolymath) has full authority over the project

  • All contributions are welcome and reviewed by the maintainer

  • Decisions are made transparently through GitHub issues and discussions

  • The project adheres to the hyperpolymath estate policies where applicable

Core Principles

Principle Description

Benevolent Dictatorship

Maintainer has final decision authority but seeks community input

Meritocracy

Contributions are judged on technical merit, not contributor identity

Transparency

All significant decisions are documented publicly

Consensus-Seeking

Maintainer prefers consensus but will decide when necessary

Open Contribution

Anyone can contribute via fork and pull request

Roles and Permissions

Role Permissions Assignment

Maintainer

Write access, merge rights, admin

@hyperpolymath

Contributors

Read access, fork, submit PRs

All GitHub users

Users

Use the software, report issues

All GitHub users

Decision Making Framework

Routine Decisions

  • Bug fixes

  • Documentation improvements

  • Minor feature additions

  • Dependency updates

Process: Maintainer reviews and merges PRs that meet quality standards.

Significant Changes

  • New major features

  • API changes

  • Architecture modifications

  • Breaking changes

Process: . Open issue describing the change . Discuss with community (minimum 72 hours) . Maintainer makes final decision . Document rationale in issue/PR

Structural Decisions

  • Repository purpose/renaming

  • License changes

  • Ownership transfer

  • Deprecation/archival

Process: . Extended discussion (minimum 1 week) . Maintainer makes final decision . Document in CHANGELOG and governance docs

Contribution Lifecycle

Stage Process

Ideation

Open issue, discuss feasibility

Development

Fork, implement, test thoroughly

Review

Submit PR, maintainer reviews within 7 days

Merge

Maintainer merges or requests changes

Release

Maintainer publishes according to project conventions

Conflict Resolution

In case of disagreements:

  1. Discuss in the relevant GitHub issue or PR

  2. Provide technical justification for positions

  3. Maintainer mediates and makes final decision

  4. Decision is documented and can be revisited later

Project Policies

This repository adheres to hyperpolymath estate-wide policies:

  • License: MPL-2.0 for code, CC-BY-SA-4.0 for prose (per standards/LICENCE-POLICY.adoc)

  • Code of Conduct: Follows hyperpolymath CODE_OF_CONDUCT.md

  • Security: Follows hyperpolymath SECURITY.md

  • Contributing: Follows hyperpolymath CONTRIBUTING.adoc conventions

Repository-Specific Conventions

Convention Description

Signing

All commits must be signed (SSH or GPG)

SPDX Headers

All source files must have SPDX license identifiers

Contractiles

Mustfile, Trustfile, Intendfile, Adjustfile in root

Machine Readable

META.a2ml in .machine_readable/6a2/

CI/CD

GitHub Actions workflows in .github/workflows/

Governance Evolution

As the project grows, this governance model may evolve:

  • Adding Co-Maintainers: When contribution volume warrants it

  • Forming a Team: For complex multi-maintainer projects

  • Adopting TPCF: For large, multi-repository projects (see rhodium-standard-repositories)

Changes to this document require the same process as Significant Changes above.

Changelog

Date Change By

2026-06-07

Initial governance model established

@hyperpolymath