Skip to content
This repository has been archived by the owner on Feb 29, 2020. It is now read-only.

Update Intl WG README to reflect decharter #47

Merged
merged 1 commit into from
Feb 19, 2018
Merged

Update Intl WG README to reflect decharter #47

merged 1 commit into from
Feb 19, 2018

Conversation

srl295
Copy link
Member

@srl295 srl295 commented Feb 16, 2018

In light of nodejs/TSC#353 and the new https://github.com/nodejs/i18n WG, change the landing page of the Intl WG to reflect its status. FYI @obensource and nodejs/community-committee#114


(FYI current WG members, please consider joining https://github.com/nodejs/i18n if desired:

@srl295 srl295 self-assigned this Feb 16, 2018
@srl295 srl295 changed the title decharter Update Intl WG README to reflect decharter Feb 16, 2018
@srl295
Copy link
Member Author

srl295 commented Feb 16, 2018

I think there are still some useful issues here. Some of them have been fixed (I did some updates)

Trott

This comment was marked as off-topic.

@srl295
Copy link
Member Author

srl295 commented Feb 16, 2018

@Trott Can I finish your march through the issues which I started then, before archiving? I think there are a few that could be useful.

  • March through the issues, close, and maybe move to i18n (pending discussion w/ @obensource and i18n WG )

@Trott
Copy link
Member

Trott commented Feb 16, 2018

@srl295 Sure.

joyeecheung

This comment was marked as off-topic.

@srl295 srl295 merged commit 336a9a1 into master Feb 19, 2018
@srl295 srl295 deleted the to-i18n branch February 19, 2018 16:52
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants