EdgeX Foundry - Stage 3 - 2023-09-06

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

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.

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

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.

We maintain a roadmap for the next 2 years and have a long term backlog that extends beyond that timeframe.  The next couple of releases are documented with pages in our Wiki (and you can see past release roadmaps) here:  https://wiki.edgexfoundry.org/display/FA/Roadmap.

Minor fixes and enhancements are also captured in issues with each repository in Github.  Github tags are used to label bugs from enhancement requests and when appropriate are associated with a specific target release.

Document that it is being used in POCs.

EdgeX is used in countless POCs worldwide so this list is actually more about production uses.

• Companies announced use of EdgeX in their products include Accenture (AIP+ product), ThunderSoft (TurboX), Jiangxing Intelligence (EdgeBox), and Tibco (Project Air), HP (Engage Edge), Advantech, UST Global. Many of the company presentations to the EdgeX community can be found at the wiki site below.
  https://wiki.edgexfoundry.org/display/FA/Vertical+Solutions+Working+Group#VerticalSolutionsWorkingGroup-MeetingMinutes
• Eaton's use of EdgeX is documented in an LF Edge Use Case publication of 2023 found here.
• HP's announcement is found here:  https://press.hp.com/us/en/blogs/2020/hp-unveils-hp-engage-edge.html
• IOTech Systems also provides a commercial implementation of EdgeX called Edge Xpert and uses that is several POC and customer projects around the globe.  https://www.iotechsys.com/our-products/edge-software-platforms/edge-xpert/

Demonstrate a substantial ongoing flow of commits and merged contributions.

Collected from LF Insights for the project since inception and for the last 1 year

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

12 successful project releases since April 2017 (2 each year)

