{"id":35,"date":"2020-01-21T09:09:24","date_gmt":"2020-01-21T09:09:24","guid":{"rendered":"https:\/\/www.w3.org\/community\/miniapps\/?p=35"},"modified":"2021-08-12T06:46:33","modified_gmt":"2021-08-12T06:46:33","slug":"miniapps-ecosystem-community-group-charter","status":"publish","type":"post","link":"https:\/\/www.w3.org\/community\/miniapps\/2020\/01\/21\/miniapps-ecosystem-community-group-charter\/","title":{"rendered":"MiniApps Ecosystem Community Group Charter"},"content":{"rendered":"\n<p>Start Date:  December 15<sup>th<\/sup> 2019 <\/p>\n\n\n\n<p>The MiniApps Ecosystem Community Group provides a forum for global community to discuss, incubate and propose MiniApp related standard ideas with the goal to bring more interoperability and robustness to MiniApp ecosystem. <\/p>\n\n\n\n<p><strong>Background <\/strong><\/p>\n\n\n\n<p>MiniApp as a new form of mobile application, leveraging both Web\ntechnologies (especially CSS and Javascript) as well as capabilities of native\napplications, is gaining more and more popularities in Asian countries such as\nChina. To enhance the interoperability between different MiniApp platforms (AKA\nthe super application or host application), main stream MiniApp vendors has\nbeen working together in <a href=\"https:\/\/www.w3.org\/2018\/chinese-web-ig\/\">W3C Chinese Web Interest Group<\/a>\nsince May 2019 and published <a href=\"https:\/\/www.w3.org\/TR\/mini-app-white-paper\/\">MiniApp Standardization\nWhite Paper<\/a> in September 2019 as the initial standardization\nexploration for MiniApp technologies. <\/p>\n\n\n\n<p>As more global companies get interested in joining the MiniApp related discussion, the MiniApp Ecosystem Community Group was proposed and approved during TPAC2019 so that global Web community can join the discussion. <\/p>\n\n\n\n<p><strong>Scope of Work <\/strong><\/p>\n\n\n\n<p>The MiniApp Ecosystem Community Group aims to discuss proposals for MiniApp features that would benefit the interoperability and robustness of MiniApp ecosystem, including: <\/p>\n\n\n\n<p><strong>Out of Scope <\/strong><\/p>\n\n\n\n<p>The group does not intend to discuss ideas related to MiniApp platform operation. <\/p>\n\n\n\n<p><strong>Current Proposals <\/strong><\/p>\n\n\n\n<p>Based on the <a href=\"https:\/\/www.w3.org\/TR\/mini-app-white-paper\/\">MiniApp Standardization\nWhite Paper<\/a> as well as previous discussion in <a href=\"https:\/\/www.w3.org\/2018\/chinese-web-ig\/\">W3C\nChinese Web Interest Group<\/a>, the following projects are proposed as initial\nstandardization exploration of MiniApp. <\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>URI scheme<\/li><li>\u009fWidget<\/li><li>Application life cycle and events <\/li><li>Manifest<\/li><\/ul>\n\n\n\n<p>New projects or status changes are communicated to the group through the\npublic mailing list. Chairs and editors should publish status updates to the group\npublic mailing list to allow group participants to monitor progress without\nhaving to directly watch every repo. <\/p>\n\n\n\n<p><strong>Coordination <\/strong><\/p>\n\n\n\n<p>It is anticipated that the group will collaborate with appropriate W3C\nWorking Groups and WHATWG work streams in order to transition spec proposals to\nthe Recommendation or Living Standard track. This group will probably get into\ncollaboration with the following groups: <\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Web Application Working Group<\/li><li>Web Performance Working Group<\/li><li>Service Workers Working Group<\/li><li>Cascading Style Sheets (CSS) Working Group<\/li><li>Devices and Sensors Working Group<\/li><li>Web Application Security Working Group<\/li><li>Immersive Web Working Group<\/li><li>Web Incubator Community Group (WICG)<\/li><li>Accessible Platform Architectures Working Group<\/li><li>Machine Learning Community Group<\/li><li>Internationalization Working Group<\/li><li>Privacy Interest Group(PING)<\/li><li>WHATWG <\/li><\/ul>\n\n\n\n<p><strong>Community Group Process and Patent Policy <\/strong><\/p>\n\n\n\n<p>The group operates under the <a href=\"https:\/\/www.w3.org\/community\/about\/agreements\/\">Community and Business\nGroup Process<\/a>. Terms of in this charter that conflict with those\nof the Community and Business Group Process are void. <\/p>\n\n\n\n<p>As with other Community Groups, W3C seeks organizational licensing\ncommitments under the <a href=\"http:\/\/www.w3.org\/community\/about\/agreements\/cla\/\">W3C Community Contributor License Agreement\n(CLA)<\/a> (Proposals in\nthis Community Group charter are applicable &#8220;Specification&#8221; in the\nCLA). When people request to participate without representing their\norganization\u2019s legal interests, W3C will in general approve those requests for\nthis group with the following understanding: W3C will seek and expect an\norganizational commitment under the CLA starting with the individual\u2019s first\nrequest to make a contribution to a group deliverable. The section on <a href=\"http:\/\/wicg.github.io\/admin\/charter.html#contrib\" target=\"_blank\" rel=\"nofollow\">Contribution\nMechanics<\/a> describes how W3C expects to monitor these\ncontribution requests. <\/p>\n\n\n\n<p><strong>Communication<\/strong><\/p>\n\n\n\n<p>The\ngroup tends to have monthly teleconferences and conducts its work on the public\nmailing list public-miniapps@w3.org as well as its <a href=\"https:\/\/github.com\/w3c\/miniapp\" target=\"_blank\" rel=\"nofollow\">GitHub Repository<\/a> for\ntechnical discussions. Other communication tools are allowed if considerable\nnumber of the group participants decide to embrace them.<\/p>\n\n\n\n<p><strong>Participation and Contribution <\/strong><\/p>\n\n\n\n<p>Membership of the group is open to everybody but all participants will\nhave signed the <a href=\"https:\/\/www.w3.org\/community\/about\/agreements\/cla\/\">W3C Community Contributor\nLicense Agreement<\/a>. Chairs and editors of feature proposals must\nensure that no contributions are adopted from anyone who is not a member of the\nCommunity Group. <\/p>\n\n\n\n<p>Specifications created for proposals in the Community Group must use the <a href=\"http:\/\/www.w3.org\/Consortium\/Legal\/2015\/copyright-software-and-document\">W3C\nSoftware and Document License<\/a>. <\/p>\n\n\n\n<p>All Github repositories attached to the Community Group must contain a\ncopy of the <a href=\"https:\/\/github.com\/w3c\/licenses\/blob\/master\/CG-CONTRIBUTING.md\" target=\"_blank\" rel=\"nofollow\">CONTRIBUTING<\/a>\nand <a href=\"https:\/\/github.com\/w3c\/licenses\/blob\/master\/CG-LICENSE.md\" target=\"_blank\" rel=\"nofollow\">LICENSE<\/a>\nfiles. <\/p>\n\n\n\n<p>Note: this CG will not use a <em>contrib<\/em> mailing list for contributions\nsince all contributions will be tracked via Github mechanisms (e.g. pull\nrequests). <\/p>\n\n\n\n<p><strong>Decision Policy <\/strong><\/p>\n\n\n\n<p>This group will seek to make decisions when there is consensus. consensus\ndecisions will be recorded through meeting minutes or its GitHub repo issue\nlist with assistance from the Chairs. <\/p>\n\n\n\n<p>Any technical specification that is planned to be proposed to a W3C\nworking group should require:<\/p>\n\n\n\n<p><strong>About This Charter<\/strong><\/p>\n\n\n\n<p>This Charter can be amended by the Chairs with consultation of the\nCommunity Group. <\/p>\n\n\n\n<p><strong>Charter History <\/strong><\/p>\n\n\n\n<p>The following table lists details of all\nchanges from the initial charter.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td>\n  <strong>Charter Period <\/strong>\n  <\/td><td> <strong>Start Date <\/strong>   <\/td><td>\n  <strong>Changes <\/strong>\n  <\/td><\/tr><tr><td>\n  <strong>Initial Charter<\/strong><strong> <\/strong>\n  <\/td><td>Dec 15   2019    <\/td><td>   <\/td><\/tr><\/tbody><\/table><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>Start Date: December 15th 2019 The MiniApps Ecosystem Community Group provides a forum for global community to discuss, incubate and propose MiniApp related standard ideas with the goal to bring more interoperability and robustness to MiniApp ecosystem. Background MiniApp as &hellip; <a href=\"https:\/\/www.w3.org\/community\/miniapps\/2020\/01\/21\/miniapps-ecosystem-community-group-charter\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":15032,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_s2mail":"yes","footnotes":""},"categories":[1],"tags":[],"class_list":["post-35","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.w3.org\/community\/miniapps\/wp-json\/wp\/v2\/posts\/35","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.w3.org\/community\/miniapps\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.w3.org\/community\/miniapps\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/miniapps\/wp-json\/wp\/v2\/users\/15032"}],"replies":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/miniapps\/wp-json\/wp\/v2\/comments?post=35"}],"version-history":[{"count":2,"href":"https:\/\/www.w3.org\/community\/miniapps\/wp-json\/wp\/v2\/posts\/35\/revisions"}],"predecessor-version":[{"id":90,"href":"https:\/\/www.w3.org\/community\/miniapps\/wp-json\/wp\/v2\/posts\/35\/revisions\/90"}],"wp:attachment":[{"href":"https:\/\/www.w3.org\/community\/miniapps\/wp-json\/wp\/v2\/media?parent=35"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.w3.org\/community\/miniapps\/wp-json\/wp\/v2\/categories?post=35"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.w3.org\/community\/miniapps\/wp-json\/wp\/v2\/tags?post=35"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}