Fwd: Process 2020 for Spec Editors

Spec Editors, in case you missed it (please see below)... exciting changes to the W3C Process that affect your work. Also, if you are not on the spec-prod mailing list, I suggest signing up. It's a very low-volume extremely high-value list. You can sign up at https://lists.w3.org/Archives/Public/spec-prod/

Both ReSpec and BikeShed are 2020 process ready. However, there might still be bugs so let Tab or I know if you encounter issues. Over next few weeks, I'll be checking over your spec to make sure they are configured properly.  

We are all just learning about the Process 2020 changes, and no doubt you might have questions. Please reach out to Leonie and I if you want to discuss putting your spec into "living standards" mode, or if you have any doubts. The Chairs will be reviewing the current set of specs and suggesting what path to take with each. 


> Begin forwarded message:
> 
> From: fantasai <fantasai.lists@inkedblade.net>
> Subject: Process 2020 for Spec Editors
> Date: 16 September 2020 at 6:54:22 am AEST
> To: spec-prod <spec-prod@w3.org>
> Cc: "chairs@w3.org" <chairs@w3.org>
> Resent-From: spec-prod@w3.org
> 
> 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
>