Initiate Persian Localization Team

[xehrad]

(1) The language and language code for l10n

• Language name: Persian
• Language two-letter code: fa

(2) List of volunteers

Name and GitHub Username for each l10n volunteer. Add [A] to make them approvers.

• [A] Mamrez Behfar(@mamrezb)
• [A] Mohammad Amin Taher (@xirehat)
• [A] Mohammad Zarei(@Moh0ps)
• [A] Behdin (@Behiuu)

[xehrad]

@Okabe-Junya Could you please review this for me? Thanks

[jihoon-seo]

• Invited people to glossary repo with write access (in https://github.com/cncf/glossary/settings/access)
  • @xehrad @Parsabz Please check and accept the invitation
  • Maintainers TODO: I sent an invitation to @blueblackcups but it might be my mistake. If so, we need to take back the write access later.
• Created new label dev-fa
• Created new branch dev-fa
• Created new branch protection rule dev-fa
  • Maintainers TODO: Give @xehrad @Mamrez @xirehat @Moh0ps @Behiuu push access to this branch protection rule (which is possible after the PR Initialize CNCF Glossary Persian L10n Team people#1313 gets merged)

[jihoon-seo]

To each Persian L10n approver candidate (@xehrad @Parsabz):
Please confirm that you understand the policy and information for localization approvers, by leaving a comment here.

• Policy for localization approvers (to be confirmed by candidates) #723

[jihoon-seo]

Note: the same concern as #3458 (comment) arises here:

I do have one concern: having only two approvers may not be enough to maintain a sustainable localization, since approvers cannot approve their own PRs, and our current settings require at least two approvals per PR.
This means that if one of the vi approvers opens a PR to dev-vi, it cannot be merged without additional approvers.

So, as we work towards the first live version, please keep an eye out for good candidates to become additional approvers. (No rush — we need qualified people who can actually help maintain the dev-vi branch.)
In the meantime, glossary maintainers can help by providing additional approvals if needed.

My suggestion is that: we proceed with 2 Persian L10n approvers this time, and in future we can add one more L10n approver later.

[seokho-son]

Note: the same concern as #3458 (comment) arises here:

I do have one concern: having only two approvers may not be enough to maintain a sustainable localization, since approvers cannot approve their own PRs, and our current settings require at least two approvals per PR.
This means that if one of the vi approvers opens a PR to dev-vi, it cannot be merged without additional approvers.
So, as we work towards the first live version, please keep an eye out for good candidates to become additional approvers. (No rush — we need qualified people who can actually help maintain the dev-vi branch.)
In the meantime, glossary maintainers can help by providing additional approvals if needed.

My suggestion is that: we proceed with 2 Persian L10n approvers this time, and in future we can add one more L10n approver later.

Hi @jihoon-seo thanks for coordinating Persian Localization initiation.
I think we need to encourage the tentative team members to bring in more initial members before we proceed.

This can also serve as part of the onboarding process to assess the minimum capabilities of the approver candidates. Since we’re giving them authority, we need to make sure they can be trusted to maintain both the quality of localization and the contributor community over time.

[mamrezb]

Note: the same concern as #3458 (comment) arises here:

I do have one concern: having only two approvers may not be enough to maintain a sustainable localization, since approvers cannot approve their own PRs, and our current settings require at least two approvals per PR.
This means that if one of the vi approvers opens a PR to dev-vi, it cannot be merged without additional approvers.
So, as we work towards the first live version, please keep an eye out for good candidates to become additional approvers. (No rush — we need qualified people who can actually help maintain the dev-vi branch.)
In the meantime, glossary maintainers can help by providing additional approvals if needed.

My suggestion is that: we proceed with 2 Persian L10n approvers this time, and in future we can add one more L10n approver later.

Hi @jihoon-seo thanks for coordinating Persian Localization initiation. I think we need to encourage the tentative team members to bring in more initial members before we proceed.

This can also serve as part of the onboarding process to assess the minimum capabilities of the approver candidates. Since we’re giving them authority, we need to make sure they can be trusted to maintain both the quality of localization and the contributor community over time.

Hi @seokho-son and @xehrad. Great to see you here as well, Seokho!
Thanks @jihoon-seo for coordinating Persian localization initiation here.

I’m actively contributing to Kubernetes Persian localization and would be glad to join the CNCF Glossary Persian localization effort and help address the approver shortage. Happy to contribute here with translations and and serve as an approver and help move it forward. I’m sure this Persian localization will go smoothly here as well!

[xehrad]

@mamrezb we’d value your help.
Join the Persian localization team and jump in on reviews/translations.
We can add you as an approver.
Tag other Persian-speaking contributors so we can add them as reviewers.