• EdgeX 2.3 (Levski) was released on Nov 9th 2022
• EdgeX 3.0 (Minnesota) was released on May 31th, 2023 (EdgeX's 3rd major release)

On track for two more releases in the next year:  3.1 (code named Napa) in fall of 2023, and a likely our second LTS release.  The spring of 2023 will release "Odessa."  It may be a dot release (to be determined).

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

• Integration of (and support to) new LF Edge project NanoMQ.
• Currently working with Alvarium to provide an EdgeX demonstration/integration project (due ~ late fall 2023)
  • See TSC meeting minutes with regard to design and action plan.
• Integration Akraino ELIOT blueprint (tested using UNH lab)
• Incubation of Open Horizon project
• Inclusion in the Open Retail Reference Architecture (with Open Horizons, and SDO)
  • Recent efforts to incorporate into IBM/Intel/Scale Computing and others demonstration lab used in a retail theft/loss prevention demonstration.
• Accomplished Baetyl/EdgeX integration (work accomplished in PRC).  See Updates of EdgeX-Baetyl collaboration attempts-v0.1.pptx
• Collaboration with and use within EdgeX of eKuiper (formerly Kuiper) project
• Fledge export connector

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.

Our current TSC is comprised of members from Intel, Canonical, IOTech, HP, Eaton, Oracle, and Beechwoods.  For names and details see:

https://wiki.edgexfoundry.org/pages/viewpage.action?pageId=88212178

Each TSC group continues to be a good mix of experienced EdgeX leaders with new members and organizations becoming involved.

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

Matters of project governance, decision making and process are covered in our project Wiki.  The following pages outline our policies.
Matters of technical decisions and voting process and rules are defined here:  https://wiki.edgexfoundry.org/display/FA/Technical+Work+in+the+EdgeX+Foundry+Project

Guidance for how to submit code contributions is defined here:  https://wiki.edgexfoundry.org/display/FA/Contributor%27s+Guide and here: https://wiki.edgexfoundry.org/display/FA/Contributor%27s+Process

Documentation on how our release process and what gets released is here:  https://wiki.edgexfoundry.org/display/FA/Release+Process and some additional information on what is considered a release artefact is defined here:  https://docs.edgexfoundry.org/1.2/design/adr/devops/0007-Release-Automation/

Significant new features are discussed via TSC approved Use Case Review (UCR) process to better refine the way in which new requirements are defined, and the Architectural Decision Records (ADR) stage of the design.

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.

Work group chairs automatically have committer rights to their work group repositories and nominate others as committers as spelled out in our governance here:  https://wiki.edgexfoundry.org/pages/viewpage.action?pageId=21823860#Contributors,Committers&Maintainers-NominationandApprovalofMaintainersandCommitters

Each repository has at least 2 committers.  The most used repository has 100 contributors and 19 committers (https://github.com/edgexfoundry/edgex-go/graphs/contributors)

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

• Integration of (and support to) new LF Edge project NanoMQ.
• Currently working with Alvarium to provide an EdgeX demonstration/integration project (due ~ late fall 2023)
  • See TSC meeting minutes with regard to design and action plan.
• Integration Akraino ELIOT blueprint (tested using UNH lab)
• Incubation of Open Horizon project
• Inclusion in the Open Retail Reference Architecture (with Open Horizons, and SDO)
  • Recent efforts to incorporate into IBM/Intel/Scale Computing and others demonstration lab used in a retail theft/loss prevention demonstration.
• Accomplished Baetyl/EdgeX integration (work accomplished in PRC).  See Updates of EdgeX-Baetyl collaboration attempts-v0.1.pptx
• Collaboration with and use within EdgeX of eKuiper (formerly Kuiper) project
• Fledge export connector

Adopt the Foundation Code of Conduct.

For any significant community meeting such as the TSC meetings or meeting where we are inviting outside community to speak or observe are always preceded by the code of conduct and anti-trust policy statements.  To date, we have had no unacceptable behavior incidents that the project has been made aware of.

EdgeX adheres to, follows and enforces the LF Edge Code of Conduct without addendum today.

https://wiki.edgexfoundry.org/display/FA/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.

Examples of these documents can be found in our main repository https://github.com/edgexfoundry/edgex-go

Additionally, project governance and committer process is fully documented in our Wiki.  Existing governance and contributor pages are located on this page and its subpages:  https://wiki.edgexfoundry.org/display/FA/Technical+Work+in+the+EdgeX+Foundry+Project
And here:  https://wiki.edgexfoundry.org/display/FA/Contributor%27s+Guide

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

Our main repository contains the Adopter document (see https://github.com/edgexfoundry/edgex-go/blob/main/ADOPTERS.md)

We also highlight user, adopters and commercial interests of EdgeX on our Website.

• https://www.edgexfoundry.org/ecosystem/users/
• https://www.edgexfoundry.org/ecosystem/adopter-series/
• https://www.edgexfoundry.org/ecosystem/members/

Intention for the upcoming year (Remain at current stage OR advance towards the next Stage)

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.

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

We are learning about new adopters all the time.   In addition to the companies that are participating in the construction of EdgeX, the following companies have announced (and presented) on EdgeX adoption:

• Canonical, IOTech, HP, Thundersoft, Jiangxing Intelligence, Tibco and Accenture

Many organizations have adopted, adopting or are considering the adoption of EdgeX and related products including:

• Wartsilla, Schneider Electric, NetEase Technology, Fanmi Technology, Danfoss, Oracle

Others who have adopted EdgeX and related products:

• Large energy/oil company, Large power supply company, large building automation company, large events and venue management company, etc

Met or exceeded goals.  Over 9 million container downloads. Regular releases for 6+ years, including the 3rd major release, second Long Term Support coming this year, indicating the stability of EdgeX to the marketplace.

Per our plan, we moved from Slack to Github discussions. Slack has the 10K limit and is not good for historical searches.

Travel restrictions / travel budgets still hamper the project's ability to have face-to-face meetings, but we did manage to hold a couple of virtual hackathons.

Working on a LTS release targeted for fall 2023 with a likely minor release for spring of 2024 (dependent on some external aspects such as embedded products and move to BSL).

Looking to continue to grow the user base with more publicly referenced adopters. Integration to some very large scale customers and industrial use cases.

We have to explore joint live events for 2024.
Join with other organizations looking to improve dev advocacy through hackathons, badging, and other programs.

• Prior to COVID, regular participation at Hannover Messe, IOT SWC, IOT World and LF events.  Our members have spoken frequently at live events all over the world. Restrictions (budget more than COVID restrictions today) mean that virtual events are more commonplace.  We hope live/face-to-face events will be in scope for 2024 (especially a semi-annual TSC planning event)
• Intel sponsored student Hackathon (just completing in fall 2023)
• EdgeX presented sessions at ONES 2022 in Seattle in November 2022.  EdgeX will present at the OneSummit China in Sept 2023.
• China continue to enjoy excellent EdgeX participation events with their now annual China EdgeX Challenge
• The EdgeX community took ownership of social media starting in Feb 2023. 

Please review, and update if needed, your Project entry on the Existing Project Taxonomy page, modifying the Last Updated / Reviewed date in the header.

Please share a LFX security report for your project in the last 30 days