Versions Compared

Old Version 4

changes.mady.by.user Daniel Lazaro

Saved on

compared with

New Version Current

changes.mady.by.user Kendall Perez

Saved on

Key

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

...

Status

  • Presented to the TAC:  March 22, 2023
  • TAC Project Review:
    • Subgroup Review Meeting:  April 3, 2023
    • Subgroup Readout: February 10, 2021 (Slides, Minutes, Recording)April 5, 2023
  • TAC Vote Approved:  April 13, 2023
  • Governing Board Vote Approved: 

Project Resources


...

Stage

...

3:

...

Impact Stage

Definition

The Impact Stage is for projects that have reached their growth goals and are now on a self-sustaining cycle of development, maintenance, and long-term support. Impact Stage projects are widely used in production environments and have largewith a significant number of public use cases. Moreover they have broad, well-established project communities with a number of contributors from at least two organizations.

...

diverse contributors.

Expectations

  • Are used in production environments.

  • Impact Stage projects are expected to participate actively in TAC proceedings, and as such have a binding vote on TAC matters requiring a formal vote, such as the election of a TAC Chair.

  • Projects that have publicly documented release cycles

...

  • .

  • Projects that are able to attract a

...

  • number of committers on the basis of its

...

  • production usefulness.

...

  • Projects that have several, publicly known, end-user deployments.

Expectations

Benefits

Impact Stage projects are expected to participate actively in TAC proceedings, and as such have a binding vote on TAC matters requiring a formal vote, such as the election of a TAC Chair. They receive ongoing financial and marketing support from the Foundation, and are expected to cross promote the foundation along with their activities.

  • Annual discretionary budget

Acceptance Criteria

To graduate from At Large or Growth status , or for a new project to join as an Impact project, a project must meet the Growth stage criteria plus Impact stage criteria:

Stage 2: Growth requirements:

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

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

  • Document that it is being used in POCs.

  • Demonstrate a substantial ongoing flow of commits and merged contributions.

  • Demonstrate that the current level of community participation is sufficient to meet

    the

    the goals outlined in the growth plan.

  • Demonstrate

    evidence of, or a plan for,

    a willingness to work with (via interoperability, compatibility or extension

    to

    ) other LF Edge

    Projects. Examples may include demonstrating modularity (ability to swap in components between projects).Since these metrics can vary significantly depending on the type, scope and size of a project, the TAC has final judgement over the level of activity that is adequate to meet these criteria

    projects to provide a greater edge solution than what can be done by the project alone.

  • Onboard all project repositories with LFX Security. Working toward or achieving OpenSSF badging would be a plus.

  • Receive a two-thirds vote of all

    TAC representatives

    TAC representatives that do not abstain the vote and a majority vote of the Governing Board to move to Growth Stage.

Stage 3: Impact requirements:

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

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

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

  • Establish a security and vulnerability process which at a minimum includes meeting ("Met" or "?") all OpenSSF best practices security questions and SECURITY.md.

  • Demonstrate evidence of interoperability, compatibility or extension to other LF Edge Projects.

     Examples

    Examples may include demonstrating modularity (ability to swap in components between projects).

  • Adopt the Foundation Code of Conduct.

  • Explicitly define a project governance and committer process. This is preferably laid

    out

    out in

    a 

    a GOVERNANCE.md

     file

    file and references

    a 

    a CONTRIBUTING.md

     and 

    and OWNERS.md

     file

    file showing the current and emeritus committers.

  • Have a public list of project adopters for at least the primary repo (e.g.,

     

    ADOPTERS.md

     or

    or logos on the project website).

  • Other metrics as defined by the applying Project during the application process in cooperation with the TAC.

  • Receive a two-thirds vote of all

    TAC representatives

    TAC representatives that do not abstain the vote and a majority vote of the Governing Board to move to Impact stage. Projects can move directly from At Large to Impact, if they can demonstrate sufficient maturity and have met all requirements.

Compliance with Requirements

...

Stage 2: Growth

RequirementEvidence
Two TAC sponsors

Joe Pearson (IBM), Jim St. Leger (Intel), Anil Vishnoi (Red Hat), Henry Lau (EdgeX Foundry)

Presentation to the TACOriginal presentation deck and recording from March 11, 2020
IP Policy: licenses for code and documentation, DCO for contributions
List project (Stage One) status on web site or READMEUpdated LF Edge project page to reference (thanks, Brett!)
>= 2/3 approval vote of TAC & majority of Governing Board SPC
  • TAC two-thirds vote approval reached on March 30, 2020.
  • Governing Board Strategic Planning Committee approval reached on April 9, 2020.
    link to page

Growth

Demonstrate regular project leadershipTechnical Steering Committee (TSC)
Growth plan

The Fledge project and community plans to create a strong ecosystem around Fledge to attract more users and stimulate community growth by:

