Skip to content

Latest commit

 

History

History
34 lines (30 loc) · 2.44 KB

project-submission-template.md

File metadata and controls

34 lines (30 loc) · 2.44 KB
Raw

Instructions

  1. Review the Project Progression Policy.
  2. Send an email to the TAC mailing list using the following template and attaching any supporting documentation. Any non-applicable response can be listed as N/A.
  3. For any questions or comments on this process please email info@confidentialcomputing.io

Project Proposal Template

General Information

1.1. Name of Project
1.2. Project Description (what it does, why it is valuable, origin and history)
1.3. How does this project align with the Consortium's Mission Statement
1.4. Project website URL
1.5. Social media accounts

Legal Information

2.1. Project Logo URL or attachment (Vector Graphic: SVG, EPS).
2.2. Project license. We recommend an OSI-approved license, so if the license is not one on the list, explain why.
2.3. Existing financial sponsorship.
2.4. Trademark status.

Technical Information

3.1. High level assessment of project synergy with existing projects under the CCC, including how the project compliments/overlaps with existing projects, and potential ways to harmonize over time. Responses may be included both inline and/or in accompanying documentation.
3.2. Describe the Trusted Computing Base (TCB) of the project. If the project supports multiple environments please describe each TCB. Also identify if dependencies of other project (both CCC or non-CCC) TCBs are taken.
3.3. Project Code of Conduct URL. We recommend a Contributor Covenant v2.0 based Code of Conduct, so if the Code of Conduct is not based on that, explain why.
3.4. Source control URL
3.5. Issue tracker URL
3.6. External dependencies (including licenses, and indicate whether each is a build time or runtime dependency)
3.7. Standards implemented by the project, if any. Include links to any such standards.
3.8. Release methodology and mechanics
3.9. Names of initial committers, if different from those submitting proposal
3.10. List of project's official communication channels (slack, irc, mailing lists)
3.11. Project Security Response Policy
3.12. Preferred maturity level (Incubation, Graduation, or Emeritus) 3.13. Any additional information the TAC and Board should take into consideration when reviewing your proposal.