w3c / strategy

team-strat, on GitHub, working in public. Current state: DRAFT
151 stars 45 forks source link

[wg/miniapps] Rechartering MiniApps Working Group #368

Closed xfq closed 8 months ago

xfq commented 1 year ago

New charter proposal, reviewers please take note.

Charter Review

MiniApps Working Group Charter 2023

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:

MiniApp vendors

Known or potential areas of concern:

Where would charter proponents like to see issues raised? (this strategy funnel issue, a different github repo, email, ...)

https://github.com/w3c/miniapp/issues

Anything else we should think about as we review?

ruoxiran commented 1 year ago

no comments from APA.

himorin commented 1 year ago

No comment nor request from i18n

plehegar commented 1 year ago

No comment from PING

svgeesus commented 1 year ago
  1. The Normative specifications section omits the Draft State and Adopted Draft items, and it is harder to find the Exclusion Draft etc because the markup has been lost. See the charter template
  2. "Note: The actual production of some of the deliverables may follow a different timeline." :)
  3. Success criteria is missing significant language and links, compared to the charter template. Please use the charter template wording here, then add any additional wording (such as the last sentence about implementing APIs securely).
  4. Performance is not part of horizontal review. Maybe it should be, but it isn't.
  5. Nice addition on allocating resources for test suites
  6. The copyright information is incorrect, please see the charter template
xfq commented 1 year ago

Thanks for the comments, Chris! I have updated the charter to fix these points.

plehegar commented 1 year ago

@xfq I added agenda+ so that strat can agree this is ready to move forward. Remove it if that's not the case.

xfq commented 1 year ago

@plehegar I think we already discussed this in strat (see https://www.w3.org/2023/04/11-strat-minutes.html#t01 ). I didn't ask for W3M approval because I think we should have a general direction regarding TAG's comment on MiniApps before starting AC review. Since we have one now (see https://github.com/w3c/miniapp/issues/195 ), I can send an email to W3M (per https://www.w3.org/Guide/process/charter.html it's still W3M and not TiLT). WDYT?

plehegar commented 1 year ago

@xfq, makes sense to me.

siusin commented 1 year ago

@xfq could you explain why MiniApp Addressing was listed as a Normative Specification but published as a Group Draft Note? Does the group have any specific expectations for this document?

xfq commented 1 year ago

@siusin Because it contains normative content, if it's on the REC track it can be protected by the W3C Patent Policy. It was a Note before because it was meant as a proposal being incubated, and the MiniApps CG was still discussing it with the TAG.

siusin commented 8 months ago

The URL of Firefox OS' Open Web Apps is broken.

Please provide a permanent URL of the charter for the charter approval.

xfq commented 8 months ago

Thank you, @siusin. Fixed now.

The permanent URL is https://www.w3.org/2023/10/miniapps-wg-charter.html . I'll remove the draft label if/when it's approved.

himorin commented 8 months ago
xfq commented 8 months ago

Done: https://www.w3.org/2023/10/miniapps-wg-charter.html