:ru version of site

[gazay]

Hello, we with some of my friends working on russian version of site. What is the new version and will be there changes in content? I mean should I skip some pages or where I can get newest site content?

[stomar]

Sorry for the delayed response.

The current content of the en version is the official base for translations. The source files (markdown) are located in the corresponding directory of this repository. There are no plans at the moment for big changes.

Note that maintaining a translation is a long-term effort that requires a team of at least 2 maintainers. Essentially, all (or at least nearly all) pages need to be translated and sometimes updated, mirroring possible changes on en. Additionally, all (future) official news posts (e.g. release and security announcements) need to be translated within a sensible amount of time.

The effort should not be underestimated. (We are still evaluating at the moment whether some badly maintained translations should be removed or not.) I hope this doesn't sound too negative, but I believe that a fragmentary and outdated translation is worse than none at all.

Please feel free to post any questions you have.

[gazay]

Yes, I understood that it is long-term maintaining and I'd like to participate. About 2 maintainers - I have several people who helping me with translation right now, I think it will not be a problem. Russian community pretty big and growing and I think that this web site – very good and important resource to community to continue to grow. Thank you for your response, right now we're in the middle of translation main pages of site and soon we'll start translate all news. Maybe you have some archived pages in russian which can help me a lot? For example I know that few pages in russian I can find here - http://preview.ruby-lang.org/ru. Maybe I can get access to sources of that site?

[stomar]

I propose the following steps:

1. I would like to get short notice/confirmation here of some of the people who help you.
2. I will make the necessary configuration changes and basic setup for a ru section. Done
3. Then we should agree on how to organize the addition of content (what priorities, ...). [See suggestions below.]

(I'll also try to migrate the content from preview.ruby-lang.org, but I might not get around to that for some days.)
Update: The content is old, and migration needs a lot of tweaking by hand. I think it's better to use the current en markdown files and possibly copy parts of the Russion text from the website.

PS. Regarding news posts: I think it would be sufficient to translate only the recent posts.

[stomar]

I added a branch with the initial setup for ru: ru-translation. Use that as a basis for contributions.

1. First thing to do: proofread / add missing locales in _config.yml. (Everything marked with ru; you might browse the English site or ask if the context of some of these snippets is not clear.)
2. Proofread index.html
3. Then preferably combine one (or more) completely translated directories in a single commit.
   A good start might be: about (do not include the license file), downloads, libraries).
4. Ask for feedback early.

Important: fork feature branches for PRs from the ru-translation branch.

General hints: Stay close to the en version. Also, do not modify language-independent content (not even add newlines, etc). The diffs are more useful that way and changes can be made on the whole bunch of languages at the same time, if necessary.

In case you disagree strongly with some content of en, do not silently change it for ru, open an issue for en instead.

[stomar]

@hsbt, @chikamichi, @postmodern, @JEG2 Your opinions on a Russian translation?

[postmodern]

I think it's a great idea, but we would need many more translators.

[JEG2]

Yep, I don't see a downside. It just needs a team.

[gazay]

Great, I'll review your suggestions this weekend and ask guys from my team to write here notice to confirm their participation. Right now we already translated index, about, community, documentation (there only ruby-from-another-languages not translated at the moment, but in progress) and posts 2001-2002 also in progress. When I started I decided not to modify current version of en branch and do expression-by-expression translation, I understood that if I or someone from my teammates want to change something we should make PR to original repo first. As we have time to did one or couple pages at once – we did commits like that, but I think it's not too hard for us to squash commits, related for each part of site in one after we complete ru branch. Thank you for preparation of ru branch, I'll look at it later on weekend.

[gazay]

P.s. you can check progress in my branch of site - https://github.com/gazay/www.ruby-lang.org/tree/ru. Guys will do PR to my branch to have similar text style through all site.

[razum2um]

I will also participate. In particular, currently "ruby from other languages" is in progress

[inossidabile]

I'm in as well.

[chikamichi]

@gazay as for the posts, I'd suggest beginning with the latest first. It's not like the old ones from 2001 are that useful now :) Maybe you could even consider translating only 2013's posts.

[gazay]

Sure, you right – I just thought that there should be one-to-one translation. And it's interesting for me to review full history of ruby by it's news, and maybe for someone else will be too :) So we'll start from the end on posts and then we'll see

[stomar]

For upcoming PRs: Please start from empty directories and then add translated pages. Do not commit the complete en version previously, which for example makes it difficult to see what translations are missing.

I would prefer discussions / PRs happening here, not in a separate repo; maybe it's ok for the moment. But at least make commit messages fit in the more general context of this repo, e.g. "Translate documentation pages (ru)" or similar.

By all means, forget 2001. I would suggest (again) to 1. proofread/complete the files already in the ru-translation branch (they provide locales for all the headers, footers, sidebar, etc.) and then 2. create a PR for e.g. some of the existing translations, and we'll see how that works out.

(I do not think it's a good idea to first complete translating the whole site and then start talking about problems, issues, conventions, ...)

[gazay]

I understood. I started from reviewing initial pages from ru-translation branch and made PR #196 which already accepted by @hsbt. Also I made PR for about section - #197. As I see, right now I have commit rights and I think I can merge my PRs to ru-translation branch after it reviewed and accepted by members from ru-translation team. What do you think?