Patch/translation ru

[alexandrtovmach]

Here is the full Russian translation of the website except guides and privacy policy

A few moments:

• Official Russian repository nodejs/nodejs-ru community is archived, and in that case I send direct PR
• If it's possible I'd happy to be a contributor and/or owner of the nodejs/nodejs-ru repository, to continue active localization process of Node.js

[Trott]

Here is the full Russian translation of the website except guides and privacy policy

A few moments:

• Official Russian repository nodejs/nodejs-ru community is archived, and in that case I send direct PR
• If it's possible I'd happy to be a contributor and/or owner of the nodejs/nodejs-ru repository, to continue active localization process of Node.js

/ping @nodejs/community-committee What's the best way for @alexandrtovmach to proceed with continued active maintenance of the Russian translation? CrowdIn? Something else? I don't want to ping @nodejs/localization because that's 165 people or something. Is there a sort of @nodejs/localization-admin team or something like that?

[keywordnew]

@obensource is this something yet within the purview of nodejs/i18n?

[WaleedAshraf]

maybe it's good to ping some of the contributors of nodejs/nodejs-ru here?
cc @Olegas @gko

[alexandrtovmach]

@WaleedAshraf I'm not sure that's useful, because they stopped active contributing 4 years ago

[alexandrtovmach]

@keywordnew nodejs/i18n group working on API docs translation, in this PR I've translated the website

[Trott]

Maybe @ChALkeR (or some other regular contributor who speaks Russian) has time to look it over a little bit and can give it a rubber-stamp approval? In other words, something like "I gave this a cursory review, skimming a few pages, and it looks good to me, but I did not review it thoroughly."

(We have two issues here: First, getting this reviewed and up on the website. Second, what is the preferred way we do these things going forward? Do we just keep the translation here and do it through PRs like this? Or is there another mechanism? I seem to recall CrowdIn being used, but I know nothing about if that's continued or not. /ping @zeke)

[ghost]

@nodejs/nodejs-ru：Anyone has a review of that？

[alexandrtovmach]

Any updates with that? How can I help to proceed now?

[Trott]

Hmmm...I'm not sure who speaks Russian in Node.js core besides Chalker, but going on educated guesswork here, maybe @indutny or @vsemozhetbyt might be able to give this at least a cursory review?

[ghaiklor]

Overall everything is ok, but sometimes there are obvious points in text, where reader can see an artifact of computer translation.

I'd say, nothing critical or blocking here, but I did not review the whole PR word by word, it is huge. For the next time, it will be much better to make smaller PRs.

[alexandrtovmach]

@ghaiklor Thanks for a quick review. I'll add this fixes in next few days.

[alexandrtovmach]

So finally I've added requested changes. Seems like we can merge

[alexandrtovmach]

@Trott Thanks for merging. We still have open question about continuing translation process. Do I need to close this PR and open separate issue?

[Trott]

Do I need to close this PR and open separate issue?

Yes, that will work!

[badJaguar]

Let's try to translate Documentation.

[alexandrtovmach]

@badJaguar To work on documentation translation please use https://crowdin.com/project/nodejs/ru