Initiate Vietnamese Localization Team

[ntheanh201]

This issue is to initiate a new l10n Team

Please only use this template for submitting a new l10n team initiation requests.

See https://github.com/cncf/glossary/blob/main/LOCALIZATION.md for basic requirements for a new l10n team.

---

(1) The language and language code for l10n

Find localization's two-letter language code from ISO 639-1 standard.

For example, the two-letter code for Korean is ko.

• Language name (ex: Korean): Vietnamese
• Language two-letter code (ex: ko): vi

(2) List of volunteers

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

Ex: - [A] Seokho Son (@seokho-son)

• [A] The Anh Nguyen (@ntheanh201)
• [A] Thuan Pham (@thuanpham582002)
• Thao Mike (@thaomike)

---

(Note) Next actions from maintainers

• Create a new development branch for the l10n. (ex: dev-ko)
• Update codeowners to add l10n contents approvers.
• Add a new label for the language.

[Okabe-Junya]

I've created the dev-vi branch and applied the same branch protection rules as for the other languages.

• FYI: https://github.com/cncf/glossary/tree/dev-vi

Maintainer Todo

• After the PR to cncf/people is merged, add vi l10n reviewers to the Restrict pushes that create matching branches setting in the branch protection rules.

[Okabe-Junya]

I have ...

• Opened a PR to cncf/people: Initialize CNCF Glossary Vietnamese Localization Team people#973
• Opened a PR to update CODEOWNERS: Update CODEOWNERS to initialize vi l10n #3460

[ntheanh201]

Thanks @Okabe-Junya 🚀

[seokho-son]

Thanks @Okabe-Junya and @ntheanh201!

I think we have a solid starting point — once the PR to update the CODEOWNERS file is merged and applied to the existing dev-vi branch.

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.

[ntheanh201]

Thanks @seokho-son,
In that case, can I promote @thaomike becoming one of our approvers?
Beside, I'm also seeking for new volunteers

[Okabe-Junya]

Ok, I have Added thaomike to vi approvers!

• cncf/people: Update CNCF Glossary Vietnamese Localization Team people#974
• CODEOWNERS: 97dd609