Closed iherman closed 1 year ago
Groups have been contacted:
Covering the two WG-s that are planned to be replaced by this Maintenance WG
i18n runs language enablement activities, in coordination with groups of experts over languages, and could find emerging requests to fill gaps to requirements of languages. To where we should contact on such case?
@himorin in the hope that I understand your question: the W3C Publishing Activity has three "pillars". The Publishing Business and Community groups, and the active WG (today the EPUB, tomorrow the proposed Maintenance WG). So the target of your contact will depend on the nature of your problem, ranging from general usage/business issues, some general technical issues, down to specific issues with our published standards or notes.
Does this answer your question? First of all, did I understand your question properly?
cc @TzviyaSiegman and @swickr (as publishing co-champions of the activity)
cc @wareid @dauwhe @shiestyle (proposed chairs for this Working Group)
looks good to APA WG.
Advance notice: https://lists.w3.org/Archives/Member/w3c-ac-members/2023JanMar/0040.html EPub charter expires in August, as well as AudioBooks.
Waiting on EPub Proposed Recommendation or REC to start AC Review for this charter.
AC review started: https://www.w3.org/2002/09/wbs/33280/pmwg/results
AC review ended: https://www.w3.org/2002/09/wbs/33280/pmwg/results, with positive results; charter approval has been submitted to TILT: https://github.com/w3c/tilt-private/issues/9
WG announced on the 20 June 2023
New charter proposal, reviewers please take note.
Charter Review
Charter: Publishing Maintenance Working Group 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, ...)
Anything else we should think about as we review?
As the introduction says, it is "only" a maintenance Working Group, the only special feature that it would pull together the maintenance of the output of two working groups into one place.