The Fledge community has been growing steadily over the years incorporating a diverse set on contributors from various organizations.

  • Recently the Fledge TSC was expanded its voting members to incorporate a diverse representation of organizations.
  • Growing attendance from a variety of users and contributors.
  • Demonstrations of new features.

The Fledge community has identified additional organizations focused on Industrial IIoT standards and systems.  We intend to grow the Fledge community  by engaging all 4 in PoCs, edge strategies and edge contributions.  The four organizations are LF Energy, OSDU, CESMII and the Eclipse Foundation.  

  • LF Energy: is an open source foundation that focuses on power systems hosted within the Linux Foundation. 
  • OSDU (Open Subsurface Data Universe): The OSDU Forum is developing an open source, standards based, technology agnostic data platform. Primarily focuses on oil and gas and renewables.
  • CESMII: Radically accelerate the development and adoption of advanced sensors, controls, platforms, and models, to enable Smart Manufacturing (SM) to become the driving sustainable engine that delivers real-time business improvements in U.S. manufacturing.
  • Eclipse Foundation: The Eclipse Foundation provides our global community of individuals and organizations with a mature, scalable, and business-friendly environment for open source software collaboration and innovation.
  • Timelords: Community of experts focused on Industrial IoT and time-series data to transform their business focused on collecting, maintaining, and using time-series data.

See more under Growth Plan, Roadmaps

Used in PoCs

Several public Use Cases cases have been documented and implemented on PoCs.

New ones include:

For further info: Use Cases

Substantial ongoing commits and contributions

Fledge LFX Insights (Last Year)

Community participation meets growth plan goals

Several industrial communities in energy verticals have been the main focus but not limited to:

  • Timelords: Community of experts focused on Industrial IoT and time-series data to transform their business focused on collecting, maintaining, and using time-series data.
  • LF Energy: is an open source foundation that focuses on power systems hosted within the Linux Foundation. 
  • OSDU (Open Subsurface Data Universe): The OSDU Forum is developing an open source, standards based, technology agnostic data platform. Primarily focuses on oil and gas and renewables.
  • NIST Team SmartIoT: Team SmartIoT was formed to leverage the breadth and the depth of the experience of the team members in IoT and physics-based flood simulation to address the realistic IoT data generation challenge.
  • UC Davis Winery of the future - Opus One/UC Davis

More information on past and ongoing collaboration can be found here: Cross-LF Edge Collaboration, Fledge Roadmap 2020/2021 and Fledge Home.

Achievements

FledgePOWER

FledgePOWER is a multi-protocol translation gateway for power systems based on the industrial IoT LF Edge project. This cross foundation collaboration between LF Edge and LF Energy ensures strong cooperative governance and technical alignment between the two communities. FledgePOWER aims to build and grow a community of end-users, developers, utilities, and other players to collaborate to solve current and future challenges in the energy space. Further information can be found on FledgePOWER Wiki and Demo

OSDU Edge

OSDU has selected Fledge and EVE as the edge stack architecture for OSDU Edge. Meeting OSDU Edge requirements with LF Edge projects mitigating lock-in through vendor-neutral governance and interoperable solutions. Fledge is now in the OSDU Edge Lab.

The architecture was successfully demoed to OSDU members in October, 2021.

See more under Growth Plan,Roadmaps

Evidence of interoperability, compatibility with other LF Edge projects

The latest Fledge collaboration includes:

More information on past and ongoing collaboration can be found here: Cross-LF Edge Collaboration, Fledge Roadmap 2020/2021 and Fledge Home.

Onboard all project repositories with LFX SecurityLFX Security Fledge

Stage 3: Impact

