Specify where to report an issue when one isn't certain which repository to report to.
@vivienlacourba is already working on this.
Since Feb 2, 2026.
- Dominant language
- HTML
- Stars
- 84
- Forks
- 69
- Avg merge
- 14h 52m
- Merged PRs (30d)
- 2
Description
Some W3C services might not correspond 1:1 to public repositories, and some might be obscurely named. A place to recommend untriaged bugs be reported to for transfer (which GitHub supports) would be an improvement. Otherwise, I would report them to .github/issues by default.
Some examples of when this would be of use are:
-
...when reporting bugs to Tracker (like
WAI/APA/track/users/?login): ^1Tracker's code (which resides in WWW/2005/06/tracker/src) hasn't been released at this stage, as it relies on the specific schemas of W3C internal databases.
-
When reporting documentation problems, like
w3c/process/issues/130#issuecomment-3349176507describes. An example of one of these is/html/body/p[9]ofw3.org/2019/01/bugzilla-shutdown.html#migration)'s placeholder:(this section still needs work)
Obviously, no correspondent repositories, nor Bugzilla products, exist for those. ^2
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.