New charter proposal, reviewers please take note.
Charter Review
Charter
diff from charter template
Expected end of charter refinement phase: unknown
If applicable:
diff from previous charter
chair dashboard
What kind of charter is this? Check the relevant box / remove irrelevant branches.
Horizontal Reviews: apply the Github label "Horizontal review requested" to request reviews for accessibility (a11y), internationalization (i18n), privacy, security, and TAG. Also add a "card" for this issue to the Strategy Funnel.
Substantive changes
Short description (or link to it) of the substantive changes in this charter. Use "None or N/A" otherwise.
- Adding new module (specification) but within current scope
- (Still under investigation) Plan to bring modules to REC, while Core API remains living model in CR
Communities suggested for outreach
Known or potential areas of concern
Where would charter proponents like to see issues raised? (this strategy funnel issue, a different github repo, email, ...)
Anything else we should think about as we review?
- No CRS updated during current charter period yet.
Note: proposed chairs should be copied @... on this issue.
/cc @AdaRoseCannon @Yonet (co-chairs)
Note: The Technical Strategy Team Lead or Project & Process Team Lead will assign the issue to a Charter Facilitator for new charters. For rechartering, the team contact is the Charter Facilitator by default, please assign the issue to them directly.
New charter proposal, reviewers please take note.
Charter Review
Charter
diff from charter template
Expected end of charter refinement phase: unknown
If applicable:
diff from previous charter
chair dashboard
What kind of charter is this? Check the relevant box / remove irrelevant branches.
Horizontal Reviews: apply the Github label "Horizontal review requested" to request reviews for accessibility (a11y), internationalization (i18n), privacy, security, and TAG. Also add a "card" for this issue to the Strategy Funnel.
Substantive changes
Short description (or link to it) of the substantive changes in this charter. Use "None or N/A" otherwise.
Communities suggested for outreach
Known or potential areas of concern
Where would charter proponents like to see issues raised? (this strategy funnel issue, a different github repo, email, ...)
Anything else we should think about as we review?
Note: proposed chairs should be copied @... on this issue.
/cc @AdaRoseCannon @Yonet (co-chairs)
Note: The Technical Strategy Team Lead or Project & Process Team Lead will assign the issue to a Charter Facilitator for new charters. For rechartering, the team contact is the Charter Facilitator by default, please assign the issue to them directly.