and SDO hosted a joint demo at ONES-NA last September.  Open Horizon integrates SDO rendezvous services into the management hub and CLI since SDO 1.8, and is continually upgrading that support as new SDO releases come out.  Open Horizon now supports SDO 1.10.  Open Horizon also has a technical and project liaisons to the SDO project.
  • Open Horizon is almost complete with integration into EdgeX Foundry's Sensor Fusion demo, which also updates Open Horizon's EXF integration work.  We're participating in their Kubernetes Support sub-project.  And we just announced our participation in the Open Retail Reference Architecture, an EXF Vertical Solutions WG sub-project, which you're all invited to participate in as well.  We plan to create an Akraino blueprint from this effort.
  • Open Horizon has worked with SOTE by providing project information, updating landscape information, submitting postcards from the edge, and providing a project liaison that regularly attends their meetings.
  • Open Horizon is about to begin collaborating with Fledge on specific deliverables.  We're now in the process of creating a sub-group under the Open Horizon TSC for those efforts.
    • We have plans and ideas about collaborations with EVE and Home Edge, and hope to make further progress on those in 2021.
    RequirementEvidence
    Have a defined governing body of at least 5 or more members (owners and core maintainers)

    The Technical Steering Committee (TSC) has expanded its voting members to 6 as follows:

    • Mark Riddoch - Dianomic - Chair
    • Tom Arthur - Dianomic
    • Daniel Lazaro - AVEVA
    • Benoit Jeanson - RTE
    • Robert Raesemann - Raesemann Enterprises - CoChair
    • Mike Styer - Google
    Documented governance, decision-making, release processes

    Fledge is an independent open-source project and not controlled by any single company. To emphasize this Fledge is governed under the Linux Foundation Edge and has graduated through the different Project Stages: Definitions and Expectations. Fledge is currently a Stage 2 project under this framework. For more information go to the Governance section.

    The following documented processes are in place:

    Healthy number of committers from at least two orgs (A committer is defined as someone with the commit bit; i.e., someone who can accept contributions to some or all of the project)

    Fledge LFX Insights (Last Year) 

    https://github.com/orgs/fledge-iot/teams/fledge-iot-committers

    Image Added

    Establish a security and vulnerability process which at a minimum includes meeting

    OpenSSF Badge

    SECURITY.md

    RequirementEvidence
    Used in PoCs
    1. DLR in Germany has created two pieces of hardware (GeoBox, HofBox) for farmers, and is proposing to work across the country in a public/private partnership program.  This technical project uses Open Horizon as a key component for their offline-first approach to edge computing.
      video link: https://www.dlr.rlp.de/Internet/global/inetcntr.nsf/dlr_web_full.xsp?src=625C012T2W&p1=KID9U06DI1&p3=34F13QLQT4&p4=6WH9QAA7AZ
    2. Foxconn Industrial Internet has ported the Open Horizon agent to work on their 5G AI Box and is using it as an integral piece of their vertical farming solution - MES Agricultural System.  It will be initially featured in their Beijing Client Demo Center.
      video link: demo_EN.mp4
    3. I could list a few other PoCs, but they use a commercial downstream distribution, so I'm not sure if they're valid examples.  For instance, the Port of Barcelona is using it in an MVP to detect and identify boats (and their bow and stern) approaching the harbor, and is using deployed inferencing algorithms to derive the location/position of those boats, all being inferred on the edge.
      link: https://es.newsroom.ibm.com/announcements?item=122614
    Substantial ongoing commits and contributions

    Image Removed Chart from https://tinyurl.com/yykvcfg5 showing commits over the last year.  Notice that the diversity of organizations making commits increased quite a bit beginning in the July timeframe, two months after we officially became an LF Edge project.  Attached are a few slides showing highlights of 2020 project stats.

    Growth planGrowth plan for 2021:
    • Add non-IBM voting members to the TSC (at least 30%)
    • Add 20 or more active volunteer contributors
    • Add three project partners contributing value
    • Bring two new members to LF Edge
    • Create a project web site
    • Mentor twelve new candidates
    • Establish ties with at least one university
    • Publish the beta release of the Open Retail Reference Architecture
    • Launch the Open Edge Services Catalog
    Community participation meets growth plan goals

    Growth plan for 2020:

  • Regular, scheduled TSC and Working Group meetings with active public community participation in Working Groups
    Met
  • Three active SIGs meeting and supporting users and solutions
    Partially Met: Created two SIGs (Manufacturing and Smart Agriculture), and the Open Retail Reference Architecture (ORRA) sub-project
  • Active effort underway with three or more partner organizations to define Open Deployment standards
    Ongoing:     Arnaud Le Hors has volunteered to help lead this effort, will begin with standards around ORRA
  • At least twenty new active (volunteer) contributors
    Missed: 8 new contributors, not 20
  • At least two Partner companies contributing value to the project
    Met: Foxconn Industrial Internet and SoftServe
  • Apply for Stage Two maturity project
    In Progress
    • Investigate opportunities for collaboration with universities
    Ongoing

    Evidence of interoperability, compatibility with other LF Edge projects

    The latest Fledge collaboration includes:

    More information on past and ongoing collaboration can be found here: Cross-LF Edge Collaboration, Fledge Roadmap 2020/2021 and Fledge Home

    Adopt LF Code of conductThe Fledge community adheres to the LF Code of Conduct as described here: Code of Conduct
    Explicitly define a project governance and committer process

    The Fledge community has defined and documented the following Repository Approval Policy as well as the committer process here: CONTRIBUTING.md and project Governance.

    Public list of project adopters

    The Fledge Community welcomes contributions of all types; documentation, code changes, new plugins, scripts, just simply reports of the way you use Fledge or suggestions of features you would like to see within Fledge. A public list of project adopters can be found in ADOPTERS.md

    >= 2/3 approval vote of TAC & majority of Governing Board


    ...