Policy for localization approvers (to be confirmed by candidates)

[seokho-son]

Policy for Localization Approvers

The policies and guidelines provided below apply to candidates for Localization Approvers (project details).

Important Notices

• All candidates must leave a comment on the relevant PR (pertaining to update ownership) to acknowledge their understanding of these policies and guidelines. Please note that without this confirmation, the PR will not be merged. (Localization teams: ensure this message is conveyed to all candidates.)
• Localization team approvers are expected to exercise their permissions responsibly.
  • As approvers, you will be granted push access to this repository, enabling you to manage (merge) PRs for localization contributions in your respective development branches.
  • However, merging PRs into the main branch is not permitted for localization approvers. Although you may review PRs targeting the main branch, you should refrain from approving them unless they pertain to your specific localization work.
• Upon the merging of the PR, new approvers will receive a GitHub invitation to collaborate from the settings[bot] of the CNCF Glossary. It is essential to accept this invitation, which you can find via email or GitHub notifications. Failing to accept will prevent maintainers from designating you as an approver for the dev-xx branch.

---

PR Merge Conditions for the main Branch

1. Only the Glossary Maintainers and English approvers are authorized to merge PRs into the main branch.
2. A minimum of one approval from the CODEOWNERS is required. CODEOWNERS are listed here for all files, including those containing English content: https://github.com/cncf/glossary/blob/main/CODEOWNERS#L13 (equivalent to chairs).
3. A minimum of two approving reviews from approvers is required.
4. While localization team approvers are technically able to approve PRs for any file, they should not do so unless the PR is relevant to their localization tasks.
   • Even with an approval from localization team approvers, they are not permitted to merge PRs into main branch, as these actions are restricted.
   • The policy regarding the merging of PRs may evolve over time, but the integrity of the main branch is ensured by the chairs.

PR Merge Conditions for dev-xx Localization Branches (e.g., dev-ko)

1. The glossary maintainers have the authority to merge PRs across all branches.
2. At least one approving review from localization CODEOWNERS is necessary:
   • For instance, CODEOWNERS for Korean content are specified here: https://github.com/cncf/glossary/blob/main/CODEOWNERS#L54 (the same individuals serve as Korean approvers).
   • If a PR include files beyond the scope of localization, the Glossary maintainers are required to conduct a review and perform the merge.
3. A minimum of two approving reviews from localization approvers is required.
4. Localization teams have the capability to merge PRs within their development branches. However, if a PR includes files not related to localization, approvals from maintainers (who are codeowners for all files) are required.
5. Ensure there is one commit per PR when localizing a document. Use the Squash and merge method for merging PRs.

---

Please be aware that we employ CODEOWNERS to automatically solicit reviews from the appropriate individuals.
(For more information on CODEOWNERS, visit GitHub's documentation)

Actual access permissions are managed through the repository settings of the CNCF Glossary repo.

• Permission changes can be made using the GitHub UI; however, we utilize the Settings app.
• The Settings app aligns repository settings with the configurations defined in the .github/settings.yml file.
• To update permissions accurately, we must modify the cncf/people repository accordingly (example: cncf/people #143).

[Imtiaz1234]

Understood the policy @seokho-son 😊

[waleed318]

Acknowledged @seokho-son

[ydFu]

@seokho-son
I have understood this regulation and will comply with the Policies for localization approvers.

[pichuang]

@seokho-son Understood and will comply with Policies

[guillaumebernard84]

Hello @seokho-son , I have read and understood the policy 👍

[tym83]

@seokho-son
I have understood this regulation and will comply with the Policies for localization approvers.

[bishal7679]

@seokho-son
I have understood this regulation and will comply with the Policies for localization approvers 👍

[justankiit]

I have understood all this regulations @seokho-son, and will comply with the Policies for localization approvers 👍

[aj11anuj]

@seokho-son
I have understood and will abide by these policies 👍

[tico88612]

@seokho-son I have understood these policies.

[symys]

Hello @seokho-son , I have read and understood the policy :)

[seb-835]

Hello @seokho-son , I have read and understood the policy :)

[asem-hamid]

@seokho-son Understood these policies

[adowair]

@seokho-son I understand and will abide by these policies. Thanks!

[seifrajhi]

Hello @seokho-son, I have understood this regulation and will comply with the Policies for localization approvers.

[mboukhalfa]

@seokho-son Acknowledged

[matteobisi]

Hello @seokho-son , read and understood. Thanks

[SaraTrap]

Hi @seokho-son, I have read and understood the policies. Thanks.

[ntheanh201]

Hi @seokho-son, I have read and understood the policies. Thanks.

[thuanpham582002]

hello @seokho-son, I have read and understood the policies. Thanks!

[xehrad]

Hello @seokho-son
I have read and understood the policy.

[mamrezb]

Hello @seokho-son
I have read and understood the policies. Thanks.

[Moh0ps]

Hi @seokho-son
I’ve read and understood the Localization policies and agree to follow these guidelines.