note: the purpose of a project charter is to provide a brief introduction to the project from a technical, community, or business 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
directions: describe how the project intersects with the Cross Project Council.
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 or by reference to a governance.md document.
directions: describe the roles and responsibilities of the ${PROJECT} Governing Body.
ex. K8s SIG Architecture Charter ex. Node.js TSC 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'.
ex. K8s SIG Architecture Charter ex. Node.js TSC Charter
directions: describe any provisions the project makes for decision-making or include the information by reference your governance.md document. If you are not using this section, please indicate your intent with the phrase, 'Section Intentionally Left Blank'.
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'.