| CARVIEW |
Select Language
HTTP/2 200
date: Mon, 06 Oct 2025 05:20:48 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 17:37:40 GMT
cache-control: max-age=2592000, public
expires: Tue, 04 Nov 2025 11:53:49 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 989cb881f8e9f162
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: HIT
set-cookie: __cf_bm=ybF0frBxbmN20ojD3fLm7U94hEsJXCAy5.FK9M6rE1c-1759728048-1.0.1.1-V4724Flo1V7FHRTj61FpNiNKbRcKXsyFD3M8KXD_WlBZ0j.H46uMwxh_tXvvJefVzHvM89zpWPYNKuMa1KY2gNyFCtxZakcZXDEeHluF8n8; path=/; expires=Mon, 06-Oct-25 05:50:48 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98a2b6293ac8f313-BLR
alt-svc: h3=":443"; ma=86400
Proposed Process 2020 Updates Explainer from fantasai on 2019-11-13 (spec-prod@w3.org from October to December 2019)
Proposed Process 2020 Updates Explainer
- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Wed, 13 Nov 2019 08:35:26 -0800
- To: spec-prod <spec-prod@w3.org>
- Message-ID: <827bef44-fda5-c947-9f57-4d3b3d2dcbe3@inkedblade.net>
Yo! Some of you were at TPAC, where plh and I presented the proposal for updating the REC track process: https://www.w3.org/2019/Talks/TPAC/continuous-standards/ We've written an explainer (and also Process document edits) which you can find here: https://www.w3.org/wiki/Process2020 Since the REC track process affects editors more than anyone, I would really like to ask for comments from you all, particularly: 1. Do you feel you understand the proposal and its impact on your work? 2. Do you like the direction it is going in? 3. If not, what specifically are your concerns? 4. Do you have any questions? Is there anything you want explained better? The AB will be discussing whether to adopt these changes next week, so if you can let me know before Monday that would be extra helpful. ^_^ Thanks~~ ~fantasai
Received on Wednesday, 13 November 2019 16:35:32 UTC