Rust RFC 的反馈窗口：为什么提案不该对所有人在所有阶段开放
Оригинальный заголовок: Feedback Windows
Заголовок и краткое изложение на выбранном языке ожидают перевода.
Rust 项目成员在讨论一个有争议的 RFC 时提出，并非所有提案在其生命周期每个阶段都对所有相关方开放反馈。作者由此总结出反馈窗口的实践：用类似根回的方式先建立共识，文档和设计未成熟前不广泛分享，明确反馈截止时间和期望的反馈类型，决策后明确“锁定”并做到 disagree and commit。作者认为，在反馈窗口之外提意见往往收效不佳并引发摩擦。
Полный текст на выбранном языке ожидает перевода. Пока показан оригинал.
Ryan Lopopolo•June 14, 2023
The Rust RFC process occurs in public on GitHub via PR reviews. RFCs are change proposals for all sorts of things (the language, the API, project governance, etc.).
On a particularly contentious RFC (I forget which), a project member made a comment that has stuck with me for a while. I don’t remember the exact quote, but paraphrasing, the nugget of wisdom went something like this:
It is not the case that all proposals are open to all feedback from all stakeholders at every point of their lifecycle.
Aligning on this as an organizational norm is pretty powerful. The following things flow from it:
- Use a nemawashi-like approach to build consensus.
- Do not share documents, plans, and designs to a wide audience before they are ready to be shared.
- Be explicit about when you expect feedback to be delivered by when shopping around a proposal.
- Be explicit about the type of feedback you are expecting and willing to consider when sharing a proposal.
- Communicate appropriately when a decision has been made and be clear that it is “locked in”.
- Disagree and commit.
- Be intentional about re-visiting a decision. Re-litigation has a very high bar for evidence of changing circumstances.
In my experience, delivering feedback outside of a feedback window is likely to be received poorly and cause lots of friction.
Источник: Ryan Lopopolo · hyperbo.la