TPAC 2025 status report
Open
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
TPAC 2025 will be hybrid.
The WebApps Working Group will meet in Kobe, Japan (and online) on:
- Monday 10 Nov
- Tuesday 11 Nov
- Thursday 13 Nov
If you plan to attend, either in person or remotely, please register here.
Editors, we need you to do two things before 30 October 2025:
- If you’d like to discuss your spec(s), add the label
TPAC2025to the relevant GitHub issues. - Complete a status report for your spec(s)
Status report
-
Please post your status report as a comment on this issue.
-
Your report should answer:
- Progress – What has your spec achieved in the last 12 months?
- Blockers – Is anything preventing it from advancing beyond CR?
- Testing – Is there a testing plan for this spec?
- Next Steps – How will you unblock it? Do you need help?
Note: Submit a status report even if you will not attend TPAC.
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
Start with the status-report questions in issue #1787 and review the relevant WebApps Working Group specification history and testing plan. Post a comment covering progress, blockers, testing, and next steps, and add the TPAC2025 label to relevant issues if discussion is needed.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100