w3c
Status of css-houdini-drafts and fxtf-drafts?
From https://github.com/w3c/csswg-drafts/issues/7523#issuecomment-3636220658 by @andruud:
But css-houdini-drafts is somewhat "deprecated" as a working arena, so I wasn't sure Async Resolution labels would be effective in that repo.
If css-houdini-drafts (and fxtf-drafts) is not an active working arena, should we merge it with this repo? There are ways to do so while fully preserving commit history.
IMO either these repos should be first-class working arenas, or merged. The current state where we have some issues about these specs in the css-houdini-drafts repo and some in csswg-drafts for better visibility is very suboptimal and makes it incredibly hard to track what's going on. For example css-properties-values-api has :
If some specs are abandoned, we should mark them as such, same as we do for csswg-drafts specs.
cc @astearns @fantasai @tabatkins @svgeesus
I moved all the fxtf specs to csswg repo this week, and have been looking for a reliable way to move all the issues over as well. fxtf can then be archived. We already had a csswg resolution to stop using it.
Houdini is a separate issue, we have no resolution on that.
We certainly discussed it at the same time. If we didn't take an official resolution that was just an oversight; we should be moving both of them back under our umbrella.
Houdini is a separate issue, we have no resolution on that.
@svgeesus Looks resolved to me?
RESOLVED: Merge houdini github repo specs and issues into csswg-drafts repo (preserving history).
Source: https://github.com/w3c/fxtf-drafts/issues/509#issuecomment-1646302109
Please also check that https://drafts.csswg.org/indexes is updated correctly. After the specs have been moved, some entries still point to the FXTF domain.
(There are also still some non-CSS entries in it.)
