- From: Peter Linss via GitHub <sysbot+gh@w3.org>
- Date: Thu, 14 Jul 2022 18:09:45 +0000
- To: public-css-archive@w3.org
@NiedziolkaMichal the purpose of this issue is *not* to note the fact that the draft server goes down sometimes, but to notify those that can fix it when it needs attention. The root cause is well understood and we've all been aware of the problem for a long time, we're not oblivious. <rant>This has all been said before, but apparently needs to be said again. Fixing the server requires about a person-month of engineering effort. The issue has been that the person maintaining this server (me) is not sponsored to do **any** work for W3C. So in addition to the ~1 day per week I spend on CSSWG and TAG work I do on my own time, paying for this server out of my own pocket, and paying all my own travel expenses for F2F meetings, asking me to take a month of additional unpaid time off to fix the server is going a bit too far. No one else has stepped up to do the work, and only one person so far has offered to fund the engineering work. That funding effort is under way and once it's in place the server will get properly fixed. Until then, re-raising complaints about the lack of reliability of a service that's completely free to you, but costs **me** time _and_ money, that have already been made ad-infinitum, is not helpful.</rant> -- GitHub Notification of comment by plinss Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6528#issuecomment-1184750613 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 14 July 2022 18:09:47 UTC