TPAC 2026 Status Report
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
Editors, TPAC 2026 is in Dublin and online, from 26 to 30 October.
WebApps will meet on Monday 26 and Tuesday 27 October, with a joint meeting with the Devices and Sensors WG on Thursday 29 October.
We need you to do two things before 30 September 2026:
- Add the
TPAC2026label to any issues you want to discuss with the WG - Post a spec status report as a comment on this issue
Your status report should answer these questions:
- What progress have you made on your spec in the last 12 months?
- What blockers, if any, are preventing you from progressing your spec to CR or Req?
- Is there a testing plan for your spec?
- What are the next steps for your spec and do you need any help?
Note: post a status report even if you will not be at TPAC. Thank you.
@LJWatson, @marcoscaceres, and @mkruisselbrink.
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 this issue and the linked TPAC 2026 information and schedule. Review the relevant specification's progress, blockers, testing plan, and next steps, then post the requested status report as a comment before 30 September 2026 and add the TPAC2026 label to issues for WG discussion.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100