Inconsistency in references between TR drafts and EDs.
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
We should probably be consistent unless we have a good reason not to be. Obviously for REC advancement we need to be referring to TR (sadly!) but we probably generally want to point people towards EDs.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or entry points. Locate references to TR drafts and EDs across the specification, determine which references should remain TR for REC advancement, and treat the work as done when the remaining references are consistently directed to the intended document.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100