Republishing Tasks Permathread

[fantasai]

Edit this comment to add things to the list.
Include a link to the latest resolution to publish and/or Agenda+ request for permission to publish, so we can follow-up.
Checkmark means has a WG resolution. Remove from list once actually published.
Link the transition request, once it has been made.

See also Estimated Publication Badness Chart and Transition Requests

• Animation Worklet
• Layout API
• Paint API
• Properties & Values API
• Typed OM
• RESOLVED: Accept the PR and republishing WD of containment 2
• scoping shadow
• CR of Color Adjust
• WD of Highlight API

[css-meeting-bot]

The CSS Working Group just discussed Republishing tasks, and agreed to the following:

• RESOLVED: Publish sizing-4
• RESOLVED: publish CRD of conditional-3
• RESOLVED: publish highlight-api

The full IRC log of that discussion

<heycam> Topic: Republishing tasks
<heycam> github: https://github.com//issues/5613
<heycam> fantasai: we are super behind on keeping outselves up to date on TR pages
<heycam> ... as of Sep 13 the Process has been updated
<heycam> ... I created this issue to make sure we get around to publications
<heycam> ... Houdini is mostly not published, for several years
<heycam> ... open request for Sizing
<heycam> ... any other people who want to request publication, agenda+ this issue
<heycam> ... then we can use this issue to track whether it got published
<heycam> ... at astearns's request, I made an "estimated publication badness chart"
<heycam> http://fantasai.inkedblade.net/style/reports/csswg-status-radar/
<astearns> q+
<heycam> fantasai: if you want to edit this file it's in GitHub
<heycam> ... there are lots of spec that need publication!
<heycam> ... it's causing confusion for other groups
<heycam> ... publishing is easy. if you're confused on how to do it, ask in IRC
<heycam> ... the one thing without resolution that needs it is sizing-4
<fantasai> https://lists.w3.org/Archives/Member/w3c-css-wg/2020OctDec/0015.html
<heycam> ... that's a WD
<Rossen_> q?
<heycam> RESOLVED: Publish sizing-4
<Rossen_> ack astearns
<chris> q+
<florian> q+
<heycam> astearns: based on fantasai's analysis of things that haven't been updated on TR, I've started reaching out to editors to see if we can get the ones that are (in some cases) nearly a decade out of date published
<heycam> fantasai: cascade-3 is blocked
<heycam> ... on various Proposed Rec things
<heycam> chris: conditional-3 has the oldest one I think, 2013
<heycam> ... it's getting there, should we get an updated CR on that?
<heycam> fantasai: CRD? we can do that
<heycam> ... Process 2020 has two types of CR publications
<heycam> ... the official snapshot, that goes through approvals etc. then there's Candidate Rec Draft, similar to WD, which allows some open issues
<heycam> ... a CRD has to represent WG consensus
<heycam> Rossen_: any delta between what would be in the CRD and what is currently in broad horizontal review?
<heycam> fantasai: yes. there a bunch of changes since the last PR
<fantasai> s/PR/CR/
<heycam> Rossen_: do we have to go and review all the changes?
<heycam> fantasai: no, purpose of CRD is so you don't have to do that, or the DoC
<heycam> ... have to list changes since the last CR, and WG consensus on material different from the last CR
<heycam> florian: goal is equivalent in quality to CR, but less process heavy
<heycam> dbaron: just need a resolution, if nobody objects, it's WG consensus
<florian> q?
<heycam> s/dbaron/chris/
<heycam> RESOLVED: publish CRD of conditional-3
<Rossen_> ack chris
<Rossen_> ack florian
<heycam> florian: back when Tess was an editor, we were going to have an event handler section in highlighter
<heycam> ... the rest of the spec is not final, but it's FPWD-ish
<fantasai> s/highlighter/highlight-api/
<heycam> ... proposing we publish it as is
<heycam> ... there's a placeholder in the ToC for event handling
<heycam> ... but having live material live off /TR for years is not good, so let's publish it
<heycam> Rossen_: who are the authors?
<hober> +1
<heycam> hober: editors will be Megan, Florian, Sanket
<heycam> florian: I will fill that in, then work with Megan/Sanket to get issues resolved after publishing
<heycam> RESOLVED: publish highlight-api
<heycam> fantasai: just want to note that env and scroll-animations also should be published
<fantasai> s/should be published/have no FPWD/
<heycam> florian: as Alan pings authors, we'll follow up with the env folks
<heycam> s/florian/Rossen/

[svgeesus]

Include a link to the latest resolution to publish and/or Agenda+ request for permission to publish, so we can follow-up.
Checkmark means has a WG resolution.

So once there is a resolution (indicated by a checkmark) the link should also be updated to point to the actual resolution. Because a transition request can't link to an Agenda+ email, it needs to link to the actual resolution

[svgeesus]

It would also be helpful if resolutions included the stage that it was resolved to publish AT. For example FPWD, WD, etc. And to note that some are republishing requests, while others are transition requests (publication being the last stage in a sucessfull transition).

[svgeesus]

RESOLVED: Publish sizing-4

Published 20 Oct 2020

[svgeesus]

RESOLVED: publish highlight-api (FPWD)

Published 22 Oct 2020

[svgeesus]

sizing-3 (once resolved edits are in)

Is that a new publication since the WD of 23 October

There is no link.

[svgeesus]

RESOLVED: Republish a new WD [of Fonts 4]

Published 17 Nov 2020