[RFC] Standardizing Formal Communication to English and Latin Script#20
Open
itsbilolbek wants to merge 1 commit intofloss-uz:mainfrom
Open
[RFC] Standardizing Formal Communication to English and Latin Script#20itsbilolbek wants to merge 1 commit intofloss-uz:mainfrom
itsbilolbek wants to merge 1 commit intofloss-uz:mainfrom
Conversation
orzklv
approved these changes
Oct 31, 2025
bahrom04
reviewed
Nov 3, 2025
| formal submissions. | ||
|
|
||
| - **Prioritize English Docs:** If you are a technical writer or contributor | ||
| to documentation, create and maintain the English version first. |
Member
There was a problem hiding this comment.
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. |
Comment on lines
+60
to
+61
| - **Issue Tracking:** All GitHub issues, bug reports, feature requests, | ||
| and issue comments **MUST** be in English. |
Comment on lines
+57
to
+58
| - **Code Review:** All Pull Request (PR) titles, descriptions, and review | ||
| comments **MUST** be in English. |
Contributor
|
@itsbilolbek resolve conversations. |
bahrom04
requested changes
Nov 8, 2025
Member
bahrom04
left a comment
bahrom04
left a comment
There was a problem hiding this comment.
resolve qilish kerak yoki guruhda maslahatlashamiz
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
Uzbek Script Standardization:
Community Enforcement and Migration: