Project EVE - Stage 3 - 2025-10-22
Completed by: Renê de Souza Pinto, ZEDEDA
Submitted to TAC Mail List: 2025/10/22
Presented on TAC Weekly Call: 2025/10/22
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 | Erik Nordmark, Mark Riddoch |
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. | Meets | Using Apache 2.0, DCO, CCA4.0 - Technical Charter |
Upon acceptance, At Large projects must list their status prominently on website/readme | Meets |
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) |
|---|---|---|
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 | The project creates a build every two weeks (for every sprint) and an LTS release twice a year. |
Document that it is being used in POCs. | Meets | Project EVE has been used in various POCs and is in large-scale production use. See https://github.com/lf-edge/eve/blob/master/ADOPTERS.md |
Demonstrate a substantial ongoing flow of commits and merged contributions. | Meets | Over the last 12 months we have had 5323 commits from 48 contributors across 10 repositories. |
Demonstrate that the current level of community participation is sufficient to meet the goals outlined in the growth plan. | Meets | The above level of commits are likely to continue as we continue deliver the items on the roadmap and grow the TSC and committers. |
Demonstrate evidence of, or a plan for, interoperability, compatibility or extension to other LF Edge Projects. Examples may include demonstrating modularity (ability to swap in components between projects). | 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), of which no more than 1/3 is affiliated with the same employer. In the case there are 5 governing members, 2 may be from the same employer. | Meets | TSC is currently at 5 members across 3 companies. From https://github.com/lf-edge/eve/blob/master/CONTRIBUTING.md:
|
Have a documented and publicly accessible description of the project's governance, decision-making, and release processes. | Meets | TSC and committer election process, and release process https://github.com/lf-edge/eve/blob/master/CONTRIBUTING.md |
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 | Currently 6 committers across 3 organizations. From https://github.com/lf-edge/eve/blob/master/MAINTAINERS.md
|
Establish a security and vulnerability process which at a minimum includes meeting ("Met" or "?") all OpenSSF best practices security questions and SECURITY.md . | Meets | Passing (164%). See https://www.bestpractices.dev/en/projects/4746 |
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 | At https://lf-edge.atlassian.net/wiki/x/BYDyCQ and also referenced in https://lf-edge.atlassian.net/wiki/download/attachments/14583946/Technical Charter -- Enterprise Cyber-Physical Edge Virtualization Engine Project FINAL 2-12-19.pdf?version=1&modificationDate=1557623052344&cacheVersion=1&api=v2 |
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 | TSC and committer election process, https://github.com/lf-edge/eve/blob/master/CONTRIBUTING.md Owners in https://github.com/lf-edge/eve/blob/master/MAINTAINERS.md
|
Have a public list of project adopters for at least the primary repo (e.g., ADOPTERS.md or logos on the project website). | Meets |
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 at stage 3 |
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. | Shows steady increase of contributions and a good contributors retention as well. |
How many maintainers do you have, and which organizations are they from? (Feel free to link to an existing MAINTAINERS file if appropriate.) | Currently six maintainers in https://github.com/lf-edge/eve/blob/master/MAINTAINERS.md
|
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.) | See https://github.com/lf-edge/eve/blob/master/ADOPTERS.md for more information. |
How has the project performed against its goals since the last review? (We won't penalize you if your goals changed for good reasons.) | The goals for 2024 were
At the time of the last review in Nov 2024 the form did not include any explicit goals for 2025. |
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? | Goals for 2026
|
How can LF Edge help you achieve your upcoming goals? | We don’t know what “glue” there is between LF Edge and CNCF, but as we are doing more and more kubernetes integration there are some topics (like any CNCF plans to add long term support). If LF Edge has a path to raise such questions that would be helpful. |
Do you think that your project meets the criteria for the next Stage? | We are already 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). | We did use it when the project started since it didn’t exist at the time. However, we have done all of the items in that checklist. |
Please review, and update if needed, your Project entry on the Existing Project Taxonomy page, modifying the Last Updated / Reviewed date in the header. | Updated on November 18, 2024 |
Please share a LFX security report for your project in the last 30 days | https://security.lfx.linuxfoundation.org/#/a092M00001IV4DuQAL/overview https://security.lfx.linuxfoundation.org/#/a092M00001IV4DuQAL/vulnerabilities Note potential confusion/overlap due to shared lf-edge GH organization; see https://projectadmin.lfx.linuxfoundation.org/project/a092M00001IV4DuQAL/tools/security/overview
|