- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 30 Jan 2023 18:44:43 +0000
- To: public-device-apis-log@w3.org
anssiko has just created a new issue for https://github.com/w3c/compute-pressure: == Wide review tracker == ### About This is a meta issue to track [wide review](https://www.w3.org/2021/Process-20211102/#wide-review) for the [Compute Pressure API](https://www.w3.org/TR/compute-pressure/). An important part of wide review is horizontal review from W3C's [key horizontal groups](https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review) listed below in **horizontal groups** section. Also feedback from **other stakeholders** is equally important. Additional pointers are welcome via comments. The list is based on the [How to do wide review](https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review) page guidance. >Legend: >🔴 Review request not submitted >🟡 Review request submitted >🔵 Review feedback received >🟢 Review closed as completed ### Horizontal groups 🔴 ♿ **Accessibility** - [x] Work through <a rel="nofollow" class="external text" href="https://w3c.github.io/apa/fast/checklist.html">this questionnaire</a> - [ ] ... - [ ] <a rel="nofollow" class="external text" href="https://github.com/w3c/a11y-request/issues/new/choose">request a review via GitHub</a> from <a rel="nofollow" class="external text" href="https://www.w3.org/WAI/APA/">APA</a> 🟡 📐 **Architecture** - [ ] Ask the <a rel="nofollow" class="external text" href="https://www.w3.org/2001/tag/">TAG</a> for review; see <a rel="nofollow" class="external text" href="https://tag.w3.org/workmode/">how to work with the TAG</a> - [x] https://github.com/w3ctag/design-reviews/issues/795 - [x] If you are developing javascript APIs you may also want to ask <a rel="nofollow" class="external text" href="mailto:public-script-coord@w3.org">public-script-coord@w3.org</a>, a technical discussion list shared by W3C and ECMA's TC 39 - [x] No issues related to JS language features that should be brought to TC 39 for consideration. 🔴 🌍 **Internationalisation** - [ ] Read the <a rel="nofollow" class="external text" href="https://www.w3.org/International/review-request">Request a review</a> page - [ ] work through the <a rel="nofollow" class="external text" href="https://www.w3.org/International/i18n-drafts/techniques/shortchecklist">Short Checklist</a> - [ ] ... - [ ] <a rel="nofollow" class="external text" href="https://github.com/w3c/i18n-request/issues/new/choose">request a review via GitHub</a> 🔴 🔍 **Privacy** - [x] Write a "Privacy Considerations" section for your document, taking into account the <a rel="nofollow" class="external text" href="https://www.w3.org/TR/security-privacy-questionnaire/">Self-Review Questionnaire: Security and Privacy</a>, <a rel="nofollow" class="external text" href="https://www.w3.org/TR/fingerprinting-guidance/">Mitigating Browser Fingerprinting in Web Specifications</a>, and <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc6973.html">RFC6973</a> - [x] Completed [Self-Review Questionnaire: Security and Privacy](https://github.com/w3c/compute-pressure/blob/main/security-privacy-self-assessment.md) - [x] Authored [Spec: Privacy Considerations](https://www.w3.org/TR/compute-pressure/#security-and-privacy-considerations) - [x] Chrome Security and Privacy team feedback https://github.com/w3c/compute-pressure/issues/79 - [ ] <a rel="nofollow" class="external text" href="https://github.com/w3cping/privacy-request/issues/new/choose">request a review via GitHub</a> from the <a rel="nofollow" class="external text" href="https://www.w3.org/Privacy/">Privacy Interest Group</a> 🔴 🔒 **Security** - [x] Write a "Security Considerations" section for your document, taking into account the <a rel="nofollow" class="external text" href="https://www.w3.org/TR/security-privacy-questionnaire/">Self-Review Questionnaire: Security and Privacy</a> - [x] Authored [Spec: Security Considerations](https://www.w3.org/TR/compute-pressure/#security-and-privacy-considerations) - [x] Chrome Security and Privacy team feedback https://github.com/w3c/compute-pressure/issues/79 - [ ] <a rel="nofollow" class="external text" href="https://github.com/w3c/security-request/issues/new/choose">request a review via GitHub</a> ### Other stakeholders From [who to ask for review](https://www.w3.org/Guide/documentreview/#who_to_ask_for_review): >Horizontal reviews [...] are only a subset of a full wide review, which must also include other stakeholders including Web developers, technology providers and implementers not active in the Working Group, external groups and standards organizations working on related areas, etc. - Zoom - positive signals and support https://github.com/w3c/compute-pressure/issues/14 - ... Please view or discuss this issue at https://github.com/w3c/compute-pressure/issues/177 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 30 January 2023 18:44:45 UTC