Project EVE - Stage 3 - 2024-11-20
- Erik Nordmark
Completed by: Erik Nordmark, ZEDEDA
Submitted to TAC Mail List: 2024-11-19
Presented on TAC Weekly Call: 2024-11-20 (Meeting Recording Video Conferencing, Web Conferencing, Webinars, Screen Sharing )
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, Joe Pearson |
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 eve/ADOPTERS.md at master · lf-edge/eve |
Demonstrate a substantial ongoing flow of commits and merged contributions. | Meets | Over the last 12 months we have had 1059 commits from 57 contributors across 10 repositories Note that in Sept 2023 we introduced the eve-kernel repository which is a clone of the Linux kernel with ots complete git history. LFX Insights picks that up, and as a result the total contributors are 25,000! One can look at less confusing data individually for the other repositories e.g., the main EVE repo. |
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 | Worked with FDO and OpenHorizon to demo a combined EVE, FDO, and OpenHorizon at One Summit 2024 in San Jose. In addition work with other LF projects like CNCF SPOS WG and Margo. Previous worked closely with EdgeX Foundry and Akraino. Plus separate work to enable the LF Edge Sandbox where EVE is a foundation for deploying different LF Edge projects and other software on edge devices. Note that “interoperability” in most of the above cases means that EVE is used as a substrate to deploy and operate these other LF Edge projects. The exception is the FDO integration which involved modifications to EVE. |
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 eve/CONTRIBUTING.md at master · lf-edge/eve:
|
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 7 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 | Worked with FDO and OpenHorizon to demo a combined EVE, FDO, and OpenHorizon at One Summit 2024 in San Jose. In addition work with other LF projects like CNCF SPOS WG and Margo. Previous worked closely with EdgeE Foundry and Akraino. Plus separate work to enable the LF Edge Sandbox where EVE is a foundation for deploying different LF Edge projects and other software on edge devices. Note that “interoperability” in most of the above cases means that EVE is used as a substrate to deploy and operate these other LF Edge projects. The exception is the FDO integration which involved modifications to EVE. |
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) | Advance to 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. | https://insights-v2.lfx.linuxfoundation.org/project-eve/trends Shows steady increase of contributors. See above note about impact of adding eve-kernel repository |
How many maintainers do you have, and which organizations are they from? (Feel free to link to an existing MAINTAINERS file if appropriate.) | Currently four 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.) | Since last review added a large chemical company and a large clothing retailer. |
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 2023 were
|
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 2024
|
How can LF Edge help you achieve your upcoming goals? |
|
Do you think that your project meets the criteria for the next Stage? | Yes |
Please summarize Outreach Activities in which the Project has participated in (e.g. Participation in conferences, seminars, speaking engagements, meetups, etc.) | OSS EU Edge Day 2024 Bilbao Plus separate work to enable the LF Edge Sandbox. Slide presentations are uploaded to the EVE Wiki (Slide presentations _
|
Are you leveraging the Technical Project Getting Started Checklist? If yes, please provide link (if publicly available). | We did you 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
|