-
Notifications
You must be signed in to change notification settings - Fork 47
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
[wg/png] PNG WG recharter #419
Comments
|
Had a quick read, and it looks perfectly reasonable and well written to me. |
Itemize in normative deliverables seems weird... First title line might be better to be moved out from itemize, like what template does. |
(PING might be pass on this one until we get someone interested within a week) |
no comment from APA. |
Oh good catch, will do |
Markup corrected on the deliverables, looks much better now. |
no comment or request from i18n |
Update:
|
@plehegar said:
If PING is unable to review, please tag as privacy review completed so I can ask TiLT for approval to send for AC review. |
(no comments from PING) |
[[ This was reverted in the template, so this needs an update. should say: |
Thanks for noticing, fixed |
AC Review started 7 Sept 2023 |
One minor tweak. |
4th sentence in 8. Decision Policy contains "Director" (at the last), which I believe we tried to omit from everything recently.
|
Charter announced, CFP sent 23 Oct 2023 |
New charter proposal, reviewers please take note.
Charter Review
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:
None
Where would charter proponents like to see issues raised? (this strategy funnel issue, a different github repo, email, ...) Strategy funnel
Anything else we should think about as we review?
The text was updated successfully, but these errors were encountered: