Open Horizon - Stage 2 - 2024-03-20

Completed by: Joseph 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

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: 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): Hashicorp Vault to OpenBao conversion (with OpenBao project) Updating FDO integration (ongoing with FDO project) Realtime Workload Metrics (with EdgeLake project) Workload Runtime Security (with KubeArmor project) WASM workload support (with atym.io) 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
Document that it is being used in POCs.	Meets	Application-centric networking - IBM Hybrid Cloud Mesh, Skupper demo at ONE Summit TBD Nephele robotics search-and-rescue use case above feature requests
Demonstrate a substantial ongoing flow of commits and merged contributions.	Meets	Insights Link - opened a Jira ticket
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	Hashicorp Vault to OpenBao conversion (with OpenBao project) Device onboarding to EVE (demo with FDO, Project EVE, and LF Edge Sandbox) Realtime Workload Metrics (with EdgeLake project) Workload Runtime Security (with CNCF KubeArmor project) Application-centric connectivity (demo with Skupper, LF Networking)

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: KubeArmor-Integration - AccuKnox Documentation - IBM FDO Support - IBM Not including Intel's contributions on ORRA since those are in edgexfoundry-holding and not open-horizon repo.
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: AccuKnox integrating KubeArmor with Open Horizon, modifying KubeArmor for bare Linux hosts to work with our Device Agent, and joining our project as Partner IBM implementing our new features in their downstream IEAM 4.5.0 product and rolling out their internal video streaming infrastructure Mainsail, Turnium, and IBM building Falcon Tactical Edge for a secure edge computing stack based on our project, Intel chips, and secure networking IBM team currently building a Container on Wheels implementation for eventual open-source contribution to Eclipse SDV Intensivate building lab to demo their RISC-V ISA SoC with ~100 units with application deployment managed by Open Horizon DLR testing container deployments to Samsung industrial android devices using Open Horizon as demonstrated at MWC 2023
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: Add non-IBM voting members to the TSC (at least 30%) See above. Non-IBM TSC membership at 28% Add 20 or more active volunteer contributors Add three project partners contributing value We now have two official Partners and at least ten Adopters Bring two new members to LF Edge Create a project web site In progress, see dev sandbox Mentor twelve new candidates Establish ties with at least one university Rensselaer Polytechnic through RCOS Publish the beta release of the Open Retail Reference Architecture Release v1 was completed. Gearing up for v2 Launch the Open Edge Services Catalog Launched as the open-horizon-services GitHub
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.)	Intel InnovatiON 15-minute segment in talk about ORRA and demo ONE Summit Five talks related to Open Horizon MWC 2023 Talk included DLR and Resilient Edge Computing in Agriculture with Open Horizon Booth showed DLR work and featured our logo Edge Expo Open Source Summit in Vancouver IBM THINK
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	SECURITY.md LFX Security - not functioning