i18n - Revive the project #579
Comments
|
@maddhruv 💯🎉🙌 I'm very interested in helping this initiative grow as well. There's so much potential and I don't think enough has changed that we can't help it start to scale again in awesome ways! I touched base with Crowdin recently and they're interested in helping out & picking up where we left off. For now we need to recalibrate, prune, identify current issues, and set up regular WG meetings – all things I'd like to help out with this week. If we get the logistics in place, the rest should start to follow 👍 |
|
I've been out of the loop; I assumed that most communication happened at the i18n meetings in Berlin (and Vancouver? in general, in person), and that there wasn't a lot of chat happening here because everything was going smoothly. I may have been wrong in that. Shall we set up a doodle? |
|
@RichardLitt 💯! Let's set one up and make sure all interested folks are invited! 🙏 |
|
How about this? Could everyone fill this out? @nodejs/i18n |
|
@RichardLitt done – thank for putting it together! 🙏 |
|
If someone could look at nodejs/nodejs.org#2906 and comment to get it moving, that would be awesome! |
Related: nodejs/i18n#72 |
|
Wonderful! |
|
It looks like either Feb. 10th at noon EST, or Friday 14th at noon EST is best. I really want to have Zeke there; is there any way you could make the 2/10 time, @zeke? |
|
I'm going to close this as it seems the project has been revived! 🚀 |
|
Gentle update - we have started receiving our crowdin translations back again |
It's been a long time no activity has happened around
i18n- no new translations or documentation update for newer releases. Crowdin got down due to some reasons.Creating the issue to know if there were some issues/problems around i18n I missed during the course of time and can we bring it back alive?
/cc @nodejs/i18n @nodejs/tsc @nodejs/community-committee
The text was updated successfully, but these errors were encountered: