@@ -29,6 +29,7 @@ back in to the TSC.
2929* [ Addon API] ( #addon-api )
3030* [ Starting a Working Group] ( #starting-a-wg )
3131* [ Bootstrap Governance] ( #bootstrap-governance )
32+ * [ Intl] ( #Intl )
3233
3334### [ Website] ( https://github.com/nodejs/website )
3435
@@ -103,6 +104,8 @@ to date and of high quality.
103104* Promotion of Node.js speakers for meetups and conferences in their
104105language.
105106
107+ Note that the i18n working groups are distinct from the [ Intl] ( #Intl ) working group.
108+
106109Each language community maintains its own membership.
107110
108111* [ nodejs-ar - Arabic (اللغة العربية)] ( https://github.com/nodejs/nodejs-ar )
@@ -140,6 +143,17 @@ Each language community maintains its own membership.
140143* [ nodejs-uk - Ukrainian (Українська)] ( https://github.com/nodejs/nodejs-uk )
141144* [ nodejs-vi - Vietnamese (Tiếng Việtnam)] ( https://github.com/nodejs/nodejs-vi )
142145
146+ ### [ Intl] ( https://github.com/nodejs/Intl )
147+
148+ The Intl Working Group is dedicated to support and improvement of
149+ Internationalization (i18n) and Localization (l10n) in Node. Its responsibilities are:
150+
151+ 1 . Functionality & compliance (standards: ECMA, Unicode…)
152+ 2 . Support for Globalization and Internationalization issues that come up in the tracker
153+ 3 . Guidance and Best Practices
154+ 4 . Refinement of existing ` Intl ` implementation
155+
156+ The Intl WG is not responsible for translation of content. That is the responsibility of the specific [ i18n] ( #i18n ) group for each language.
143157
144158### [ Evangelism] ( https://github.com/nodejs/evangelism )
145159
0 commit comments