Governance: Difference between revisions
mw push |
mw push |
||
| Line 25: | Line 25: | ||
* [[GetStarted|Getting started]] | * [[GetStarted|Getting started]] | ||
== Contribute / | == Contribute / next steps == | ||
When raising governance questions, include the affected system, impact radius, and decision needed. That gives maintainers enough context to route and resolve the issue efficiently. | When raising governance questions, include the affected system, impact radius, and decision needed. That gives maintainers enough context to route and resolve the issue efficiently. | ||
Revision as of 23:20, 28 February 2026
What this page is
This page describes how decisions are made for shared 44Net resources and documentation. Use it when you need to understand ownership, authority, or escalation paths.
What you can do today
- Read stewardship context in About 44Net.
- Check current expectations in Policies.
- Raise unclear ownership questions through Community and mailing lists.
- Keep proposed edits scoped and reviewable via Contributing.
What this page will cover
- Decision domains: policy, operations, and documentation.
- Maintainer roles and delegation patterns.
- How proposals are reviewed and accepted.
- Escalation path for unresolved technical disputes.
- Recordkeeping for governance decisions.
Related pages
Contribute / next steps
When raising governance questions, include the affected system, impact radius, and decision needed. That gives maintainers enough context to route and resolve the issue efficiently.