Add missing sections to Russian translation (#3830)

* Add the missing sections to the downloads navigation

* Add the FAQ section to the documentation (ru)

* Add missing items to the Contribution section (ru)

* Add missing items to the community section (ru)

* Update site structure for the Russian language is now aligned with the English version

Author: ablzh

_data/locales/ru.yml

@@ -8,6 +8,12 @@ navigation:
     url: /ru/documentation/installation/
   - text: Скачать
     url: /ru/downloads/
+  - text: Релизы
+    url: /ru/downloads/releases/
+  - text: Ветки
+    url: /ru/downloads/branches/
+  - text: Зеркала
+    url: /ru/downloads/mirrors/
   - text: Менеджеры пакетов
     submenu:
     - text: rbenv
@@ -44,6 +50,8 @@ navigation:
       url: /ru/documentation/ruby-from-other-languages/to-ruby-from-php/
     - text: В Ruby из Python
       url: /ru/documentation/ruby-from-other-languages/to-ruby-from-python/
+  - text: FAQ
+    url: /ru/documentation/faq/
   - text: Начните сейчас & Исследуйте
     submenu:
     - text: TryRuby
@@ -94,6 +102,10 @@ navigation:
     url: /ru/documentation/repository-guide/
   - text: Почтовые рассылки
     url: /ru/community/mailing-lists/
+  - text: Правила списков рассылки
+    url: /ru/community/mailing-lists/ruby-talk-guidelines/
+  - text: Руководство по созданию патчей
+    url: /ru/community/ruby-core/writing-patches/
   - text: Прочее
     submenu:
     - text: ruby/ruby
@@ -114,6 +126,10 @@ navigation:
     url: /ru/community/user-groups/
   - text: Блоги и рассылки
     url: /ru/community/weblogs/
+  - text: Подкасты
+    url: /ru/community/podcasts/
+  - text: Кодекс поведения
+    url: /ru/conduct/
   - text: События и конференции
     submenu:
     - text: RubyKaigi
@@ -122,6 +138,11 @@ navigation:
     - text: Ruby Events
       url: https://www.rubyevents.org/
       external: true
+  - text: Организации
+    submenu:
+    - text: Ruby Association
+      url: https://www.ruby.or.jp/en/
+      external: true
 - text: Новости
   url: /ru/news/
   submenu:

ru/community/mailing-lists/ruby-talk-guidelines/index.md

@@ -0,0 +1,82 @@
+---
+layout: page
+title: "Posting Guidelines for the Ruby-Talk Mailing List"
+lang: ru
+---
+
+You should follow these guidelines when posting to the ruby-talk mailing list.
+{: .summary}
+
+
+1. **Always** be friendly, considerate, tactful, and tasteful. We want to
+   keep this list hospitable to the growing ranks of newbies, very
+   young people, and their teachers, as well as cater to fire breathing
+   wizards. :-)
+
+2. Keep your content relevant and easy to follow. Try to keep your
+   content brief and to the point, but also try to include all relevant
+   information.
+
+   1. The general format guidelines (aka Netiquette) are
+      matters of common sense and common courtesy that make life
+      easier for third parties to follow along (in real time or when
+      perusing archives):
+
+      * **Please note:**
+        Include quoted text from previous posts **before** your responses
+        and **selectively** quote as much as is relevant.
+      * Use **plain text**; don't use HTML, RTF, or Word.
+        Most email programs have an option for this; if yours doesn't,
+        get a (free) program or use a web-based service that does.
+      * Include examples from files as **in-line** text; don't use
+        attachments.
+
+   2. If reporting a problem, give **all** the relevant information
+      the first time; this isn't the psychic friends newsgroup. :-)
+
+      When appropriate, include:
+
+      * an example (preferably simple) that produces the problem
+      * the actual error messages
+      * the version of Ruby (`ruby -v`)
+      * the OS type and version (`uname -a`)
+      * the compiler name and version used to build Ruby
+
+3. Make the subject line maximally informative, so that people who
+   should be interested will read your post and so that people who
+   wouldn't be interested can easily avoid it.
+
+   **Usefully** describe the contents of your post.
+
+   This is OK:
+
+   * "How can I do x with y on z?"
+   * "Problem: did x, expected y, got z."
+   * "BUG: doing x with module y crashed z."
+
+   This is **not** OK:
+
+   * "Please help!!!"
+   * "Newbie question"
+   * "Need Ruby guru to tell me what's wrong"
+
+   These prefixes have become common for subject lines:
+
+   * `[ANN]` (for announcements)
+   * `[BUG]` (for bug reports)
+   * `[OT]`  (for off-topic, if you must post off-topic)
+
+4. Finally, be considerate: Don't be too lazy. If you are seeking
+   information, first make a reasonable effort to look it up. As
+   appropriate, check the [Ruby home page][ruby-lang],
+   check the [Ruby FAQ][faq] and other documentation,
+   use a search engine to search past postings, and so on.
+
+
+_These guidelines where adopted from the [comp.lang.ruby FAQ][clrFAQ]._
+
+
+
+[ruby-lang]: /en/
+[faq]: /en/documentation/faq/
+[clrFAQ]: http://rubyhacker.com/clrFAQ.html

