|
| 1 | +--- |
| 2 | +title: Issue 管理者 |
| 3 | +content_type: concept |
| 4 | +weight: 20 |
| 5 | +--- |
| 6 | +<!-- |
| 7 | +title: Issue Wranglers |
| 8 | +content_type: concept |
| 9 | +weight: 20 |
| 10 | +--> |
| 11 | + |
| 12 | +<!-- overview --> |
| 13 | + |
| 14 | +<!-- |
| 15 | +Alongside the [PR Wrangler](/docs/contribute/participate/pr-wranglers),formal approvers, and reviewers, members of SIG Docs take week long shifts [triaging and categorising issues](/docs/contribute/review/for-approvers.md/#triage-and-categorize-issues) for the repository. |
| 16 | +--> |
| 17 | +除了承担 [PR 管理者](/zh-cn/docs/contribute/participate/pr-wranglers)的职责外， |
| 18 | +SIG Docs 正式的批准人（Approver）、评审人（Reviewer）和成员（Member） |
| 19 | +按周轮流[归类仓库的 Issue](/zh-cn/docs/contribute/review/for-approvers.md/#triage-and-categorize-issues)。 |
| 20 | + |
| 21 | +<!-- body --> |
| 22 | + |
| 23 | +<!-- |
| 24 | +## Duties |
| 25 | +
|
| 26 | +Each day in a week-long shift the Issue Wrangler will be responsible for: |
| 27 | +
|
| 28 | +- Triaging and tagging incoming issues daily. See [Triage and categorize issues](https://github.com/kubernetes/website/blob/main/content/en/docs/contribute/review/for-approvers.md/#triage-and-categorize-issues) for guidelines on how SIG Docs uses metadata. |
| 29 | +- Keeping an eye on stale & rotten issues within the kubernetes/website repository. |
| 30 | +- Maintenance of the [Issues board](https://github.com/orgs/kubernetes/projects/72/views/1). |
| 31 | +--> |
| 32 | +## 职责 {#duties} |
| 33 | + |
| 34 | +在为期一周的轮值期内，Issue 管理者每天负责： |
| 35 | + |
| 36 | +- 对收到的 Issue 进行日常分类和标记。有关 SIG Docs 如何使用元数据的指导说明， |
| 37 | + 参阅[归类 Issue](https://github.com/kubernetes/website/blob/main/content/en/docs/contribute/review/for-approvers.md/#triage-and-categorize-issues)。 |
| 38 | +- 密切关注 kubernetes/website 代码仓库中陈旧和过期的 Issue。 |
| 39 | +- 维护 [Issues 看板](https://github.com/orgs/kubernetes/projects/72/views/1)。 |
| 40 | + |
| 41 | +<!-- |
| 42 | +### Requirements |
| 43 | +
|
| 44 | +- Must be an active member of the Kubernetes organization. |
| 45 | +- A minimum of 15 [non-trivial](https://www.kubernetes.dev/docs/guide/pull-requests/#trivial-edits) contributions to Kubernetes (of which a certain amount should be directed towards kubernetes/website). |
| 46 | +- Performing the role in an informal capacity already |
| 47 | +--> |
| 48 | +### 要求 {#requirements} |
| 49 | + |
| 50 | +- 必须是 Kubernetes 组织的活跃成员。 |
| 51 | +- 至少为 Kubernetes 做了 15 |
| 52 | + 个[非小微](https://www.kubernetes.dev/docs/guide/pull-requests/#trivial-edits)的贡献 |
| 53 | + （其中某些应是直接针对 kubernetes/website 的贡献）。 |
| 54 | +- 已经以非正式身份履行该职责。 |
| 55 | + |
| 56 | +<!-- |
| 57 | +### Helpful [Prow commands](https://prow.k8s.io/command-help) for wranglers |
| 58 | +--> |
| 59 | +### 对管理者有帮助的 [Prow 命令](https://prow.k8s.io/command-help) |
| 60 | + |
| 61 | +<!-- |
| 62 | +``` |
| 63 | +# reopen an issue |
| 64 | +/reopen |
| 65 | +
|
| 66 | +# transfer issues that don't fit in k/website to another repository |
| 67 | +/transfer[-issue] |
| 68 | +
|
| 69 | +# change the state of rotten issues |
| 70 | +/remove-lifecycle rotten |
| 71 | +
|
| 72 | +# change the state of stale issues |
| 73 | +/remove-lifecycle stale |
| 74 | +
|
| 75 | +# assign sig to an issue |
| 76 | +/sig <sig_name> |
| 77 | +
|
| 78 | +# add specific area |
| 79 | +/area <area_name> |
| 80 | +
|
| 81 | +# for beginner friendly issues |
| 82 | +/good-first-issue |
| 83 | +
|
| 84 | +# issues that needs help |
| 85 | +/help wanted |
| 86 | +
|
| 87 | +# tagging issue as support specific |
| 88 | +/kind support |
| 89 | +
|
| 90 | +# to accept triaging for an issue |
| 91 | +/triage accepted |
| 92 | +
|
| 93 | +# closing an issue we won't be working on and haven't fixed yet |
| 94 | +/close not-planned |
| 95 | +``` |
| 96 | +--> |
| 97 | +``` |
| 98 | +# 重新打开 Issue |
| 99 | +/reopen |
| 100 | +
|
| 101 | +# 将不切合 k/website 的 Issue 转移到其他代码仓库 |
| 102 | +/transfer[-issue] |
| 103 | +
|
| 104 | +# 更改陈旧 Issue 的状态 |
| 105 | +/remove-lifecycle rotten |
| 106 | +
|
| 107 | +# 更改过期 Issue 的状态 |
| 108 | +/remove-lifecycle stale |
| 109 | +
|
| 110 | +# 为 Issue 指派 SIG |
| 111 | +/sig <sig_name> |
| 112 | +
|
| 113 | +# 添加具体领域 |
| 114 | +/area <area_name> |
| 115 | +
|
| 116 | +# 对新手友好的 Issue |
| 117 | +/good-first-issue |
| 118 | +
|
| 119 | +# 需要帮助的 Issue |
| 120 | +/help wanted |
| 121 | +
|
| 122 | +# 将 Issue 标记为某种支持 |
| 123 | +/kind support |
| 124 | +
|
| 125 | +# 接受某个 Issue 的归类 |
| 126 | +/triage accepted |
| 127 | +
|
| 128 | +# 关闭还未处理且未修复的 Issue |
| 129 | +/close not-planned |
| 130 | +``` |
| 131 | + |
| 132 | +<!-- |
| 133 | +### When to close Issues |
| 134 | +
|
| 135 | +For an open source project to succeed, good issue management is crucial. But it is also critical to resolve issues in order to maintain the repository and communicate clearly with contributors and users. |
| 136 | +--> |
| 137 | +### 何时关闭 Issue {#when-to-close-issues} |
| 138 | + |
| 139 | +一个开源项目想要成功，良好的 Issue 管理非常关键。 |
| 140 | +但解决 Issue 也很重要，这样才能维护代码仓库，并与贡献者和用户进行清晰明确的交流。 |
| 141 | + |
| 142 | +<!-- |
| 143 | +Close issues when: |
| 144 | +
|
| 145 | +- A similar issue is reported more than once.You will first need to tag it as /triage duplicate; link it to the main issue & then close it. It is also advisable to direct the users to the original issue. |
| 146 | +- It is very difficult to understand and address the issue presented by the author with the information provided. |
| 147 | + However, encourage the user to provide more details or reopen the issue if they can reproduce it later. |
| 148 | +- The same functionality is implemented elsewhere. One can close this issue and direct user to the appropriate place. |
| 149 | +- The reported issue is not currently planned or aligned with the project's goals. |
| 150 | +- If the issue appears to be spam and is clearly unrelated. |
| 151 | +- If the issue is related to an external limitation or dependency and is beyond the control of the project. |
| 152 | +--> |
| 153 | +关闭 Issue 的时机包括： |
| 154 | + |
| 155 | +- 类似的 Issue 被多次报告。你首先需要将其标记为 /triage duplicate； |
| 156 | + 将其链接到主要 Issue 然后关闭它。还建议将用户引导至最初的 Issue。 |
| 157 | +- 通过所提供的信息很难理解和解决作者提出的 Issue。 |
| 158 | + 但要鼓励用户提供更多细节，或者在以后可以重现 Issue 时重新打开此 Issue 。 |
| 159 | +- 相同的功能在其他地方已实现。管理者可以关闭此 Issue 并将用户引导至适当的位置。 |
| 160 | +- 报告的 Issue 当前未被计划或不符合项目的目标。 |
| 161 | +- 如果 Issue 看起来是垃圾信息并且明显不相关。 |
| 162 | +- 如果 Issue 与外部限制或依赖项有关并且超出了本项目的控制范围。 |
| 163 | + |
| 164 | +<!-- |
| 165 | +To close an issue, leave a `/close` comment on the issue. |
| 166 | +--> |
| 167 | +要关闭 Issue，可以在 Issue 中留下一条 `/close` 的评论。 |
0 commit comments