1 *********************************************
2 Linux Foundation Networking Project Lifecycle
3 *********************************************
8 The Linux Foundation Networking umbrella consists of multiple projects. This
9 document describes the lifecycle of those LFN projects.
11 Each LFN project governs itself. LFN projects may consist of multiple
12 subprojects with their own lifecycles. This document's scope is limited to
13 top-level LFN projects.
18 LFN projects have a lifecycle. That lifecycle is characterized by Project
19 States and State Transitions.
24 +---------------+-------------------------------------------------------------+
25 | Project State | State Summary |
26 +===============+=============================================================+
27 | Non-LFN | Project does not exist or exists outside of LFN. |
28 +---------------+-------------------------------------------------------------+
29 | Non-TAC | Project is admitted to the LFN but does not have a |
30 | | representative on the TAC. |
31 +---------------+-------------------------------------------------------------+
32 | TAC | Project is granted TAC representation. |
33 +---------------+-------------------------------------------------------------+
34 | Archived | Project is no longer active. |
35 +---------------+-------------------------------------------------------------+
37 Project State Transitions
38 =========================
40 +--------------+-------------------+----------------------+-------------------+
41 | From State | To State | TAC Review | Board Review |
42 +==============+===================+======================+===================+
43 | Non-LFN | Non-TAC | LFN Entry Review | LFN Entry Review |
44 +--------------+-------------------+----------------------+-------------------+
45 | Non-TAC | TAC | TAC Admission Review | |
46 +--------------+-------------------+----------------------+-------------------+
47 | * | Archived | Archival Review | |
48 +--------------+-------------------+----------------------+-------------------+
49 | * | Non-LFN | LFN Exit Review | LFN Exit Review |
50 +--------------+-------------------+----------------------+-------------------+
55 For each review, the project must instantiate the Project Data Template. If the
56 project has already submitted a template for a past review, they can update it
57 (taking in to account any changes to the base template) for the new review.
59 Additionally, a project must publicly announce their intention to undergo a
60 review at least two weeks prior to the date of the review. The announcement
61 must include a link to the instantiated Project Data Template for the review.
62 The public may comment on the document. The project must engage with comments,
63 answer questions and address feedback.
65 Reviews must be conducted in a manner that allows a global community to
66 participate. For example, at a time that is amenable to as many stakeholders as
67 possible and using tooling that is generally accessible.
72 The Board and the TAC both review proposals for new LFN projects.
77 Review by the TAC for creating new projects under the LFN or admitting existing
78 non-LFN projects into the LFN.
80 TAC LFN Entry Reviews should happen before, and provide input into, Board LFN
83 Required Information for TAC LFN Admission Review
84 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
86 An up-to-date instantiation of the Project Data Template is required for an LFN
89 Criteria for TAC LFN Admission Review
90 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
92 Mandatory criteria for successful completion of the LFN Entry Review is
93 documented governance that is clear, complete, and easily and obviously
94 accessible (such as a link from of the project's main page). That governance
95 must minimally specify:
98 * How people come to fill project roles.
99 * How people are removed from project roles.
100 * Who currently fills all project roles.
101 * How disputes are definitively resolved (usually by majority vote).
102 * How the governance evolves over time.
103 * What is the top level technical decision making body for the project,
104 analogous to a TSC, to which the TAC should look for interfaces.
106 Outcome for TAC LFN Admission Review
107 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
109 As an outcome of the TAC's LFN Entry Review, the TAC will provide the following
110 feedback to the LFN Governing Board for use as input to the LFN Board's LFN
113 * Summary of findings
114 * Recommendation to accept the project into LFN or not.
116 Board LFN Entry Review
117 ++++++++++++++++++++++
119 It is up to the Board to define its own criteria and process of the Board's LFN
120 Entry Review. The TAC recommends the Board make its LFN Entry Review criteria
121 and process public and accept design input from the public.
126 The TAC Admission Review is intended for the TAC to consider whether a
127 Non-TAC Project should have a representative on the TAC. It is initiated by a
128 TAC Admission Request from the Non-TAC Project.
130 Required Information for TAC Admission Review
131 +++++++++++++++++++++++++++++++++++++++++++++
133 An up-to-date instantiation of the Project Data Template is required for a TAC
136 Criteria for TAC Admission Review
137 +++++++++++++++++++++++++++++++++
139 Mandatory criteria for successful completion of the TAC Admission Review are
140 maintenance of the mandatory criteria for LFN Entry and demonstration of
141 adequate project Diversity, a clear statement of how the Project will select
142 its TAC Representative and adherence to the LFN Principles.
144 Outcome for TAC Admission Review
145 ++++++++++++++++++++++++++++++++
147 Upon approval by the TAC of the Admission of a project to the TAC that project
148 will be considered a TAC project. The TAC will notify the Board immediately of
154 A Project may be Archived if it has received no significant commits within the
155 previous 12 months or by a majority vote of the Project's TSC to request the
156 project be Archived. Prior to TAC initiation of an Archival Review of a
157 Project, a good faith effort must be made to contact the Project's TSC and
158 initiate a dialog about the future of the Project.
160 Criteria for Archival Review
161 ++++++++++++++++++++++++++++
163 Mandatory criteria for Archiving a project are one of:
165 * A clear request from the Project to be archived.
166 * Clear evidence of the project has received no significant commits within the
167 previous 12 months and demonstration of a good faith effort by the TAC to
168 contact the Project's TSC and come to a positive resolution.
170 Outcome for Archival Review
171 +++++++++++++++++++++++++++
173 The TAC will notify the Board immediately of any decision to Archive a project.
178 A Project may request to leave the LFN by majority vote of its TSC.
180 Should a project request to leave the LFN, it is the obligation of the TAC to
181 forward that request to the Board immediately upon notification.
183 The Board may cause a project to exit LFN at their discretion.
185 Recommendations to Candidate Project
186 ------------------------------------
188 The TAC will provide the following feedback to the candidate projects for all
191 * If TAC recommends that the candidate project lifecycle state transition be
192 approved, the TAC will provide recommendations for improving the project.
193 * If TAC recommends that the candidate project lifecycle state transition not
194 be approved, the TAC will give feedback about which criteria the project did
195 not adequately meet and what changes to the candidate project would be
196 required to change the TAC's recommendation.
198 Disposition of Existing Projects
199 --------------------------------
201 OpenDaylight, OPNFV, FD.io, and ONAP are in state TAC. PNDA and SNAS are in
202 state Non-TAC. Tungsten Fabric was `conditionally inducted by the Board
203 <tf-condit-induct-email_>`__ as Non-TAC and should do an LFN Entry Review once
204 the process is established.
206 .. _tf-condit-induct-email: https://lists.lfnetworking.org/g/TAC/message/250
208 Amendment of Technical Governance
209 ---------------------------------
211 This Technical Governance may be amended by a 2/3 vote of the TAC subject to
212 approval by the LFN Board.