<Angel> scribe: xfq
<scribe> Meeting: MiniApp CG Teleconference
[Introduction] MiniApps Ecosystem Community Group
Angel: I'll send review for the charter later
... a few parts: introduction, scope, liason, process, license, decision policy etc.
... group intro is:
<Angel> MiniApp as a new form of mobile application, leveraging both Web technologies (especially CSS and Javascript) as well as capabilities of native applications, is gaining more and more popularities in Asia countries such as China.
<Angel> To enhance the interoperability between different MiniApp platforms(AKA the super application or host application), main stream MiniApp vendors worked together in W3C Chinese Web Interest Group and published MiniApp Standardization White Paper in September 2019 as the initial standardization exploration for MiniApp.
<Angel> The MiniApps Ecosystem Community Group （MECG） provides a forum for global community to discuss, incubate and propose mini App related standard ideas with the goal to bring more interoperability and robustness to MiniApp ecosystem.
Angel: introduced the white paper we worked on, and future work we would like to work on
<Angel> 1. Basic architecture of MiniApp such as the URI scheme, widget, application lifecycle and event, as well as manifest;
<Angel> [updated] 1. Basic architecture of MiniApp such as the URI scheme, Widget, Application lifecycle and event, as well as Manifest;
<Angel> 2. Basic elements and APIs that would enhance the interoperability among different MiniApp platforms including UI display APIs, Device API, and those advanced ones like Account API, Map API, Payment API.
Angel: any modification to the intro and scope parts of the charter?
zlei: I think "Basic elements" should be "advanced elements"
Angel: we can also remove the word "basic"
<Angel> [update] 2. Elements and APIs that would enhance the interoperability among different MiniApp platforms including UI display APIs, Device API, and those advanced ones like Account API, Map API, Payment API.
zlei: agreed
Xiaoqian: what is "UI display API"?
zlei: I suggest that we change "UI display APIs" to "UI elements"
<Angel> [update] 1. Basic architecture and essential functions of MiniApp such as the URI scheme, widget, application lifecycle and event, as well as manifest;
Chunming: I suggest that we change "architecture" to "specific aspects", because these items don't look like architecture to me
Xiaowei: goal of the CG?
... only work on new features? or also interoperability of existing features?
Angel: for existing work in W3C, we work with relevant WGs
... for new work, we incubate them in the CG
Xiaoqian: we can mention it in the charter
Angel: proposed new text (of working with existing WGs in W3C) ^
<Angel> 3. Coordination with current W3C efforts, especially PWA on the commonality of Web features
Angel: any objection?
[silence]
Angel: now we are talking "out of scope" part of the charter
<Angel> The group does not intend to discuss ideas related to MiniApp platform operation. Neither will the group try to eliminating differences between various MiniApp platforms.
Chunming: I agree with the first sentence
... regarding the second sentence, do we need to mention this in the charter?
... I understand the intention, but suggest that we change the text to something more positive
Keith: I think eliminating/reducing differences is one of our goals
Angel: any suggested change to the text?
... any objection to deleting the second sentence?
<Angel> scope: 4. security, privacy, a11y, i18n
Xiaoqian: should we mention seeking horizontal review for accessibility, internationalization, privacy, and security?
<Angel> [update: seeking horizontal review for accessibility, internationalization, privacy, and security for MiniApp spec
Angel: regarding current proposals
... we can draft an initial timeline of these proposals next week
<Angel> * URI scheme * Widget * Application life cycle and events * Manifest
Angel: any changes to these proposals?
<Angel> • Web Application Working Group • Web Performance Working Group • Service Workers Working Group • Cascading Style Sheets (CSS) Working Group • Devices and Sensors Working Group • Web Application Security Working Group • Immersive Web Working Group • Web Incubator Community Group (WICG) • Accessible Platform Architectures Working Group
Angel: Xiaoqian compiled a list of relevant W3C WGs (see above)
... any changes to the list?
Xiaoqian: WHATWG?
Angel: ok, adding WHATWG
@@: Machine Learning CG?
<xiaoqian> PING
Angel: ok
... also adding i18n WG
... and PING
Angel: license http://www.w3.org/community/about/agreements/cla/
... contributions to specifications are made under the W3C CLA
... communication
... 1. mailing list
... 2. github repo
... 3. WeChat group
... #1 for admin issues
... #2 for techinical issues
... #3 also for admin issues
... how to use github?
Xiaoqian: one of my groups require 2 approvals for PRs, ideally from different vendors
Angel: we can think more about it, no need to mention it in the charter
<Angel> http://www.w3.org/Consortium/Legal/2015/copyright-software-and-document
https://github.com/w3c/licenses/blob/master/CG-LICENSE.md
Dan_Zhou: Is there a limit on the number of people joining the CG from one company? Can we have more than a dozen people in our company?
Angel: no limit on the number of CG participants
Angel: decision policy
... 2/3 vendors + reasonable amount of developers
... I'll send the charter for review later
<Angel> * full supermajority vote, which shall mean 66% or more of the then current group members who are MiniApp vendors. * Reasonable support from MiniApp developers
Angel:Chairs of the CG: Zhixing Lei (Baidu), Chen Yinli (Xiaomi), Keith Gu (Google), and me
Angel: future teleconferences
... we can hold monthly teleconf
[discussion about the time slot of the meeting]
<Chunming> +1
Angel: date of the next CG call
... propose Nov 14 9am (Beijing time)?
@@: Chrome Dev Summit is in that week
Xiaoqian: Nov 7 9am (Beijing time)?
... hearing no objections
Xueyuan: about minutes of the meetings
... we can call for review in the internal mailing list first
... then sending to the public mailing list
Angel: we can also highlight/summarize the minutes
... Thanks everyone for the input!
[adjourned]