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 large, well-established project communities with a number of contributors from at least two organizations.
Examples
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.
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 plus Impact stage criteria:
Compliance with Requirements
Requirement | Evidence |
---|---|
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.
The Fledge community has identified 4 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.
See more under Growth Plan. |
Used in PoCs | Several public Use Cases cases have been documented and implemented on PoCs. New ones include:
For further info: Fledge Home |
Substantial ongoing commits and contributions | |
Community participation meets growth plan goals | Two main industrial communities in energy verticals have been the main focus but not limited to:
More information on past and ongoing collaboration can be found here: Cross-LF Edge Collaboration, Fledge Roadmap 2020/2021 and Fledge Home. AchievementsFledgePOWERFledgePOWER 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: OSDU EdgeOSDU 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. The architecture was successfully demoed to OSDU members in October, 2021. See more under Growth Plan. |
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. |
Requirement | Evidence |
---|---|
Governing body of at least 5, no more 1/3 from same employer | The Technical Steering Committee (TSC) has expanded its voting members to 6 as follows:
|
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 | |
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 and here Fledge Roadmap 2020/2021. |
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 here. For a complete list: Fledge Home. |
>= 2/3 approval vote of TAC & majority of Governing Board |