Re: [csswg-drafts] CSS WG drafts server (#12054)

> I just want the WG to have consensus about any infrastructure changes with full knowledge of what may be lost before making changes.

Yup, def, I just want to make sure we're making forward progress at getting difficult things out of your hands when there's no good reason for you to be the one handling them, especially since your involvement in the group has drastically reduced over the last several years.

> You're also not addressing the loss of the historical versions. The WG needs to decide if this is valuable (all the current historical versions are stored as (gzipped) flat files, I can provide the archive). I presume the GH workflow can also be augmented to preserve previous copies if that's desired. The main thing you'd lose is the ability to lookup by dated URL.

Yeah, I assume the value of those are *approximately* zero. I think I've looked one up *once*, and afaict it's similar for everyone else, if they even know the historical versions exist in the first place. If anyone does need a historical version, they can check out a reasonable commit and build it locally.

> There's a lot more there than meeting info. 

Right, but meeting coordination is what the wiki is *mostly* used for these days. The rest needs to be preserved and transferred, of course.

> IIRC there were some strong opinions over the choice of wiki software. Past discussions about moving to a GH wiki were not accepted.

Yeah, I remember those discussions, but they were also years ago. Anecdotally, it feels like people have warmed to the idea, or at least just don't object so strongly to hosting our wiki on GH servers.

-- 
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12054#issuecomment-2856091043 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 6 May 2025 21:37:10 UTC