- From: Peter Linss via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Apr 2025 19:19:39 +0000
- To: public-css-archive@w3.org
> Is there anything else, @plinss? Quite a bit, I need to head out for an appointment but I'll give a full list this evening. > > Could we move drafts.csswg.org to serving off of GitHub first, so we don't even touch Peter's server for the most common case? > That would seem to be a quick and easy way to lessen the load and to improve responsiveness and uptime. It does have a caching proxy of GitHub that's served first, and has been doing so for some time. If you track uptime of individual drafts vs the home page (which fails when the PHP engine is overwhelmed) you'll find that the drafts (the non dated-ones) have very high uptime. > > 3. Historical versions of drafts are on Peter's server. Are these required? Are they valuable? > I don't recall every using this, personally, but maybe others have. I would use git blame and so on for that sort of task. The main value of the historical versions is the cross references. As features move around from spec to spec, there's no way to know where a link was pointing at any time in the past. The server can show any spec as it was *generated* on a given date. -- GitHub Notification of comment by plinss Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12054#issuecomment-2784395619 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 7 April 2025 19:19:40 UTC