Files
MokoOnyx/GOVERNANCE.md
Jonathan Miller 8258ed804a
Some checks failed
Standards Compliance / Secret Scanning (push) Successful in 3s
Standards Compliance / License Header Validation (push) Successful in 4s
Standards Compliance / Repository Structure Validation (push) Successful in 5s
Standards Compliance / Coding Standards Check (push) Failing after 3s
Standards Compliance / Version Consistency Check (push) Successful in 3s
Standards Compliance / Workflow Configuration Check (push) Failing after 2s
Standards Compliance / Documentation Quality Check (push) Successful in 3s
Standards Compliance / README Completeness Check (push) Successful in 3s
Standards Compliance / Git Repository Hygiene (push) Successful in 2s
Standards Compliance / Script Integrity Validation (push) Successful in 4s
Standards Compliance / Line Length Check (push) Failing after 4s
Standards Compliance / File Naming Standards (push) Successful in 2s
Standards Compliance / Insecure Code Pattern Detection (push) Successful in 3s
Standards Compliance / Code Complexity Analysis (push) Successful in 3s
Standards Compliance / Code Duplication Detection (push) Successful in 4s
Standards Compliance / Dead Code Detection (push) Successful in 3s
Standards Compliance / File Size Limits (push) Successful in 2s
CodeQL Security Scanning / Analyze (javascript) (push) Failing after 1m9s
Standards Compliance / Binary File Detection (push) Successful in 4s
CodeQL Security Scanning / Analyze (actions) (push) Failing after 1m11s
Standards Compliance / TODO/FIXME Tracking (push) Successful in 3s
Standards Compliance / Dependency Vulnerability Scanning (push) Successful in 5s
Standards Compliance / Broken Link Detection (push) Successful in 5s
Standards Compliance / Unused Dependencies Check (push) Successful in 7s
Standards Compliance / API Documentation Coverage (push) Successful in 3s
Standards Compliance / Accessibility Check (push) Successful in 3s
Standards Compliance / Performance Metrics (push) Successful in 3s
Standards Compliance / Enterprise Readiness Check (push) Successful in 3s
Standards Compliance / Repository Health Check (push) Successful in 4s
Standards Compliance / Terraform Configuration Validation (push) Successful in 6s
CodeQL Security Scanning / Security Scan Summary (push) Successful in 1s
Standards Compliance / Compliance Summary (push) Successful in 1s
Repo Health / Access control (push) Successful in 1s
Auto-Update SHA Hash / Update SHA-256 Hash in updates.xml (release) Successful in 4s
Repo Health / Release configuration (push) Failing after 3s
Repo Health / Scripts governance (push) Successful in 3s
Repo Health / Repository health (push) Failing after 3s
MokoOnyx v01.00.00 — initial release (successor to MokoCassiopeia)
All files renamed from mokocassiopeia to mokoonyx.
Update server points to MokoOnyx repo.
Bridge migration removed (clean standalone template).
Version reset to 01.00.00.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-19 17:19:03 -05:00

3.9 KiB

Governance Overview

This document defines the governance framework for the MokoOnyx project. The objective is to ensure clear ownership, predictable decision making, and accountable stewardship across development, releases, and community interaction.

Project Ownership

MokoOnyx is owned and maintained by Moko Consulting. Final authority for project direction, releases, and policy enforcement resides with the project owner.

Roles and Responsibilities

Maintainers

Maintainers are responsible for:

  • Setting technical direction and release priorities.
  • Reviewing and approving pull requests.
  • Managing releases and distribution artifacts.
  • Enforcing repository policies, including security and conduct requirements.

Contributors

Contributors may:

  • Submit pull requests and issues.
  • Propose enhancements and report defects.
  • Participate in technical discussions.

Contributors do not have merge authority unless explicitly granted.

Decision Making

Decisions are made using a maintainers led model:

  • Routine changes are approved through pull request review.
  • Material changes affecting architecture, branding, licensing, or release processes require maintainer consensus.
  • The project owner retains final decision authority if consensus cannot be reached.

Change Management

Significant changes should:

  • Be documented through issues or pull requests with clear rationale.
  • Consider backward compatibility and upgrade impact.
  • Include documentation updates when behavior or usage changes.

Release Authority

Only maintainers may:

  • Cut releases and publish artifacts.
  • Update version numbers and manifests.
  • Publish update metadata or advisories.

Release processes follow documented workflows and automation standards.

Security Governance

Security issues are governed by the SECURITY.md policy. Maintainers are responsible for confidential handling, coordinated disclosure, and publication of advisories when appropriate.

Conduct Enforcement

Behavior within the project is governed by CODE_OF_CONDUCT.md. Maintainers are responsible for enforcement actions and escalation handling.

Conflict Resolution

Conflicts are handled through:

  • Direct discussion between involved parties when appropriate.
  • Maintainer mediation when necessary.
  • Final determination by the project owner if required.

External Dependencies

The project depends on Joomla core and other third party components. Governance of upstream projects remains outside the scope of this repository, but upstream changes may influence project decisions.

Jurisdiction

This project is managed from Tennessee, USA. This statement is informational and does not constitute legal advice.


Metadata

Revision History

Date Change Summary Author
2025-12-18 Initial publication of governance model, roles, and decision processes. Moko Consulting