From 3691307558512af6a148e18eb637962896a21e11 Mon Sep 17 00:00:00 2001 From: Heather Flanagan Date: Mon, 13 Jan 2025 10:46:13 -0800 Subject: [PATCH 1/6] Revert "Update proposals-CG-WG.md " This reverts commit e2019ccd966ec254923dc5b3f70afb6922d10653. --- proposals-CG-WG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals-CG-WG.md b/proposals-CG-WG.md index 5bc0af0..cc9d996 100644 --- a/proposals-CG-WG.md +++ b/proposals-CG-WG.md @@ -13,7 +13,7 @@ This is a proposal to break proposals into 5 stages of maturity, with clear guid * [Stage 3](#stage3): **Implementation** of the preferred Proposal * [Stage 4](#stage4): **Publication** of a Proposed Recommendation -These stages support the W3C process and align with the [TC39 process](https://tc39.es/process-document/) and the [WHATWG process](https://whatwg.org/stages). If there is ever any question between W3C process requirements and how the groups will progress their work, the W3C process has precedence. +These stages support the W3C process and align with the [TC39 process](https://tc39.es/process-document/) and the [WHATWG process](https://whatwg.org/stages). If there is ever any question between W3C process requirements and how the groups will progress their work, the W3C process has precedent. # Stage 0: Exploration From aceeee6464ef91aa2f1ed888ca500b77672c752b Mon Sep 17 00:00:00 2001 From: Heather Flanagan Date: Mon, 13 Jan 2025 10:46:37 -0800 Subject: [PATCH 2/6] Revert "Update proposals-CG-WG.md " This reverts commit 4c332650f4b8a0044f7c1a28e184a0814c922214. --- proposals-CG-WG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals-CG-WG.md b/proposals-CG-WG.md index cc9d996..804ba46 100644 --- a/proposals-CG-WG.md +++ b/proposals-CG-WG.md @@ -71,7 +71,7 @@ The purpose of Stage 3 Proposals is to increase implementation and deployment co # Stage 4: Publication - The purpose of Stage 4 Proposals is to produce a [W3C Recommendation](https://www.w3.org/policies/process/#RecsW3C). At this stage, the spec is merged and has finished editorial review. This editorial review could be lengthy, especially if the feature is large and/or the contributor is new to W3C process, but it will usually be short. + The purpose of Stage 4 Proposals is to produce a [W3C Recommendation](https://www.w3.org/policies/process/#RecsW3C). At this stage, the spec is merged and has finished editor review. This editor review could be lengthy, especially if the feature is large and/or the contributor is new to W3C process, but it will usually be short. * What's needed from champions? * [ ] Documented [implementation experience](https://www.w3.org/policies/process/#implementation-experience) across multiple environments. From 3f12154eb995d299a6cd610e90fa9865661ab3c9 Mon Sep 17 00:00:00 2001 From: Heather Flanagan Date: Mon, 13 Jan 2025 10:47:11 -0800 Subject: [PATCH 3/6] Revert "Update proposals-CG-WG.md " This reverts commit 36b00ebdab72386d2b519ea1788a76a8442bff57. --- proposals-CG-WG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals-CG-WG.md b/proposals-CG-WG.md index 804ba46..429d243 100644 --- a/proposals-CG-WG.md +++ b/proposals-CG-WG.md @@ -38,7 +38,7 @@ The purpose of Stage 1 proposals is to explore the Solution Space and pick a pre # Stage 2: Formalization -The goal of Stage 2 is to refine the preferred solution into a detailed, cohesive proposal that addresses known issues and integrates feedback from stakeholders. The Proposal enters Stage 2 with a list of issues that block advancement to the next stage, and exits with all of the issues resolved. This stage focuses on preparing the proposal for Working Group review and creating a complete, formal draft. +The goal of Stage 2 is to refine the preferred solution into a detailed, cohesive proposal that addresses known issues and integrates feedback from stakeholders. The Proposal enters Stage 2 with a list of blocking issues to advance to the next stage and exits with all of the issues resolved. This stage focuses on preparing the proposal for Working Group review and creating a complete, formal draft. * What's needed from champions? * [ ] An [explainer](https://tag.w3.org/explainers/). From f623717a36078a9761521801a648b4a76ab3d918 Mon Sep 17 00:00:00 2001 From: Heather Flanagan Date: Mon, 13 Jan 2025 10:47:16 -0800 Subject: [PATCH 4/6] Revert "Update proposals-CG-WG.md (date format)" This reverts commit 64dc551dd39bfc3337f0120be31d1f48fd6d2ef4. --- proposals-CG-WG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals-CG-WG.md b/proposals-CG-WG.md index 429d243..eb8221a 100644 --- a/proposals-CG-WG.md +++ b/proposals-CG-WG.md @@ -2,7 +2,7 @@ Author: @samuelgoto Created: 2024-08-11 -Last update: 2024-11-26 +Last update: 11/26/2024 Status: under review This is a proposal to break proposals into 5 stages of maturity, with clear guidelines and requirements to advance them: From 1d7b0f2f8db83b6458eb13a87ddb4b51bd777202 Mon Sep 17 00:00:00 2001 From: Heather Flanagan Date: Mon, 13 Jan 2025 10:47:20 -0800 Subject: [PATCH 5/6] Revert "Update proposals-CG-WG.md (date format)" This reverts commit dc2c13704423bb0531cb89e43f590447ea760f73. --- proposals-CG-WG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals-CG-WG.md b/proposals-CG-WG.md index eb8221a..2e65f8f 100644 --- a/proposals-CG-WG.md +++ b/proposals-CG-WG.md @@ -1,7 +1,7 @@ # CG/WG Proposal Stages Author: @samuelgoto -Created: 2024-08-11 +Created: 08/11/2024 Last update: 11/26/2024 Status: under review From d972b27309fa4ed2f708797565aa453ba2ab12ed Mon Sep 17 00:00:00 2001 From: Heather Flanagan Date: Mon, 13 Jan 2025 10:57:24 -0800 Subject: [PATCH 6/6] reverting purely editorial changes --- proposals-CG-WG.md | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/proposals-CG-WG.md b/proposals-CG-WG.md index 2e65f8f..f2cbab2 100644 --- a/proposals-CG-WG.md +++ b/proposals-CG-WG.md @@ -29,11 +29,11 @@ The purpose of Stage 0 proposals is to allow anyone to raise and explore the Pro The purpose of Stage 1 proposals is to explore the Solution Space and pick a preferred direction. This is where most of the work gets done because it involves exploring alternatives, understanding tradeoffs, gathering implementation experience, incubating alternatives, gathering evidence of demand and fitness for purpose, and finally, identifying the best out of the many alternatives. * What's needed from individuals? - * [ ] Identification of [champions](https://github.com/tc39/how-we-work/blob/main/champion.md). - * [ ] An understanding of the Problem Space. - * [ ] Optionally, alternatives under consideration. + * [ ] Identification of [champions](https://github.com/tc39/how-we-work/blob/main/champion.md) + * [ ] An understanding of the Problem Space + * [ ] Optionally, alternatives under consideration * What's asked of the **Community Group**? - * [ ] The Community Group consensus that the problem is worth spending the Community Group’s time working on. + * [ ] The Community Group consensus that the problem is worth spending the Community Group’s time working on * [ ] A home for incubating the proposal. Small features will incubate in issues. If and when the champions are ready to more thoroughly document their proposal, the WG chairs will create a repo for the champions to develop the feature (e.g., [example](https://github.com/fedidcg/LightweightFedCM)). # Stage 2: Formalization @@ -66,8 +66,8 @@ The purpose of Stage 3 Proposals is to increase implementation and deployment co * [ ] Web Platform Tests are available. * [ ] At least two independent implementers and no unresolved objections (where resolution may include an agreement not to address the issue). * What's asked of the **Working Group**? - * [ ] Working Group consensus that the [Working Draft](https://www.w3.org/policies/process/#RecsWD) sufficiently resolves all of the issues raised at [Stage 2](#stage-2). - * [ ] Working Group consensus to publish the [Working Draft](https://www.w3.org/policies/process/#RecsWD) as the Working Group's [Candidate Recommendation](https://www.w3.org/policies/process/#RecsCR). + * [ ] Working Group consensus that the [Working Draft](https://www.w3.org/policies/process/#RecsWD) sufficiently resolves all of the issues raised at [Stage 2](#stage-2) + * [ ] Working Group consensus to publish the [Working Draft](https://www.w3.org/policies/process/#RecsWD) as the Working Group's [Candidate Recommendation](https://www.w3.org/policies/process/#RecsCR) # Stage 4: Publication @@ -76,8 +76,8 @@ The purpose of Stage 3 Proposals is to increase implementation and deployment co * What's needed from champions? * [ ] Documented [implementation experience](https://www.w3.org/policies/process/#implementation-experience) across multiple environments. * What's asked of the **Working Group**? - * [ ] Working Group consensus that the [Candidate Recommendation](https://www.w3.org/policies/process/#RecsCR)'s implementation experience is complete. - * [ ] Working Group consensus to publish it as a [Proposed Recommendation](https://www.w3.org/policies/process/#RecsPR). + * [ ] Working Group consensus that the [Candidate Recommendation](https://www.w3.org/policies/process/#RecsCR)'s implementation experience is complete + * [ ] Working Group consensus to publish it as a [Proposed Recommendation](https://www.w3.org/policies/process/#RecsPR) # Prior Art @@ -85,17 +85,17 @@ The purpose of Stage 3 Proposals is to increase implementation and deployment co * Proposals Repo: [https://github.com/tc39/proposals](https://github.com/tc39/proposals) * Stages: [https://tc39.es/process-document/](https://tc39.es/process-document/) * Examples - * Decorators Repo: [https://github.com/tc39/proposal-decorators](https://github.com/tc39/proposal-decorators) - * Temporal Repo: [https://github.com/tc39/proposal-temporal](https://github.com/tc39/proposal-temporal) + * Decorators Repo: [https://github.com/tc39/proposal-decorators](https://github.com/tc39/proposal-decorators) + * Temporal Repo: [https://github.com/tc39/proposal-temporal](https://github.com/tc39/proposal-temporal) * Immersive Web CG/WG * Proposals Repo: [https://github.com/immersive-web/proposals](https://github.com/immersive-web/proposals) * Stage 0 Issues: [https://github.com/immersive-web/proposals/issues](https://github.com/immersive-web/proposals/issues) * Examples - * \ Repo: [https://github.com/immersive-web/model-element](https://github.com/immersive-web/model-element) - * Depth sensing Repo: [https://github.com/immersive-web/depth-sensing](https://github.com/immersive-web/depth-sensing) + * \ Repo: [https://github.com/immersive-web/model-element](https://github.com/immersive-web/model-element) + * Depth sensing Repo: [https://github.com/immersive-web/depth-sensing](https://github.com/immersive-web/depth-sensing) * WebAssembly * Proposals Repo: [https://github.com/WebAssembly/proposals](https://github.com/WebAssembly/proposals) * Examples - * Tail call Repo: [https://github.com/WebAssembly/tail-call](https://github.com/WebAssembly/tail-call) - * GC Repo: [https://github.com/WebAssembly/gc](https://github.com/WebAssembly/gc) + * Tail call Repo: [https://github.com/WebAssembly/tail-call](https://github.com/WebAssembly/tail-call) + * GC Repo: [https://github.com/WebAssembly/gc](https://github.com/WebAssembly/gc)