01:05:00 RRSAgent has joined #miniapp 01:05:00 logging to https://www.w3.org/2019/11/07-miniapp-irc 01:05:17 Chair: Angel 01:05:28 Agenda + CG charter review 01:05:31 zakim, who is here? 01:05:31 Present: Angel, Chunming, xiaoqian, xfq, chumming, dan_zhou, Jayzhou, KeithGu, NicoleYu, Peipei, Xueyuan, Qing_An, Peipei_guo, shouqun_liu, Siyang_liu, ternence, Tgf, Wanming_lin, 01:05:35 ... xiaowei, Yinli_chen, zuming 01:05:35 On IRC I see RRSAgent, xiaoqian, dbaron, Angel, xfq, xueyuan, Zakim, ella, sangwhan, jungkees, slightlyoff, cwilso, wseltzer 01:05:39 present+ Fuqiao 01:05:45 Meeting: MiniApps Ecosystem Community Group Call 01:05:53 zakim, clear agenda 01:05:53 agenda cleared 01:05:59 zakim, clear agenda 01:05:59 agenda cleared 01:06:06 Agenda + CG charter review 01:06:20 present- Chunming 01:06:29 present- Jayzhou 01:06:41 present- NicoleYu 01:06:45 agenda + CG projects plan review 01:06:51 agenda +AoB 01:06:56 present+ Angel 01:07:06 present - shouqun_liu, Siyang_liu, ternence, Tgf, Wanming_lin 01:07:14 present+ dbaron 01:07:14 Meeting: MiniApp CG Call 01:07:34 present- zuming 01:07:50 scribenick: xfq 01:07:52 present+ berg 01:08:30 zakim, take up item 1 01:08:30 agendum 1. "CG charter review" taken up [from Angel] 01:08:59 charter of CG:https://w3c.github.io/miniapp/charter.html 01:09:03 angel: current agenda proposal ^ 01:09:52 ... for background 01:09:52 ... the directions of the CG was discussed during TPAC 2019 Chinese IG F2F 01:10:09 ... please let us know if you have any comment for the charter 01:10:29 ... I'll send it for review for a 5-6 day review period 01:10:42 ... any question? 01:10:55 [silence] 01:11:04 agenda? 01:11:09 zakim, close agenda 1 01:11:09 agendum 1, CG charter review, closed 01:11:10 I see 2 items remaining on the agenda; the next one is 01:11:10 2. CG projects plan review [from Angel] 01:11:16 zakim, take up item 2 01:11:16 agendum 2. "CG projects plan review" taken up [from Angel] 01:11:52 angel: the CG has 4 initial projects 01:11:53 ... URI scheme, Widget, Application lifecycle and event, as well as Manifest 01:11:55 Lifecycle: https://github.com/w3c/miniapp/issues/13 01:12:00 URI scheme: https://github.com/w3c/miniapp/issues/12 01:12:03 Widget: https://github.com/w3c/miniapp/issues/14 01:12:13 ... here's the timeline of these projects ^ 01:12:36 ... let's look at URI scheme 01:13:07 [going through URI scheme] 01:13:28 berg: we will draft an initial version and put it on github 01:14:14 angel: let's look at application lifecycle next 01:14:30 ... is An Qing on the call? 01:14:36 [silence] 01:14:47 Angel: let's skip this for now 01:14:57 Peipei_Guo has joined #MiniApp 01:15:16 ... anyone from Xiaomi can give an intro of the widget timeline? 01:15:34 https://github.com/w3c/miniapp/issues/14 01:16:07 [going through the widget timeline] 01:16:56 yajun_chen has joined #MiniApp 01:17:33 q+ 01:17:34 xiaowei: the deadline is Q3 2020 currently 01:17:34 ... any comment from the CG participants on that? 01:18:01 ack xiaoqian 01:18:11 angel: let's go with the plan you're comfortable now 01:18:12 ... and adjust based on the development status 01:18:45 https://github.com/w3c/miniapp/issues/15 01:18:59 xiaoqian: @marcoscaceres filed an issue re gap analysis of W3C widgets and mini app widgets 01:19:17 ... could you look into this, xiaowei? 01:21:04 angel: there are two parts in Marcos' issue 01:21:04 ... one is the gap analysis 01:21:04 ... the other is to update the white paper to include more information 01:21:04 ... am I understanding correctly? 01:21:48 q+ to mention explainers 01:22:26 xiaoqian: I think just putting the content in Xiaomi's widget document is an option 01:22:27 ... of course we can update the white paper too if needed 01:23:02 yingli: we will include the gap analysis of our widget spec of previous attempts 01:23:13 xiaoqian: sounds good 01:23:39 s/the gap analysis of/the gap analysis of use cases in/ 01:23:56 ack dbaron 01:23:56 dbaron, you wanted to mention explainers 01:24:24 https://w3ctag.github.io/explainers 01:25:48 dbaron: I just wanted to mention the idea of explainers 01:25:49 ... sometimes the TAG has a reviewing process 01:25:49 ... and an explainer explainer 01:25:49 ... I don't mean that you need to write an explainer, but it may help answer questions like Marcos' 01:26:29 angel: any exact suggestion? 01:26:30 dbaron: I don't have any exact suggestion 01:26:30 ... but just want to point out that an explainer may be helpful 01:26:55 angel: only for widget, or for other stuff in the CG as well? 01:27:14 dbaron: it can be used when you build something new 01:27:33 ... it's useful to write a short explanation 01:27:52 angel: understood, thank you 01:28:12 ... anything else we need to discuss re Xiaomi's widget plan? 01:28:26 berg: I agree with David 01:28:51 ... it's useful for URI scheme and other activities in the group too 01:29:11 [An Qing joins] 01:29:44 Qing: can I give a brief intro of https://github.com/w3c/miniapp/issues/13 01:30:20 ... there are some related work in W3C such as Page Visibility 01:30:21 ... we'll look into that 01:30:52 angel: any question on application lifecycle? 01:31:27 yajun_ch_ has joined #MiniApp 01:31:49 Qing: Alibaba volunteers work on this 01:31:49 ... anyone who is interested is welcome 01:31:49 berg: Baidu will join 01:33:19 scribe: xueyuan 01:33:40 Angel: anyone from Huawei to introduce the Manifest? 01:33:51 xfq_ has joined #MiniApp 01:34:39 ... Huawei seems not here, if any of you like to volunteerly work together with Huawei on Manifest, please let me know. 01:35:02 ... action for each projects leading company 01:35:34 ... please provide your editors' names and email addresses, before @@ Nov. 01:37:19 s/@@/14th 01:37:57 ... you are very welcomed to join all the projects discussion 01:39:04 ... we expect the leading company to lead/drive each projects 01:39:57 Berg: there're indeed similar part between widgets and miniapps 01:40:25 ... @1 01:41:11 scribenick: xfq 01:41:13 yingli: we need to define the scope 01:41:14 ... for example, widget may also contains URI scheme and lifecycle 01:41:43 berg: we need to make the specs modular 01:42:06 ... not a giant widget spec 01:42:39 yingli: if there's already a W3C spec, can we just refer to it 01:42:40 xiaoqian: sure 01:43:27 ... we can also get in touch with the relavant W3C spec editors 01:43:27 ... like Marcos about widget 01:44:30 angel: what yingli aksed is an important question 01:44:30 ... we need to ensure that the four project dont' do duplicated work 01:44:39 s/aksed/asked 01:45:14 ... we can discuss more technical details in future teleconferences 01:46:47 zhoudan: @@ 01:46:48 xiaoqian: you can look at the explainer dbaron just mentioned 01:47:49 zhoudan: how to ensure that we don't do duplicated work? 01:47:49 ... should we collaborate as early as possible? 01:47:56 xiaoqian: I think so 01:48:33 zhoudan: one potential issue is that the timeline of the projects do not sync with each other 01:49:08 s/@@/what's the best way to analysis the difference between the existing technology and other W3C specs? 01:49:45 xiaoqian: e.g, if some of your work in URI scheme is related to manifest 01:49:45 ... you can ping the manifest editor in a github issue as soon as you publish your draft on github 01:49:56 agenda? 01:50:26 angel: next teleconference: Dec 6 01:50:27 ... any objection? 01:50:27 [silence] 01:51:00 s/Dec 6/Dec 5/ 01:51:09 angel: any other business? 01:51:36 ... hearing none, the meeting is adjourned 01:51:37 rrsagent, make log team 01:52:04 rrsagent, draft minutes 01:52:04 I have made the request to generate https://www.w3.org/2019/11/07-miniapp-minutes.html Angel 01:52:04 rrsagent, make minutes 01:52:04 I have made the request to generate https://www.w3.org/2019/11/07-miniapp-minutes.html xfq_ 01:52:06 s/Dec 5/ 9-10am (Beijing, UTC+8) Dec 5 (Thursday) 01:52:14 rrsagent, make minutes 01:52:14 I have made the request to generate https://www.w3.org/2019/11/07-miniapp-minutes.html xfq_ 01:52:16 rrsagent, make log public 01:58:09 xfq__ has joined #MiniApp 02:51:50 xfq__ has joined #MiniApp 03:04:07 agenda? 03:10:53 xueyuan has joined #miniapp 03:14:53 rrsagent, bye 03:14:53 I see no action items