diff --git a/charter/charter.md b/charter/charter.md index 641c220ba770f9c9b8edd086e86283fee7ce88d5..588b128fee97b5c24b2f2fcea827b5dbc5ff7ba0 100644 --- a/charter/charter.md +++ b/charter/charter.md @@ -1,4 +1,5 @@ -# Quick App Initiative – Charter +# MiniApp Initiative – Charter +## (replaces the Quick App Initiative charter) [PDF version of the Charter](https://quick-app-initiative.ow2.io/docs/charter.pdf) @@ -9,21 +10,21 @@ | Initiative Name | Initiative Name | | --------------- | --------------- | -| OW2 Quick App Initiative | QAI | +| OW2 MiniApp Initiative | MAI | ### Initiative Point of Contact | Data | Value | | ---- | ----- | | First Name, Last Name | Christian, PATERSON | -| Organization | EU-SID CBG, Huawei Europe | +| On behalf of | EU-SID CBG, Huawei Europe | | Telephone | 00 33 (0)6 70 03 03 47 | -| E-mail address | christian.paterson.ext@huawei.com | -| Remarks | Christian Paterson is an external consultant assisting Huawei. | +| E-Mail address | christian.paterson.ext@huawei.com | +| Remarks | Christian Paterson is founder of [Open Up](https://www.openup-consulting.eu/). He is assistaing Huawei as an external consultant. | ### Quick Description -This initiative will focus on Quick Apps, a new platform to build and interact using a new paradigm of light hybrid applications. These apps do not require installation and enable quick and easy access. +This initiative will focus on MiniApps, a new paradigm for containerized, lightweight hybrid applications being fostered within the World Wide Web Consortium (W3C). As a concept, MiniApps may be realised using different implementation approaches, for example Quick Apps or Mini Programs, and use new technologies such as ArkTS. MiniApps do not typically require installation on a host device, and benefit from small download sizes. These characteristics enable users to quickly and easy launch MiniApps in the same way that they might launch a "Web App". ## Initiative Purpose @@ -32,68 +33,77 @@ This initiative will focus on Quick Apps, a new platform to build and interact u There exist several technologies for developing mobile device application experiences for end-users, and these can be broadly classed under 3 categories: -- **Web Apps**. Applications that run on web browsers, including the classic web applications, Progressive Web Applications (PWA) and other non-standard packaging formats such as kaiOS Apps and Fire OS Web Apps. -- **Native Apps**. Applications that run natively on operating systems. These can be developed using platform-specific SDKs, including the official SDKs, and cross-platform SDKs, enabling developers to release various versions for different operating systems using the same code. -- **Hybrid Applications**. Native applications that takes elements of the above types of apps, using specific system features and relying on an internal Web View engine to deliver content and interact with the user. +- **Web Apps**. Applications that run *within* web browsers, including the classic web applications, Progressive Web Applications (PWA) and other non-standard packaging formats such as kaiOS Apps and Fire OS Web Apps. +- **Native Apps**. Applications that run natively *on* operating systems. These can be developed using platform-specific SDKs, including the official SDKs, and cross-platform SDKs, enabling developers to release various versions for different operating systems using the same code. +- **Hybrid Applications**. Native applications that take elements from the above, add specific system features, and use an *internal* web engine (for example Blink or WebKit) to deliver content and interact with users. + +**This initiative will focus on MiniApps**, a new approach to building lightweight hybrid applications. MiniApps as a concept was born out of a desire to harmonize efforts on Quick Apps, with efforts focused on MiniPrograms, and to bring these unique approaches to a wider audience. + +- **Quick Apps**. Hybrid lightweight applications that run as standalone apps on a device. They are containerised/supported using a Quick App engine that sits above the OS. +- **Mini Programs**. Hybrid lightweight applications that run within a "Super App" (the container). So called "Super Apps" are typically native apps. + +#### A quick look at Quick Apps + +In 2018, a group of ten Chinese device makers (Huawei, Gionee, Lenovo, Meizu, Nubia, OnePlus, Oppo, Vivo, Xiaomi, and ZTE) launched the [Quick App Alliance](https://www.quickapp.cn/), a forum to develop Quick Apps as a new platform of Android light applications. The Quick App Alliance has developed technology, documentation, IDEs and tools for developers, albeit targeted at the Chinese market rather than the international one. The Quick App Alliance continues to evolve the Quick App platform whilst also providing support to companies and individuals that want to adopt this technology. + +In 2019, some of the MiniApp Alliance members, along with other light app vendors like Alibaba, Baidu, and Google, launched the World Wide Web Consortium (W3C) [MiniApp Ecosystem Community Group](https://www.w3.org/community/miniapps/), exploring a new homogeneous specification for this new paradigm of light applications. One year later, the W3C MiniApp Ecosystem Community Group proposed creating a working group to define the MiniApp Standard as a universal solution to develop light apps. In January 2021, the [W3C MiniApps Working Group](https://www.w3.org/2021/miniapps/) [was created](https://www.w3.org/blog/2021/01/w3c-launches-the-miniapps-working-group/) by consensus, with the support of the leading technology companies, including Apple, Google, Microsoft, Mozilla and the W3C staff. -**This initiative will focus on Quick Apps**, a new platform to build and interact using a new paradigm of light hybrid applications. These apps do not require installation and enable quick and easy access. +Quick Apps are a concrete implementation of the abstract [MiniApp](https://www.w3.org/TR/mini-app-white-paper/#what-is-miniapp) Standard, allowing light applications in native environments for smart devices. -In 2018, a group of ten Chinese device makers (Huawei, Gionee, Lenovo, Meizu, Nubia, OnePlus, Oppo, Vivo, Xiaomi, and ZTE) launched the [Quick App Alliance](https://www.quickapp.cn/), a forum to develop Quick Apps as a new platform of light applications for Android. The Quick App Alliance has developed technology, documentation, IDEs and tools for developers, albeit targeted at the Chinese market. The Quick App Alliance also provides support to companies and individuals that want to adopt this technology. +#### Why the move from Quick App to Mini App OW2 initiative? -In 2019, some of the Quick App Alliance members, along with other light app vendors like Alibaba, Baidu, and Google, launched the World Wide Web Consortium (W3C) [MiniApp Ecosystem Community Group](https://www.w3.org/community/miniapps/), exploring a new homogeneous specification for this new paradigm of light applications. One year later, the W3C MiniApp Ecosystem Community Group proposed creating a working group to define the MiniApp Standard as a universal solution to develop light apps. In January 2021, the [W3C MiniApps Working Group](https://www.w3.org/2021/miniapps/) [was created](https://www.w3.org/blog/2021/01/w3c-launches-the-miniapps-working-group/) by consensus, with the support of the leading technology companies, including Apple, Google, Microsoft, Mozilla and the W3C staff. -Quick Apps is a concrete implementation of the abstract [MiniApp](https://www.w3.org/TR/mini-app-white-paper/#what-is-miniapp) Standard, allowing light applications in native environments for smart devices. ### Opportunity -[MiniApp technology](https://www.w3.org/TR/mini-app-white-paper/#what-is-miniapp) is based on the front-end Web technology stack (i.e., CSS, JavaScript and Web APIs), yet offers advanced access to device features and supporting native rendering. Quick App is a way to develop, package and distribute MiniApp compliant applications across platforms, facilitating the process of development through advanced UI components and predefined native APIs (e.g., push notifications, network monitoring, Bluetooth, or camera) that enable developers to design and build usable, reliable and efficient applications rapidly. +[MiniApp technology](https://www.w3.org/TR/mini-app-white-paper/#what-is-miniapp) is based on the front-end Web technology stack (i.e., CSS, JavaScript and Web APIs), yet offers advanced access to device features and supporting native rendering. MiniApp is a way to develop, package and distribute MiniApp compliant applications across platforms, facilitating the process of development through advanced UI components and predefined native APIs (e.g., push notifications, network monitoring, Bluetooth, or camera) that enable developers to design and build usable, reliable and efficient applications rapidly. -Quick Apps are coded using HTML-like markup language, CSS and JavaScript. +MiniApps are coded using HTML-like markup language, CSS and JavaScript. -When compared to a native Android app, and looking at equivalent functions, Quick Apps require 20% less lines of code – easier for the developer, lighter on download infrastructures, less impact on device storage. The conversion of HTML5 apps into Quick Apps is straightforward and can be done in a short time. +When compared to a native Android app, and looking at equivalent functions, MiniApps require 20% less lines of code – easier for the developer, lighter on download infrastructures, less impact on device storage. The conversion of HTML5 apps into MiniApps is straightforward and can be done in a short time. -Equally, the process of updating and maintaining Quick Apps is more straightforward than for native apps. Developers may update Quick Apps and deliver new versions to the end-users in a transparent way. +Equally, the process of updating and QAIntaining MiniApps is more straightforward than for native apps. Developers may update MiniApps and deliver new versions to the end-users in a transparent way. -Following the MiniApp Standard, Quick App supports multi-channel distribution, using deep links, marketplaces, web-links, and specific device assistants, maximizing discoverability and app exposure opportunities. Thus, this technology enables app providers to perform innovative marketing activities to promote their services and products. +Following the MiniApp Standard, MiniApp supports multi-channel distribution, using deep links, marketplaces, web-links, and specific device assistants, maximizing discoverability and app exposure opportunities. Thus, this technology enables app providers to perform innovative marketing activities to promote their services and products. This initiative will be driven by a multidisciplinary group of experts from different organizations and different countries. It will cover a wide range of industries and topics, fostering innovation and entrepreneurship, preserving core values such as sustainability, resilience, user privacy, and ethical use of the technology. #### Objectives -The main objectives of the Quick App Initiative are the following: +The QAIn objectives of the MiniApp Initiative are the following: - **Create an open community**: Any organization or individual may participate in the activities, and become a member of the initiative, according to participation rules (see [Participation section](#code-of-activity)); - **Multi-stakeholder community**: Public and private organizations, academia, and individuals are invited to enrich the community ecosystem; -- **Vendor-neutral oriented**: The initiative will be focused on developing tools, documentation, training, use cases, code examples and awareness raising about Quick Apps as a technology from a vendor-neutral perspective. This regardless of any individual or collective business activities that may be performed by the participants within or without the scope of the initiative; -- **Not-for-profit association**: The Quick App Initiative is established as not-for-profit. However, members may be invited to (co)fund and (co)sponsor activities like events, materials, tools development and test-beds where appropriate; +- **Vendor-neutral oriented**: The initiative will be focused on developing tools, documentation, training, use cases, code examples and awareness raising about MiniApps as a technology from a vendor-neutral perspective. This regardless of any individual or collective business activities that may be performed by the participants within or without the scope of the initiative; +- **Not-for-profit association**: The MiniApp Initiative is established as not-for-profit. However, members may be invited to (co)fund and (co)sponsor activities like events, materials, tools development and test-beds where appropriate; - **Transparent and driven by group’s consensus**: Resolutions of the group and the activities will be based on consensus under the principles of openness and transparency (see [Decision Policy section](#decision-policy)); -- **Topic-oriented work**: Quick App Initiative participants may propose specific Working Groups or [Task Forces](#task-forces) to better enable focused collaboration around a specific need or objective. Any new action must be approved by the initiative’s [Steering Committee](#steering-committee) and comply with OW2 policies; +- **Topic-oriented work**: MiniApp Initiative participants may propose specific Working Groups or [Task Forces](#task-forces) to better enable focused collaboration around a specific need or objective. Any new action must be approved by the initiative’s [Steering Committee](#steering-committee) and comply with OW2 policies; - **Open Source advocate**: The initiative is committed to the Open Source paradigm, fostering the production and release of Free Libre and Open Source code (OSI or FSF approved license), open documentation and open data (Creative Commons). -The initiative may explore vertical applications where Quick Apps have the potential to be part of a solution, and transversal activities to further core technologies that apply across verticals, including (as appropriate) usability, accessibility, sustainability, privacy, security and **ethical standards**. +The initiative may explore vertical applications where MiniApps have the potential to be part of a solution, and transversal activities to further core technologies that apply across verticals, including (as appropriate) usability, accessibility, sustainability, privacy, security and **ethical standards**. #### Participants -The Quick App Initiative is expected to have a wide variety of participants, opening the participation to any interested organization or individual, including, but not limited to: +The MiniApp Initiative is expected to have a wide variety of participants, opening the participation to any interested organization or individual, including, but not limited to: - Any organization or individual regardless of geographic location; -- Operating system and device vendors that implement Quick App engines, marketplaces and other supporting tools for Quick Apps; -- Content and service providers interested in end-user interactions using Quick Apps; -- Marketing experts interested in the promotion of Quick Apps as a paradigm; +- Operating system and device vendors that implement MiniApp engines, marketplaces and other supporting tools for MiniApps; +- Content and service providers interested in end-user interactions using MiniApps; +- Marketing experts interested in the promotion of MiniApps as a paradigm; - Developers, including professionals, hobbyists and students, interested in Web and native app technologies; - Public institutions, including municipalities, with specific needs such as accessible services for citizens and visitors; - Research centers and academic institutions interested in innovation through agile technologies; - Innovative entrepreneurs and SMEs. -All the participants in the Quick App Initiative agree to be bound by this charter and are required to follow the OW2 governing laws and policies, not least the [OW2 Code of Conduct](https://www.ow2.org/view/Membership_Joining/Code_of_Conduct). +All the participants in the MiniApp Initiative agree to be bound by this charter and are required to follow the OW2 governing laws and policies, not least the [OW2 Code of Conduct](https://www.ow2.org/view/Membership_Joining/Code_of_Conduct). -Initiative participants may contribute to any [Task Force](#task-forces) or Project created under the Quick App Initiative, and they have no obligation to commit resources. Still, only the active participants will be able to have a representative in the [Steering Committee](#steering-committee) . +Initiative participants may contribute to any [Task Force](#task-forces) or Project created under the MiniApp Initiative, and they have no obligation to commit resources. Still, only the active participants will be able to have a representative in the [Steering Committee](#steering-committee) . ### Alignment -The Quick App Initiative aims to be a neutral forum for advancing Quick Apps, as a concrete implementation of the W3C [MiniApp](https://www.w3.org/TR/mini-app-white-paper/#what-is-miniapp) Standard. The initiative’s activities will be driven by real-world challenges, developer needs and business opportunities that maximize the technology's promotion and uptake. +The MiniApp Initiative aims to be a neutral forum for advancing MiniApps, as a concrete implementation of the W3C [MiniApp](https://www.w3.org/TR/mini-app-white-paper/#what-is-miniapp) Standard. The initiative’s activities will be driven by real-world challenges, developer needs and business opportunities that maximize the technology's promotion and uptake. -The Quick App Initiative will be a place to foster awareness, develop documentation and use cases, collaborate on tooling and coordinate grassroots activities in support of a Quick App implementation of the W3C MiniApp Standard. It will enable the active collaboration of different stakeholders, from device vendors to app/content providers, within a neutral, Open Source based structure. +The MiniApp Initiative will be a place to foster awareness, develop documentation and use cases, collaborate on tooling and coordinate grassroots activities in support of a MiniApp implementation of the W3C MiniApp Standard. It will enable the active collaboration of different stakeholders, from device vendors to app/content providers, within a neutral, Open Source based structure. The initiative will embrace the ideals of Open Source transparency, meritocracy and respectful global collaboration. @@ -106,22 +116,22 @@ Financial sponsorship of the initiative and/or significant provision of person t ### Initiative Leadership Organization Justification -Huawei Member of the W3C MiniApp standard working group and active promoter of Quick Apps +Huawei Member of the W3C MiniApp standard working group and active promoter of MiniApps | ORGANIZATION | JUSTIFICATION | | ------------ | ------------- | -| Huawei | Member of the W3C MiniApp standard working group and active promoter of Quick Apps | +| Huawei | Member of the W3C MiniApp standard working group and active promoter of MiniApps | ### Initiative Participants | ORGANIZATION | CONTRIBUTION AND BENEFITS | | ------------ | ------------------------- | -| CTIC | Research and innovation center working on smart territories, active aging and well-being, and industrial digital transformation, interested in exploring new Quick App use. +| CTIC | Research and innovation center working on smart territories, active aging and well-being, and industrial digital transformation, interested in exploring new MiniApp use. | European Alliance for Technology Development (Alliance Tech) | Association that offers a co-creation framework for investors, entrepreneurs, private and public sector leaders, academia and R&D centers, developing uses cases. | -| Famobi GmbH | Pioneer in the H5 gaming industry, using the newest cross-platform technology to bring native app-quality to the web. The company has been working with Quick Apps since 2019. | -| FRVR | Successful games development company actively using Quick Apps as a means to distribute applications. | -| RSI | A new foundation in the process of being launched out of Switzerland to promote sustainability. RSI is interested in leveraging Quick Apps to enable sustainability in domains such as apparel and footwear. | -| Santillana Group | Leading company that transformed education in Latin America and Spain through innovative platforms and digital content. Interested in exploring the Quick App paradigm as a new concept to deliver content to students. | +| Famobi GmbH | Pioneer in the H5 gaming industry, using the newest cross-platform technology to bring native app-quality to the web. The company has been working with MiniApps since 2019. | +| FRVR | Successful games development company actively using MiniApps as a means to distribute applications. | +| RSI | A new foundation in the process of being launched out of Switzerland to promote sustainability. RSI is interested in leveraging MiniApps to enable sustainability in doQAIns such as apparel and footwear. | +| Santillana Group | Leading company that transformed education in Latin America and Spain through innovative platforms and digital content. Interested in exploring the MiniApp paradigm as a new concept to deliver content to students. | ### Initiative Prospective Participants @@ -136,14 +146,14 @@ Huawei Member of the W3C MiniApp standard working group and active promoter of Q | First Name, Last Name | Christian, PATERSON | | Organization | EU-SID CBG, Huawei Europe | | Telephone | 00 33 (0)6 70 03 03 47 | -| E-mail address | christian.paterson.ext@huawei.com | +| E-QAIl address | christian.paterson.ext@huawei.com | | Justification | Respected Open Source actor, previous OW2 board member. | ### Management Team members -| First, Last Name | e-mail | Organization | Management team role | +| First, Last Name | e-QAIl | Organization | Management team role | | ---------------- | ------ | ------------ | -------------------- | -| Martin, Alvarez Espinar | martin.alvarez.espinar@huawei.com | Huawei Europe | MiniApp W3C liaison + Quick App expert | +| Martin, Alvarez Espinar | martin.alvarez.espinar@huawei.com | Huawei Europe | MiniApp W3C liaison + MiniApp expert | | Alejandro Montarroso | amontarroso@santillana.com | Santillana Group | Educational out-reach coordinator | ## Initiative Scope @@ -153,7 +163,7 @@ Huawei Member of the W3C MiniApp standard working group and active promoter of Q | OW2 Project | Justification | | ----------- | ------------- | | | No existing OW2 project foreseen to be involved in the initiative at this stage | -| Quick App Tooling | A project submission to the OW2 code base is envisaged. | +| MiniApp Tooling | A project submission to the OW2 code base is envisaged. | ### Non-OW2 Projects | Other Projects | Project Affiliation | Organization | Justification | @@ -162,7 +172,7 @@ Huawei Member of the W3C MiniApp standard working group and active promoter of Q ### Initiative Deliverable -The Quick App Initiative structures its activities in thematic [Task Forces](#task-forces). Each [Task Force](#task-forces) may address horizontal topics such as outreach and promotion, but also vertical joint [Projects](#initiative-projects). Project outputs depend on the specific requirements and needs of the [Task Force](#task-forces) and its participants. +The MiniApp Initiative structures its activities in thematic [Task Forces](#task-forces). Each [Task Force](#task-forces) may address horizontal topics such as outreach and promotion, but also vertical joint [Projects](#initiative-projects). Project outputs depend on the specific requirements and needs of the [Task Force](#task-forces) and its participants. [Task Forces](#task-forces) must be described in a specific space in the online workspace, which also can be used to store or link documents, software code, or other deliverables produced during the [Task Force](#task-forces) activities. @@ -172,17 +182,17 @@ Examples of the expected outcomes are, but not limited to: - Technical documentation and reference materials for developers, including code samples, articles, and technical documents; - Methodologies and practical recommendations for marketing and development; - Best practices on usability and accessibility for specific audiences (e.g., general consumers, elderly, rural citizens, vehicle drivers, etc.); -- Samples and source code to enable third-parties to develop, implement and support Quick Apps; +- Samples and source code to enable third-parties to develop, implement and support MiniApps; - Networking opportunities for stakeholders; -- Technical documents with feedback to standardization bodies, including W3C and Quick App Alliance (i.e., new features, accessibility, multilingual, efficiency, etc.); +- Technical documents with feedback to standardization bodies, including W3C and MiniApp Alliance (i.e., new features, accessibility, multilingual, efficiency, etc.); - Presentations for promotional and technical events; - Press releases, position papers, and journal articles; ### Standards -The [World Wide Web Consortium (W3C)](https://www.w3.org) hosts the [W3C MiniApps Working Group](https://www.w3.org/2021/miniapps/) aiming at harmonizing the heterogeneous MiniApp ecosystem, including platforms like Alipay Mini Apps, Baidu Smart Programs, and Quick Apps. This working group develops specifications and recommendations for enabling interoperability among the different MiniApp platforms, maximizing the convergence of MiniApps and the World Wide Web, reducing the development costs and facilitating the adoption of this technology. +The [World Wide Web Consortium (W3C)](https://www.w3.org) hosts the [W3C MiniApps Working Group](https://www.w3.org/2021/miniapps/) aiming at harmonizing the heterogeneous MiniApp ecosystem, including platforms like Alipay MiniApps, Baidu Smart Programs, and MiniApps. This working group develops specifications and recommendations for enabling interoperability among the different MiniApp platforms, maximizing the convergence of MiniApps and the World Wide Web, reducing the development costs and facilitating the adoption of this technology. -The Quick App Initiative will align with the standards defined by the W3C MiniApps Working. +The MiniApp Initiative will align with the standards defined by the W3C MiniApps Working. ## Initiative Outlook @@ -198,17 +208,17 @@ The Quick App Initiative will align with the standards defined by the W3C MiniAp | ----- | ----------- | | Formal acceptance of initiative creation and this charter by OW2 | During the month of June 2021 | | Public launch | At OW2con’2021 | -| White paper | Publication of a white paper explaining Quick Apps and the initiative. The aim is to time this with the initiative launch. | +| White paper | Publication of a white paper explaining MiniApps and the initiative. The aim is to time this with the initiative launch. | | Start of 1st [Task Forces](#task-forces) | The initiative will organize deliverables around [Task Forces](#task-forces) (work groups). It is aimed that initial [Task Forces](#task-forces) and their respective rapporteurs/animators will be setup before the summer recess. | ## Constraints ### Key Efforts -The main areas of perceived work are: +The QAIn areas of perceived work are: - Awareness raising within both developer and business communities. -- Exploration and enrichment of Quick App use cases. +- Exploration and enrichment of MiniApp use cases. - Creation of technical documentation adapted to western developers. - Creation of support tools adapted to western developers. - Coordination with the W3C MiniApp working group. @@ -217,17 +227,17 @@ The main areas of perceived work are: There are several identified risks: -- Quick Apps as both a technology and paradigm are not widely known outside of Asia. -- Little Quick App documentation exists in English. -- Tooling (include IDEs) is mainly in Chinese, or not vendor neutral. -- Currently only Xiaomi and Huawei have native Quick App support. Gaining traction with other vendors will be important. -- There exist other technologies that are similar (but not the same) as Quick Apps. Notably PWA. +- MiniApps as both a technology and paradigm are not widely known outside of Asia. +- Little MiniApp documentation exists in English. +- Tooling (include IDEs) is QAInly in Chinese, or not vendor neutral. +- Currently only Xiaomi and Huawei have native MiniApp support. Gaining traction with other vendors will be important. +- There exist other technologies that are similar (but not the same) as MiniApps. Notably PWA. ## IPR Policy ### Business Rationale -The Quick App Initiative aims at facilitating the broadest distribution and use of its outcomes. Deliverables (documents, code) produced by the initiative should be licensed under the following: +The MiniApp Initiative aims at facilitating the broadest distribution and use of its outcomes. Deliverables (documents, code) produced by the initiative should be licensed under the following: - Software source code: Any OSI approved license (Apache 2.0 is the preference). - Documentation: A creative commons license (CC-BY 4.0 is the preference) @@ -236,9 +246,9 @@ During the process to create a new [Task Force](#task-forces), the [Task Force]( Such communication can be made through the initiative’s GitLab collaboration space. -Public Quick App Initiative code and document repositories must contain an explicit LICENSE file with information about the license by default. +Public MiniApp Initiative code and document repositories must contain an explicit LICENSE file with information about the license by default. -Neither the initiative, nor OW2, seek ownership of project related trademarks. These will remain the property of the relevant parties. In the event that a trademark is donated to the initiative, or the initiative seeks to create a trademark, this will be organized through OW2 in discussion with the [Steering Committee](#steering-committee) and any other relevant party. +Neither the initiative, nor OW2, seek ownership of project related trademarks. These will reQAIn the property of the relevant parties. In the event that a trademark is donated to the initiative, or the initiative seeks to create a trademark, this will be organized through OW2 in discussion with the [Steering Committee](#steering-committee) and any other relevant party. It is the responsibility of each participant to respect Third party IPR and copyright to the full extent of their knowledge and capacity. The initiative will not be held liable in any way for any copyright or IP infringement. @@ -252,13 +262,13 @@ Each contributor will be requested to provide a signed [Developer Certificate of ### Trademarks -The name “OW2 Quick App initiative” will remain a trademark of OW2. All other names will remain trademarks of their respective holders. +The name “OW2 MiniApp initiative” will reQAIn a trademark of OW2. All other names will reQAIn trademarks of their respective holders. ## Code of activity ### Steering Committee -The Quick App Initiative Steering Committee is the governing body responsible for the strategic decisions of the initiative. The role of the Steering Committee covers activities such as: +The MiniApp Initiative Steering Committee is the governing body responsible for the strategic decisions of the initiative. The role of the Steering Committee covers activities such as: - Decisions about the creation or ending of [Task Forces](#task-forces). - Decisions about the use of copyright licenses that deviate from the list described in [section 7](#ipr-policy). @@ -300,7 +310,7 @@ Activities of the initiative (e.g., outreach and promotion, test-beds, standardi All Task Forces must be submitted for prior validation and approval by the [Steering Committee](#steering-committee). -Participants of the Quick App Initiative may propose Task Forces to address specific needs. Task Forces are organizational structures that deliver concrete results within a set scope and/or time-frame. A Task Force often, but not always, encapsulates one or more [Projects](#initiative-projects). +Participants of the MiniApp Initiative may propose Task Forces to address specific needs. Task Forces are organizational structures that deliver concrete results within a set scope and/or time-frame. A Task Force often, but not always, encapsulates one or more [Projects](#initiative-projects). New proposals will be discussed during [Steering Committee](#steering-committee) meetings. They will be submitted at least ten calendar days before the next [Steering Committee](#steering-committee) meeting. Submission should be made using the initiative’s GitLab collaboration space where a Task Force Proposal Template will be made available. @@ -347,11 +357,11 @@ Extraordinary coordination meetings may be made based on participants’ request [Task Forces](#task-forces) may propose their calendar of meetings and organize the work according to their needs and expectations. Most of meetings will focus on discussing particular needs and will be conducted on an as-needed basis. -Task Force Representatives will be responsible for scheduling the meetings, conducting them, delivering notes, and the main action points after the discussion. +Task Force Representatives will be responsible for scheduling the meetings, conducting them, delivering notes, and the QAIn action points after the discussion. ### Communication -Participation to the Quick App Initiative is not subject to non-disclosure agreement (NDA). +Participation to the MiniApp Initiative is not subject to non-disclosure agreement (NDA). Minutes will be produced after any official meeting (Steering Committee, [Task Forces](#task-forces), and Projects), reflecting key points, issues and actions raised during the session. To increase openness of discussion, meetings will generally be conducted using the Chatham House Rule. The following provisions are made: @@ -368,17 +378,17 @@ Information about the different [Task Forces](#task-forces) (including details a As mentioned in [section 8.9](#collaborative-financing) of this charter, matters relating to finance spending will be made public. -The group will use a participant-only mailing list. +The group will use a participant-only QAIling list. ### Decision Policy -The Quick App Initiative will seek to make decisions through consensus. Typically, the chairperson or any participant makes an initial proposal, which is then reviewed and refined. Consensus emerges when there are no strong rejections against the proposal. +The MiniApp Initiative will seek to make decisions through consensus. Typically, the chairperson or any participant makes an initial proposal, which is then reviewed and refined. Consensus emerges when there are no strong rejections against the proposal. #### Consensus Any resolution taken in a face-to-face meeting or teleconference will be considered provisional to afford asynchronous decisions and organizational deliberation. -A call for consensus will be issued for all resolutions (via email, GitHub issue, or web-based survey), with a response period of at least one week. If no objections are raised by the end of the response period, the resolution will be considered to have reached a consensus as to the resolution of the concrete issue. +A call for consensus will be issued for all resolutions (via eQAIl, GitHub issue, or web-based survey), with a response period of at least one week. If no objections are raised by the end of the response period, the resolution will be considered to have reached a consensus as to the resolution of the concrete issue. #### Formal Votes @@ -402,7 +412,7 @@ The following decision mechanism will be applied: ### Public Visibility -The initiative aims to foster and grow public visibility of the Quick App technology through a variety of channels such as events, sponsorship, press-releases, white-papers, articles and social media. +The initiative aims to foster and grow public visibility of the MiniApp technology through a variety of channels such as events, sponsorship, press-releases, white-papers, articles and social media. The initiative is Open Source and as such participants are always public knowledge. @@ -421,7 +431,7 @@ At the discretion of the Initiative [Steering Committee](#steering-committee) ( - Develop Initiative marketing materials and carry out Initiative communication actions. - Provide bursaries or grants through independent organizations such as Start-Up Hubs, Competitively Poles and education establishments. - Co-finance expert assistance and necessary resourcing to the Initiative itself (PMO, out-reach “ambassador(s)”…) -- Organize and support (within reason) local non-profit Quick App developer “clubs”. +- Organize and support (within reason) local non-profit MiniApp developer “clubs”. Equally, initiative participants and/or interested other parties may at any time voluntarily provide funding into the Initiative’s fund pool. @@ -433,7 +443,7 @@ All funding actions (spend) will always be made public. Any and all funds will be managed uniquely through the OW2 management office. This includes reception and payment of funds. -In the event of closure/dissolution of the initiative, any and all remaining funds will revert to OW2 for use at its sole discretion. +In the event of closure/dissolution of the initiative, any and all reQAIning funds will revert to OW2 for use at its sole discretion. **No participant (individual or organization) will be held responsible in any way for fund management. Legal and fiduciary oversight of finances and funding will be the sole responsibility of OW2.**