-
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
CSS WG rechartering #338
Comments
history table lacks a link to the current running charter as https://www.w3.org/2020/12/css-wg-charter.html (at bottom line)? |
We are looking forward to discussing accessible navigation on TPAC, there is no other comment from APA WG. |
Thanks for noticing, will fix. |
@himorin any other comments from an I18n perspective? Are you the one reviewing the charter, or did you just happen to notice the missing link? |
@samuelweiler any comments from your perspective? |
no comment/request from i18n. (Sorry for delay on responding after 1 week internal discussion slot) |
No problem at all. I'm hoping to have this charter discussed at the 24 Aug W3M, so thanks for completing your review well before that! |
@swickr is the second reviewer. |
@samuelweiler any comments? If not, please mark the privacy and security review as complete? |
With apologies for the delay, no comments. |
In 4.1: I think you want to adjust the digital publishing group: [[ Selectors API was abandoned and moved in the DOM spec in 2020. I don't think there is a need to liaise with WebApps anymore |
(waiting to start the AC review) |
Contribution from Fuqiao 30% → 10% |
Formal objection from fantasai Suggested replacement text looks fine, but this is a comment on the charter template not specifically on the CSS WG proposed charter. |
Formal objection resolved, w3m approval requested. |
w3m approved 11 Jan 2023 |
Charter Review
Draft charter
What kind of charter is this? Check the relevant box / remove irrelevant branches.
diff
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, ...)
Anything else we should think about as we review?
The text was updated successfully, but these errors were encountered: