Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Meeting Agenda : 2020-03-23 #57

Closed
romulocintra opened this issue Feb 27, 2020 · 3 comments · Fixed by #71
Closed

Meeting Agenda : 2020-03-23 #57

romulocintra opened this issue Feb 27, 2020 · 3 comments · Fixed by #71

Comments

@romulocintra
Copy link
Collaborator

romulocintra commented Feb 27, 2020

Intl.MessageFormat - WG Meeting

Meeting Notes :Link

Call : Link

TCQ: Link

Agenda

  • Chair Group announcements
  • Review TODO's from last meeting

Next meeting actions/issues

  • Create issues to split topics related with Design Principles Design Principles #50
  • Data Model Discussion, Open issue to design and work on that with examples , discussions etc …
  • Decide/vote : “Big decision we ought to be making: do we really want to be driving all of i18n/l10n to be using one message - format, or do we want to build an environment which can support many or all message formatting languages? All of what we're considering and covering could work with either of those, but they're very different worlds.”
  • Define goals and non-goals of MFWG related with Document why MessageFormat needs a successor #49
@romulocintra
Copy link
Collaborator Author

romulocintra commented Mar 20, 2020

Add to Agenda - Establish the decision making process #58

@romulocintra
Copy link
Collaborator Author

Add to Agenda Goals and Non-Goals #59

@romulocintra
Copy link
Collaborator Author

romulocintra commented Mar 23, 2020

Topic Not Covered: Add to Agenda Design Principle: Data Model vs. Syntax #68 & #64 (Can be reviewed as well)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant