...
https://docs.google.com/presentation/d/1mnMpxQvUofmwayh0Gixfne7pWKrq27nRNM_kTyazT4c/edit?usp=sharing
Meetings
Date: every Monday Pacific, every Tuesday Beijing
Time: 8pm Pacific, 11am Beijing, summer time
Location: https://armltd.zoom.us/j/96365095099?pwd=aStFZWNDdXQ5bUhDbUY1UUJOVTF2UT09&from=addon
Required Information | Responses (Please list N/A if not applicable) |
Name of Project | AI Edge |
Project Description (what it does, why it is valuable, origin and history) | AI Edge is a project that integrates AI and IoT on the edge, enabling real-time decision making and analytics. This technology extends the advantages of AI and Machine Learning to edge devices, thus aligning with the LF Edge Mission Statement. This technology can enhance applications in various sectors including manufacturing, telecommunications, healthcare, automotive (autonomous driving and smart cockpit), and retail. AI Edge originated as part of the AI Edge Blueprint Family (https://wiki.akraino.org/display/AK/The+AI+Edge+Blueprint+Family) and is based on the Shifu Framework (https://github.com/Edgenesis/shifu).
|
Statement on alignment with Foundation Mission Statement | AI Edge aligns with the LF Edge Mission Statement by creating an open, scalable, and interoperable framework for edge computing. This project embodies LF Edge's vision for edge applications by extending AI and Machine Learning benefits to edge devices. |
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. | AI Edge enhances the overall LF Edge ecosystem by providing an AI/ML interface for edge devices. It does not overlap significantly with existing projects but brings unique capabilities to the table. Harmonization potential exists with IoT and edge computing-focused projects. |
Link to current Code of Conduct | N/A |
2 TAC Sponsors, if identified (Sponsors help mentor projects) - See full definition on Project Stages: Definitions and Expectations | N/A |
Project license | Apache 2.0 |
Source control (GitHub by default) | GitHub |
Issue tracker (GitHub by default) | GitHub |
External dependencies (including licenses) |
|
Release methodology and mechanics | |
Names of initial committers, if different from those submitting proposal | Liya Yu, Baidu Yu, Liya C.C., Allegro fanweixiao Jun Chen, Baidu Jun Chen Tom Qin, Edgenesis Tom Qin Yongli Chen, Edgenesis Kevin Zheng, Edgenesis Wenhui Zhang, Bytedance/TikTok Wenhui Zhang Joe Speed, Ampere Ray Chi, Advantech Roger Chen, SuperMicro |
Current number of code contributors to proposed project | 6 |
Current number of organizations contributing to proposed project | 4 (Baidu, Allegro, Edgenesis, TikTok) |
Briefly describe the project's leadership team and decision-making process | |
Advisors | Ranny Haiby Tina Tsou |
List of project's official communication channels (slack, irc, mailing lists) | N/A |
Link to project's website | N/A |
Links to social media accounts | N/A |
Existing financial sponsorship | N/A |
Infrastructure needs or requests (to include GitHub/Gerrit, CI/CD, Jenkins, Nexus, JIRA, other ...) | GitHub |
Currently Supported Architecture | x86-64, AArch64 |
Planned Architecture Support | N/A |
Project logo in svg format (see https://github.com/lf-edge/lfedge-landscape#logos for guidelines) | N/A |
Trademark status | N/A |
Does the project have a Core Infrastructure Initiative security best practices badge? (See: https://bestpractices.coreinfrastructure.org) | No |
Any additional information the TAC and Board should take into consideration when reviewing your proposal? | N/A |
...