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

Moving all translation to Crowdin and retiring all i18n groups #763

Closed
Trott opened this issue Jan 19, 2023 · 18 comments
Closed

Moving all translation to Crowdin and retiring all i18n groups #763

Trott opened this issue Jan 19, 2023 · 18 comments

Comments

@Trott
Copy link
Member

Trott commented Jan 19, 2023

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
Copy link
Member

ovflowd commented Jan 19, 2023

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
Copy link
Member

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

@ovflowd
Copy link
Member

ovflowd commented Jan 20, 2023

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

@ovflowd
Copy link
Member

ovflowd commented Feb 27, 2023

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
Copy link
Member

ovflowd commented Feb 27, 2023

Also, this Issue is a continuation of: #650

@Trott
Copy link
Member Author

Trott commented Feb 28, 2023

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

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

@ovflowd
Copy link
Member

ovflowd commented Feb 28, 2023

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
Copy link
Member Author

Trott commented Mar 2, 2023

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
Copy link
Member

ovflowd commented Mar 2, 2023

Sounds like a plan :)

@ovflowd
Copy link
Member

ovflowd commented Mar 3, 2023

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

@Trott
Copy link
Member Author

Trott commented Mar 12, 2023

@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
Copy link
Member Author

Trott commented Mar 12, 2023

@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
Copy link
Member

ovflowd commented Mar 12, 2023

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

@mhdawson
Copy link
Member

I'm +1 to moving forward with the steps proposed.

@Trott
Copy link
Member Author

Trott commented Mar 18, 2023

@mcollina
Copy link
Member

@Trott we briefly talked about this in the TSC meeting and there were no objections noted. Note that we did not have quorum.

@mcollina
Copy link
Member

SGTM

@Trott
Copy link
Member Author

Trott commented Mar 22, 2023

This is now done.

@Trott Trott closed this as completed Mar 22, 2023
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

5 participants