From 2bb248786833b528d1985615499d03df8acc41a0 Mon Sep 17 00:00:00 2001 From: Chris Harrelson <3453258+chrishtr@users.noreply.github.com> Date: Mon, 19 Aug 2024 09:04:24 -0700 Subject: [PATCH 1/3] Add a link to features using the Stages --- Stages.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Stages.md b/Stages.md index 6510eff..314796b 100644 --- a/Stages.md +++ b/Stages.md @@ -1,5 +1,7 @@ # WHATWG Stages +**[See here](https://github.com/search?q=org%3Awhatwg+type%3Aissue+is%3Aopen+label%3A%22stage%3A+1%22%2C%22stage%3A+2%22%2C%22stage%3A+3%22&type=issues) for the current list of features using the Stages process and their current status.** + The WHATWG's approach to "documenting reality" is ideal for nailing down [fundamental parts of the platform](https://spec.whatwg.org/) and improving interoperability and developer satisfaction. It can sometimes be daunting for new [Contributors](./IPR%20Policy.md#contributor), who don't know how to reliably get implementer feedback or editor time commitment. The WHATWG Stages process is an optional, opt-in process that both new and established [Contributors](./IPR%20Policy.md#contributor) can use if they want to get more formal signals on support for their [Contribution](./IPR%20Policy.md#21-contribution). This tool is generally used for medium-to-large [Contributions](./IPR%20Policy.md#21-contribution); it's not expected to be used for each [Contribution](./IPR%20Policy.md#21-contribution). Stages asks for explicit implementer involvement at multiple checkpoints, starting from notification that the problem is being worked on, then sign-off on the rough API and specification, and finally agreement on the full specification text. These checkpoints are also useful to the broader community, helping web developers monitor the [Contributions](./IPR%20Policy.md#21-contribution) that are moving through the various stages. By explicitly signaling a [Contribution](./IPR%20Policy.md#21-contribution)'s progress, including implementer involvement, the community has a better idea of what is going on in the WHATWG. From a31d4c376e7133ac5c744d695fb9cdbd339c4b6e Mon Sep 17 00:00:00 2001 From: Chris Harrelson <3453258+chrishtr@users.noreply.github.com> Date: Mon, 19 Aug 2024 10:21:07 -0700 Subject: [PATCH 2/3] Rephrase per feedback from annevk --- Stages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Stages.md b/Stages.md index 314796b..4324761 100644 --- a/Stages.md +++ b/Stages.md @@ -1,6 +1,6 @@ # WHATWG Stages -**[See here](https://github.com/search?q=org%3Awhatwg+type%3Aissue+is%3Aopen+label%3A%22stage%3A+1%22%2C%22stage%3A+2%22%2C%22stage%3A+3%22&type=issues) for the current list of features using the Stages process and their current status.** +**See [all features using the Stages process](https://github.com/search?q=org%3Awhatwg+type%3Aissue+is%3Aopen+label%3A%22stage%3A+1%22%2C%22stage%3A+2%22%2C%22stage%3A+3%22&type=issues) and their current states.** The WHATWG's approach to "documenting reality" is ideal for nailing down [fundamental parts of the platform](https://spec.whatwg.org/) and improving interoperability and developer satisfaction. It can sometimes be daunting for new [Contributors](./IPR%20Policy.md#contributor), who don't know how to reliably get implementer feedback or editor time commitment. The WHATWG Stages process is an optional, opt-in process that both new and established [Contributors](./IPR%20Policy.md#contributor) can use if they want to get more formal signals on support for their [Contribution](./IPR%20Policy.md#21-contribution). This tool is generally used for medium-to-large [Contributions](./IPR%20Policy.md#21-contribution); it's not expected to be used for each [Contribution](./IPR%20Policy.md#21-contribution). From 94cb84694658dbf298f055956794a149736cc448 Mon Sep 17 00:00:00 2001 From: Chris Harrelson <3453258+chrishtr@users.noreply.github.com> Date: Mon, 19 Aug 2024 10:22:13 -0700 Subject: [PATCH 3/3] Change search link per feedback from annevk --- Stages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Stages.md b/Stages.md index 4324761..eb9737e 100644 --- a/Stages.md +++ b/Stages.md @@ -1,6 +1,6 @@ # WHATWG Stages -**See [all features using the Stages process](https://github.com/search?q=org%3Awhatwg+type%3Aissue+is%3Aopen+label%3A%22stage%3A+1%22%2C%22stage%3A+2%22%2C%22stage%3A+3%22&type=issues) and their current states.** +**See [all features using the Stages process](https://github.com/search?q=org%3Awhatwg+is%3Aopen+label%3A%22stage%3A+1%22%2C%22stage%3A+2%22%2C%22stage%3A+3%22&type=issues) and their current states.** The WHATWG's approach to "documenting reality" is ideal for nailing down [fundamental parts of the platform](https://spec.whatwg.org/) and improving interoperability and developer satisfaction. It can sometimes be daunting for new [Contributors](./IPR%20Policy.md#contributor), who don't know how to reliably get implementer feedback or editor time commitment. The WHATWG Stages process is an optional, opt-in process that both new and established [Contributors](./IPR%20Policy.md#contributor) can use if they want to get more formal signals on support for their [Contribution](./IPR%20Policy.md#21-contribution). This tool is generally used for medium-to-large [Contributions](./IPR%20Policy.md#21-contribution); it's not expected to be used for each [Contribution](./IPR%20Policy.md#21-contribution).