TPAC 2026 Status Report

未关闭
  • 哪里不对？
#418 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
18/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
活跃
领域
documentation

调研方向

This is a coordination request for spec editors, not a code change, and it is addressed to the named editors (@LJWatson, @marcoscaceres, @mkruisselbrink). Done means a status comment answering the four questions on this issue and the TPAC2026 label added to any issues to discuss, both before 30 September 2026. A newcomer would need to be an editor of the Push API spec to contribute, so it is not a good first issue.

由索引模型根据 Issue 内容生成。

描述

TPAC2026

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:

  1. Add the TPAC2026 label to any issues you want to discuss with the WG
  2. Post a spec status report as a comment on this issue

Your status report should answer these questions:

  1. What progress have you made on your spec in the last 12 months?
  2. What blockers, if any, are preventing you from progressing your spec to CR or Req?
  3. Is there a testing plan for your spec?
  4. 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.

主要语言
HTML
星标
158
派生
43
平均合并
2 天 6 小时
30 天内合并 PR
2

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

w3c/push-api 的其他 Issue

查看 w3c/push-api 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。