Status of css-houdini-drafts and fxtf-drafts?

[LeaVerou]

From #7523 (comment) 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 :

• 17 open issues here (21 total)
• 26 open issues in css-houdini-drafts (91 total)

If some specs are abandoned, we should mark them as such, same as we do for csswg-drafts specs.

cc @astearns @fantasai @tabatkins @svgeesus

[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.

[tabatkins]

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.

[andruud]

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: w3c/fxtf-drafts#509 (comment)