- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Jul 2023 22:34:06 +0000
- To: public-fxtf-archive@w3.org
The CSS Working Group just discussed `[all] Fold the FXTF specs back into CSSWG?`, and agreed to the following: * `RESOLVED: move all fxtx specs into CSSWG github org` * `RESOLVED: move all issues into CSSWG repos` * `RESOLVED: Merge houdini github repo specs and issues into csswg-drafts repo (preserving history).` <details><summary>The full IRC log of that discussion</summary> <ntim> tabatkins: we made fxtx to bridge the gap between csswg and svg, we do not want to hold the bureaucracy cost of holding 2 repos<br> <ntim> tabatkins: the svg working group is no longer relevant<br> <florian> Florian: Yes, do it.<br> <smfr> q+<br> <ntim> dbaron: for moving the spec to the other repo, we should preserve git history<br> <Rossen_> ack dbaron<br> <ntim> dbaron: you can do it as a merge or rebase, rebase is preferable<br> <ntim> dbaron: i don't have strong opinion, i mostly want the history<br> <dbaron> s/rebase is/maybe rebase is/<br> <ntim> smfr: this isn't just about moving the repo, this is also about folding the work into the CSSWG<br> <fantasai> There's been a lot of confusion about where issues should be filed, so this will simplify a lot of that for contributors and for ourselves<br> <florian> q+<br> <Rossen_> ack smfr<br> <ntim> we are resolving on the process<br> <Rossen_> ack florian<br> <dbaron> presumably there's a github issue migration as wel<br> <ntim> florian: this is already in our charter, already in our scope<br> <ntim> RESOLVED: move all fxtx specs into CSSWG github org<br> <ntim> RESOLVED: move all issues into CSSWG repos<br> <florian> q+<br> <Rossen_> ack florian<br> <ntim> florian: maybe setup redirects?<br> <ntim> tabatkins: redirects are easy<br> <ntim> florian: let's do that<br> <emilio> +1<br> <ntim> florian: there has never been anyone outside the CSSWG involved in fxtx, so it's ok to do it without outside folks opinion<br> <fantasai> s/fxtf/houdini/<br> <dbaron> Scribe+<br> <dbaron> TabAtkins: let's repeat the same discussion, but for Houdini instead of FXTF<br> <fantasai> fantasai: The TAG is technically not allowed to publish on the REC track, so they technically can't be co-publishing with us anyway<br> <florian> s/there has never been anyone outside the CSSWG involved in fxtx, so it's ok to do it without outside folks opinion//<br> <dbaron> ?: though the TAG still exists<br> <dbaron> ?: but has anyone on the TAG who's not in CSSWG been involved?<br> <florian> All the TAG members who have been involved in this are also CSSWG members<br> <dbaron> Rossen: would like plinss's opinion<br> <fantasai> [note to scribe, the last several lines are out of order]<br> <florian> q+<br> <dbaron> Rossen: Last I spoke to plinss about Houdini, I think he wanted to continue task force between TAG and CSS WG. And that is the definition of CSS Houdini. Whether all the work needs to happen in that repo, or we can move the specs into the CSS WG repo, we can debate. I'd prefer for him to be part of this decision.<br> <dbaron> Rossen: He was one of the original folks behind forming Houdini.<br> <Rossen_> q?<br> <dbaron> TabAtkins: overall point is that collaboration with TAG as a bureaucratic split doesn't seem to have achieved anything. If the TAG wants to continue working with us, that's great.<br> <fantasai> hober: with my Apple hat off and my TAG hat on<br> <myles> q+<br> <dbaron> hober: As another TAG member, agree with what Tab said -- to the extent that there's productive collaboration to be done between TAG participants and CSSWG members -- nothing stopping us from doing that wherever the spec's live. TAG doesn't need the structure of a TF to do that.<br> <dbaron> hober: And, empirically, having that formal structure doesn't seem to have bought us anything.<br> <dbaron> hober: I don't think it going away would impair the TAG's ability to contribute.<br> <Rossen_> ack florian<br> <dbaron> florian: I agree. If we want to have special days of F2F dedicated to Houdini topics, can still be done even if single repo.<br> <Rossen_> ack myles<br> <dbaron> florian: formally the TAG doesn't publish REC-track documents.<br> <Rossen_> ack myles<br> <dbaron> RESOLVED: Merge houdini github repo specs and issues into csswg-drafts repo (preserving history).<br> <fantasai> scribenick: fantasai<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/509#issuecomment-1646302109 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 21 July 2023 22:34:08 UTC