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

Sorting out Intl vs I18n labels, teams, and repos #813

Closed
sam-github opened this issue Feb 6, 2020 · 9 comments
Closed

Sorting out Intl vs I18n labels, teams, and repos #813

sam-github opened this issue Feb 6, 2020 · 9 comments

Comments

@sam-github
Copy link
Contributor

I think something is out of sync with naming, we seem to have both i18n and intl, but they mean different things in different contexts, and sometimes seem to switch meaning.

Repos:

?!?!

Teams:

These team's descriptions point to their corresponding github repos above, but that means that there isn't a team that refers to the node core i18n support. Does such a team exist, or is it just @srloomis all the time?

No team for ICU and related i18n APIs?

Labels:

The intl label is for i18n? That's not confusing at all... :-) can I rename the label to i18n?

I'm not sure what should be done with the teams and repos.... perhaps

  • nodejs/intl should, in fact, be the new (and only) repo?
  • And nodejs/i18n should be archived?
  • And at-nodejs/intl should be the nodejs/intl team (as it is)?
  • And at-nodejs/i18n should be the nodejs/node/core i18n team, associated with the i18n label?

cc: @srloomis @nodejs/intl @nodejs/i18n

@srl295
Copy link
Member

srl295 commented Feb 14, 2020

For reference: #353

@srl295
Copy link
Member

srl295 commented Feb 14, 2020

  • Could the Intl team be renamed @nodejs/i18n/api or some such?

can I rename the label to i18n

Yes, good idea.

@srl295
Copy link
Member

srl295 commented Feb 21, 2020

https://github.com/nodejs/i18n

this is the new i18n

https://github.com/nodejs/Intl Described as the "new i18n", but its archived and the (old?) i18n above is not.

I was trying to use the description of nodejs/Intl there as a redirection: Node.js Intl Team (see new i18n WG) with URL https://github.com/nodejs/TSC/issues/353. We could unarchive, reword, and rearchive the dechartered nodejs/Intl. @sam-github do you have suggested better wording?

@sam-github
Copy link
Contributor Author

see new --> replaced by the ?

@srl295
Copy link
Member

srl295 commented Feb 28, 2020

replaced by the

https://github.com/nodejs/Intl - better?

@srl295
Copy link
Member

srl295 commented Feb 28, 2020

@obensource @nodejs/i18n — I have requested to move the Intl team (now called i18n-api) under i18n — says it's pending approval.

@srl295
Copy link
Member

srl295 commented Feb 28, 2020

I renamed the Intl label to i18n-api.

So now, i18n-api consistently refers to API related stuff.

@obensource
Copy link
Member

@srl295 approved! 🚀

@srl295
Copy link
Member

srl295 commented Feb 28, 2020

These team's descriptions point to their corresponding github repos above, but that means that there isn't a team that refers to the node core i18n support. Does such a team exist, or is it just @srloomis all the time?

Actually there are a couple of others in @nodejs/i18n-api

@sam-github I think all issues are resolved here, close this? On the i18n-WG side there are issues such as nodejs/i18n#210 to improve the WG's docs and such, but I don't think that should keep this #813 open.

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

No branches or pull requests

3 participants