...
Stage 1 Criteria (from the PLD) | Meets / Needs Improvement / Missing / Not Applicable | Supporting Data (if needed, include links to specific examples) |
|---|---|---|
2 TAC Sponsors, if identified (Sponsors help mentor projects) - See full definition on Project Stages: Definitions and Expectations | Meets | Joe Pearson (IBM), Brad Corrion (IOTech) |
The typical IP Policy for Projects under the LF Edge Foundation is Apache 2.0 for Code Contributions, Developer Certificate of Origin (DCO) for new inbound contributions, and Creative Commons Attribution 4.0 International License for Documentation. Projects under outside licenses may still submit for consideration, subject to review/approval of the TAC and Board. |
|
|
Upon acceptance, At Large projects must list their status prominently on website/readme | Meets | Displayed proudly on EdgeX wiki:  … and on the EdgeX website:  |
...
Stage 2 Criteria (from the PLD) | Meets / Needs Improvement / Missing / Not Applicable | Supporting Data (if needed, include links to specific examples) |
|---|---|---|
Demonstrate regular project leadership (typically TSC) meetings. Project leadership should meet monthly at a minimum unless there are extenuating circumstances (ex: holiday period) | Meets | TSC meetings are held bi-weekly. All information and recordings are held on the wiki pages here: https://lf-edgexfoundry.atlassian.net/wiki/spaces/FA/pages/11667441/Technical+Steering+Committee+TSC |
Development of a growth plan (to include both roadmap of projected feature sets as well as overall community growth/project maturity), to be done in conjunction with their project mentor(s) at the TAC. | Meets |
|
Document that it is being used in POCs. | Meets | EdgeX is used in countless POCs worldwide so this list is actually more about production uses.
|
Demonstrate a substantial ongoing flow of commits and merged contributions. | Meets | Collected from LF Insights for the project since inception and for the last 12 months:   |
Demonstrate that the current level of community participation is sufficient to meet the goals outlined in the growth plan. | Meets | 13 successful project releases since April 2017 (usually 2 each year)
On track for two more releases in the next year: Odessa, likely version 4.0 at end of 2024, and Palau 4.2 half way through 2025. |
Demonstrate a willingness to work with (via interoperability, compatibility or extension) other LF Edge projects to provide a greater edge solution than what can be done by the project alone. | Meets |
|
...
Additional Information Requested from All Projects | Supporting Data (if needed, include links to specific examples) |
|---|---|
Intention for the upcoming year (Remain at current stage OR advance towards the next Stage) | Remain Impact Project, release our 4th major release and potentially a third LTS version |
Include a link to your project’s LFX Insights page. We will be looking for signs of consistent or increasing contribution activity. Please feel free to add commentary to add color to the numbers and graphs we will see on Insights. | |
How many maintainers do you have, and which organizations are they from? (Feel free to link to an existing MAINTAINERS file if appropriate.) |
|
What do you know about adoption, and how has this changed since your last review / since you joined the current Stage? If you can list companies that are end users of your project, please do so. (Feel free to link to an existing ADOPTERS file if appropriate.) | We are learning about new adopters all the time. In addition to the companies that are participating in the construction of EdgeX (IOTech, Intel, Eaton, Schneider Electric, Danfoss, Yiqisoft), the following companies have announced (and presented) on EdgeX adoption:
Many organizations have adopted, adopting or are considering the adoption of EdgeX and related products including:
Others who have adopted EdgeX and related products:
|
How has the project performed against its goals since the last review? (We won't penalize you if your goals changed for good reasons.) | Met or exceeded goals. Over 9 million container downloads. 14 releases since 2017. Currently planning V4 and another LTS version, indicating the stability of EdgeX to the marketplace. |
What are the current goals of the project? For example, are you working on major new features? Or are you concentrating on adoption or documentation? | Working on a new major release targeted for Dec 2024 / Early 2025. The main aim right now is to focus on enabling EdgeX deployments and massive scale out. Challenges relating to third party OS license changes is one of the current activities. Also enhancement/replacement of the incumbent database technology with PostgreSQL. Looking to continue to grow the user base with more publicly referenced adopters. |
How can LF Edge help you achieve your upcoming goals? | More events such as the LF Edge Day in Vienna this month - which was an excellent forum for EdgeX awareness etc. |
Do you think that your project meets the criteria for the next Stage? | N/A. We are at stage 3 |
Please summarize Outreach Activities in which the Project has participated in (e.g. Participation in conferences, seminars, speaking engagements, meetups, etc.) |
|
Are you leveraging the Technical Project Getting Started Checklist? If yes, please provide link (if publicly available). | This was developed after our project launched, but we already follow all steps. |
Please review, and update if needed, your Project entry on the Existing Project Taxonomy page, modifying the Last Updated / Reviewed date in the header. | Up to date |
Please share a LFX security report for your project in the last 30 days | https://security.lfx.linuxfoundation.org/#/a0941000005osNnAAI/overview |