note: the purpose of a project charter is to provide a brief introduction to the project from a technical and community perspective. The document also connects a project's community leadership and governance with the OpenJS Foundation's governance.
directions: provide a concise, high-level statement about the project's long-term principles, values, or mission.
ex. Electron Governance Charter ex. AMP Charter
directions: Include a 3-4 sentence summary of what the project does, and/or what problems it solves. Imagine trying to explain your work to a colleague who is familiar with related technical concepts but unfamiliar with the project. You may also want to describe the project's value to community and/or business stakeholders.
ex. K8s SIG Architecture Charter
directions: list or bullet out problem spaces, use cases, repositories or other projects which are included with the work but may not be readily apparent. This may help differentiate the project from other solutions in the space. If you are not using this section, please indicate your intent with the phrase, 'Section Intentionally Left Blank'.
ex. K8s SIG Architecture Charter
directions: list or bullet out areas that may be seen to be related but are not included in the scope of this project. This may help clarify the kind of features, contributions, issues or problems the project is looking for. If you are not using this section, please indicate your intent with the phrase, 'Section Intentionally Left Blank'.
ex. K8s SIG Architecture Charter
The OpenJS Cross Project Council (CPC) delegates technical leadership of this project to the governing body defined in Section 3 of this charter.
This project is entitled to representation in the CPC through voting members as described in Section 4 of the CPC Charter.
directions: describe any additional affiliations or groups that liaise with the project in a formal way (such as a W3C Community Group, for example). If you are not using this section, please indicate your intent with the phrase, 'Section Intentionally Left Blank'.
directions: describe the structure of the group responsible for managing the project and its respective organization and repositories. If there are specific rules for membership or participation in the group, list them here.
The responsibilities of this project's governing body are described in Section 6 of the CPC Charter.
directions: use this section to describe any other specific tasks the ${PROJECT} Governing Body may be responsible for regarding process or project operations and management. If you are not using this section, please indicate your intent with the phrase, 'Section Intentionally Left Blank'.
directions: the recommendation is to adopt the CPC decision-making and voting processes, as described in Section 9 and 10 of the CPC Charter. If so, just leave the below text. Alternatively, replace the below text with a different process.
Decision making and voting follow the practices adopted by the CPC and described in Section 9 and Section 10 of the CPC Charter respectively.
directions: please describe any election mechanism you might have below.
directions: describe other roles within the project, such as chairperson, tech lead, collaborator, contributor, maintainer, etc. and any responsibilities or rights such role confers. You can also include this information by reference to your governance.md document. If you are not using this section, please indicate your intent with the phrase, 'Section Intentionally Left Blank'.
directions: include any definitions that may help clarify terms or ideas found in this charter document. If you are not using this section, please indicate your intent with the phrase, 'Section Intentionally Left Blank'.
Changes to this document require approval from the CPC.