Project EVE - Stage 2 - 2022-01-26

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

Need second sponsor

@Erik Nordmark (ZEDEDA),

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

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/

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

See Feature Roadmap for the projected feature sets.

The  community growth and project maturity are discussed in the goals below.

In December 2021 we had the first EVE design summit, which had to be scaled back/postponed significantly at the last minute due to COVID restrictions in Germany. We plan to hold such summits once or twice a year to grow the community of contributors and users.

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 in production as can be gleaned from https://zededa.com/transform/  and include Schlumberger, BOBST, PeopleFlow, PTC, etc.

In addition there is commercial use as shown in:

https://azuremarketplace.microsoft.com/en-us/marketplace/apps/zededa.annual_enterprise_license

https://www.supermicro.com/solutions/Solution-Brief_Zededa.pdf

Demonstrate a substantial ongoing flow of commits and merged contributions.

Meets

Over the last year we have had 1240 Commits from 36 Authors to 6 Repositories
LFX Insights-EVE Commits

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 deliver the items on the roadmap

LFX Insights- EVE Community

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

There is an Akraino Blueprint family with EVE and Fledge

We are doing experiments with the new Project Alvarium.

Together with Fledge we've worked with OSDU 

In addition, we have been working with other projects like https://ipxe.org/ https://https://tinkerbell.org/ for scalable installation and testing.

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.

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.

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)

Move to Stage 3 as the community diversity grows

Include a link to your project’s CommunityBridge 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.

Over the last year we have had 1240 Commits from 36 Authors to 6 Repositories. See more details at

LFX Insights-EVE Commits

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

Note: For EVE, we do not have many branches, so for us we are using the term Maintainer as someone who is has a major part in determining our direction.  Namely people who are planning features or producing architectural diagrams that will shape how we move forward. 

ACTIVE CONTRIBUTORS: 66    200.00% increase over the year (according to insigjhts)

Committers: 5 (the TSC)

• Avi Deitcher avi@deitcher.net

• Erik Nordmark erik@zededa.com

• Gianluca Guida glguida@gmail.com

• Gopi Krishna Kodali gkodali@zededa.com

• Roman Shaposhnik rvs@zededa.com

Maintainers:  7

@Erik Nordmark ZEDEDA

@Roman Shaposhnik ZEDEDA

@Avi Deitcher Atomic

@Jason Shepherd ZEDEDA

@Stefano Stabellini Xilinx

@Петр Федченков ZEDEDA

@Milan LencoZEDEDA

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

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 in production as can be gleaned from https://zededa.com/transform/  and include Schlumberger, BOBST, PeopleFlow, PTC, etc.

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 2021 were

1. Graduate to Stage 3. Deferred due to difficulty to grow community during the pandemic

2. Grow the number of project maintainers. Slight improvement

3. Grow the ecosystem of qualified hardware and edge applications running on EVE. Ongoing. Currently 56 hardware models

4. Provide full integration with existing LF Edge applications: EdgeX, Fledge, SDO, Open Horizon. Fledge Done. Others deferred.

5. Codify our relationship with existing LF Edge applications via 1-3 Akraino Blueprints Done

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 2022

1. Deliver on the  Feature Roadmap 

2. Continue growing the ecosystem of qualified hardware and edge applications running on EVE

3. Continue growing the number of project maintainers

4. Graduate to Stage 3

How can LF Edge help you achieve your upcoming goals?

Upstream: Moby ecosystem, OCI, CNCF (esp. K3S), OSDU
Downstream: Edge Application and Hardware Vendors

Bringing in more edge application and hardware vendors as members in LF Edge would be helpful not only for EVE but for LF Edge as a whole.

Do you think that your project meets the criteria for the next Stage?

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

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

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

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

5. Adopt the Foundation Code of Conduct.

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

7. Have a public list of project adopters for at least the primary repo (e.g., ADOPTERS.md or logos on the project website).

Project Stages: Definitions and Expectations

1. Have a TSC. Need more diversity of companies

2. Done

3. Need to expand diversity of companies

4. Done. Currently working with multiple projects

5. Done

6. Done in https://github.com/lf-edge/eve/blob/master/CONTRIBUTING.md

7. List of adopters not yet added to the github repo

Please summarize Outreach Activities in which the Project has participated in (e.g. Participation in conferences, seminars, speaking engagements, meetups, etc.)

May 15, 2021 AlpineConf "Taking Alpine to the Edge and Beyond With Linux Foundation's Project EVE"

Sept 28, 2021 LF OSS/ELC "EVE: a Secure API for the Edge That Delights App Developers"

Oct 7, 2021 P99 Conf "RISC-V on Edge: Porting EVE and Alpine Linux to RISC-V"

Aug 18-19, 2021 ZEDEDA Transform where the second day was about Project EVE and open source

Oct 12, 2021 LF ONES "Lightweight EVE-OS Carries Heavyweight Security to Safely Enable Edge Software Orchestration"

Dec 6, 2021 RISC-V Summit "RISC-V on Edge: Porting EVE and Alpine Linux to RISC-V"

Dec 8, 2021 Edgehog Day "Open Source at the Edge from LF Edge with Project EVE Demo"

Dec 7-8, 2021 EVE Design Summit

Are you leveraging the Technical Project Getting Started Checklist? If yes, please provide link (if publicly available).

No, we came in before it existed