Merge pull request #22747 from tengqm/zh-sync-wranglers

[zh] Sync PR wranglers reorg

content/zh/docs/contribute/advanced.md

@@ -27,132 +27,6 @@ client and other tools for some of these tasks.
 
 <!-- body -->
 
-<!--
-## Be the PR Wrangler for a week
--->
-## 做一周的 PR 管理者
-
-<!--
-SIG Docs [approvers](/docs/contribute/participating/#approvers) take week-long turns [wrangling PRs](https://github.com/kubernetes/website/wiki/PR-Wranglers) for the repository.
-
-The PR wrangler’s duties include:
--->
-SIG Docs 的[批准人（Approvers）](/zh/docs/contribute/participating/#approvers)们每周轮流负责
-[管理仓库的 PRs](https://github.com/kubernetes/website/wiki/PR-Wranglers)。
-
-PR 管理者的工作职责包括：
-
-<!--
-- Review [open pull requests](https://github.com/kubernetes/website/pulls) daily for quality and adherence to the [style guide](/docs/contribute/style/style-guide/).
-    - Review the smallest PRs (`size/XS`) first, then iterate towards the largest (`size/XXL`).
-    - Review as many PRs as you can.
-- Ensure that the CLA is signed by each contributor.
-    - Help new contributors sign the [CLA](https://github.com/kubernetes/community/blob/master/CLA.md).
-    - Use [this](https://github.com/zparnold/k8s-docs-pr-botherer) script to automatically remind contributors that haven’t signed the CLA to sign the CLA.
-- Provide feedback on proposed changes and help facilitate technical reviews from members of other SIGs.
-    - Provide inline suggestions on the PR for the proposed content changes.
-    - If you need to verify content, comment on the PR and request more details.
-    - Assign relevant `sig/` label(s).
-    - If needed, assign reviewers from the `reviewers:` block in the file's front matter.
-    - Assign `Docs Review` and `Tech Review` labels to indicate the PR's review status.
-    - Assign `Needs Doc Review` or `Needs Tech Review` for PRs that haven't yet been reviewed.
-    - Assign `Doc Review: Open Issues` or `Tech Review: Open Issues` for PRs that have been reviewed and require further input or action before merging.
-    - Assign `/lgtm` and `/approve` labels to PRs that can be merged. 
-- Merge PRs when they are ready, or close PRs that shouldn’t be accepted.
-- Triage and tag incoming issues daily. See [Intermediate contributing](/docs/contribute/intermediate/) for guidelines on how SIG Docs uses metadata.
--->
-- 每天检查[悬决的 PR](https://github.com/kubernetes/website/pulls) 的质量并确保它们遵守[样式指南](/zh/docs/contribute/style/style-guide/)和[内容指南](/zh/docs/contribute/style/content-guide/)。
-    - 首先查看最小的 PR（`size/XS`），然后逐渐扩展到最大的 PR（`size/XXL`）。
-    - 尽可能多地审阅 PR。
-- 确保每个贡献者完成 CLA 签署。
-    - 指导新的贡献者签署 [CLA](https://github.com/kubernetes/community/blob/master/CLA.md)。
-    - 使用[此脚本](https://github.com/zparnold/k8s-docs-pr-botherer)自动提醒尚未签署 CLA 的贡献者签署 CLA。
-- 针对所建议的更改提供反馈，并帮助协调其他 SIG 成员进行技术审核。
-    - 为 PR 所建议的内容更改提供在线反馈。
-    - 如果您需要验证内容，请在 PR 上发表评论并要求贡献者提供更多细节。
-    - 设置相关的 `sig/` 标签。
-    - 如果需要，请从文件开头的 `reviewers:` 块中指定审阅者。
-    - 设置 `Docs Review` 和 `Tech Review` 标签以标示 PR 的审阅状态。
-    - 为尚未审阅的 PR 设置 `Needs Doc Review` 或者 `Needs Tech Review` 标签。
-    - 为已审阅的但在合并前需要更多信息的或采取措施的 PR 设置 `Doc Review: Open Issues` 或者 `Tech Review: Open Issues` 标签。
-    - 为可以合并的 PR 添加 `/lgtm` 和 `/approve` 标签。
-- 合并已经就绪的，或关闭不应该接受的 PR。
-- 每天对新增的 Issue 报告进行分类和判别。有关 SIG 文档如何使用 metadata 的准则，请参见
-  [对 Issue 进行分类](/zh/docs/contribute/review/for-approvers/#triage-and-categorize-issues)。
-
-<!--
-### Helpful GitHub queries for wranglers
-
-The following queries are helpful when wrangling. After working through these three queries, the remaining list of PRs to be
-reviewed is usually small. These queries specifically exclude localization PRs, and only include the `master` branch (except for the last one).
--->
-### 对于管理人有用的 GitHub 查询
-
-执行管理操作时，以下查询很有用。完成以下三个查询后，剩余的要审阅的 PR 列表通常很小。
-这些查询都排除了本地化的 PR，并仅包含 `master` 分支上的 PR（除了最后一个查询）。
-
-<!--
-- [No CLA, not eligible to merge](https://github.com/kubernetes/website/pulls?q=is%3Aopen+is%3Apr+label%3A%22cncf-cla%3A+no%22+-label%3Ado-not-merge+label%3Alanguage%2Fen):
-  Remind the contributor to sign the CLA. If they have already been reminded by both the bot and a human, close
-  the PR and remind them that they can open it after signing the CLA.
-  **Do not review PRs whose authors have not signed the CLA!**
-- [Needs LGTM](https://github.com/kubernetes/website/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+-label%3Ado-not-merge+label%3Alanguage%2Fen+-label%3Algtm+):
-  If it needs technical review, loop in one of the reviewers suggested by the bot. If it needs docs review
-  or copy-editing, either suggest changes or add a copyedit commit to the PR to move it along.
-- [Has LGTM, needs docs approval](https://github.com/kubernetes/website/pulls?q=is%3Aopen+is%3Apr+-label%3Ado-not-merge+label%3Alanguage%2Fen+label%3Algtm):
-  Determine whether any additional changes or updates need to be made for the PR to be merged. If you think the PR is ready to be merged, comment `/approve`.
-- [Not against master](https://github.com/kubernetes/website/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+-label%3Ado-not-merge+label%3Alanguage%2Fen+-base%3Amaster): If it's against a `dev-` branch, it's for an upcoming release. Make sure the [release meister](https://github.com/kubernetes/sig-release/tree/master/release-team) knows about it by adding a comment with `/assign @<meister's_github-username>`. If it's against an old branch, help the PR author figure out whether it's targeted against the best branch.
--->
-- [没有签署 CLA, 不能合并](https://github.com/kubernetes/website/pulls?q=is%3Aopen+is%3Apr+label%3A%22cncf-cla%3A+no%22+-label%3Ado-not-merge+label%3Alanguage%2Fen):
-  提醒贡献者签署 CLA。如果机器人和审阅者都已经提醒他们，请关闭 PR，并提醒他们在签署 CLA 后可以重新提交。
-  **在作者没有签署 CLA 之前，不要审阅他们的 PR！**
-- [需要 LGTM](https://github.com/kubernetes/website/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+-label%3Ado-not-merge+label%3Alanguage%2Fen+-label%3Algtm+):
-  如果需要技术审查，请告知机器人所建议的审阅者。如果 PR 需要文档审查或复制编辑，提交更改建议或向 PR 提交一个 copyedit 以使之进入下一步。
-- [有 LGTM ，需要批准](https://github.com/kubernetes/website/pulls?q=is%3Aopen+is%3Apr+-label%3Ado-not-merge+label%3Alanguage%2Fen+label%3Algtm):
-  确定 PR 是否需要进行其他更改或更新才能合并。如果您认为 PR 已准备好合并，请输入 `/approve`。
-- [快速批阅](https://github.com/kubernetes/website/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+base%3Amaster+-label%3A%22do-not-merge%2Fwork-in-progress%22+-label%3A%22do-not-merge%2Fhold%22+label%3A%22cncf-cla%3A+yes%22+label%3A%22size%2FXS%22+label%3A%22language%2Fen%22+)：对于针对 master 分支的小规模 PR，可以快速审阅。
-  在浏览 PR 时，可以注意到 size 标签为 "XS" 的 PRs。
-- [非 master 分支的 PR](https://github.com/kubernetes/website/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+-label%3Ado-not-merge+label%3Alanguage%2Fen+-base%3Amaster)：
-  如果 PR 针对 `dev-` 分支，则表示它适用于即将发布的版本。请添加带有 `/assign @<负责人的 github 账号>` 的注释，确保[发行版本负责人](https://github.com/kubernetes/sig-release/tree/master/release-team)注意到该 PR。如果 PR 是针对旧分支，请帮助 PR 作者确定是否所针对的是最合适的分支。
-
-<!--
-### When to close Pull Requests
-
-Reviews and approvals are one tool to keep our PR queue short and current. Another tool is closure.
--->
-### 什么时候关闭 PR
-
-审查和批准是缩短和更新我们的 PR 队列的一种方式；另一种方式是关闭 PR。
-
-<!--
-- Close any PR where the CLA hasn’t been signed for two weeks. 
-PR authors can reopen the PR after signing the CLA, so this is a low-risk way to make sure nothing gets merged without a signed CLA.
-
-- Close any PR where the author has not responded to comments or feedback in 2 or more weeks.
-
-Don't be afraid to close pull requests. Contributors can easily reopen and resume works in progress. Oftentimes a closure notice is what spurs an author to resume and finish their contribution.
-
-To close a pull request, leave a `/close` comment on the PR.
--->
-- 关闭两个星期未签署 CLA 的 PR。
-  PR 作者可以在签署 CLA 后重新打开 PR，因此这是确保未签署 CLA 的 PR 不会被合并的一种风险较低的方法。
-
-- 如果作者在两周或更长时间内未回复评论或反馈，请关闭 PR。
-
-不要害怕关闭 PR。贡献者可以轻松地重新打开并继续工作。通常，关闭通知会激励作者继续完成其贡献。
-
-要关闭 PR，请在 PR 上输入 `/close`。
-
-<!--
-An automated service, [`fejta-bot`](https://github.com/fejta-bot) automatically marks issues as stale after 90 days of inactivity, then closes them after an additional 30 days of inactivity when they become rotten. PR wranglers should close issues after 14-30 days of inactivity.
--->
-
-{{< note >}}
-一项名为 [`fejta-bot`](https://github.com/fejta-bot) 的自动服务会在 Issue 停滞 90
-天后自动将其标记为过期；然后再等 30 天，如果仍然无人过问，则将其关闭。
-PR 管理者应该在 issues 处于无人过问状态 14-30 天后关闭它们。
-{{< /note >}}
-
 <!--
 ## Propose improvements