- From: Martin Thomson <notifications@github.com>
- Date: Thu, 05 Sep 2024 18:11:51 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/pull/988/review/2284392703@github.com>
@martinthomson commented on this pull request. I'll reorder the paragraphs. > - The group where the work on this specification is currently being done: - - The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): + - The group where standardization of this work is intended to be done: Yeah, I was on the fence there. > ² A Security and Privacy questionnaire helps us understand potential security and privacy issues and mitigations for your design, and can save us asking redundant questions. See https://www.w3.org/TR/security-privacy-questionnaire/. -³ For your own organization, you can simply state the organization's position instead of linking to it. Chromium doesn't have a standards-positions repository and [prefers](https://source.chromium.org/chromium/chromium/src/+/main:docs/standards/positions/GoogleChrome/README.md) to use comments from the teams that maintain the relevant area of their codebase. +³ For your own organization, you can simply state the organization's position instead of linking to it. This includes items on [Mozilla standards-positions](https://github.com/mozilla/standards-positions), and [WebKit standards-positions](https://github.com/WebKit/standards-positions). Chromium doesn't have a standards-positions repository and [prefers](https://source.chromium.org/chromium/chromium/src/+/main:docs/standards/positions/GoogleChrome/README.md) to use comments from the teams that maintain the relevant area of their codebase. + +⁴ Include a link to [Chrome Status](https://chromestatus.com/), [Mozilla's](https://bugzilla.mozilla.org/), [WebKit's Bugzilla](https://bugs.webkit.org/), or trackers for other implementations if those are known to you. ```suggestion ⁴ Include links to [Chrome Status](https://chromestatus.com/), [Mozilla's](https://bugzilla.mozilla.org/), [WebKit's Bugzilla](https://bugs.webkit.org/), and trackers for other implementations if those are known to you. ``` A moratorium on "and/or"... -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/pull/988#pullrequestreview-2284392703 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/pull/988/review/2284392703@github.com>
Received on Friday, 6 September 2024 01:11:55 UTC