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

Thanks for the list, @plinss! Running down them one by one, then:

> * Draft servers for CSSWG, FXTF, and Houdini

This we can kill by just moving to GitHub hosting the drafts. We already do that, I just redirect any GH urls to the "proper" draft.csswg.org URLs, which are then hitting your server currently. Should be trivial to just update DNS to point that domain to GH instead.

> * The hosted Bikhshed service.

This one is indeed still being used, tho likely much much less now that most people build their specs with the GH Action now. We should see if the W3C can take this responsibiliy over, tho, as there's still some value in it.

> * The IRC logbot (log.csswg.org)

Now that we log our meetings to GH comments with github-bot, and do most of our discussions in issues (where in years past they'd often take place in the IRC), this is probably no longer necessary. If we want to keep it for historical purposes (which I think is valuable), moving a static version to a GH repo is probably sufficient.

> * An IRC bouncer, not clear how many people are still using this.

Yeah, no idea.

> * The CSSWG Wiki (a Dokuwiki instance)

I think we can move this to a GH wiki; this would simplify people's account management, and it's a low-traffic wiki anyway, mostly used to host meeting coordination info. I can do the migration if you send me the data files.

> * An email server hosting an archive of www-style available via IMAP.

Unclear value here, since the W3C archives exist. (mailman archives suck, but at least they exist) We can probably kill this?

> * A proxy to the W3CTAG's Nextcloud instance used for calendars (not sure if this has transitioned to the W3C calendar, but I still see updates). If this continues to be used it should probably get its own Nextcloud instance.

Yeah, dunno how the calendars work. I think @astearns knows a little bit about this?

> * Shepherd, which includes the spec parsers that provide (provided?) anchor data to Bikeshed.

Definitely "provided", I moved off of Shepherd for hosting those a few years back. Bikeshed's definitions are now handled by WebRef, run by the W3C.

> * The CSSWG test harness and it's API for spec annotations.
> * The CSS2.1 test suites

I assume this is of historical interest but no longer being actively used for anything. If necessary, presumably we can migrate some version of it to the W3C for archival purposes.

> * Active defenses against bots (and other cybersecurity threats). The hosting company does provide DDOS protection, but many bots get past that.
> * Various server infra, like DNS, LDAP, email, monitoring, admin pages, etc.

Once we move the rest of this out of your hands, these should no longer be actively necessary, or at least much much less necessary.

> * Probably something else I'm forgetting

If you come up with anything else as we start transitioning things off of your plate, just let us know. ^_^

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


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

Received on Sunday, 4 May 2025 19:42:31 UTC