- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Mar 2025 16:14:06 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Republishing Tasks Permathread`, and agreed to the following: * `RESOLVED: Publish FPWD of CSS Forms` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> ntim: I'd like to request FPWD of Forms<br> <TabAtkins> ntim: currently an unofficial draft, woudl like to get ball rolling<br> <TabAtkins> ntim: the current draft defines appearance:base, and a set of pseudo-elements for form controls<br> <TabAtkins> ntim: a few more things for form control styling<br> <TabAtkins> ntim: this has been discussed in teh joint openui/csswg meetingws<br> <TabAtkins> astearns: there are a bunch of open issues, so clearly people are interested<br> <TabAtkins> astearns: are there also pending PRs?<br> <TabAtkins> ntim: yes, i've approved most of them. currently one left open, i think<br> <TabAtkins> astearns: so your intent is to merge everything we've got in the pipeline before fpwd?<br> <TabAtkins> ntim: not necessarily<br> <TabAtkins> astearns: i'd like to get some more co-editors to help out<br> <TabAtkins> astearns: would you prefer that before fpwd, or after?<br> <TabAtkins> ntim: after<br> <TabAtkins> astearns: k, i'll plan to do that right after fpwd<br> <TabAtkins> no questions, spec looks reasoanble for an early fpwd<br> <TabAtkins> ??: can someone remind me about the process? what does being a WD do?<br> <TabAtkins> astearns: a FPWD is our intent to work on this. IPR becomes an issue for merging things into an official FPWD, as opposed to an editor's draft that hasn't been adopted yet.<br> <florian> q+<br> <astearns> ack florian<br> <TabAtkins> florian: yeah, until it's a WD of some kind (incluing FPWD) it's not actuallya deliverable fo the group, this is the official start<br> <TabAtkins> florian: as mentioned, this has patent implications, W3C patent rules start applying to WD, not EDs<br> <TabAtkins> florian: member companies don't need to license things just because we start publishiing, but they do need to start paying attention. their lawyers will get a notification, becuase eventually they'll need to license patents if they don't object.<br> <TabAtkins> fantasai: the name is "first PUBLIC working draft"; in the past editor's draft werent' public so this was the first that was public<br> <TabAtkins> fantasai: in the interest of "release early, release often" we don't want to wait for a polished spec, but want it up enough that people know how the spec is going to go<br> <TabAtkins> fantasai: major conflicts, might want to delay for a bit. like in Variables, early on there were a lot of possible directions and none of them caught traction.<br> <TabAtkins> fantasai: when we finally hit on the current model and it caught, we finally made the FPWD for it<br> <TabAtkins> fantasai: so the point at which you're aksing for feedback outsdie the WD, that's when yous hould FPWD<br> <TabAtkins> florian: other topic. I understand this is also supposed to take over some parts of CSS UI 4<br> <TabAtkins> florian: some issues in the spec asking about taking over bits<br> <fantasai> s/major conflicts/major conflicts in underlying model/<br> <TabAtkins> florian: i think we probably should, for most at least. don't think we need to solve those for fpwd, since the text is already in a spec, but we should decide on which things move and which things stay soonish.<br> <TabAtkins> florian: happy to work with Tim to figure this out either before or after fpwd, whatever's helpful<br> <TabAtkins> ntim: let's do it after<br> <TabAtkins> ntim: i think it's weird to move something from a higher level spec to an unofficial draft<br> <TabAtkins> florian: sure, so FPWD to get the new stuff, then migrate once it's official. works for me.<br> <astearns> ack fantasai<br> <TabAtkins> fantasai: some notes, FPWD patent stuff is like 90 days or 120 days from the first public draft for the timer to kick in, so even if you add stuff afterwards, it's as if it was in the fpwd<br> <TabAtkins> fantasai: also note, all Working Drafts have some degree of patent protections, while none of our Editors Drafts do. so it's actually important ot publish your drafts.<br> <TabAtkins> astearns: proposed resolution is to publish a FPWD of CSS Forms. Objecteions?<br> <TabAtkins> RESOLVED: Publish FPWD of CSS Forms<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6900#issuecomment-2737246908 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 March 2025 16:14:07 UTC