Select and commit the license, publish a clear change summary, and make pre-launch status visible anywhere install expectations are set.
Repository readiness
Open-source launch should give early operators enough context to act safely.
This is the public repository gate for The Gateway: license, support scope, install evidence, contribution boundaries, and privacy claims must be clear before broad distribution.
Publish install, rollback and recovery, hardware matrix, route/DNS verification, fallback checks, and first-run evidence.
Keep support access explicit, time-limited, revocable, and logged. Document what support will not do.
Use templates for bugs, installs, hardware reports, documentation fixes, PRs, security contact links, and the issue label guide.
Explain how The Gateway helps verify routing, DNS, fallback, and leak behavior without promising anonymity by itself. Use the posture checklist.
Public copy stays focused on operator value, product readiness, support boundaries, privacy limits, and evidence.
Published screenshots use realistic synthetic values and note the claim each image supports.
Public copy stays focused on operator value, product readiness, support boundaries, privacy limits, and evidence before broad release.
Published repository assets should avoid private notes, local paths, credentials, temporary hosts, and machine-specific assumptions.
Require redaction for logs, screenshots, support bundles, topology, private hostnames, and account identifiers before public submission.
Security checks report no unresolved high-severity issues before broad repository launch.
Public repository materials should avoid private notes, local paths, credentials, and machine-specific assumptions.
License, security policy, contribution guide, support policy, install guide, rollback guide, hardware matrix, issue templates, issue label guide, release checklist, security audit, build hygiene, and proof artifacts are present.
Contact addresses are placeholders, install has not passed on a fresh machine, rollback is undocumented, or anonymity/privacy limits are vague.
Repository evidence
Public repository claims need operator screenshots beside install proof.
Supports the first-run evidence requirement without exposing private hostnames or topology.
Supports the repository claim that route and DNS verification are observable and repeatable.
Supports hardware and install reports by showing which device classes were actually in scope.