TPAC 2026 Status Report
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- documentation
Research direction
Start with the TPAC 2026 schedule and review the File API work from the last 12 months. Post a comment answering the four status questions about progress, blockers, testing, and next steps or help needed, and add the TPAC2026 label to relevant issues before 30 September 2026.
Written by the indexing model from the issue text.
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.
- Dominant language
- HTML
- Stars
- 118
- Forks
- 52
- Avg merge
- 9d 16h
- Merged PRs (30d)
- 1
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.
More from w3c/FileAPI
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100