W3C home > Mailing lists > Public > spec-prod@w3.org > July to September 2020

Re: Process 2020 for Spec Editors

From: Fuqiao Xue <xfq@w3.org>
Date: Wed, 16 Sep 2020 07:32:03 +0800
To: fantasai <fantasai.lists@inkedblade.net>
Cc: spec-prod <spec-prod@w3.org>, chairs@w3.org
Message-ID: <f11551392b6fd506dd86804366ca4e3d@w3.org>
Wow!! Configurations!!

Special thanks to Florian, Coralie, Philippe, fantasai, Wendy, Dom, and 
other folks in the AB, Process CG, and PSIG for the edits, discussions, 
presentations (and implementing it in IPP/ReSpec/Bikeshed/Pubrules)!


On 2020-09-16 04:54, fantasai wrote:
> Process 2020 is taking effect today, 15 September 2020.
> Here's the major points you need to know:
> 1. Candidate Recommendation as you know it is now called Candidate
> Recommendation Snapshot. Various spec templates have been changed.
> Please make sure you're on the latest ReSpec or Bikeshed builds.
> 2. Other changes to the spec development Process are additive. Aside
> from updating to the latest spec templates, there is nothing that you
> *need* to do differently.
> 3. A new status, Candidate Recommendation Draft, is available. A WG
> can publish CRDs at-will (similar to WDs) in between CR snapshots in
> order to keep /TR up-to-date with the latest changes.
> -> CRDs are expected to have the same level of quality as a CR, must
> represent WG consensus, and are protected as WDs under the Patent
> Policy.
> -> CRs have been generally required to document substantive changes
> from the previous publication; for CRDs, the list of changes should be
> against the most recent CR Snapshot (and for CRSs, since the previous
> Snapshot).
> 4. There is now an amendment process for RECs. WGs can annotate RECs
> with inline errata and/or intended changes and republish them with
> those annotations, and there's a process for getting the changes
> approved and folded into an updated REC.
> -> If you want to use this process, talk to plh, we're still working
> out the implementation details. See
> http://fantasai.inkedblade.net/style/design/w3c-restyle/2020/readme#amendment
> for the current status of experimentation.
> -> You can also annotate WDs and CRs with candidate changes using the
> same markup as for REC amendments, in case that seems useful.
> Process 2020 makes it easier than ever to publish your latest work on
> /TR, even for CRs and RECs. Publish early, publish often, and don't
> hesitate to ask your Staff Contact for help.
> Process 2020
> Official: https://www.w3.org/2020/Process-20200915/#Reports
> Explainer: https://www.w3.org/wiki/Process2020
> Detailed Changelog: 
> https://www.w3.org/2020/Process-20200915/#changes-2019
> Diffs: https://www.w3.org/wiki/Process2020#Process_Document_Edits
> Process 2020 AC Presentation
> Presentation: https://www.w3.org/2020/05/AC/talk/Process2020#align
> Audio Only: 
> https://florian.rivoal.net/talks/process2020/process2020.mp3
> Transcript Only: 
> https://florian.rivoal.net/talks/process2020/transcript
> Slides Only: https://florian.rivoal.net/talks/process2020/slides
> Note: If you want to keep up with updates for spec editors, please
> subscribe to the (low-traffic) spec-prod@w3.org discussion list.
> ~fantasai
Received on Tuesday, 15 September 2020 23:32:07 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 15 September 2020 23:32:08 UTC