Contributing: Difference between revisions
mw push |
mw push |
||
| Line 6: | Line 6: | ||
== What you can do today == | == What you can do today == | ||
* Start by identifying a specific gap from [[GetStarted|Getting started]] or [[ | * Start by identifying a specific gap from [[GetStarted|Getting started]] or [[Provisioning Methods|Provisioning Methods]]. | ||
* Share proposed changes in [[Community|Community and mailing lists]] before major edits. | * Share proposed changes in [[Community|Community and mailing lists]] before major edits. | ||
* Prefer small, verifiable updates over broad rewrites. | * Prefer small, verifiable updates over broad rewrites. | ||
Latest revision as of 01:14, 1 March 2026
What this page is
This page explains how to contribute useful work to 44Net docs and operations. It is for operators, maintainers, and new participants who want to help.
What you can do today
- Start by identifying a specific gap from Getting started or Provisioning Methods.
- Share proposed changes in Community and mailing lists before major edits.
- Prefer small, verifiable updates over broad rewrites.
- Add concrete context: device role, NAT posture, tunnel endpoint, routing behavior, and observed outcomes.
What this page will cover
- Contribution workflow for wiki content.
- Standards for operational accuracy and scope.
- How to document procedures with rollback and safety notes.
- Review expectations for networking and policy content.
- Ownership and maintenance for long-lived pages.
Related pages
- Community and mailing lists
- Governance
- Policies
- What People Build
- Getting started
- Routing and connectivity
Contribute / next steps
When proposing edits, include the problem statement, what changed in real operation, and what remains unverified. That allows reviewers to approve updates without guessing intent or risk.