Thanks for taking an interest. TaskTrack is a draft specification, so feedback and proposals are particularly welcome at this stage.
- Discussions — open-ended topics: should the spec do X, alternative designs, questions about intent, RFC-style proposals.
- Issues — concrete, actionable items: typos, broken links, internal inconsistencies, MiniMark/Specify compliance defects, missing rules for a case the spec should clearly cover.
If you're unsure which fits, open a Discussion. Maintainers can convert it to an Issue if it turns out to be actionable.
- For typos, link fixes, and other small editorial changes, a direct PR is fine.
- For anything that changes the meaning of the specification — new rules, removed rules, changed semantics, renamed terms — please open an Issue or Discussion first so the change can be agreed before review.
- Keep PRs focused. One conceptual change per PR.
- The golden source is
spec/TaskTrack.md. Do not edit publications (files namedTaskTrack-[REVISION_IDENTIFIER].md); those are produced from the golden source at release time. - All TaskTrack files must remain valid MiniMark documents. In particular: no tabs, ATX headings only, fenced code blocks with a language identifier, straight quotes only.
By submitting a contribution (issue text, discussion text, or pull request) you agree that it is licensed under CC BY 4.0, the same license as the rest of this repository. No separate CLA is required.