Page tree
Skip to end of metadata
Go to start of metadata



Completed by: Erik Nordmark , ZEDEDA

Submitted to TAC Mail List: 

Presented on TAC Weekly Call: 



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

 

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.


Apache 2.0, DCO, CCA4.0 - Technical Charter

Upon acceptance, At Large projects must list their status prominently on website/readme

 

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.



Document that it is being used in POCs.



Demonstrate a substantial ongoing flow of commits and merged contributions.


LFX Insights-EVE Commits

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


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


Joint Demo with Fledge and Akraino Blueprint family and Blueprint(s)
Future projects: working with OH and EdgeX

LF projects- ACRN and XEN

outreached to LF Energy


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.



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-

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


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

  1. Graduate to Stage 3
  2. Grow the number of project maintainers
  3. Grow the ecosystem of qualified hardware and edge applications running on EVE
  4. Provide full integration with existing LF Edge applications: EdgeX, Fledge, SDO, Open Horizon
  5. Codify our relationship with existing LF
    Edge applications via 1-3 Akraino Blueprints
    (Industrial IoT Edge BP in progress)
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?

  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. The contributing.md file has this. Need to make sure that there is a link to the governance part
  7. 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).No, we came in before it existed
  • No labels