Public: anyone can read this; the crew can change it.
Decision written: how a person with no account gets in to contribute to a public app #9573
Reviewed pull #9600 at its head: ticked docs/features/guests.md lays out the options in plain words (their own forge and a guest pull from it, an invite request, a guest account limited to forks and pulls), what each risks, and which one the crew recommends.. left open: The issue is closed only after the owner or a writer comments the choice; the doc records it. — No owner or writer choice is commented yet and the doc says Decision: not yet recorded..
Left open after pull #9600 landed: 1 unticked item remains (The issue is closed only after the owner or a writer comments the choice; the doc records it.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Left open on purpose: the last box is the owner's choice, not a builder's task. docs/features/guests.md (landed in #9600) lays out the options and the crew's recommendation. When the owner or a writer comments which way in to take, the doc records it and the issue closes.
The doc is written (docs/features/guests.md); the remaining box is the owner's choice, not a builder's work. Closing so it stops waiting on the board: when the owner or a writer comments the choice on #334, the planner opens one issue to record it in the doc and build it.
Deferred behind the Later gate: docs/features/guests.md lays out the options; the remaining box is the owner's choice. When the owner or a writer comments it, the planner opens one issue to record and build it.
Correction: not deferred. #9574 builds what this decides, so this stays open in P2, held for a person: the owner or a writer comments the choice here, records it in docs/features/guests.md (or asks the crew to), and closes it. No builder is handed it.
Still held for a person, not deferred: #9574 builds what this decides, so it cannot sit behind the Later gate, and the planner cannot drop a person's ask. The options and the crew's recommendation are in docs/features/guests.md. The owner or a writer comments the choice here; then the doc records it and this closes.
Unchanged on purpose, and asked on #334: the one open box is the owner's choice. Opening a builder issue for it would hand a builder a decision that is not theirs, and #9574 waits for it. Pick one of the ways in from docs/features/guests.md in a comment here; the planner then opens the issue that records it and #9574 builds it.
From #9428 box 5. Signup on the root forge is invite-only, so contributing needs a decided way in. This issue is the written decision with the options and their costs; a person picks.
Done looks like:
docs/features/guests.mdlays out the options in plain words (their own forge and a guest pull from it, an invite request, a guest account limited to forks and pulls), what each risks, and which one the crew recommends.Files: docs/features/guests.md. Risks: no code change here; it decides what pk4 builds.