Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Feature Roadmap

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 1059 commits from 57 contributors across 10 repositories 
LFX Insights-EVE Commits. At the 2023 annual review those numbers were 907 Commits from 28 Contributors to 6 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.

...

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 7 committers across 3 organizations. From https://github.com/lf-edge/eve/blob/master/MAINTAINERS.md

  • Avi Deitcher avi@deitcher.net

  • Nikolay Martyanov nikolay@zededa.com

  • Erik Nordmark erik@zededa.com

  • Milan Lenco milan@zededa.com

  • Roman Penyaev romanp@zededa.com

  • Renê Pinto rene@zededa.com

  • Roman Shaposhnik rvs@apache.org

Establish a security and vulnerability process which at a minimum includes meeting ("Met" or "?") all OpenSSF best practices security questions and SECURITY.md .

Meets

TBD

https://github.com/lf-edge/eve/blob/master/docs/SECURITY.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).

 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

TBD link

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

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

...