Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 33 additions & 1 deletion lifecycle-policy/project-lifecycle-policy.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,6 +72,38 @@ Every NeoNephos Foundation project has an associated maturity level. Proposed pr

Representatives from all projects may attend TAC meetings and contribute work regardless of their stage.

### Sandbox Stage

#### Definition

Sandbox projects are projects which the TAC believes are worthwhile to pursue but are either temporary or do not fulfill the criteria of the other maturity levels. The Sandbox stage provides a low threshold way to ensure projects are nurtured by the NeoNephos ecosystem, even if they are experimental or otherwise not in alignment with the other stages.

##### Examples

* New projects that may only have a proof-of-concept.
* Experimental projects that are worthwhile to pursue in the eyes of the TAC.

##### Expectations

A project can remain a Sandbox project for a maximum of one year. Sandbox projects are experimental and their output is not intended to be used in production. Projects that release production-ready artifacts should transition to a more mature stage.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You might want to give the TAC some wiggle room here that allows the TAC to extend being in Sandbox longer under certian circumstances.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you think about:

A project can remain a Sandbox project for a maximum of one year unless extended by the TAC.


##### Acceptance Criteria

To be considered for the Sandbox Stage, the project must meet the following requirements:
* Submission of the Project Proposal, as defined above.
* Have a charter document with an intellectual property policy that leverages open licenses, including, in the case of contributions of code, the use of one or more licenses approved as "open" by the Open Source Initiative. The staff of the NeoNephos Foundation can assist projects in preparing a technical charter following the NeoNephos Foundation’s standard template.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd recommend replacing L94-95 with:

  • Complete and approve the Technical Charter and agree to transfer any relevant trademarks and/or assets to Linux Foundation Europe, and to assist in filing for any relevant unregistered ones.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good, thanks.

* In the case of existing projects, an agreement to transfer the project name and electronic account assets (source code repository, social media accounts, domain names, etc.) to Linux Foundation Europe for the benefit of the NeoNephos Foundation.

##### Approval Process

Once the above Acceptance Criteria have been completed, the project will be scheduled to present their project at an upcoming TAC meeting.

After the review, to be accepted at the Sandbox Stage, the project must receive a simple majority of the TAC.

##### Benefits

Sandbox projects can prominently display on their website/README their status as a NeoNephos Foundation Sandbox Project. Projects at the Sandbox Stage will receive support from the NeoNephos Foundation in support of the Project’s progression.

### Incubation Stage

#### Definition
Expand Down Expand Up @@ -197,4 +229,4 @@ For projects at the Emeritus stage, the NeoNephos Foundation will continue to ho

The TAC shall develop an annual review process to determine whether projects are in the stage that accurately reflects their needs and goals.

Projects are not required to have their annual review approved, nor will the TAC need to renew a project annually. Instead, the TAC can vote to change the project’s lifecycle stage per the approval requirements listed for each Stage above.
Projects are not required to have their annual review approved, nor will the TAC need to renew a project annually. Instead, the TAC can vote to change the project’s lifecycle stage per the approval requirements listed for each Stage above.