Versions Compared

Old Version 1

changes.mady.by.user Joe Pearson

Saved on

compared with

New Version 2

changes.mady.by.user Joe Pearson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Meets

Anil Vishnoi, Red Hat

Erik Nordmark, Zededa

Jim White, EdgeX Foundry

Joe Pearson, IBM

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

Code repositories use Apache 2.0

Documentation uses CC-by-4.0

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

Meets

On https://www.lfedge.org/projects/openhorizon/

On https://github.com/open-horizon

Marketing website not yet launched, but will reference.


Stage 1 Projects, please skip to Additional Information Requested from All Projects

...

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.

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

Meets

Features are released iteratively as testable units are completed.
Agent releases happen every Thursday.

Upcoming work :(Feature Requests

  • CORS support
  • AKKA to Pekko conversion

    • Project maturity:

    All Working Group Chairs will identify backup/replacement and begin training

    ):

    Project maturity:

    • All WG repos will list MAINTAINERS and keep updated - completed
    • Add two or more project Partners this year (which will also dilute IBM's influence on the TSC)Add/recruit more non-IBM Contributors to all WGs(to reduce IBM TSC votes below 33%)
    • Expand ecosystem with OSS partnerships
    • Add commercial usage: IBM Hybrid Cloud Mesh is the third

    Community growth:

    • Develop ties with Eclipse SDV, contribute code demonstrating CD/CD pipeline for workload placement decisions
    • Work with AgStack Foundation (LF Ag) on open vision models for crop ID
    • Grow ORRA by adding edge networking and security features, new use cases
    • Continue to work with universities
      • Added Georgia Tech's summer internship program last month
      • Working with ZHAW on Nephele

    Document that it is being used in POCs.

    Meets

    Demonstrate a substantial ongoing flow of commits and merged contributions.

    Meets

    Insights Link

    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

    ...