- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Tue, 03 Mar 2026 19:43:48 +0000
- To: public-css-archive@w3.org
(I went on vacation *just* as this blew up, so pretend this response isn't actually unaccountably delayed.) > So, after taking advantage of my generosity for around 8 years, and you personally treating me like you're entitled to my labor, you actually think the best way to answer to my pushback it to criticize my response and dictate how I should have handled it? FWIW, yes, I do think that's the best answer. You and I discussed the servers and replacement services as recently as TPAC in November, just a few months ago, and you did not at that time express anything near this level of frustration that you've apparently been simmering with for (it appears) years. You have been *publicly* treating it as a relatively low-priority thing with nothing like a deadline that would be great to handle "sometimes", so everyone continued to treat it as a relatively low-priority thing with nothing like a deadline that would be great to handle "sometime". It would have been **100% fine** to have, for example, announced at TPAC "hey guys, this shit sucks and I'm about done with it, I'm gonna stop handling any of this in March. We've been discussing how to move off of my servers for a while, it's time to step those up and make it happen.". Or announcing that at the last f2f, which would have at least given us more than a month. Or not at any meeting, just with a message to the WG to that effect, sometime multiple weeks ago. It was **0% fine** to have started quietly ignoring any of the problems and just letting things fall over when no one knew that this was apparently bothering you so much, and then announcing a *very short* timeline (3 weeks) for getting everything off your servers before you shut things down, and doing so, as Oriol said, buried in an incident thread rather than a top-level message. This was an unprofessional way to handle this entire situation, but worse, it was *unkind*. You've been a part of this WG and a friend to many of us for many years. Silently holding in all of this frustration and letting it build until it reached this breaking point was not the behavior I would have expected from you. You took a responsibility onto yourself many years ago, and it's both (a) reasonable for people to continue to rely on that as long as you allow it, and (b) reasonable for you to communicate that you can no longer shoulder that responsibility, and to get others to take it up. I'm glad that several WG members have been able to emergency-divert their time to keep these necessary resources going. It should never have been an emergency, tho; we should have had a friendly handover with some reasonable planning. I know you've been low-interaction with the WG for several years now, as your interests have moved elsewhere. I appreciate what you've continued to do for us, and the times we've hung out together as friends. This just wasn't a very friendly thing to do, in several ways. > `drafts.csswg.org` FWIW, I'm happy to take over hosting the `csswg.org` domain name for now, if you want to transfer it. Now that we've moved the wiki over to a GitHub repo, the "wiki user registration" issue should be moot now, so you can either change the DNS records or ask me to do it after transferring. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12743#issuecomment-3993141254 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 3 March 2026 19:43:49 UTC