Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move Technical Charter and license scan requirements to the Sandbox s… #824

Merged
merged 2 commits into from
Oct 10, 2024
Merged
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
4 changes: 2 additions & 2 deletions process/lifecycle.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,8 @@ Projects submitted to the Academy Software Foundation at the Sandbox Stage are i

To be accepted at the Sandbox stage, a project must:

* Have completed and approved the Technical Charter and agree to transfer any relevant trademarks to The Linux Foundation or its affiliate, LF Projects, LLC, and to assist in filing for any relevant unregistered ones.
* Have had a successful license scan with any critical issues remedied.
* Submit a completed [Project Contribution Proposal Template](proposal_template.md) to the TAC.
* Provide such additional information as the TAC may reasonably request.
* Present the project’s proposal to the TAC. Project teams should be prepared to present a detailed (20-30 minutes in length) overview of the project and speak to the information in the contribution proposal.
Expand Down Expand Up @@ -81,13 +83,11 @@ A project at the Incubation Stage has begun to form a community and develop its

To be accepted at the Incubation stage, a project must meet the Sandbox requirements plus:

* Have completed and approved the Technical Charter and agree to transfer any relevant trademarks to The Linux Foundation or its affiliate, LF Projects, LLC, and to assist in filing for any relevant unregistered ones.
* Have defined its technical governance, including:
* A README file welcoming new community members to the project and explaining why the project is useful and how to get started ( follow the guidelines at the [README checklist](https://github.com/ddbeck/readme-checklist) to create an excellent README file ).
* A CODEOWNERS or COMMITTERS file to define individuals or teams responsible for code in a repository; document current project owners and current and emeritus committers.
* A RELEASE file that documents the release methodology, cadence, criteria, etc.
* Have achieved and maintained an OpenSSF Best Practices Badge at the [Passing Level](https://bestpractices.coreinfrastructure.org/en/criteria).
* Have had a successful license scan with any critical issues remedied.
* Have a defined project mission and scope
* An overview of the project’s architecture and features defined ( equivalent to the [documentation_architecture](https://www.bestpractices.dev/en/criteria?details=true&rationale=true#1.documentation_architecture) OpenSFF Best Practices Silver Level badge requirement. )
* A documented project roadmap ( equivalent to the [documentation_roadmap](https://www.bestpractices.dev/en/criteria?details=true&rationale=true#1.documentation_roadmap) OpenSFF Best Practices Silver Level badge requirement. )
Expand Down