Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[meta] Wide review tracker #270

Open
15 tasks done
xfq opened this issue Aug 6, 2020 · 1 comment
Open
15 tasks done

[meta] Wide review tracker #270

xfq opened this issue Aug 6, 2020 · 1 comment

Comments

@xfq
Copy link
Member

xfq commented Aug 6, 2020 •
edited
Loading

As a requirement for revising a Candidate Recommendation the group:

MUST show that the proposed changes have received wide review

To satisfy this requirement, we use this tracker issue as evidence that wide review from horizontal groups has been received.
@xfq xfq mentioned this issue Aug 7, 2020
Closed
@samuelweiler
Copy link
Member

samuelweiler commented Aug 20, 2020 •
edited
Loading

I flagged two issues found by the privacy (PING) reviewer as "security". The security review isn't back yet.

@rakuco rakuco mentioned this issue Sep 15, 2020
Closed
rakuco added a commit to rakuco/wake-lock that referenced this issue Sep 16, 2020
@rakuco
Add an Explainer document to the repository.
9b9c20e 
This is a short summary of what is already in the spec. The document is
required as part of the TAG review process, which itself is part of w3c#270.

Fixes w3c#284.
@rakuco rakuco mentioned this issue Sep 16, 2020
Merged
rakuco added a commit to rakuco/wake-lock that referenced this issue Sep 21, 2020
@rakuco
Add an Explainer document to the repository.
de5acc0 
This is a short summary of what is already in the spec. The document is
required as part of the TAG review process, which itself is part of w3c#270.

Fixes w3c#284.
rakuco added a commit that referenced this issue Sep 21, 2020
@rakuco
Add an Explainer document to the repository. (#286)
c3ebf77 
This is a short summary of what is already in the spec. The document is
required as part of the TAG review process, which itself is part of #270.

Fixes #284.
@anssiko anssiko mentioned this issue Aug 27, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@xfq @samuelweiler