Completed by:  Erik Nordmark, ZEDEDA

Submitted to TAC Mail List:  2024/07/23 TBD

Presented on TAC Weekly Call:  2024/07/24 (Meeting Recording TBD)



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

https://www.lfedge.org/projects/eve/


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

Feature Roadmap

Document that it is being used in POCs.

Meets

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.

Meets

Over the last 10 months we have had 950 commits from 56 contributors across 10 repositories 
LFX Insights-EVE Commits. At the previous annual review those numbers were 907 Commits from 28 Contributors to 6 Repositories

Note that 10 months ago we introduce the eve-kernel repository which is a clone of the Linux kernel with complete git history. LFX Insights picks that up. 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.

MeetsThe 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

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

Plus separate work to enable the LF Edge Sandbox.


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.

 TBD
TSC is currently at 3 members across 3 companies

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 4 committers across 3 origanizations

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

 Meets
See above evidence under stage 2

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

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

TBD

Need to get agreement to publish names

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

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

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

  1. Deliver on the  Feature Roadmap, including technical investigations are in the area of storage/compute clustering, additional networking functionality, evolve security, more integrated kubernetes runtime(s).
  2. Expand the TSC and get a list of public adopters.
  3. Graduate to Stage 3
How can LF Edge help you achieve your upcoming goals?
Do you think that your project meets the criteria for the next Stage?Two items missing - grow the TSC and get a public list of adopters
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
Kubecon NA 2023 Chicago
Kubecon EU 2024 Paris
ONE Summit 2024 San Jose

Plus separate work to enable the LF Edge Sandbox.

Are you leveraging the Technical Project Getting Started Checklist? If yes, please provide link (if publicly available).No, started before that checklist existed.

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

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


  • No labels