Added the "Translation contributing" section to README_ru.md

[AlexeiCrystal]

PR Type

Documentation

---

Description

• Added "Translation contributing" section to Russian README

• Provided Crowdin link for translation contributions

• Documented process for adding new languages

---

Diagram Walkthrough

flowchart LR
  README["README_ru.md"] -- "adds translation section" --> CONTRIB["Translation Contributing"]
  CONTRIB -- "references" --> CROWDIN["Crowdin Project"]
  CONTRIB -- "documents" --> NEWLANG["New Language Process"]

Loading

File Walkthrough

	Relevant files
Documentation	README_ru.md Add translation contributing guidelines section                    README_ru.md Added new "Участие в переводе" (Translation Contributing) section Included link to Crowdin project for translation contributions Added instruction to create issue before adding new languages +3/-0

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Not Applicable: The PR only adds documentation text and does not introduce or modify any code paths related to auditing or logging of critical actions. Referred Code ## Участие в переводе Вы можете помочь с переводом через [Crowdin](https://crowdin.com/project/micts) Если вы хотите добавить новый язык, сначала создайте issue Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Documentation Only: This change adds prose to a README and does not introduce identifiers or code naming subject to this guideline. Referred Code ## Участие в переводе Вы можете помочь с переводом через [Crowdin](https://crowdin.com/project/micts) Если вы хотите добавить новый язык, сначала создайте issue Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: No Runtime Code: The PR modifies documentation only and does not add executable logic where error handling would apply. Referred Code ## Участие в переводе Вы можете помочь с переводом через [Crowdin](https://crowdin.com/project/micts) Если вы хотите добавить новый язык, сначала создайте issue Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Not Applicable: No user-facing error messages or handling changes are introduced; only README content was added. Referred Code ## Участие в переводе Вы можете помочь с переводом через [Crowdin](https://crowdin.com/project/micts) Если вы хотите добавить новый язык, сначала создайте issue Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Documentation Only: The change is limited to documentation and does not add or modify logging behavior or content. Referred Code ## Участие в переводе Вы можете помочь с переводом через [Crowdin](https://crowdin.com/project/micts) Если вы хотите добавить новый язык, сначала создайте issue Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: No Input Handling: The PR adds README guidance and does not introduce input processing, data handling, or security-relevant code paths. Referred Code ## Участие в переводе Вы можете помочь с переводом через [Crowdin](https://crowdin.com/project/micts) Если вы хотите добавить новый язык, сначала создайте issue Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.