- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Jan 2022 16:12:16 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `MQ3 Rec update`, and agreed to the following: * `RESOLVED: Publish a Proposed Correction for MQ3, along with any necessary antecedents as determined by florian/chris/fantasai` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> Topic: MQ3 Rec update<br> <TabAtkins> github: https://github.com/w3c/csswg-drafts/issues/6962<br> <TabAtkins> florian: Elika suggests we might want an update since it's been a while<br> <TabAtkins> florian: We haven't touched it since 2012<br> <TabAtkins> florian: Presumably we thought 4 and 5 would be done<br> <TabAtkins> florian: Also haven't rebuilt it since then, since it's on the old preprocessor<br> <TabAtkins> florian: Some edits went into source, some went into output<br> <TabAtkins> florian: I synced them, and deleted the source since nobody uses it anymore<br> <TabAtkins> florian: And made a few markup fixes<br> <TabAtkins> florian: Also errata. Most are editorial<br> <TabAtkins> florian: One was later overturned, but we didn't remove it from errata<br> <TabAtkins> florian: One was normative, so I've included it as a candidate correction<br> <TabAtkins> florian: I think we're ready to publish.<br> <TabAtkins> florian: But if the group agrees I'd rather have it as a proposed correction rather than candidate correction<br> <TabAtkins> chris: don't think you can do that<br> <TabAtkins> chris: a proposed correction must have the same text as a candidate correction<br> <TabAtkins> florian: hm, you might be right, but i think we could do two pubs in a five minute span<br> <TabAtkins> chris: true there's no minimum review period<br> <TabAtkins> chris: Think it's an abuse of process, but it's not disallowed<br> <TabAtkins> astearns: So we could od candidate corr, let the AC know...<br> <TabAtkins> florian: Letting the AC know is the *proposed* correction thing<br> <TabAtkins> astearns: So you're suggesting do a candidate correction now, and do a proposed correction sometime later?<br> <TabAtkins> florian: I propose doing it immediately after since we gain nothing from a delay, but we can wait a bit if necessary<br> <TabAtkins> chris: you can do a proposed correction and ask the director and see what happens, but it might take more time<br> <TabAtkins> florian: We don't need toa sk the director, these are nonnormative until they're folded in<br> <TabAtkins> [missing some process discussion]<br> <TabAtkins> TabAtkins: Propose we resolve to publish a Proposed Correction, along with any necessary antecedents?<br> <TabAtkins> RESOLVED: Publish a Proposed Correction for MQ3, along with any necessary antecedents as determined by florian/chris/fantasai<br> <chris> https://www.w3.org/Guide/transitions?profile=REC&rec=substantive<br> <TabAtkins> florian: Maybe a followup, maybe implied<br> <TabAtkins> florian: Once this is done we should clear the errata<br> <TabAtkins> chris: You automatically start with a new blank errata when3eve ryou publish a doc<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6962#issuecomment-1016625291 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 January 2022 16:12:18 UTC