https://gitlab.synchro.net/main/sbbs/-/commit/c504019e0f2b623f9d17a0a0
Modified Files:
src/doors/syncmoo1/README.md src/doors/syncretro/README.md src/doors/syncrpg/README.md src/doors/syncscumm/README.md
Log Message:
doors: drop internal "Mx" milestone jargon from the door READMEs
The door READMEs described status in terms of "M1/M2/M3..." milestones -- opaque shorthand that means nothing to a reader and, worse, is reused
across every door/lib/project to mean something different each time. A
user on IRC hit exactly this ("what is M5?"). READMEs and other user/sysop-facing docs should describe what works in plain terms.
- syncretro: "Status: M1 (video), M2 (input), M3 (multi-core), M4
(audio) and M6 (Windows) complete" -> named plainly; the "(M5: ...)"
remaining-work label reworded to "core options and save states".
- syncmoo1: "Status: M1 + audio" -> "playable, not yet polished"; dropped
"milestones" from the DESIGN.md pointer.
- syncrpg, syncscumm: dropped "milestones" from the See-also pointers.
Docs only. Internal design docs (DESIGN.md, plans/, the M#_*.md notes,
etc.) keep their milestone tracking -- that's legitimate developer-facing
use; this change is scoped to the user/sysop-facing READMEs. Prompted by Accession's question on IRC.
Co-Authored-By: Claude Opus 4.8 (1M context) <
noreply@anthropic.com>
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)