Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Council decision side effects

未关闭
#751 23 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
停滞
技术栈
html
领域
documentation

调研方向

先从链接的 Process Draft 中关于 sustaining an objection、Team 和 Formal Objection 的章节开始,然后查看包含 23 条评论的讨论串,了解其中尚未解决的决定。完成的标准是:Council 的建议和缓解权限在 Process 文档中有一致的措辞;issue 未指定要运行的文件或测试。

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

描述

FO/Council

When sustaining an objection, it should recommend a way forward. If the overturned decision has already had consequences (e.g., if the objection concerns material already in a published document) the Council should suggest how these consequences might be mitigated. The Team is responsible for making sure that adequate mitigations are enacted in a timely fashion; and the Formal Objection is not considered fully addressed until then.

This attaches new and relatively unconstrainted powers to the Council -- what is the status of their 'recommendations' and 'mitigations'? Are the required to be followed? If they have unanticiapted side effects on other matters that have consensus, can they be appealed?

The safest thing to do would be to remove this text and only empower the Council to give a thumbs up/down. Failing that, stating that the recommentations are to the WG are suggestions for further consideration, without formal standing would help. Any mitigations that require Team action should be limited to those activities which the Team has authority to perform.

主要语言
HTML
星标
263
派生
195
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

w3c/process 的其他 Issue

查看 w3c/process 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

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