You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This directory contains the meeting notes, process documentations, and other materials related to this project.
Project Intake checklist
This is a checklist for TSC's to review as part of the intake process. The TSC should review this entire list during the kickoff meeting. For anything outstanding, create an issue to track and link to it in the list
Copy this checklist to a project specific location for tracking
Acceptance Criteria
Have an open and documented 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.
A CONTRIBUTING file explaining to other developers and your community of users how to contribute to the project. The file should explain what types of contributions are needed and how the process works.
A CODE_OF_CONDUCT file that sets the ground rules for participants’ behavior associated and helps to facilitate a friendly, welcoming environment. By default projects should leverage the Linux Foundation Code of Conduct unless an alternate Code of Conduct is approved prior.
Complete and approve 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.
Demonstrate growth in the project’s community, including
Growth in the number of commits to the project, number of project committers, and organizational diversity of contributions and committers.
Production or planned production use of the project by at least two independent end users which, in the TAC’s judgment, are of adequate quality and scope.
Technical Governance of the project is operational, as measured by:
A Technical Steering Committee with at least 5 members and a chairperson elected by the members, holding regular open meetings.
Development of a growth plan, to be done in conjunction with their project mentor(s) at the TAC. This plan should address the following points:
Release plans for the next 18 months.
Target end-users.
Identification of any regulatory or standards body requirements for deployment, and plans for implementation.
Plans for growth of project contributors and committers to support the growth plan.
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.
Identification of any infrastructure resources needed to fulfill the growth plan.
Prepare and schedule presentation to the TAC of the project’s growth, technical governance, and growth plan ( link to presentation deck )
Receive the affirmative majority vote of the TAC and Governing Board
Graduated Project 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 fulfilled or are on track to complete the growth plan defined in the Early Adoption stage proposal.
Have a healthy number of contributions or committers from at least three organizations, with any one organization not composing more than 50% of the contributions or committers. Committers must be identified within the project in a COMMITTERS file.
Have a public list of project adopters for at least the primary repo (e.g., ADOPTERS.md or logos on the project website).
Achievement of the Core Infrastructure Initiative Best Practices badge at the Gold level.
Prepare and schedule presentation to the TAC on the fulfillment of these requirements ( provide link to presentation ).
Receive a ⅔ majority vote from the TAC a to move to Graduated stage ( provide date ).
Prepare and schedule presentation to the Governing Board on the fulfillment of these requirements ( provide link to presentation ).
Receive a majority vote of the Governing Board to move to Graduated stage ( provide date ).
The text was updated successfully, but these errors were encountered:
TSC Materials for Arras Energy
This directory contains the meeting notes, process documentations, and other materials related to this project.
Project Intake checklist
This is a checklist for TSC's to review as part of the intake process. The TSC should review this entire list during the kickoff meeting. For anything outstanding, create an issue to track and link to it in the list
tsc
directory in main repo, and thenmeetings
under thetsc
directory )The text was updated successfully, but these errors were encountered: