Files
xinjian0101-continuity-dire…/MAINTAINERS.md
xinjian0101 57993f8a3e feat: establish OSS maintainer governance and health automation
Add maintainer ownership, governance, roadmap, ecosystem and adoption documentation, release and security processes, Dependabot, structured adoption reporting, and automated maintainer-health checks.
2026-06-19 17:46:35 +08:00

1.9 KiB

Maintainers

Continuity Director is maintained as a public open-source project.

Primary maintainer

GitHub Role Scope
@xinjian0101 Primary maintainer Architecture, code review, issue triage, releases, security, documentation, and community support

The primary maintainer owns day-to-day repository operations, including accepting or rejecting changes, maintaining compatibility, responding to reports, and preparing releases.

Maintenance responsibilities

  • Review pull requests and protect public node identifiers and workflow compatibility.
  • Triage bug reports, feature requests, support requests, and security reports.
  • Maintain CI, release packaging, changelog entries, and supported-version documentation.
  • Keep GitHub Actions and maintenance automation current.
  • Publish roadmap changes and explain material scope decisions.
  • Avoid publishing fabricated adoption, download, or user metrics.

Response targets

These are operational targets, not service-level guarantees:

Item Target
New issue triage Within 7 days
Pull-request acknowledgement Within 7 days
Security report acknowledgement Within 72 hours when private reporting is available
Roadmap review Monthly while the project is active
Patch release review After validated fixes accumulate or a material compatibility issue is resolved

Adding maintainers

Regular contributors may be invited as reviewers or maintainers after demonstrating sustained, high-quality participation. Expanded access is based on project need, review quality, security awareness, and compatibility discipline.

Inactivity and succession

If the primary maintainer expects an extended absence, the repository roadmap should be updated and an active trusted contributor may be granted temporary or permanent maintenance responsibility. Ownership changes must be documented publicly.