Page History

2 TAC Sponsors, if identified (Sponsors help mentor projects) - See full definition on Project Stages: Definitions and Expectations

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

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.

Feature Roadmap

Process documents for TSC and committer expansion are now in place. Will expand on those.

Document that it is being used in POCs.

Project EVE has been used in various POCs and is in production use. Some production users have made it public that they are using Project EVE  as can be seen in https://zededa.com/resources/case-studies/ (Switch Automation, PV Hardware, BOBST, PeopleFlow) while others have presented at https://zededa.com/transform/  (VMware, Emerson, Rockwell Automation, SLB)

In addition there is production use by a top-3 automobile manufacturer at car dealers.

Demonstrate a substantial ongoing flow of commits and merged contributions.

Demonstrate that the current level of community participation is sufficient to meet the goals outlined in the growth plan.

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).

Done work with Project Alvarium (see webcast below)

Continued work with Fledge 

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.

Have a documented and publicly accessible description of the project's governance, decision-making, and release processes.

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.

Currently the three TSC members

https://github.com/lf-edge/eve/blob/master/MAINTAINERS.md

Demonstrate evidence of interoperability, compatibility or extension to other LF Edge Projects. Examples may include demonstrating modularity (ability to swap in components between projects).

Adopt the Foundation Code of Conduct.

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.

TSC and committer election process, https://github.com/lf-edge/eve/blob/master/CONTRIBUTING.md 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).

Intention for the upcoming year (Remain at current stage OR advance towards the next Stage)

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 stready increase of contributors

How many maintainers do you have, and which organizations are they from? (Feel free to link to an existing MAINTAINERS file if appropriate.)

Currently the TSC (Three people from three different organizations)

• Avi Deitcher avi@deitcher.net
• Erik Nordmark erik@zededa.com
• Roman Shaposhnik rvs@apache.org (thepaperclipproject.eu)

Added a top-3 automobile manufacturer.

The goals for 2022 were

1. Deliver on the  Feature Roadmap (done)
2. Continue growing the ecosystem of qualified hardware and edge applications running on EVE (partial)
3. Continue growing the number of project maintainers (needed process/criteria clarification)
4. Graduate to Stage 3 (deferred)

Goals for 2023

1. Deliver on the  Feature Roadmap, including

1. technical investigations are in the area of storage/compute clustering, and additional networking functionality,
2. Expand the TSC and committers
3. Graduate to Stage 3

ONE Summit 2022

webcast: How LF Edge projects track CO2 footprint with secure monitoring at the Edge

EVE-OS and security featured on https://techfieldday.com/appearance/zededa-presents-at-edge-field-day-1/

Please review, and update if needed, your Project entry on the Existing Project Taxonomy page, modifying the Last Updated / Reviewed date in the header.

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

Hard to understand data; matching something else since no dpkg in build or output but 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1664

Note potential confusion/overlap due to shared lf-edge GH organization; see https://projectadmin.lfx.linuxfoundation.org/project/a092M00001IV4DuQAL/tools/security/overview