[META] Support W3C Process 2021

[marcoscaceres]

From the changes section, it might be good for us to start planning:

• Registries track documents
  • Requirements at https://www.w3.org/Consortium/Process/Drafts/#reg-pub
  • Might require its own ReSpec profile... the documents are somewhat different, but not too different.
• Note track:
  • Add "Discontinued Draft" status
  • Add "Draft Note" as a status
  • Support "W3C Statement" type of Note

cc @dontcallmedom, @deniak, @plehegar, @tidoust, @caribouW3.

[marcoscaceres]

Mockups:
https://w3c.github.io/tr-design/p2021mockup/

[marcoscaceres]

We need to come up with a list of changes and verify the changes via Specberus.

We are targeting September 23rd.

[sidvishnoi]

w3c/spec-prod#3 could be helpful for SpecBerus validation. We can use spec-prod in regressions workflow.

[marcoscaceres]

Maybe useful resource for this: https://www.w3.org/Guide/transitions?profile=REC&rec=new

[marcoscaceres]

Some notes from meeting with @plehegar... (might be incoherent to anyone but us... but enough for me to start various branches on).

Templates:
https://w3c.github.io/tr-design/p2021mockup/

FPWD:
- Details element
- History link (new item) - maybe configurable. Look at this version link.
- Use the level.
- Note to update HR time to use level.
Feedback header (Participate)
- MUST one of Github, mailing list
- Maybe allow adding custom HTML to feedback
Copyright stays the same

Visual change

SoTD
Shorter sentence is shorter.
The second para is different
"Ending change" - recommendation track.
- Look at the other templates ... note track, reg track

CR Version
https://w3c.github.io/tr-design/p2021mockup/cr-6.3.8.1.html

• Sentence about wide review?

CR - Snapshot (including the first) -> CRD

• And to get to CR, you need wide review.
• "A Candidate Recommendation Snapshot has received wide review,"

Group Notes

• https://w3c.github.io/tr-design/p2021mockup/dnote-6.4.2.html
  • Only "Group Notes" (no more WG or IG Notes)
  • Only certain groups are allowed to publish notes: WG, IG, AB, TAG
  • W3C API gives us back that data. We might need to look at the data object to see if it's not a CG!
  • "Group Draft Notes are not endorsed by the W3C nor its Membership.
  • Patent policy links are completely different
  • "The 1 August 2017 W3C Patent Policy does not carry any licensing requirements or commitments on this document." from data object.

DRY:
- "W3C recommends the wide usage of this registry."
- "A W3C Registry is a specification that, after extensive consensus-building, has received the endorsement of the W3C and its Members."

Invisible Changes
What's style sheet?
link stylesheet 2021/...
Fixup + maybe another script

What happens when you change the short name?
Echidna doesn't support it.
We might want to add a list of "short names".

• data-previous-shortnames='hr-time'
• Add a previous short name configuration or just allow it to be defined in HTML

Maybe of interest:
w3c/transitions#361

PR

• Implementation Report must appear

REC
- Errata moves to the head of the document as a dt/dd
- Can be link or "incorporated"
- "W3C recommends the wide deployment of this specification as a standard for the Web."

[xfq]

Can we close this now? Or is there more work to be done?

[xfq]

Ah, we still need to document the new statuses in https://respec.org/docs/#specStatus

[nigelmegitt]

Please can we have RY-ED and DRY-ED too? See w3c/webcodecs#644 (comment) for the motivation behind this request. @tidoust