New charter proposal, reviewers please take note.
Charter Review
Draft Charter
Note that is it still using an old version of the template, changes were made from the last charter, update to the new template is in progress.
diff from charter template
Expected end of charter refinement phase: unknown
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.
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, ...)
Use "webtransport" label
Anything else we should think about as we review?
Note: proposed chairs should be copied @... on this issue.
@wilaw @jan-ivar
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
Draft Charter
Note that is it still using an old version of the template, changes were made from the last charter, update to the new template is in progress.
diff from charter template
Expected end of charter refinement phase: unknown
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.
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, ...)
Use "webtransport" label
Anything else we should think about as we review?
Note: proposed chairs should be copied @... on this issue.
@wilaw @jan-ivar
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.