Meeting minutes
[Round-table introduction of the group participants]
Work mode and tooling
<Angel> https://
angel: background for new participants
… MiniApps WG is based on work incubated in the Chinese IG and the MiniApps CG
… developed a few proposals
… happened in the past 14 months
… will talk about the deliverables later
<Angel> https://
angel: please have a look at three documents
… first is W3C Patent Policy
… W3C standards are Royalty-Free
[angel explains W3C Patent Policy]
Angel: the second document is the W3C Process Document
<Angel> https://
Angel: pretty long document
… I was hoping there was some document for lazy people
… the AB is working on that
… the standards track will follow the process in this document
<Angel> https://
Angel: the third document I want everybody to pay attention to is Code of Ethics and Professional Conduct
… developed by the Positive Work Environment Community Group
… work on a active, collaborative, and cheerful environment
… any questions about this working group or these documents?
[silence]
Angel: the way a WG runs might be a little bit different from a CG because of these documents
… I would suggest every participant has at least some look at these documents
https://
Fuqiao: W3C currently uses GitHub for communications, and all tech discussions could happen there
… so the MiniApps WG will also use GitHub
… I filed an issue about how to transition the specs (previously developed by the MiniApps CG) from CG to WG
… options:
… 1) one repo for all the work in the CG and WG
… 2) two repos, one for CG, one for WG
… 3) multiple repos, one for each spec
zyj: personally support option 3
<zyj> 3
<Angel> 3
<zuming> 3
<martin_> 3
<xfq> 3
zyj: how long will it take to separate the repos?
Fuqiao: at most one week
<QingAn> 3
Action: fuqiao to set up the repos for the WG
[Consensus on GitHub repos: option 3]
Angel: mailing lists for notifications to group members
https://
Angel: we have member-visible list which we post the group call dial-in info, which shouldn't be shared outside the group
https://
Angel: we also have a public-visible list ^^
… we use IRC
Angel: other tools you like to use?
zyj: how to manage write access to GitHub repos?
xiaoqian: I would like to provide some suggestions on how to approve pull requests
… each pull request needs to reviewed by at least one reviewer
… the reviewer is in the WG
… there's an IPR bot
… if the person is in a member organization and the member has joined the WG, and they have associated their GitHub account with W3C account, should be OK
… some groups require 1 reviewer and some groups require 2 reviewers
… the Chairs/Editors/long-term group participants can review/approve the pull requests
… the public have read access to the repos
zyj: thanks
Angel: can you draft the rules and share with the group, xiaoqian?
Xiaoqian: how may reviewers you think we need for each normative/technical change to a spec, 1 or 2?
Angel: we can go with 2 reviewers
zyj: 2 sounds good
angel: any objections?
[silence]
Angel: yongjing suggested to use Outlook invitations, I can test it.
Action: Angel to test the outlook invitation for the memeber mailing list
Meeting cadence
Angel: would everybody prefer us to have a monthly call? or other frequency?
… one week after the CG call?
zyj: I think we can start with monthly
… we can accelerate at some point but starting with monthly is ok
Angel: let's resolve with monthly, one week after the CG call for now
… next CG call is March 25
… next WG call will be April 1
Review of time table and what we have in hand
Angel: we have normative specs and other deliverables
… MiniApp Manifest, Packaging, Lifecycle, Addressing, and Widget Requirements
https://
Angel: first I need to have editors for these specs
<martin_> I will
Angel: for manifest, do we have volunteers?
zyj: I can continue to edit this spec
xfq: Do we need to move editors in CG but not in WG to "Former editor(s)"?
angel: we can do that
zyj: that sounds ok
angel: Packaging
https://
<martin_> I volunteer
zyj: martin can lead that, I will also help
Dan_Zhou: I'll continue to help
<QingAn> I will
Tengyuan_Zhang: I'll continue to edit the Packaging spec
angel: let's have a big editor team for Packaging then
Angel: MiniApp Lifecycle
Qing_An: I'll continue
angel: MiniApp Addressing
Dan_Zhou: I'll continue
angel: MiniApp Widget Requirements
xiaoqian: xiaomi is still reviewing the W3C Patent Policy
Timeline
Angel: let's look at the timeline
… FPWD in Q1 2021
xfq: Q2 2021 for Packaging
angel: I ask all the editors to refine the draft in the coming 30 days
… we still have one month to refine our work before the decision
zyj: a question about the publication
… we used to develop the specs in a bilingual fasion
… is that still the expectation?
Angel: it's nice to have, but not a must
… English version will be the priority
… any questions?
CJK meeting
Angel: thinking about whether a CJK meeting is needed
… doesn't have to be purely about standards
… look at differently @@ forms
… start from these three countries
https://
Angel: xfq is working on the web page
… will be an online event
… April 8
… collecting speakers and presentations for this event
… the Japan host and the Korea chapter will help us
… if you want to be a speaker please contact xfq or xiaoqian
xfq: who will be the chair(s) of this meeting?
Angel: I can do it, and maybe other co-chairs
xueyuan: do you think it's suffice for us to announce it next week and open the registration?
… for the current topics
angel: I think that page looks good but we need more agenda items
xueyuan: sounds good, can we do that before next Tuesday
angel: a bit challenging, let's target next Thursday
Angel: for the Chinese vendors it will be relatively quick, not sure about other global vendors
xiaoqian: I don't think to we need to confirm the speakers when we announce the event
Angel: I will work with the co-chairs of the CG/WG to reach out to the Chinese vendors
… try to announce it next week
… xiaoqian, please help reach out to Japanese and Korean vendors
xiaoqian: sure
xueyuan: can the chairs send an invitation email to all W3C members?
Angel: yes
… thank you all!
… next meeting will be April 1
[adjourned]