| 09:06 | <sideshowbarker> | PSA: FYI for anybody who’s been frustrated — or had your work blocked — by the almost-daily https://drafts.csswg.org outages: Today I raised https://github.com/w3c/csswg-drafts/issues/7500 to suggest it’s time to consider replacing the backend with something known to be much more reliable (and doesn’t require funding for a person-month of engineering effort to make happen) — namely the https://andreubotella.com/csswg-auto-build/ setup. I didn’t raise the issue as a troll and it’s not meant to be hostile or provocative — I went out of my way to try to word it as diplomatically as possible — but instead it’s a good-faith effort to try to start a constructive discussion about the problem and the requirements and about one possible solution to consider. |
| 09:13 | <niedziolka_michal> | Thanks for doing that. At least 2 or 3 times a week I get frustrated that this service is not working properly and I was thinking to raise the issue on MDN to switch to alternative page like andreubotella.com. |
| 09:15 | <niedziolka_michal> | It's very surprising that Peter Linss needs to do so much work in order for drafts.csswg.org to operate and still service is unavailable few times a week |
| 16:55 | <TabAtkins> | It's because the code was written years ago and various things have bitrotted, plus it gets way more spam/spider traffic now than it did when it was first stood up. He hasn't had time to do updates on it in his free time; "keeping it up" is just repeatedly kicking the server when something's crashed. |
| 16:55 | <TabAtkins> | But yeah there's a contract going thru the corp machinery to actually pay Peter for his time to get it all refreshed and up to date |
| 16:56 | <TabAtkins> | And as Peter said, "just" fixing the front-end specs will just leave the rest of the infrastructure rotting even worse, so we're not avoiding anything meaningful by jumping ahead of the work. |