-
Notifications
You must be signed in to change notification settings - Fork 46
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.
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
Web Application Security (webappsec) WG 2021 recharter #253
Comments
APA WG is ok with this charter. We note the requirement for accessibility impact sections, and for horizontal review. While there is not an explicit liaison to APA, it doesn't seem needed in this case. Over to @brewerj to complete accessibility horizontal review. |
no comment/request from i18n. marking as reviewc ompleted. |
The chairs plan to propose a better-described path for specifications and bring back to the WG for consensus before bringing to the AC. |
The issue is tagged "Security Review Completed" and "Privacy Review Completed", however there is a new issue in the w3c/webappsec worth considering: Web Applications should not have internet access by default (#578) |
Snapshot of charter for AC review: https://www.w3.org/2021/06/webappsec-proposed-charter-2021.html Diff of snapshot v. 2019 charter AC review (not yet open) |
Results of AC review: https://www.w3.org/2002/09/wbs/33280/webappsec2021/results, 2021-06-09 to 2021-07-09. |
Recharter proposal, reviewers please take note.
Charter Review
Charter
diff from 2019 charter
What kind of charter is this? Check the relevant box / remove irrelevant branches.
Horizontal Reviews: apply the Github label "Horizontal review requested" to request reviews for accessibility (a11y), internationalization (i18n), privacy, and security. Also add a "card" for this issue to the Strategy Funnel.
Communities suggested for outreach:
Known or potential areas of concern:
Where would charter proponents like to see issues raised? (this strategy funnel issue, a different github repo, email, ...)
https://github.com/w3c/webappsec/issues
Anything else we should think about as we review?
The text was updated successfully, but these errors were encountered: