Skip to content

Commit

Permalink
Reorganize changelog
Browse files Browse the repository at this point in the history
  • Loading branch information
@frivoal
frivoal committed Oct 22, 2024
1 parent d61b4c0 commit 6fcd993
Showing 1 changed file with 115 additions and 101 deletions.
216 changes: 115 additions & 101 deletions index.bs
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5746,128 +5746,142 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove

In addition to a number of editorial adjustments and minor teaks, the following is a summary of the main differences:

<ul>
<li>
Council dismissal vote counts must be reported.
(See <a href="https://github.com/w3c/process/issues/748">Issue 748</a>)

<li>
Exclude TAG/AB from voting on their own decisions/proposals.
(See <a href="https://github.com/w3c/process/issues/749">Issue 749</a>)

<li>
Add a requirement to make progress on external issues for update requests
(See <a href="https://github.com/w3c/process/issues/781">Issue 781</a>)
<dl>
<dt>Changes to formal decision making and escalation
<dd>
<ul>
<li>
Put constraints on the timing of making Formal Objections public.
(See <a href="https://github.com/w3c/process/issues/735">Issue 735</a>)

<li>
Enable Team to replace defunct registry custodians when no-one else can.
(See <a href="https://github.com/w3c/process/issues/699">Issue 699</a>)
<li>
Adjust the rules guiding initiation of Councils,
to make the deadline strict,
and to provide a fallback mechanism if they are not met.
(See <a href="https://github.com/w3c/process/pull/925">Pull Request 925</a>)

<li>
Stop citing the superseded TAG charter.
(See <a href="https://github.com/w3c/process/issues/794">Issue 794</a>)
<li>
Make the Council's short-circuit a little more flexible.
(See <a href="https://github.com/w3c/process/issues/852">Issue 852</a>)

<li>
Rename “registry sections” to [=embedded registries=]
to avoid confusion over whether they can be split across multiple sections of a [=Recommendation=].
(See <a href="https://github.com/w3c/process/issues/800">Issue 800</a>)
<li>
Exclude TAG/AB from voting on their own decisions/proposals.
(See <a href="https://github.com/w3c/process/issues/749">Issue 749</a>)

<li>
Put constraints on the timing of making Formal Objections public.
(See <a href="https://github.com/w3c/process/issues/735">Issue 735</a>)
<li>
Council dismissal vote counts must be reported.
(See <a href="https://github.com/w3c/process/issues/748">Issue 748</a>)

<li>
<li>
Adjust AC appeal vote threshold based on participation,
aligning with the thresholds and super majority requirements
for "Requisite Member Vote" from the W3C Bylaws.
(See <a href="https://github.com/w3c/process/issues/886">Issue 886</a>)

Rename "Draft Note" into "Note Draft",
and "Draft Registry" into "Registry Draft"
to be consistent with other statuses that uses the word "Draft",
and to make that word stand out more.
(See <a href="https://github.com/w3c/process/issues/779">Issue 779</a>)
<li>
Fine-tune the rules about
how changes can be incorporated into a proposal
following an AC Review.
(See <a href="https://github.com/w3c/process/issues/825">Issue 825</a>)

<li>
Clarify the definition of a Registry (see <a href="https://github.com/w3c/process/issues/800">Issue 800</a>)
and of Recommendation Track Documents (see <a href="https://github.com/w3c/process/pull/831">Pull Request 831</a>).
<li>
Let the originator of a proposal decide whether to try again
after addressing feedback
following an AC Appeal.
(See <a href="https://github.com/w3c/process/issues/844">Issue 844</a>)
</ul>

<li>
Clarify how the outcome of certain ballots are determined.
(See <a href="https://github.com/w3c/process/issues/836">Issue 836</a>, <a href="https://github.com/w3c/process/pull/838">Issue 838</a>)
<dt>Changes to technical reports and their publication
<dd>
<ul>
<li>
Retire the Proposed Recommendation phase of the Recommendation track.
It was only used as a short-lived transition
during which various verifications and votes about CR were done.
These can be done on a CR
without having to republish it as a separate thing.
This simplifies the Process without changing the actual quality or consensus expectations.
(See <a href="https://github.com/w3c/process/issues/861">Issue 861</a>)

<li id="streamlined-update">
Retire “<a href="https://www.w3.org/policies/process/20231103/#streamlined-update">Streamlined Publication Approval</a>”.
This was meant to enable REC track publication with fewer/faster approval steps
when some stricter than usual criteria were fulfilled.
However, regular REC track publication have improved enough
that this became unnecessary,
and nobody was using it.
(See <a href="https://github.com/w3c/process/issues/856">Issue 856</a>)

