- From: Michael[tm] Smith via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 Jun 2022 23:30:17 +0000
- To: public-css-archive@w3.org
When I reopened the issue, the server was showing a directory listing rather serving the actual specification I needed. > Let's please reserve this issue for when the server needs human attention. e.g.: I believe that from a user point of view, getting a directory listing rather than the spec content they need is an issue that needs human attention, especially if it happens repeatedly — multiple times a week or even multiple times a day. > The server has been unresponsive for a long time (over an hour) Users who are trying to view CSS specs don’t know how long the server has been unresponsive — nor do they have any way of knowing other than (I guess) repeatedly checking to see if they can finally actually read the spec they need. Instead users come in trying to read a particular CSS spec but finding that they can’t. And when that happens, it stops them from solving whatever immediate information need it is that they had for wanting to read that particular spec at that moment — which stops whatever work they’re trying to do. So when a user gets a directory listing rather than a spec, it should be completely appropriate for them to re-open this issue to record the fact that the server is broken at the point in time at which they’re trying to access what they need. It does not seem appropriate to tell users to avoid reporting an issue when something they rely on and need to use isn’t working. -- GitHub Notification of comment by sideshowbarker Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6528#issuecomment-1162459858 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 21 June 2022 23:30:18 UTC