Draft new charter and goals for v49/v50 and beyond #1065
Conversation
|
@macchiati @eemeli Comments on this initial bit, please. |
aphillips
added
the
organizational
| and other appropriate materials to include a user guide, MF1 migration guide, | ||
| implementation support, and usage materials while maintaining a high bar | ||
| as a model for other Unicode websites. | ||
| - Support a determination there are at least ### additional interoperable implementations. |
There was a problem hiding this comment.
This seems more like a measure of how well we've succeeded at the preceding goal.
| - Support a determination there are at least ### additional interoperable implementations. |
There was a problem hiding this comment.
The is a strawman for an implementation goal. Yes, it's a measure of how well our documentation has worked, but I envision a slightly more muscular approach to platforms teams (especially members)
| - Support migration and adoption by moving all functions and options necessary to match the features of | ||
| ICU MessageFormat ("MF1") to Stable. |
There was a problem hiding this comment.
This needs some qualifiers, as e.g. ChoiceFormat is still technically valid MF1, and there are places (e.g. datetime skeletons) where we're considering shipping a strict subset of the MF1 capabilities.
| ## Deliverables | ||
|
|
||
| The original deliverables were: |
There was a problem hiding this comment.
What's the utility of retaining this? If there is a need, then the section title ought to be qualified to reflect the status.
There was a problem hiding this comment.
It's temporary while we work through the current charter.
Co-authored-by: Eemeli Aro <[email protected]>
Co-authored-by: Eemeli Aro <[email protected]>
Co-authored-by: Eemeli Aro <[email protected]>
Fixes #1051