<li>
Reorganize and rephrase [[#CharterReview]] for readability and ease of understanding.
This change, while moderate in size, is purely editorial.
(See <a href="https://github.com/w3c/process/pull/850">Pull Request 850</a>)
<li>
Add a requirement to make progress on external issues for update requests
(See <a href="https://github.com/w3c/process/issues/781">Issue 781</a>)

<li id="streamlined-update">
Retire “<a href="https://www.w3.org/policies/process/20231103/#streamlined-update">Streamlined Publication Approval</a>”.
This was meant to enable REC track publication with fewer/faster approval steps
when some stricter than usual criteria were fulfilled.
However, regular REC track publication have improved enough
that this became unnecessary,
and nobody was using it.
(See <a href="https://github.com/w3c/process/issues/856">Issue 856</a>)
<li>
Enable Team to replace defunct registry custodians when no-one else can.
(See <a href="https://github.com/w3c/process/issues/699">Issue 699</a>)

<li>
Consolidate and harmonize into a <a href="#no-group-maintenance">one section</a>
the various parts of the Process
that described whether and how the Team can maintain technical reports
that no longer have a Group chartered to maintain them.
(See <a href="https://github.com/w3c/process/pull/860">Pull Request 860</a>)
<li>
Rename “registry sections” to [=embedded registries=]
to avoid confusion over whether they can be split across multiple sections of a [=Recommendation=].
(See <a href="https://github.com/w3c/process/issues/800">Issue 800</a>)

<li>
Require Chairs to be listed in Charters.
(See <a href="https://github.com/w3c/process/issues/823">Issue 823</a>)
<li>
Rename "Draft Note" into "Note Draft",
and "Draft Registry" into "Registry Draft"
to be consistent with other statuses that uses the word "Draft",
and to make that word stand out more.
(See <a href="https://github.com/w3c/process/issues/779">Issue 779</a>)

<li>
The URL of this document was changed
from /Consortium/Process/ to /policies/process/
for better integration in the W3C website architecture.
<li>
Clarify the definition of a Registry (see <a href="https://github.com/w3c/process/issues/800">Issue 800</a>)
and of Recommendation Track Documents (see <a href="https://github.com/w3c/process/pull/831">Pull Request 831</a>).

<li>
Shift most of the informative discussion about Workshops to [[GUIDE]],
and reorganize the remaining normative requirements.
(See <a href="https://github.com/w3c/process/pull/876">Pull Request 876</a>)
<li>
Consolidate and harmonize into a <a href="#no-group-maintenance">one section</a>
the various parts of the Process
that described whether and how the Team can maintain technical reports
that no longer have a Group chartered to maintain them.
(See <a href="https://github.com/w3c/process/pull/860">Pull Request 860</a>)
</ul>

<li>
Make the Council's short-circuit a little more flexible.
(See <a href="https://github.com/w3c/process/issues/852">Issue 852</a>)
<dt>Changes to chartering
<dd>
<ul>
<li>
Introduce a formal [=Charter Refinement=] phase prior to the [=AC Review=].
(See <a href="https://github.com/w3c/process/issues/580">Issue 580</a>)

<li>
Introduce a formal [=Charter Refinement=] phase prior to the [=AC Review=].
(See <a href="https://github.com/w3c/process/issues/580">Issue 580</a>)
<li>
Reorganize and rephrase [[#CharterReview]] for readability and ease of understanding.
This change, while moderate in size, is purely editorial.
(See <a href="https://github.com/w3c/process/pull/850">Pull Request 850</a>)

<li>
Adjust AC appeal vote threshold based on participation,
aligning with the thresholds and super majority requirements
for "Requisite Member Vote" from the W3C Bylaws.
(See <a href="https://github.com/w3c/process/issues/886">Issue 886</a>)
<li>
Require Chairs to be listed in Charters.
(See <a href="https://github.com/w3c/process/issues/823">Issue 823</a>)
</ul>

<li>
Retire the Proposed Recommendation phase of the Recommendation track.
It was only used as a short-lived transition
during which various verifications and votes about CR were done.
These can be done on a CR
without having to republish it as a separate thing.
This simplifies the Process without changing the actual quality or consensus expectations.
(See <a href="https://github.com/w3c/process/issues/861">Issue 861</a>)
<dt>Other changes
<dd>
<ul>
<li>
Clarify how the outcome of certain ballots are determined.
(See <a href="https://github.com/w3c/process/issues/836">Issue 836</a>, <a href="https://github.com/w3c/process/pull/838">Issue 838</a>)

<li>
Fine-tune the rules about
how changes can be incorporated into a proposal
following an AC Review.
(See <a href="https://github.com/w3c/process/issues/825">Issue 825</a>)
<li>
Stop citing the superseded TAG charter.
(See <a href="https://github.com/w3c/process/issues/794">Issue 794</a>)

<li>
Let the originator of a proposal decide whether to try again
after addressing feedback
following an AC Appeal.
(See <a href="https://github.com/w3c/process/issues/844">Issue 844</a>)
<li>
The URL of this document was changed
from /Consortium/Process/ to /policies/process/
for better integration in the W3C website architecture.

<li>
Adjust the rules guiding initiation of Councils,
to make the deadline strict,
and to provide a fallback mechanism if they are not met.
(See <a href="https://github.com/w3c/process/pull/925">Pull Request 925</a>)
</ul>
<li>
Shift most of the informative discussion about Workshops to [[GUIDE]],
and reorganize the remaining normative requirements.
(See <a href="https://github.com/w3c/process/pull/876">Pull Request 876</a>)
</ul>


<h3 id=changes-previous class=no-num oldids="changes-2023-1, changes-2023, changes-2021, changes-2020, changes-2019, changes-2018, changes-2017">
Expand Down

0 comments on commit 6fcd993

Please sign in to comment.