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.

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

Closed
1 task done
svgeesus opened this issue Jul 30, 2022 · 19 comments
Closed
1 task done

CSS WG rechartering #338

svgeesus opened this issue Jul 30, 2022 · 19 comments

Comments

@svgeesus
Copy link
Contributor

svgeesus commented Jul 30, 2022

Charter Review

Draft charter

What kind of charter is this? Check the relevant box / remove irrelevant branches.

  • Existing
  • Existing WG recharter

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?

@himorin
Copy link

himorin commented Aug 2, 2022

history table lacks a link to the current running charter as https://www.w3.org/2020/12/css-wg-charter.html (at bottom line)?

@ruoxiran
Copy link

ruoxiran commented Aug 3, 2022

We are looking forward to discussing accessible navigation on TPAC, there is no other comment from APA WG.

@svgeesus
Copy link
Contributor Author

svgeesus commented Aug 5, 2022

lacks a link to the current running charter

Thanks for noticing, will fix.

svgeesus added a commit to w3c/charter-drafts that referenced this issue Aug 5, 2022
@svgeesus
Copy link
Contributor Author

@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?

@svgeesus
Copy link
Contributor Author

@samuelweiler any comments from your perspective?

@svgeesus
Copy link
Contributor Author

@wseltzer I discussed W3M review with @plh and he agreed to be one reviewer; we also thought that W3M review could start even before horizontal review is complete.

Could you be the other reviewer? (I know you are very busy now with LE bylaws and such, so "no" is a perfectly acceptable answer)

@himorin
Copy link

himorin commented Aug 12, 2022

no comment/request from i18n. (Sorry for delay on responding after 1 week internal discussion slot)

@svgeesus
Copy link
Contributor Author

Sorry for delay on responding

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!

@svgeesus
Copy link
Contributor Author

@swickr is the second reviewer.

@svgeesus
Copy link
Contributor Author

svgeesus commented Sep 1, 2022

@samuelweiler any comments? If not, please mark the privacy and security review as complete?

@samuelweiler
Copy link
Member

With apologies for the delay, no comments.

@plehegar
Copy link
Member

In 4.1:

I think you want to adjust the digital publishing group:
s/Audiobooks Working Group/EPub 3 Working Group/

[[
Web Applications Working Group
The Group reviews the Selectors API module, being developed by the
Web Applications Working 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

svgeesus added a commit to w3c/charter-drafts that referenced this issue Oct 3, 2022
@svgeesus
Copy link
Contributor Author

svgeesus commented Oct 4, 2022

@plh I believe both your comments are addressed.

@swickr did you have comments? (If sent by email my apologies, I still have a backlog)

@plehegar
Copy link
Member

plehegar commented Oct 6, 2022

(waiting to start the AC review)

@svgeesus
Copy link
Contributor Author

svgeesus commented Oct 6, 2022

@svgeesus
Copy link
Contributor Author

Contribution from Fuqiao 30% → 10%

@svgeesus
Copy link
Contributor Author

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.

@svgeesus
Copy link
Contributor Author

svgeesus commented Jan 9, 2023

Formal objection resolved, w3m approval requested.

@svgeesus
Copy link
Contributor Author

w3m approved 11 Jan 2023

@svgeesus svgeesus moved this from Chartering to Strategy Work Concluded in Strategy Team's Incubation Pipeline (Funnel) Jan 17, 2023
@svgeesus svgeesus closed this as completed Apr 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

5 participants