W3C

– DRAFT –
MiniApps WG Call

26 August 2021

Attendees

Present
angel, Canfeng_Chen, Dan_Zhou, gaoliang, Manvi_Kapoor_Rakuten, martin_alvarez, Tengyuan_Zhang, tomayac3, Wenli_Zhang, xfq, xiaoqian, xuying07, yanyumeng, Yongjing_Zhang, Zitao_Wang
Regrets
-
Chair
Angel
Scribe
xfq

Meeting minutes

Deliverables status review

angel: Deliverables status review

https://github.com/w3c/miniapp/tree/gh-pages/specs#wg-documents

angel: Lifecycle
… Qing An may be late for a while
… let's move to Manifest

martin: relatively quite

https://github.com/w3c/miniapp-manifest/pull/29

martin: ^ Infra types and alignment with Web App Manifest definitions

martin: editorial changes

https://github.com/w3c/miniapp-manifest/pull/23

https://github.com/w3c/miniapp-manifest/pull/28

Zitao_Wang: updated the manifest json schema

angel: any objection on merging #23 and #28?

[no objection]

angel: Packaging

martin: not too many updates
… refining the spec, haven't sent the PR yet
… clean the spec in order to request wider review
… clarifying the terms
… will do it this week

angel: in our WG charter we plan to publish the CRs in Q4 2021
… we might need to hurry up a little
… I would like to urge our editors and participants to get the CR draft ready
… get the draft ready at least before November

xfq: Before CR, we need at least 2-3 months for wide review

angel: right

angel: we can request wide review during TPAC

xfq: We can also request wide review before TPAC and discuss issues during TPAC

martin: I think we can have a solid draft in the next week or in a couple of weeks
… hopefully before the next WG call

angel: I'll convey the info to Qing An as well

angel: Addressing

Dan_Zhou: please comment on PR

https://github.com/w3c/miniapp-addressing/pull/3

<angel> https://github.com/w3c/miniapp-addressing/pull/4

Dan_Zhou: first PR is image fix for explainer

angel: there's a comment from Yongjing
… do you think we should vote for merging this PR or we should wait for more comemnts?

angel: if there's no comment in the next month we do a group vote

angel: Widget Requirements

Canfeng_Chen: open for receiving comments for Widget Requirements
… no update

angel: we don't have a timetable for it on the charter, but still some progress would be appreciated

TPAC 2021 planning

angel: 25 - 29 October

angel: group meetings and joint group meetings

<angel> https://www.w3.org/wiki/TPAC/2021/GroupMeetings

angel: do we want to meeting during TPAC?
… I assume yes
… if we could let's try to meet on 12 UTC, October 28 (Thursday)
… do we want to schedule joint meetings with other groups?
… like WebApps WG for Manifest discussions

Yongjing_Zhang: we need to sync on i18n

angel: maybe 1 hour for the WG and 1 hour for the CG

angel: 12-14 UTC

angel: I'll talk to the CG chairs

<martin> +1 to Angel's proposal

Canfeng_Chen: can we invite more international companies to join our meeting?

angel: we used to have the TPAC week offline
… during the TPAC week most WGs and IGs will meet
… some groups chose to have joint meetings
… for example, CSS WG met with SVG WG
… it's a tradition
… now we moved offline to online
… great to have cross-group discussions
… your suggestion is good
… by international companies do you mean W3C Members or non-member organizations?

Canfeng_Chen: either is fine
… looking forward to see their comments

<martin> What about to organize a dedicated session as a breakout session? We can present these tools and implementations mentioned by Zitao, also an opportunity for other companies as Chen Canfeng mentioned.

angel: this WG is a pretty international one, for example, we have people from Google and Rakuten on the call today
… I agree with you that we need more involvement from other organizations
… there is a Patent Policy guiding the meeting
… we cannot accept technical input from non-members

martin: breakout session is public

<angel> https://www.w3.org/2002/09/wbs/34257/TPAC2021-F2FSocial/

angel: a breakout session might work

angel: we can organize a tpac breakout session
… what do you think, Canfeng?

Canfeng_Chen: in the first half of this year we invited some international companies to attend our meeting but did not get much feedback
… hope we get more feedback this time
https://github.com/w3c/miniapp/issues/170
… I think feedback is quite important

angel: a wider review would be good, but not every company have relevant products
… comments are welcome

https://www.w3.org/wiki/TPAC2021/Demos_and_Group_updates

xfq: Apart from the TPAC and breakout sessions, in this TPAC event, there is a dedicated session for demos and implementations.

angel: will fill in the table(s) on the TPAC wiki page

White paper maintenance

<angel> https://github.com/w3c/miniapp/issues?q=is%3Aissue+is%3Aopen+label%3A%22white+paper%22

angel: ^ open issues

angel: one is recent, opened in May

angel: others were opened in 2019

angel: the MiniApps WG decided to maintain the white paper

angel: what do we want to use it for?

angel: while people are thinking, I can share some initial thoughts of mine
… 3 years ago we began to think about writing a white paper for MiniApps
… because most people don't understand what miniapp is
… it was a good starting point
… with the help of this white paper we explained what is MiniApp and why we want to standardize it
… then we created the CG and WG
… we achieved the goal and what's the next step
… the white paper can be seen as a "bigger picture" of MiniApps at W3C
… current status and future work in WG and CG
… if it's not too much work maybe we could publish it yearly
… look at it before Christmas and publish it after the New Year
… see the current status of MiniApp and what problems we solved

angel: shouldn't take too much time

<martin> +1 to keep the white paper as a reference document

angel: this is a personsal proposal

Zitao_Wang: makes sense to me
… provide the whole picture of MiniApps
… help others understand what we do
… explain why we need MiniApps
… help the developers and other people to understand

Canfeng_Chen: we should continue to improve the white paper
… I suggest that we limit the technical details of white paper
… the white paper should be easy for non-tech-savvy users to understand too
… for the details we can point to other documents
… people can click the links

xiaoqian: first, I'd like to thank the all editors of the white paper
… Many developers inside and outside China have cited this document
… I agree that we should continue the work
… in the future work of the white paper we should also focus on explaining the relationship of MiniApps, WebView, browsers, and PWAs
… because it's frequently asked
… Could you write down the plan of the white paper in a GitHub issue, angel or xfq?

angel: I have some initial plan to revise the framework of the white paper
… we can start working in November
… and publish it in January
… do this once a year
… I'll provide more information on GitHub soon

xiaoqian: thank you!

martin: +1 to angel

angel: set up a TF to revise the 2022 version of white paper

angel: look forward to working with you to maintain the white paper

AOB

angel: next meeting, September 23?

<martin> +1 sep 23

Minutes manually created (not a transcript), formatted by scribe.perl version 147 (Thu Jun 24 22:21:39 2021 UTC).