|Table of Contents|
The Linux Foundation Networking umbrella consists of multiple projects. This document describes the lifecycle of those LFN projects.
Each LFN project governs itself. LFN projects may consist of multiple subprojects with their own lifecycles. This document's scope is limited to top-level LFN projects.
LFN projects have a lifecycle that is characterized by Project State that is defined by their project maturity.
|Project State||State Summary|
|Candidate||Projects looking to integrate with the LFN umbrella of projects may be inducted at any lifecycle state, provided it meets The Linux Foundation's proven best practices for success.|
|Sandbox||The Sandbox stage is designed to provide a lightweight entry process for new projects that align with the LFN mission and meet the It is ideal for early-stage projects that require time to explore their community, governance, and technical roadmap. Project proposals should meet the|
|Incubation||The project meets all the conditions for the Sandbox stage, and in addition: The Incubation stage is for projects that have demonstrated progress toward open source best practices, including contributor diversity and open governance, and have a documented release process. Projects in this stage should be actively working on integration with other LFN projects, participating in cross-LFN initiatives, and/or contributing to extending or strengthening the LFN scope.|
|The project meets all the conditions for the Incubation stage, and in addition: The Graduated TAC Project stage is for projects that have met the demonstrated project diversity, adherence to open source best practices, active participation in LFN, and have a documented release process and a history of following it. Projects in this stage have a voting representative on the TAC.|
|Archived||A project can be Archived if it has received no significant commits within the previous 12 months or if the Project's TSC requests archiving. An Archival Review will be initiated to determine if the project meets the criteria for archiving.|
The Linux Foundation advocates several best practices for running a successful open source community. These practices promote a healthy, inclusive, and productive environment for collaboration and innovation. Here are some key best practices:
More details about The Linux Foundation's Best Practices may be found here: https://www.linuxfoundation.org/resources/open-source-guides
Project Benefits by Lifecycle Stage
Each stage of the LFN project lifecycle comes with various benefits and access to resources. The availability of these benefits is dependent on the project's lifecycle stage, and the adoption of services is optional. LFX tooling is available for all projects, regardless of their current stage. New projects joining the LFN are not required to start at a lower lifecycle stage if they already meet the requirements for a higher stage.
- Any open source project that develops technology related to computer networking is welcome to seek induction into the LFN umbrella project.
- The LFN goal is to create the best set networking software projects that address the industry needs. Incoming projects may offer functionality that was not covered before by existing projects and/or provide a new approach in areas that are covered by projects that already exist in LFN.
- Incoming projects may continue to exist as standalone projects for as long as they see fit, or decide to seek merger with existing LFN projects, assuming the will to merge is mutual in both the incumbent and new projects.
- Creating integrations with existing LFN projects is encouraged but not mandated. The LFN provides opportunities for such integrations in the form of super-blueprints, developer forums, and others. Their participation is left to the discretion of the individual project communities.
Project State Transitions
|none||Sandbox||LFN Entry Review Periodic Health Review||LFN Entry Review|
|Sandbox||Incubation||Incubation Review||Incubation Review|
|Incubation||Graduated||TAC Admission Review||Graduated Admission Rvw|
|Graduated||Incubation||Incubation Reversal Review|
|none||LFN Exit Review||LFN Exit Review|
An open source project may request a review from the Technical Advisory Council at any time. Project Reviews are held for a variety of reasons. For each review, the project must instantiate the Project Data Template. If the project has already submitted a template for a past review, they can update it (taking into account any changes to the base template) for the new review.
Reviews must be conducted in a manner that allows a global community to participate. For example, at a time that is amenable to as many stakeholders as possible and using tooling that is generally accessible.
LFN Entry Review
The LFN Board and TAC both evaluate proposals for new projects to be admitted into the LFN. Projects can be inducted at any level of maturity, provided they meet the necessary requirements. The TAC conducts the review first, followed by the Board.
Information and Criteria for TAC LFN Entry Review
To apply for an LFN Entry Review, projects must provide an up-to-date Project Data Template, and inbound code must pass an "intake scan" as defined by LF Legal. The review focuses on the project's accessible governance, which must minimally specify project roles, release processes, decision-making bodies, dispute resolution mechanisms, and more. The review also checks whether the project scope is within the scope of the LFN.
Criteria for LFN Entry Review
Mandatory criteria for successful completion of the LFN Entry Review is documented governance that is clear, complete, and easily and obviously accessible (such as a link from the project's main page). That governance must minimally specify:
Additionally, the review will confirm that the incoming project scope is within the scope of the LFN and a recommended lifecycle entry state.
Outcome for LFN Entry Review
As an outcome of the TAC's LFN Entry Review, the TAC will provide the following feedback to the LFN Governing Board for use as input to the LFN Board's LFN Entry Review:
- Summary of findings
- Recommendation to accept the project into LFN or not.
Board LFN Entry Review
It is up to the Board to define its own criteria and process of the Board's LFN Entry Review. Such review may include legal, trademark, and license reviews. The TAC strongly recommends the Board make its LFN Entry Review criteria and process public and accept design input from the public.
Budget Guidance: The TAC recommends that the governing board allocate no or limited funding to Sandbox projects and that those projects cannot use cross-project funding buckets. Sandbox projects should still be able to take advantage of LFN membership that does not require additional funding, such as logo inclusion in marketing materials or attendance at LFN events.
Projects inducted in the Sandbox state will have their community reviewed on a periodic basis by the TAC. The goal of the health review is to assist the projects in their participation in LFN and ensure the project's community remains healthy. The reviews will be based on the content available from LFX tools to minimize the burden on the project's community.
Similar to the LFN Entry Review, proposals for projects moving to the Incubation state will be reviewed by the TAC and the Board. TAC Incubation Reviews should happen periodically, with the goal of ensuring that the project remains healthy. The reviews will be based on the content available from LFX tools to minimize the burden on the project's community.
Criteria for Incubation Review
Mandatory criteria for successful completion of the Incubation review is the documented demonstrable progress since induction toward open source best practices. This would include but is not limited to contributor diversity and open governance, and the release process.
As part of Incubation Reviews, the TAC should identify how the project fits with other LFN projects, including any overlap or harmonization potential.
Outcome for Incubation Review
As an outcome of the TAC's Incubation Review, the TAC will provide the following feedback to the LFN Governing Board for use as input to the LFN Board's Incubation Review:
- Summary of findings
- Recommendation to accept the project into the Incubation stage or not.
Board Incubation Review
It is up to the Board to define its own criteria and process for the Board's Incubation Review. The TAC strongly recommends the Board make its Incubation Review criteria and process public and accept design input from the public. The reviews will be based on the content available from LFX tools to minimize the burden on the project's community.
Budget Guidance: The TAC recommends to the board that any new Incubation project not erode existing TAC project budgets.
Annual Health Review
The TAC should review all projects on an annual basis. The goal of the annual health review is to assist the projects in their participation in LFN, ensure the project's community remains healthy, and, where appropriate, assist the project in transitioning the lifecycle stage of the Project.
Graduated Project Review
Projects advancing to the Graduated Project state undergo a review process by both the TAC and the Board. This review is triggered by a TAC Request from a Project and allows the TAC to decide whether the Project should have TAC representation.
Criteria for Graduated Project Review
Mandatory criteria for successful completion of the Graduated Project Reviews are maintenance of the criteria for LFN Entry, a demonstration of adequate project diversity, a clearly defined release process, a history of following it, and documented information on how to participate in the community. The project should also show demonstrable progress in integrating security design principles and security testing into their SDLC.
As an additional (non-mandatory) guideline, the project should show continued progress in marketplace adoption.
Outcome for Graduated Project Review
As an outcome of the Review, the TAC will provide the following feedback to the LFN Governing Board for use as input to the LFN Board's Review:
- Summary of findings
- Recommendation to accept the project into the Graduated Project stage or not.
Board Graduated Project Review
It is up to the Board to define its own criteria and process of the Board's Review. The TAC strongly recommends the Board make its TAC Review criteria and process public and accept design input from the public.
Budget Guidance: The TAC recommends to the board that any new TAC project receives funding through the existing board and TAC process for determining budget priorities.
A project, whether in the Graduated or Incubation state, may be reverted to a previous lifecycle state if the TAC, by majority vote, determines that the project no longer fulfills the criteria for its current status. Additionally, if the Project's Technical Steering Committee (TSC), by majority vote, requests to move the project back to a lower lifecycle state. Before initiating a Reversion to a different lifecycle state, the TAC must make a sincere effort to reach out to the Project's TSC to discuss the project's future.
Criteria for Reversal Reviews
The mandatory criteria for moving a TAC project to a lower lifecycle state are one of:
- A direct request from the Project to be moved to a different lifecycle state
- Clear signs of reduced project activity resulting in the project no longer meeting the criteria for its current status, such as project diversity, adherence to open source best practices, or overall LFN participation. This should also include evidence of the TAC's sincere effort to engage the Project's TSC in a constructive discussion.
Outcome for Reversal Review
The TAC will notify the Board immediately of any decision to move a project back to lower lifecycle states.
A Project may be Archived if it has received no significant commits within the previous 12 months or by a majority vote of the Project's TSC to request the project be Archived. Prior to TAC initiation of an Archival Review of a Project, a good faith effort must be made to contact the Project's TSC and initiate a dialog about the future of the Project.
Criteria for Archival Review
Mandatory criteria for Archiving a project are one of:
- A clear request from the Project to be archived.
- Clear evidence that the project has received no significant commits within the previous 12 months and a demonstration of a good faith effort by the TAC to contact the Project's TSC and come to a positive resolution.
Outcome for Archival Review
The TAC will notify the Board immediately of any decision to Archive a project.
A Project may be revived by following the same steps as an Entry Review.
LFN Exit Review
A Project may request to leave the LFN by a majority vote of its TSC.
The Board may cause a project to exit LFN at its discretion.
Recommendations to Candidate Project
The TAC will provide the following feedback to the candidate projects for all reviews.
- If TAC recommends that the candidate project lifecycle state transition be approved, the TAC will provide recommendations for improving the project.
- If TAC recommends that the candidate project lifecycle state transition not be approved, the TAC will give feedback about which criteria the project did not adequately meet and what changes to the candidate project would be required to change the TAC's recommendation.
Disposition of Existing Projects
As of , OpenDaylight, Anuket, FD.io, and ONAP are in state Graduated (TAC). Tungsten Fabric is in state Incubation. EMCO, XGVela, L3AF and ODIM are in a state of Sandbox.
Amendment of Technical Governance
This Technical Governance may be amended by a 2/3 vote of the TAC subject to approval by the LFN Board.