- From: Johannes Wilm <notifications@github.com>
- Date: Mon, 08 Dec 2025 08:25:21 -0800
- To: w3c/editing <editing@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/editing/pull/515/review/3552926541@github.com>
@johanneswilm commented on this pull request. > + + + + <section id="decisions"> + <h2> + Decision Policy + </h2> + <p> + This group will seek to make decisions through consensus and due process, per the <a href="https://www.w3.org/Consortium/Process/#Consensus">W3C Process Document (section 5.2.1, Consensus)</a>. Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required.</p> + <p> + However, if a decision is necessary for timely progress and consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote and record a decision along with any objections. + </p> + <p> + To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional. + + A call for consensus (CfC) will be issued for all resolutions (for example, via email, GitHub issue or web-based survey), with a response period from <span id='cfc'>one week</span>, depending on the chair's evaluation of the group consensus on the issue. @siusin Is it possible to adjust the wording here that a CfC is issued implicitly automatically with every resolution to make it clear that we do not start a separate manual process of issuing a CfC with every resolution? -- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/pull/515#pullrequestreview-3552926541 You are receiving this because you are subscribed to this thread. Message ID: <w3c/editing/pull/515/review/3552926541@github.com>
Received on Monday, 8 December 2025 16:25:25 UTC