Skip to content

Conversation

@itsbilolbek
Copy link
Contributor

This pull request introduces a new RFC document that mandates English as the primary language for all formal communication and technical documentation within the FLOSS Uzbekistan network. It also standardizes the use of the Latin alphabet for Uzbek technical writing, deprecating Cyrillic script. These changes are aimed at aligning the community with global open-source standards, improving accessibility, and preparing contributors for international collaboration.

Language and Communication Standardization:

  • Introduces a requirement that all formal communications (RFCs, PRs, issues, announcements) within FLOSS Uzbekistan must be conducted in English.
  • Establishes English as the canonical source for all technical documentation, with Uzbek translations encouraged but not mandatory.

Uzbek Script Standardization:

  • Mandates the use of the Latin alphabet for all Uzbek technical content, deprecating the use of Cyrillic script and requiring migration for existing materials.

Community Enforcement and Migration:

  • Specifies enforcement guidelines for maintainers, including rejecting non-English submissions and outlining a migration plan for Cyrillic-based documentation.

@bahrom04 bahrom04 self-requested a review October 31, 2025 09:06
formal submissions.

- **Prioritize English Docs:** If you are a technical writer or contributor
to documentation, create and maintain the English version first.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
to documentation, create and maintain the English version first.
to documentation, create and maintain the either English or Uzbek version first depending on your preference

Comment on lines +97 to +99
- **English is the Default:** When you open a PR, write an RFC, or report
a bug on GitHub, use clear, concise English. This is non-negotiable for
formal submissions.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

en va uz default

Comment on lines +60 to +61
- **Issue Tracking:** All GitHub issues, bug reports, feature requests,
and issue comments **MUST** be in English.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

English or Uzbek

Comment on lines +57 to +58
- **Code Review:** All Pull Request (PR) titles, descriptions, and review
comments **MUST** be in English.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

English or Uzbek

@orzklv orzklv requested a review from lambdajon November 8, 2025 13:11
@lambdajon
Copy link
Contributor

@itsbilolbek resolve conversations.

@bahrom04 bahrom04 self-requested a review November 8, 2025 13:58
Copy link
Member

@bahrom04 bahrom04 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

resolve qilish kerak yoki guruhda maslahatlashamiz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants