-
Notifications
You must be signed in to change notification settings - Fork 48
[ig/wai] WAI IG recharter #441
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
Comments
Group has been extended |
Given the group is not wanting to do work beyond email discussions right now, and there are no substantive changes to the group or next charter, other work has taken priority over creating and processing a new charter. It remains on the To Do list... |
I assume charter shepherd is @iadawn |
Charter changed to be for two years |
is it actually necessary to have a charter, to continue running this mailing list? many moons ago, this group held face-to-face meetings and had more engagement efforts that made a charter necessary. i'm not opposed, just wondering if such a charter is still needed. |
No comment or request from i18n |
No comment or request from APA |
@nitedog The moon is rising again. :) We are working on a potential hybrid meeting soon and more engagement later this year. We'd like to charter for another 2-year period so we have it in place as we refine engagement through the Interest Group. |
No comment from Security |
The "Motivation and Background" talks mostly about the mailing list, so maybe to address questions similar to @nitedog 's one above, it may be useful to explain a bit more the expected role of the IG as meeting host as well. |
"This Interest Group does not develop deliverables." Do you only really wish to prevent the IG from even publishing Group Notes? The W3C Process already prevents the IG from publishing Rec-track documents. |
Section 5.1 W3C Groups:
This list a few W3C Groups without given a rational for listing them. While I can understand that the WAI Groups are listed since the IG will review and raise of their deliverables. Does it do the same with the i18n Core WG? |
Thank you for the input. We addressed comments with w3c/charter-drafts#668 We held a WAI IG session in May. (We didn't get it organized in time to be a formal meeting.) We will share the link to the recording after the captions are done. We are exploring two options for hybrid meetings later this year, including W3C TPAC. We will process this and request AC review soon. |
[Google hat rather than TAG hat] |
replies in w3c/charter-drafts#669 (comment) |
Uh oh!
There was an error while loading. Please reload this page.
Charter Review
Charter
Diff from charter template
Diff from previous charter
Chair dashboard
What kind of charter is this? Check the relevant box / remove irrelevant branches.
If this is a charter extension or revision, link a coming later diff from previous charter, and any issue discussion: none.
Horizontal Reviews: apply the Github label "Horizontal review requested" to request reviews for accessibility (a11y), internationalization (i18n), privacy, and security. @@todo: Also add a "card" for this issue to the Strategy Funnel.
Communities suggested for outreach
None at this time.
Known or potential areas of concern
None at this time.
This is request for an extension of the existing charter so we can propose a new charter. We don't expect any substantive changes to that charter.
Where would charter proponents like to see issues raised? (this strategy funnel issue, a different github repo, email, ...)
https://github.com/w3c/charter-drafts/issues?q=in%3Atitle%20ig%2Fwai
Anything else we should think about as we review?
The new charter extends the group for three years and aligns with the latest charter template. There are no other material changes.
The text was updated successfully, but these errors were encountered: