W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2020

Re: [csswg-drafts] Republishing Tasks Permathread (#5613)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Mon, 19 Oct 2020 20:26:55 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-712422438-1603139214-sysbot+gh@w3.org>
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`

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

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5613#issuecomment-712422438 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 19 October 2020 20:26:57 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:20 UTC