Charter Guide

Each HCA DCP project must have a charter that specifies its scope, responsibilities, and leadership roles.

The charter process provides a simple and consistent path for new projects to be formed that align with the direction and priorities of the HCA DCP.

What the process is

Fork the HumanCellAtlas dcp-community repository
Make a subdirectory named charters/MYPROJECTNAME
Copy charters/charter-template.md to charters/MYPROJECTNAME/charter.md
Fill in the charter with attention to detail
Submit a pull request. Add the "charter-proposed" label
Share a link to the pull request for community review on the HumanCellAtlas #dcp slack channel
Feedback is added to the pull request comment thread by community members. The Science PM (or a delegate) reviews for appropriate oversight from HCA Science governance.
Update the pull request in response to feedback

For charters with software deliverables:

Share a link to the pull request for approval on the HumanCellAtlas #tech-architecture slack channel when all feedback is addressed. Replace "charter-proposed" with "charter-final-review".
The request will be discussed at the next meeting of DCP Architecture (Technical Leads). If approved, the Technical Leads replace "charter-final-review" with "charter-approved" and merge the pull request. If rejected, the Technical Leads replace "charter-final-review" with "charter-rejected" and add a rationale to the pull request comment thread.

For charters with governance or process deliverables:

Share a link to the pull request for approval on the HumanCellAtlas #dcp-project-mgmt slack channel when all feedback is addressed. Replace "charter-proposed" with "charter-final-review".
The request will be discussed at the next meeting of DCP PM (Project Leads and Product Owners). If approved, the PM(s) replace "charter-final-review" with "charter-approved" and merge the pull request. If rejected, the PM(s) replace "charter-final-review" with "charter-rejected" and add a rationale to the pull request comment thread.