- From: Sam Sneddon via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Aug 2022 17:29:38 +0000
- To: public-css-archive@w3.org
> > All of those requirements are separate from the requirement for users to be able to reliably read drafts.csswg.org specs. > > But all of those requirements do exist, and they all need maintenance too. I don't think anybody is suggesting those requirements don't exist. What people are arguing is they are lower priority, and have softer uptime needs than hosting of the drafts themselves. That others have taken upon themselves to create parallel infrastructure for the hosting of drafts suggests that it is indeed a higher priority, whereas funding to deal with the broader set of needs of the CSS WG has been hard to come by. Thus this further suggests that we _can_ and _should_ view the uptime requirements for these two things as separate concerns, and consider disentangling them. > Fixing the current infrastructure will result in a stable draft server far faster than this conversation is even likely to be concluded. Frankly, this seems _silly_. AIUI, the things stopping us from moving the draft hosting _this month_ are: * Needing to redo the YAML configuration files of @andreubotella's work to use Netlify to redirect `drafts.csswg.org/api/` etc. to a new subdomain, * Getting WG consensus that we believe the new setup will be more reliable for those viewing specs. > Rather than research the root problems, the knee-jerk response is to throw out what we have and build something new and shiny. **Without any plan or even discussion of how that new thing will be maintained going forward**. I have much more faith in our collective ability to maintain a relatively small Python script and a few YAML files, and GitHub/Netlify to provide reliable hosting, than the current setup for hosting the drafts—even if the server is more reliable than it is today. -- GitHub Notification of comment by gsnedders Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7500#issuecomment-1212278097 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 11 August 2022 17:29:40 UTC