Governance: document public maintainer and release ownership policy #6

Closed
opened 2026-06-23 16:46:21 +00:00 by mik-tf · 1 comment
Owner

Context

dioxus-bootstrap-css moved from a single-maintainer GitHub repository to Forge primary with a GitHub mirror. The public repo should document the maintainer model clearly enough that contributors understand where decisions and releases happen.

Desired behavior

Document a public, non-sensitive ownership policy:

  • Forge is the primary source repository.
  • GitHub is a mirror and Pages host.
  • Releases are cut from Forge-primary development via version tag.
  • The crate should not depend on exactly one human account for release ownership.

Acceptance criteria

  • Add a public maintainer/release ownership note in docs or README.
  • Explain maintainer roles and release authority without mentioning credentials, private operational details, or secret handling.
  • Keep the document neutral and organization-oriented rather than personal-account-oriented.

Signed-by: mik-tf mik-tf@noreply.invalid

## Context `dioxus-bootstrap-css` moved from a single-maintainer GitHub repository to Forge primary with a GitHub mirror. The public repo should document the maintainer model clearly enough that contributors understand where decisions and releases happen. ## Desired behavior Document a public, non-sensitive ownership policy: - Forge is the primary source repository. - GitHub is a mirror and Pages host. - Releases are cut from Forge-primary `development` via version tag. - The crate should not depend on exactly one human account for release ownership. ## Acceptance criteria - Add a public maintainer/release ownership note in docs or README. - Explain maintainer roles and release authority without mentioning credentials, private operational details, or secret handling. - Keep the document neutral and organization-oriented rather than personal-account-oriented. Signed-by: mik-tf <mik-tf@noreply.invalid>
Author
Owner

Implemented in f1b5306: added docs/GOVERNANCE.md and linked it from README.

The page documents the Forge-primary development home, GitHub mirror/Pages role, design rule, maintainer expectations, release branch/tag policy, and public issue expectations.

Forge Actions run 14 is green:

  • MSRV 1.85: success
  • Check, lint, format: success

Signed-by: mik-tf mik-tf@noreply.invalid

Implemented in `f1b5306`: added `docs/GOVERNANCE.md` and linked it from README. The page documents the Forge-primary development home, GitHub mirror/Pages role, design rule, maintainer expectations, release branch/tag policy, and public issue expectations. Forge Actions run 14 is green: - MSRV 1.85: success - Check, lint, format: success Signed-by: mik-tf <mik-tf@noreply.invalid>
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/dioxus-bootstrap-css#6
No description provided.