[Docs] Give the alpha one findable page saying what it is not yet #610
Labels
No labels
accepted
bug
declined
docs
duplicate
enhancement
good first issue
in-progress
needs-info
privacy
security
triage
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
LibreKAT/Ocideck#610
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found in the pre-publication product review.
Evidence:
docs/FAQ.md:277-283is the only roadmap, and it is stale: it lists "Additional chart visualizations and data types" as planned whileREADME.mdalready enumerates thirteen chart types, and "Improved performance for large presentations" without saying what currently goes wrong. There is noROADMAP.mdand noKNOWN_ISSUES.md.The honesty that does exist is scattered across five files: the translation gaps in the README feature line, export accessibility in
docs/ACCESSIBILITY.md, web limitations indocs/HOSTING.md§5, "nothing to download yet" indocs/FAQ.md:36.Why this matters now: expectation management that a reader has to assemble from five files does not work. A critic finds the gaps first and presents them as a discovery rather than as your openness. For a 0.1.0 alpha, "what is broken" is a feature, not an embarrassment — this project is unusually good at that kind of candour and gets no credit for it because the candour is not in one place.
Proposal: one
KNOWN_LIMITATIONS.mdof at most one screen that gathers the five existing admissions with a pointer to each source, plus a line at the top of the README. Replace the stale roadmap section indocs/FAQ.mdwith a link to it — a roadmap you do not maintain is worse than none.Opgelost in #656 (gemerged).
make checkgroen op de gerebasede kop.