ru/community/podcasts/index.md

@@ -0,0 +1,42 @@
+---
+layout: page
+title: "Podcasts"
+lang: ru
+---
+
+Listen to news, interviews, and discussions about Ruby and its community.
+
+[On Rails][onrails]
+: Ruby on Rails developers share real-world technical challenges,
+  architectural decisions, and scaling strategies. Join experienced
+  engineers for technical deep-dives and retrospectives on building
+  production Rails applications.
+
+[Ruby Rogues][rogues]
+: The Ruby Rogues podcast is a panel discussion about topics relating to
+  programming, careers, community, and Ruby.
+
+[Ruby on Rails Podcast][rorpodcast]
+: The Ruby on Rails Podcast, a weekly conversation about Ruby on Rails,
+  open source software, and the programming profession.
+
+[Remote Ruby][remote_ruby]
+: Virtual meetup turned podcast, Remote Ruby celebrates and highlights
+  the Ruby community in an informal setting.
+
+[Rooftop Ruby][rooftop_ruby]
+: Collin and Joel discuss Ruby, software development, open source, career,
+  and a lot more together and with guests.
+
+### Getting Involved
+
+Podcast hosts are always looking for guests. If you have some Ruby
+wisdom to share, get in touch with the creators of these shows.
+
+You can also start your own Ruby podcast and get added to this list!
+
+[onrails]: https://podcast.rubyonrails.org/
+[rooftop_ruby]: https://www.rooftopruby.com
+[remote_ruby]: https://www.remoteruby.com
+[rorpodcast]: https://www.therubyonrailspodcast.com
+[rogues]: https://rubyrogues.com

ru/community/ruby-core/writing-patches/index.md

@@ -0,0 +1,52 @@
+---
+layout: page
+title: "Patch Writer’s Guide"
+lang: ru
+---
+
+Here follow some tips, straight from Matz, on how to get
+your patches considered.
+{: .summary}
+
+These guidelines were adopted from a [post by Matz][ruby-core-post]
+on the Ruby-Core mailing list:
+
+* Implement one modification per patch
+
+  This is the biggest issue for most deferred patches. When you
+  submit a patch that fixes multiple bugs (and adds features) at once,
+  we have to separate them before applying it. It is a rather hard task
+  for us busy developers, so this kind of patches tends to be deferred.
+  No big patches please.
+
+* Provide descriptions
+
+  Sometimes a mere patch does not sufficiently describe the problem it fixes.
+  A better description (the problem it fixes, preconditions, platform, etc.)
+  would help a patch to be merged earlier.
+
+* Diff to the latest revision
+
+  Your problem might have been fixed in the latest revision. Or the code
+  might be totally different by now. Before submitting a patch, try to fetch
+  the latest version (the `trunk` branch for the latest development version,
+  `{{ site.svn.stable.branch }}` for {{ site.svn.stable.version }})
+  from the Subversion repository, please.
+
+* Use `diff -u`
+
+  We prefer `diff -u` style unified diff patches to `diff -c`
+  or any other style of patches. They are far easier to review.
+  Do not send modified files, we do not want to make a diff by ourselves.
+
+* Provide test cases (optional)
+
+  A patch providing test cases (preferably a patch to `test/*/test_*.rb`)
+  would help us understand the patch and your intention.
+
+We might move to a Git style push/pull workflow in the future.
+But until then, following the above guidelines would help you to avoid
+frustration.
+
+
+[ruby-core-post]: https://blade.ruby-lang.org/ruby-core/25139

ru/conduct/index.md

@@ -0,0 +1,22 @@
+---
+layout: page
+title: "The Ruby Community Conduct Guideline"
+lang: ru
+---
+
+We have picked the following conduct guideline based on an early proposed draft
+of the PostgreSQL CoC, for Ruby developers community for safe, productive
+collaboration.
+Each Ruby related community (conference etc.) may pick their own Code of Conduct.
+{: .summary}
+
+This document provides community guidelines for a safe, respectful, productive,
+and collaborative place for any person who is willing to contribute to the Ruby
+community. It applies to all "collaborative space", which is defined as
+community communications channels (such as mailing lists, submitted patches,
+commit comments, etc.).
+
+ * Participants will be tolerant of opposing views.
+ * Participants must ensure that their language and actions are free of personal attacks and disparaging personal remarks.
+ * When interpreting the words and actions of others, participants should always assume good intentions.
+ * Behaviour which can be reasonably considered harassment will not be tolerated.