Moving all translation to Crowdin and retiring all i18n groups

[Trott]

Once the website repos and teams have been unified (which @ovflowd is working on), it would probably be beneficial to move all translation efforts to Crowdin and retire the very large number of almost-entirely-inactive translation GitHub teams.

@nodejs/tsc @nodejs/i18n

[ovflowd]

One of the reasons (I believe) we have the Website translators within the org was to easily know who is a translator for which language and to easily tag them.

With Crowdin we can easily manage that, not to mention, when new translations are required, the respective translators are automatically tagged.

This would allow us to only keep maintainers of the i18n WG to stay within the org.

(Note we should possibly also audit the current list of translators on Crowdin...)

[nschonni]

The actual i18n group is also used for things other than translations, like https://github.com/nodejs/full-icu-npm

[ovflowd]

Yeah the idea is to just keep the i18n maintainers/non-translation stuff.

[ovflowd]

I've also seen that the "translators" team probably would need to be sunset. I also believe we need to audit the current members of Crowdin. This kind of change would likely need an announcement for our current translators.

@Trott, how are we on track to making this change happen?

[ovflowd]

Also, this Issue is a continuation of: #650

[Trott]

@Trott, how are we on track to making this change happen?

I'm not sure. What are the steps that need to happen?

[ovflowd]

I would say:

• Announce to all Translators about the move to Crowdin (probably via Org-wide Discussions)
• Then remove the members and teams
• Accept the invites on Crowdin? (I will also remove current translators that are not active on Crowdin (they can be readded at any moment/time if they request)

[Trott]

I would say:

* Announce to all Translators about the move to Crowdin (probably via Org-wide Discussions)

* Then remove the members and teams

* Accept the invites on Crowdin? (I will also remove current translators that are not active on Crowdin (they can be readded at any moment/time if they request)

The first two would be likely handled by someone on the TSC (like me). The third one is something you would do once the first two are done?

[ovflowd]

Sounds like a plan :)

[ovflowd]

@Trott can we add tsc-agenda for this one? and #650?

[Trott]

@Trott can we add tsc-agenda for this one? and #650?

What do you hope to get out of the TSC? Awareness? Approval? A certain action?

[Trott]

@Trott can we add tsc-agenda for this one? and #650?

What do you hope to get out of the TSC? Awareness? Approval? A certain action?

I guess maybe the thing to get from the TSC is agreement and commitment from one or more TSC members to do these items:

• Announce to all Translators about the move to Crowdin (probably via Org-wide Discussions)

• Then remove the members and teams

[ovflowd]

Yup! Forgot to answer you, but that pretty much was it :)