Fledge - Mature to Stage Three (Impact)

Owned by Daniel Lazaro
Last updated: Apr 13, 2023 by Kendall Perez
8 min read

Status

  • Presented to the TAC: March 22, 2023

  • TAC Project Review:

    • Subgroup Review Meeting: April 3, 2023

    • Subgroup Readout: 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 on a self-sustaining cycle of development, maintenance, and long-term support. Impact Stage projects are widely used in production environments with a significant number of public use cases. Moreover they have broad, well-established communities with a number of 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.

Benefits

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 a project must meet the Growth stage criteria plus:

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 goals outlined in the growth plan.

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

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

  • 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 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 in a GOVERNANCE.md file and references a CONTRIBUTING.md and OWNERS.md 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 logos on the project website).

  • Receive a two-thirds vote of all 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

Requirement

Evidence

Requirement

Evidence

Demonstrate regular project leadership

Technical 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 Security

LFX Security Fledge

Stage 3: Impact

Requirement

Evidence

Requirement

Evidence

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

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

OpenSSF Badge

SECURITY.md

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 conduct

The 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