Introduction Materials and Useful Links
| Required Information | Responses (Please list N/A if not applicable) |
| Name of Project | Project EdgeGallery |
| Project Description (what it does, why it is valuable, origin and history) | The EdgeGallery community focuses on the MEC platform framework of the carrier network’s edge. It builds the basic framework of MEC edge resources, applications, security and management, and de facto standards of network openness services through open-source collaboration, and implements interconnection with the public cloud. A unified MEC application ecosystem is constructed based on compatibility with heterogeneous edge infrastructures. |
| Statement on alignment with Foundation Mission Statement | Project EdgeGallery is well-aligned with LF Edge's mission to foster industry collaboration, scale the adoption of edge computing and harmonize the MEC ecosystem. It enables MEC edge resources and applications, whilst providing both security and management capabilities. It also offers interconnectivity with the public cloud. The result is the creation of a unified MEC application ecosystem, which we believe is best for carriers' heterogeneous edge infrastructure. |
| High level assessment of project synergy with existing projects under LF Edge, including how the project compliments/overlaps with existing projects, and potential ways to harmonize over time. Responses may be included both here and/or in accompanying documentation. | EdgeGallery is highly complementary to existing LF Edge projects. It has connections with Akraino regarding integration BPs and API definitions. Its architecture absorbs EdgeX and could integrate Open Horizon, EVE into its MEP PaaS sub-system. In addition, the commercial deployment of EdgeGallery could help LF Edge Projects be more widely used in Carrier's networks. |
| Link to current Code of Conduct | We would adopt the LF Edge Code of Conduct |
| 2 TAC Sponsors, if identified (Sponsors help mentor projects) - See full definition on Project Stages: Definitions and Expectations | |
| Project license | Apache 2.0 |
| Source control (GitHub by default) | https://github.com/edgegallery |
| Issue tracker (GitHub by default) | https://github.com/edgegallery |
| External dependencies (including licenses) | Apache 2.0 License https://github.com/EdgeGallery/community/tree/master/Test%20WG/Test%20Release/3rdparty%20dependencies%20Licenses |
| Release methodology and mechanics | New Release will be published every 3 months |
| Names of initial committers, if different from those submitting proposal | |
| Current number of code contributors to proposed project | |
| Current number of organizations contributing to proposed project | |
| Briefly describe the project's leadership team and decision-making process | EdgeGallery community is organized similarly to any LF project. It has Board, TSC, secretariat, working group, and projects. Board and TSC do the decisions, as others focusing on technical tasks. |
| List of project's official communication channels (slack, irc, mailing lists) | |
| Link to project's website | https://www.edgegallery.org/ |
| Links to social media accounts | https://space.bilibili.com/526590956 |
| Existing financial sponsorship | Currently being funded by community members |
| Infrastructure needs or requests (to include GitHub/Gerrit, CI/CD, Jenkins, Nexus, JIRA, other ...) | Github+Jenkins integration for CI/CD, part-time consulting role from LF would be helpful. |
| Currently Supported Architecture | Linux (x86/64, ARM) |
| Planned Architecture Support | Linux (x86/64, ARM) |
| Project logo in svg format (see https://github.com/lf-edge/lfedge-landscape#logos for guidelines) |
|
| Trademark status | Already applied |
| Does the project have a Core Infrastructure Initiative security best practices badge? (See: https://bestpractices.coreinfrastructure.org) | Not yet |
| Any additional information the TAC and Board should take into consideration when reviewing your proposal? |
