Page Comparison

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.

Meets

• EdgeX is an Apache 2.0 license project.  We require all contributions comply with this license agreement as stated in our Wiki below: EdgeX contributors guide

• EdgeX policy to review new libs, modules, etc. brought into the project to insure anything we use (or is used indirectly by modules we bring in) is compliant with this license. https://wiki.edgexfoundry.org/display/FA/Vetting+Process+for+3rd+Party+Dependencies

• We also conduct code scans regularly (with each PR) for any license compliance issues

• Recently challenges are emerging with some third party products changing their open source license policy (Redis, Vault, Consul). This is being addressed in upcoming EdgeX releases

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

Meets

Displayed proudly on EdgeX wiki:

Image Added

… and on the EdgeX website:

Image Added

Demonstrate regular project leadership (typically TSC) meetings.  Project leadership should meet monthly at a minimum unless there are extenuating circumstances (ex: holiday period)

Meets

TSC meetings are held bi-weekly. All information and recordings are held on the wiki pages here: https://lf-edgexfoundry.atlassian.net/wiki/spaces/FA/pages/11667441/Technical+Steering+Committee+TSC

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

• 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 (e.g., "Odessa" tags on the Core Working Group project board here: https://github.com/orgs/edgexfoundry/projects/56 for an example).

Document that it is being used in POCs.

Demonstrate a substantial ongoing flow of commits and merged contributions.

Meets

Collected from LF Insights for the project since inception and for the last 12 months:

Image Added

Image Added

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

Meets

13 successful project releases since April 2017 (usually 2 each year)

• EdgeX 3.0 (Minnesota was a new major release version, released on May 31st 2023

• EdgeX 3.1 (Levski) also released on Nov 15th 2023 was the latest LTS version with a 24 month community support cycle

On track for two more releases in the next year:  Odessa, likely version 4.0 at end of 2024, and Palau 4.2 half way through 2025.

Demonstrate a willingness to work with (via interoperability, compatibility or extension) other LF Edge projects to provide a greater edge solution than what can be done by the project alone. 

Meets

• Planned adoption of OpenBao as the reference/supplied secret store with EdgeX

• Collaboration with and use within EdgeX of eKuiper (formerly Kuiper) project

• Collaboration with and potential use of NanoMQ within EdgeX (the MQTT broker is pluggable)

• Integration with Akraino ELIOT blueprint (tested using UNH lab)

• Incubation of Open Horizon project

• Inclusion in the Open Retail Reference Architecture (with Open Horizons, and SDO)

• Accomplished Baetyl/EdgeX integration (work accomplished in PRC).  See Updates of EdgeX-Baetyl collaboration attempts-v0.1.pptx

• Use of EdgeX in HomeEdge and continued support of that project

• Fledge export connector