Status
- Presented to the TAC:
- TAC Project Review:
- Subgroup Review Meeting:
- Subgroup Readout:
- TAC Vote Approved:
- 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 large, well-established project communities with a number of contributors from at least two organizations.
Examples
- Projects that have publicly documented release cycles and plans for LTS.
- Projects that have themselves become platforms for other projects.
- Projects that are able to attract a healthy number of committers on the basis of its production usefulness (not simply 'developer popularity').
- Projects that have several, publicly known, end-user deployments.
Expectations
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.
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 plus Impact stage criteria:
Stage 2: Growth requirements:
- 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 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).
- 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.
- 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), 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.
- 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).
- 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 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 |
|---|
| 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.
Beyond the LF Edge community, Fledge focuses on industrial use cases so one of the primary goals is to meet the industrial communities outside of LF Edge where they do. Two main industrial communities in energy verticals have been the main focus but not limited to: - 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.
See more under Growth Plan. |
| Used in PoCs | Several public Use Cases cases have been documented and implemented on PoCs. New ones include:
|
| Substantial ongoing commits and contributions | |
| Community participation meets growth plan goals | LF Energy - FledgePower: FledgePOWER is a multi-protocol translation gateway for power systems based on the industrial IoT LF Edge project. Fledge. FledgePower Wiki for further information. OSDU has selected Fledge and EVE as the edge stack architecture for OSDU Edge. |
| Evidence of interoperability, compatibility with other LF Edge projects | Fledge Roadmap 2020/2021 Cross-LF Edge Collaboration |
Stage 3: Impact