Grow together

How to Contribute

1.View Documentation

With the release of the EdgeGallery community version, the community documentation will be updated accordingly:

Visit Documentation to view the latest version of the  document.

2.Download version

The EdgeGallery community releases a version every 3 months. After the version is released, the latest version of the installation package will be provided. Please visit the official website to download the latest version.

  • EdgeGallery supports both X86 and ARM architectures, please choose to download according to your needs;
  • There are three installation modes for each architecture, please download according to your needs:
  1. Edge:This mode is generally deployed at the remote end, close to the device; MEPM and MEP need to be deployed.
  2. Controller:The mode is generally deployed on the central side, requiring the deployment of APP store, developer and MECM.
  3. All:That is, the All-In-One mode we usually call, this mode is convenient for testing, in a single node, the central side and the edge side are deployed on the same virtual machine.

3.Experience Deployment

You can click Install and deploy to get the latest support method. You can also find the Readme file through the installer repository of the EdgeGallery community.


4.Read the Contributor Guide

It is recommended that you read the Contributor’s Guide before developers join the community. This guide introduces the community code of conduct, how to make contributions from easy to difficult, how to participate in existing working groups and community projects, and to lead the operating procedures of new projects and working groups.

4.1Study video case

You can also learn more about the EdgeGallery project by visiting the video case study.



5.Participate in Community Activities

5.1 Regular Community Meeting

The technical meetings of the community are all public. If you are interested in a certain technical group, you can join the regular community meeting of this group to feed back your thoughts and suggestions.

Community Project Team MEP MECM App&Dev Joint
Community Working Group  Architecture Intergration Test
   Security Blockchain User

Attachment: meeting timetable

5.2 Community Developer Salon

Every month, there will be community developer salons organized by community partners in the community. It has been carried out in Beijing, Xi’an, Nanjing, Guangzhou, Dongguan and other cities. Please follow our WeChat public account to get event information in time, and you can also visit the community Developer salon view event information.

5.3 Community Developer Summit & Hackathon

Every month, there will be community developer salons organized by community partners in the community. It has been carried out in Beijing, Xi’an, Nanjing, Guangzhou, Dongguan and other cities. Please follow our WeChat public account to get event information in time, and you can also visit the community Developer salon view event information.

6.Participate in Community Contributions

6.1 Submit Questions and Requirements

Questions and requirements are carried using Gitee’s Issue (task), and are distinguished by different types.

Classification Describe
Epic Initially required to submit
Story Minimum feature-level requirements that can be independently tested, decomposed by Epic
Task Minimal task decomposed from Story
Bug Problems or questions found
Test Test case
Vulne Vulnerability

For specific guidelines, please refer to: (the following two links are to be provided)

Submit a bug guide

Guidelines for submitting requirements

6.2 Submit code

Please refer to Submit PR (link to be provided)

6.3 Other contributions

In addition to questions, requirements and codes, you also have many ways to contribute to the community. For example, you can contribute applications to the community and enrich the AppStore; you can also contribute your valuable experience and form a case.

7.Get a Seat in the Community



The organizational structure of the community, except for the community board of directors and the secretariat, are all technical organizations. For the introduction of technical organizations and related roles, please refer to the technical charter of the community.

The members of the Community Technical Steering Committee (TSC) are composed of senior partner representatives and RM.

The community working group is composed of the working group chairman and group members, and the working group chairman is elected by the group members;

The community project team is composed of PTL, commuter, and contributor, and the three roles have certain promotion requirements, as shown in the following figure:

The following content is taken from the community technical charter. In case of conflict, the latest charter shall prevail:

Project Technical Leader

PTL is the de facto spokesperson for the project, and the PTL first needs to be the Committer of the project. PTL needs to be responsible for the normal progress of the project on a regular basis, including but not limited to regularly organizing regular project team meetings, communicating the progress of the project team in a timely manner, and participating in TSC meetings on behalf of the project. The first batch of project PTLs are designated, with a term of one year. After one year, all PTLs need to be qualified through public elections. The election mechanism of the project leader: If any of the following conditions is met, the technical director will be elected:

  • A new project is created;
  • The PTL of the existing project resigns;
  • It has been more than 1 year since the last PTL election for this project.


Each project has a group of Contributors, they have the right to submit the code to the library, Committer must be the Contributor of the project, and decide the design, code, patch and release of the project. The initial Committer of the project is specified when the project is created, and the rights of subsequent Committer are obtained through contributions to the community and community trust. If the project does not have an active Committer, TSC can appoint a temporary Committer from the active Contributor; Committer can retire by requesting resource resignation from the PTL publicly. For the destructive or long-term inactive Committer, the PTL or the Committer vote of the project (more than two-thirds) of the voting method is determined, and the PTL will notify the TSC of this information before it will take effect. Committer must be an active Contributor for at least one version of the time. The first batch of Committers will be designated for a one-year term. After one year, all Committers need to be eligible through public elections.


Everyone who contributes to the project is the Contributor of the project, and the contribution can be in the form of code, code review or other deliverables. Contributor owns the voting rights of the project. Contributor can be active in many ways (including but not limited to the following forms):

  • Create or participate in the review of PR, but do not have the right to merge
  • File or comment on issues
  • Participate in PG, WG or community discussions (open meetings, wiki comments, email exchanges, etc.)
  • The creation of documents or wiki content to promote the development of the EdgeGallery community. As long as you are willing to contribute, you can apply to join a specific project by yourself and start your official contribution after signing the CLA.