From cd33fba097c708317ac1db0da7510451271a47b1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tantek=20=C3=87elik?= Date: Thu, 1 Sep 2022 13:27:25 -0700 Subject: [PATCH 1/3] distinguish standards-track drafts vs proposals distinguish standards-track drafts vs proposals right up front to help reduce confusion that WICG (or any CG) is standards-track (or in any way produces "standards") --- README.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 80304f67..f0a60f70 100644 --- a/README.md +++ b/README.md @@ -5,10 +5,12 @@ _See [the dashboard](https://mozilla.github.io/standards-positions/) for Mozilla ## What is this Repository? This repo is where [Mozilla](https://mozilla.org/) decides and documents what it thinks about -emerging technical specifications for the Web. Typically they're draft documents in the -[IETF](https://ietf.org/), [W3C](https://w3.org/) (including the [WICG](https://wicg.github.io/)), -[WHATWG](https://whatwg.org/), and [Ecma TC39](https://github.com/tc39), but they could come from -elsewhere too. +emerging technical specifications for the Web. Typically they're standards-track drafts in the +[IETF](https://ietf.org/), [W3C](https://w3.org/), +[WHATWG](https://whatwg.org/), and [Ecma TC39](https://github.com/tc39), +but they could come from elsewhere such as proposals +from W3C Community Groups (like [WICG](https://wicg.github.io/)) +or other community incubation efforts with well-understood IPR terms. Having a clear Mozilla position on these specifications helps us align our thinking and communicate it clearly to these standards bodies, as well as other browsers. From 01a19cb156f075aae5b735564fd01d3d1eacd698 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tantek=20=C3=87elik?= Date: Thu, 1 Sep 2022 14:20:00 -0700 Subject: [PATCH 2/3] incorporate suggestions from @jgraham grammar edits, simpler sentences, and incorporate suggestions from @jgraham --- README.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index f0a60f70..8b96c12d 100644 --- a/README.md +++ b/README.md @@ -5,12 +5,14 @@ _See [the dashboard](https://mozilla.github.io/standards-positions/) for Mozilla ## What is this Repository? This repo is where [Mozilla](https://mozilla.org/) decides and documents what it thinks about -emerging technical specifications for the Web. Typically they're standards-track drafts in the +emerging technical specifications for the Web. Typically such specs are standards-track drafts in the [IETF](https://ietf.org/), [W3C](https://w3.org/), -[WHATWG](https://whatwg.org/), and [Ecma TC39](https://github.com/tc39), -but they could come from elsewhere such as proposals -from W3C Community Groups (like [WICG](https://wicg.github.io/)) -or other community incubation efforts with well-understood IPR terms. +[WHATWG](https://whatwg.org/), and [Ecma TC39](https://github.com/tc39). +We may also provide positions on documents located outside a standards process, +e.g. those in W3C Community Groups such as [WICG](https://wicg.github.io/) +or other community incubation efforts with well-understood IPR terms, +but as a general rule believe that any such work must be moved to a formal standards track +before it’s appropriate for adoption as part of the web platform. Having a clear Mozilla position on these specifications helps us align our thinking and communicate it clearly to these standards bodies, as well as other browsers. From 267eced28832c9e6c2f3ea7545a6adcaf135177c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tantek=20=C3=87elik?= Date: Thu, 1 Sep 2022 14:26:34 -0700 Subject: [PATCH 3/3] add abbr to expand IPR --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 8b96c12d..c92b4937 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,8 @@ emerging technical specifications for the Web. Typically such specs are standard [WHATWG](https://whatwg.org/), and [Ecma TC39](https://github.com/tc39). We may also provide positions on documents located outside a standards process, e.g. those in W3C Community Groups such as [WICG](https://wicg.github.io/) -or other community incubation efforts with well-understood IPR terms, +or other community incubation efforts with well-understood +IPR terms, but as a general rule believe that any such work must be moved to a formal standards track before it’s appropriate for adoption as part of the web platform.