Completed by:  Joe Pearson, IBM

Submitted to TAC Mail List:  TBD

Presented on TAC Weekly Call:  TBD



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

Meets

Joe Pearson, IBM

Randy Templeton, Intel

Erik Nordmark, Zededa

Anil Vishnoi, Red Hat

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

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

Project maturity:

  • All WG repos will list MAINTAINERS and keep updated - completed
  • Add project Partners (to reduce IBM TSC votes below 33%)
  • Expand ecosystem with OSS partnerships
  • Add commercial usage: IBM Hybrid Cloud Mesh is the third

Community growth:

  • Continue to work with universities
    • Added Georgia Tech's summer internship program last month
    • Working with ZHAW on Nephele
  • Support developers by turning ONE Summit demos into evergreen examples that anyone can run and learn from
  • Launch marketing web site with information on adopters and demos, better LF Edge Sandbox integration

Document that it is being used in POCs.

Meets

Demonstrate a substantial ongoing flow of commits and merged contributions.

Meets

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


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

Needs Improvement

Link to TSC page on wiki.  Current composition is:

  • IBM - 5 (71%)
  • AccuKnox - 1  (14%)
  • mimik Technologies - 1 (14%)

Actively working to expand TSC voting membership outside of IBM.

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

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.

Meets

  • Governance - high level description of goals
  • Community - organizational structure, roles, process
  • Contributions - feature requests & lifecycle process
  • Release - feature releases & roadmap
    see Growth Plan above

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.

Meets

See Insights links above.

NOTE: Current Insights organization report not accurate.

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

Meets

See interoperability section above.

Adopt the Foundation Code of Conduct.

Meets

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

Meets

Added Anylog/EdgeLake, atym.io, AgriLife (Texas A&M), ZHAW/Nephele

Mainsail, Turnium, IBM, Intel, Samsung, DLR (Rhineland-Palatinate), AgriRegio Projekt, AccuKnox, mimik, Scale Computing, Boston Dynamics, Promare, Intensivate, expeer

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)

We intend to advance to Stage Three when the project and our TAC Sponsors feel we're ready.  At this point, the largest sticking point is increasing non-IBM contributions.  Open Horizon should not be a single-source open-source project.

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.

Insights Link

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

We feature a MAINTAINERS file in each repo, ex: 

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

The most recent adoptions are:

  • Anylog contributing EdgeLake and working with Open Horizon on Realtime Metrics demo
  • Nephele at ZHAW using Open Horizon for their search-and-rescue mapping service
  • IBM embedding Open Horizon into their Hybrid Cloud Mesh product to dynamically deploy and move L7 Skupper/RHSI gateways to maintain application connectivity
  • Texas A&M's AgriLife using Open Horizon for soil moisture research and data collection
  • Intensivate building lab to demo their RISC-V ISA SoC with ~100 units with application deployment managed by Open Horizon
How has the project performed against its goals since the last review? (We won't penalize you if your goals changed for good reasons.)

Previous Goals:

  • Bring two new members to LF Edge
    Referred Orange, and brought OpenBao, EdgeLake to LF Edge
  • Establish ties with at least one university
    Added Texas A&M, GaTech
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?See the Stage Two Growth Plan above.
How can LF Edge help you achieve your upcoming goals?We need some assistance with fundraising so we can offer LFX Mentorships and run hackathon events.
Do you think that your project meets the criteria for the next Stage?Not quite yet.  We need to diversify our TSC company representation.
Please summarize Outreach Activities in which the Project has participated in (e.g. Participation in conferences, seminars, speaking engagements, meetups, etc.)


Are you leveraging the Technical Project Getting Started Checklist? If yes, please provide link (if publicly available).No

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

No changes needed.

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

Badge level for project 4300 is in_progress

SECURITY.md

LFX Security - not functioning

  • No labels