Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tighten the how sustantive changes are handled post AC-Review #910

Merged
merged 3 commits into from
Sep 11, 2024
Merged

Tighten the how sustantive changes are handled post AC-Review #910

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
81e459f
Tighten the how sustantive changes are handled post AC-Review
frivoal Apr 18, 2024
8bbec65
Phrasing simplification
frivoal Aug 20, 2024
e973c36
phrasing improvement
frivoal Sep 11, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 30 additions & 5 deletions index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2772,13 +2772,31 @@ Determining the W3C Decision</h4>
If the proposal is adopted with changes other than <a href="#class-1">class 1 (markup) changes</a>,
then those changes <em class=rfc2119>must</em> be announced to the [=AC=]
and to the [=Group=] that owns the document (if any).

Additionally, when adopting a proposal with [=substantive changes=] integrated,
the announcement <em class="rfc2119">must</em> include rationale
for the substantive changes,
and those changes must have the [=consensus=]
of the subset of the [=AC=] that voted on the proposal
(including anyone who explicitly abstained).
for the substantive changes.

[=Substantive changes=] to the proposal <em class=rfc2119>may</em> only be adopted
if the revised proposal has [=consensus=]
frivoal marked this conversation as resolved.
Show resolved Hide resolved
of the subset of the [=AC=] that voted on the initial proposal
(including anyone who explicitly abstained),
or if any [=Formal Objections=] against the revised proposal are retracted or [=overruled=]
and the revised proposal otherwise has sufficient support to achieve [=consensus=].
For clarity,
the [=Team=] <em class=rfc2119>should</em> seek a response from this subset of the [=AC=]
using the same tooling and degree of formality as it did for the [=AC Review=];
and as is the case during [=AC Reviews=],
[=dissent=] in this context <em class=rfc2119>must</em> be expressed as a [=Formal Objection=].

Any [=Formal Objection=] raised at this stage against the revised proposal
frivoal marked this conversation as resolved.
Show resolved Hide resolved
is handled by the same [=Council=] responsible for [=Formal Objections=] raised against the initial proposal,
if any.

Note: Such a [=Council=] has the ability to
clear either the original or the revised proposal for advancement
by [=overruling=] all [=Formal Objections=] against the original or revised proposal,
respectively.

For publications which have conditions in addition to [=AC=] approval
for introducing [=substantive changes=]
(such as [=Group=] consensus or implementation experience),
Expand All @@ -2798,6 +2816,13 @@ Determining the W3C Decision</h4>
because that would fail to trigger a patent exclusion opportunity.
</div>

In the case of [=charters=],
frivoal marked this conversation as resolved.
Show resolved Hide resolved
substantive changes from the initial proposal that underwent [=AC Review=]
<em class=rfc2119>must not</em> include any increase to the scope.
If any such change is desired,
it <em class=rfc2119>must</em> be returned for additional work
and go through a complete new [=AC Review=].

This document does not specify
time intervals between the end of an [=Advisory Committee review=] period
and the [=W3C decision=].
Expand Down
Loading