- From: sam goto <notifications@github.com>
- Date: Wed, 26 Jun 2019 17:37:10 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/391@github.com>
こんにちはTAG! I'm requesting a TAG review of: - Name: SMS Receiver API - Specification URL: not yet available - Explainer (containing user needs and example code)¹: [explainer](https://github.com/samuelgoto/sms-receiver/blob/master/README.md) - GitHub issues (if you prefer feedback filed there): [issues](https://github.com/samuelgoto/sms-receiver/issues) - Tests: [WPT](https://cs.chromium.org/chromium/src/third_party/blink/web_tests/external/wpt/sms/) - Primary contacts (and their relationship to the specification): @samuelgoto, @sso-google Further details: - Relevant time constraints or deadlines: [please provide] - [x] I have read and filled out the [Self-Review Questionnare on Security and Privacy](https://www.w3.org/TR/security-privacy-questionnaire/). The [assessment is here](url). - [x] I have reviewed the TAG's [API Design Principles](https://w3ctag.github.io/design-principles/) - The group where the work on this specification is: We recommend the explainer to be in [Markdown](https://github.github.com/gfm/). On top of the [usual information expected in the explainer](https://w3ctag.github.io/explainers), it is strongly recommended to add: - Links to major pieces of multi-stakeholder review or discussion of this specification: - Links to major unresolved issues or opposition with this specification: You should also know that... [please tell us anything you think is relevant to this review] We'd prefer the TAG provide feedback as (please select one): - [x] open issues in our GitHub repo for each point of feedback - [ ] open a single issue in our GitHub repo for the entire review - [ ] leave review feedback as a comment in this issue and @-notify [github usernames] -------------------------- _Please preview the issue and check that the links work before submitting._ In particular, if anything links to a URL which requires authentication (e.g. Google document), please make sure anyone with the link can access the document. ¹ For background, see our [explanation of how to write a good explainer](https://w3ctag.github.io/explainers). -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/391
Received on Thursday, 27 June 2019 00:37:32 UTC