- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 May 2025 09:43:45 +0000
- To: public-css-archive@w3.org
Just wanted to echo two bits from the list: > > * Draft servers for CSSWG, FXTF, and Houdini > > This we can kill by just moving to GitHub hosting the drafts. We already do that, I just redirect any GH urls to the "proper" draft.csswg.org URLs, which are then hitting your server currently. Should be trivial to just update DNS to point that domain to GH instead. +1. I suspect that this accounts for most of the data being served. On top of spec crawlers that hit draft CSS specs directly, MDN also tends to target draft CSS specs, which likely generates traffic as well (including from additional crawlers). Speaking from a Reffy/Webref perspective, we throttle network requests and only fetch the resources that we need to get to the contents of the specs (for example, the crawler already avoids fetching stylesheets, images and additional scripts that specs may embed). If there are further improvements to consider, I'm happy to look into them! In the meantime, serving drafts out of GitHub Pages would help! > > * The hosted Bikhshed service. > > This one is indeed still being used, tho likely much much less now that most people build their specs with the GH Action now. We should see if the W3C can take this responsibiliy over, tho, as there's still some value in it. W3C currently hosts ReSpec services, e.g., the [xref search](https://respec.org/xref/). It makes sense to me to keep Bikeshed's online service up and running, and for W3C to host it. Side note: W3C tends to like hosting things under the same domain name but it may make sense to consider hosting the service under a dedicated domain name, as done for ReSpec, because Bikeshed and ReSpec are now generic tools used beyond W3C. Moving away from `api.csswg.org` to a more generic name can be done at a later time in any case. -- GitHub Notification of comment by tidoust Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12054#issuecomment-2857899528 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 May 2025 09:43:46 UTC