Commit 2e2eeb13b3
Verified · cmc
Layout: unified · split
docs/roadmap.org +18 −11
| @@ -85,14 +85,21 @@ Recorded so their absence reads as a decision, not an oversight: | |||
| 85 | - email patch flow — revisit only if sourcehut-style demand appears | 85 | - email patch flow — revisit only if sourcehut-style demand appears |
| 86 | - federation (ForgeFed) and Postgres — no current need at this scale | 86 | - federation (ForgeFed) and Postgres — no current need at this scale |
| 87 | 87 | ||
| 88 | * Open questions | 88 | * Decisions |
| 89 | 89 | ||
| 90 | - **What is gitbay.org?** Today: the author's personal forge and the | 90 | - **gitbay.org will eventually be open to all.** (Decided 2026-08-24.) |
| 91 | project's home. Options: keep it closed (flagship demo), invite-only | 91 | Sequencing consequence: before flipping =registration = "open"=, the |
| 92 | for collaborators, or eventually open registration (which pulls #14, | 92 | instance needs #14 (audit log, rate limiting, quotas), #9 (web |
| 93 | #9, and rate limiting forward). No decision needed until Phase 1 | 93 | signup), an SMTP relay configured for verification mail, and enough |
| 94 | lands. | 94 | of Phase 1 that new users get a credible product. Interim step: |
| 95 | - **Versioning**: nothing is tagged. Suggest cutting v0.1.0 with #26 and | 95 | invite mode for early collaborators as soon as [mail] is configured. |
| 96 | adopting semver for the protocol_version relationship. | 96 | - **Versioning**: semver, starting at v0.1.0 on the current state. |
| 97 | - **Second-contributor readiness**: CONTRIBUTING notes, and whether MRs | 97 | 0.x signals moving surfaces; =protocol_version= increments only on |
| 98 | from outside collaborators imply moving gitbay.org to invite mode. | 98 | breaking envelope/command changes and is otherwise decoupled from |
| 99 | release numbers. v1.0.0 when Phase 1 and #26 land. Tags are | ||
| 100 | annotated and signed. | ||
| 101 | - **Second contributors**: invite mode is the on-ramp (their keys and | ||
| 102 | verified emails make signed-main enforceable for them too). A | ||
| 103 | CONTRIBUTING file states the workflow: fork on gitbay.org, MR with | ||
| 104 | signed commits, =go test ./...= green, review required once #19 | ||
| 105 | exists. No CLA — 0BSD needs none; sign-off optional. | ||