EdgeX Foundry - Stage 3 - 2024-09-25
- James Butcher
Completed by: James Butcher, IOTech Systems
Submitted to TAC Mail List: 2024/09/25
Presented on TAC Weekly Call: 2024/09/25 (Meeting Recording)
Below is a self-assessment submitted by TSC Chair/Maintainers of the Project. Comments/questions/feedback is welcome either a) in the Comments at the bottom of the page or b) during the TAC call when information is presented
Stage 1: At Large Projects
Stage 2 and Stage 3 Projects also requested to complete this section, as PLD acceptance criteria requires meeting current as well as prior stage requirements
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 1 Projects, please skip to Additional Information Requested from All Projects
Stage 2: Growth Stage
Stage 3 Projects also requested to complete this section
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 |
|
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 | Already at stage 3. Demonstrated maturity by 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.1 during 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 |
|
Stage 2 Projects, please skip to Additional Information Requested from All Projects
Stage 3: Impact Stage
Criteria | Meets / Needs Improvement / Missing / Not Applicable | Supporting Data (if needed, include links to specific examples) |
|---|---|---|
Have a defined governing body of at least 5 or more members (owners and core maintainers) | Meets |
|
Have a documented and publicly accessible description of the project's governance, decision-making, and release processes. | Meets |
|
Have a healthy number of committers from at least two organizations. A committer is defined as someone with the commit bit; i.e., someone who can accept contributions to some or all of the project. | Meets |
|
Establish a security and vulnerability process which at a minimum includes meeting ("Met" or "?") all OpenSSF best practices security questions and SECURITY.md. | Meets | The project has a well defined security & vulnerability process as defined here: Security The LTS releases have have CVE patches applied to them, for example: Napa 3.1.1 (Bug Release to LTS) |
Demonstrate evidence of interoperability, compatibility or extension to other LF Edge Projects. Examples may include demonstrating modularity (ability to swap in components between projects). | Meets |
|
Adopt the Foundation Code of Conduct. | Meets |
|
Explicitly define a project governance and committer process. This is preferably laid out in a GOVERNANCE.md file and references a CONTRIBUTING.md and OWNERS.md file showing the current and emeritus committers. | Meets |
|
Have a public list of project adopters for at least the primary repo (e.g., ADOPTERS.md or logos on the project website). | Meets | Our main repository contains the Adopter document (see https://github.com/edgexfoundry/edgex-go/blob/main/ADOPTERS.md ) We also highlight user, adopters and commercial interests of EdgeX on our Website. |
Additional Information Requested from All Projects
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, plan to release our 4th major release and potentially a third LTS version by end of year, keeping strong with our Apache 2.0 based licensing across all components |
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.) | EdgeX users are now most often at the deployment stage. Reference Keith Steele’s EdgeX talk in Vienna “From Promise to Production –The Maturity of EdgeX and Large-Scale Industrial Edge Deployments” But 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. 13 releases since 2017. Currently planning V4 and another LTS version, all 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? |
|
How can LF Edge help you achieve your upcoming goals? | More events such as the LF Edge Day at LF OSS 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 |