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

It's not my decision, but a solution that breaks all existing links to a wiki that has around a 20 year history and is supposed to be a stable repository of knowledge doesn't seem like the best approach. At the very minimum, we should have something at the old URLs that can translate and redirect or proxy to the new ones.

I'd also consider finding an approach that doesn't rely on domain names that are outside the control of the WG.

FWIW, the DokuWiki software and the existing wiki isn't a large burden, and by itself, can be hosted on an inexpensive server. The only current dependency on the legacy server is user registration. A long time ago the wiki was getting flooded by registrations from spambots, so I switched user registration off and relied on the existing registration system used by Shepherd, the test harness, and the draft server (the W3C auth system didn't exist at the time and they closed off their LDAP). It's possible that DokuWiki has since improved their bot defenses, I haven't checked. It's also fairly easy to write auth plugins for DokuWiki to authenticate against something else, like W3C's account system, which IMO would be a huge improvement. So there are alternatives to migrating...

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


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

Received on Friday, 13 February 2026 18:43:55 UTC