I would like to become a member

[lxmarinkovic]

Hi @Trott & @nschonni , I would like to become a member and to contribute with Serbian (Latin or Cyrillic) or translation, mostly for API docs and web site as well

[Trott]

@zeke @obensource @RichardLitt Is this still a thing? What should @lxmarinkovic do?

[RichardLitt]

I'm unsure. Haven't been active in a while, and I should probably resign from the board as being inactive in general, unfortunately.

[Trott]

I'm unsure. Haven't been active in a while, and I should probably resign from the board as being inactive in general, unfortunately.

I'll remove you as a maintainer but leave you as a member unless you indicate otherwise.

[zeke]

Sadly, I have to say the same. I haven't been active in this space for a while and it's a disservice to the community for me to pretend otherwise.

[RichardLitt]

I'll remove you as a maintainer but leave you as a member unless.

This actually sounds good to me. Thanks, @Trott.

[Trott]

@obensource @bnb Any chance you can provide guidance here?

[Trott]

@nodejs/i18n What should happen here? Is i18n group still a thing? Is CrowdIn still being used? Or should @lxmarinkovic open pull requests for translations directly against the nodejs.org repo?

[srl295]

@obensource

[ovflowd]

Hey there 👋 I'm also interested in contributing to the i18n team in general. From this thread it feels like the i18n team is not receiving currently much help, is this correct?

I also saw that the Crowdin integration is broken, and I'd like to help there if possible 👀 (Also with the Website Working Group).

I'd love to chat, @ovflowd:gnome.org on Matrix :)

[Trott]

@nodejs/tsc If the larger i18n coordination effort is to be revived, it will need a commitment from leadership, I think. Hopefully someone (@RichardLitt @bnb @obensource @zeke) can confirm or correct this summary but my impression is that:

• The larger i18n effort was a CommComm thing. So it doesn't have a home anymore.
• None of the people who used to lead it are involved in it anymore.
• It's basically broken and in stasis.
• It's different/separate from the general website localization efforts in that....here's where I don't actually know. I think the idea was to use Crowdin to make it easier for more people to do translations than our current open-a-pull-request-in-the-nodejs.org-repo method. It may have also had the intention of localization for the API docs but that never came to fruition as far as I know.

I think winding it down and telling people to continue submitting PRs to the website repository is a valid option, and a better option if we're not prepared to put real time and potentially resources (via the foundation, I suppose) into a larger effort. Almost everything that has ever happened with localization happened with individuals submitting PRs to the website repo. I'm not sure that this initiative ever bore much fruit (which is fine--lots of things get tried and don't work out). Again, I could be wrong, and maybe one of the folks who was involved in it can comment and add some context or info I don't have.

[JohnTitor]

I think your summary comment is almost right. The problem here is that all the folks that have access to Crowdin are out of contact and I cannot promote things to integrate. I feel using Crowdin UI makes translations easier and we should have a lot of translated texts, so integrating into it would be great. Maybe we could focus on API docs for now and continue the current style for the website (submitting PRs to the repo). Or at least I'd like to move the texts on Crowdin to somewhere.

[Trott]

Maybe we could focus on API docs for now

How/where do we published localized API docs? Or is making the translations widely available part of the problem that a larger initiative would solve?

[TiagoDanin]

How/where do we published localized API docs? Or is making the translations widely available part of the problem that a larger initiative would solve?

There is currently an integration (it's broken for the reason @JohnTitor mentioned) between this repository and Crowdin. The Crowdin via bot create PR keep the translated documents synchronized.

Part of the problem we need to solve is making the contents of this repository available to Node.org.
Part of this discussion can be seen #328 and #315