Page Comparison

...

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

Additional Information Requested from All Projects-

...

-where has Project EVE be talked about: conferences
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)
Move to Stage 3
(add in information into this column, more than just links)

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.
https://lfanalytics.io/projects/lfedge%2Fedgex-foundry/dashboard
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.
Contributors: 40 over the last year
Committers: 14 (the TSC)
Maintainers: 4
Erik Nordmark ZEDEDA
Roman Shaposhnik ZEDEDA
Avi Deitcher Atomic
Jason Shepherd ZEDEDA

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.) info from Jason (ZEDEDA)
How has the project performed against its goals since the last review? (We won't penalize you if your goals changed for good reasons.) This is the first review.
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 2021
Graduate to Stage 3
Grow the number of project maintainers
Grow the ecosystem of qualified hardware and edge applications running on EVE
Provide full integration with existing LF Edge applications: EdgeX, Fledge, SDO, Open Horizon
Codify our relationship with existing LF
Edge applications via 1-3 Akraino Blueprints
(Industrial IoT Edge BP in progress)
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?
need to edit and list
X, Y and Z
How can LF Edge help you achieve your upcoming goals? Upstream: Moby ecosystem, OCI, CNCF (esp. K3S), OSDU
Downstream: Edge Application and Hardware Vendors
Do you think that your project meets the criteria for the next Stage?
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.
-review stage 3 requirements
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).
Project Stages: Definitions and Expectations
have a TSC- need more diversity of companies
done
Need to expand diversity of companies
done- Currently working with multiple projects
done
The contributing.md file has this. Need to make sure that there is a link to the governance part
Need to work on public adopters
Please summarize Outreach Activities in which the Project has participated in (e.g. Participation in conferences, seminars, speaking engagements, meetups, etc.)
Sample Project had a kiosk at IOT SWC as well as ONES NA. Also participated in the LF Edge "On the Edge" webinar series.
Speakers at many conferences about OSS, IoT, and IIoT
Extensive work on the user groups creation
Extensive work on the LF Edge Whitepaper
Are you leveraging the Technical Project Getting Started Checklist? If yes, please provide link (if publicly available). Are we using it or just doing things that happen to be on the list. No, we came in before it existed

Version	Old Version 7	New Version 8
Changes made by	Aaron Williams	Aaron Williams
Saved on	Nov 30, 2020	Dec 01, 2020

Versions Compared

Key

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)	Move to Stage 3 (add in information into this column, more than just links)
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.	https://lfanalytics.io/projects/lfedge%2Fedgex-foundry/dashboard
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.	Contributors: 40 over the last year Committers: 14 (the TSC) Maintainers: 4 Erik Nordmark ZEDEDA Roman Shaposhnik ZEDEDA Avi Deitcher Atomic Jason Shepherd ZEDEDA
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.)	info from Jason (ZEDEDA)
How has the project performed against its goals since the last review? (We won't penalize you if your goals changed for good reasons.)	This is the first review.
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 2021 Graduate to Stage 3 Grow the number of project maintainers Grow the ecosystem of qualified hardware and edge applications running on EVE Provide full integration with existing LF Edge applications: EdgeX, Fledge, SDO, Open Horizon Codify our relationship with existing LF Edge applications via 1-3 Akraino Blueprints (Industrial IoT Edge BP in progress)
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?	need to edit and list X, Y and Z
How can LF Edge help you achieve your upcoming goals?	Upstream: Moby ecosystem, OCI, CNCF (esp. K3S), OSDU Downstream: Edge Application and Hardware Vendors
Do you think that your project meets the criteria for the next Stage? 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. -review stage 3 requirements 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).	Project Stages: Definitions and Expectations have a TSC- need more diversity of companies done Need to expand diversity of companies done- Currently working with multiple projects done The contributing.md file has this. Need to make sure that there is a link to the governance part Need to work on public adopters
Please summarize Outreach Activities in which the Project has participated in (e.g. Participation in conferences, seminars, speaking engagements, meetups, etc.)	Sample Project had a kiosk at IOT SWC as well as ONES NA. Also participated in the LF Edge "On the Edge" webinar series. Speakers at many conferences about OSS, IoT, and IIoT Extensive work on the user groups creation Extensive work on the LF Edge Whitepaper
Are you leveraging the Technical Project Getting Started Checklist? If yes, please provide link (if publicly available).	Are we using it or just doing things that happen to be on the list. No, we came in before it existed