@@ -21,20 +21,21 @@ to learn about more ways to contribute. You need to use the Git command line
21
21
client and other tools for some of these tasks.
22
22
-->
23
23
24
- 如果你已经了解如何[ 贡献新内容] ( /zh/docs/contribute/new-content/overview / ) 和
25
- [ 评阅他人工作] ( /zh/docs/contribute/review/reviewing-prs/ ) ,并准备了解更多贡献的途径,
24
+ 如果你已经了解如何[ 贡献新内容] ( /zh-cn /docs/contribute/new-content/ ) 和
25
+ [ 评阅他人工作] ( /zh-cn /docs/contribute/review/reviewing-prs/ ) ,并准备了解更多贡献的途径,
26
26
请阅读此文。你需要使用 Git 命令行工具和其他工具做这些工作。
27
27
28
28
<!-- body -->
29
29
30
30
<!--
31
31
## Propose improvements
32
32
33
- SIG Docs [members](/docs/contribute/participate/roles-and-responsibilities/#members) can propose improvements.
33
+ SIG Docs [members](/docs/contribute/participate/roles-and-responsibilities/#members)
34
+ can propose improvements.
34
35
-->
35
- ## 提出改进建议
36
+ ## 提出改进建议 {#propose-improvements}
36
37
37
- SIG Docs 的 [ 成员] ( /zh/docs/contribute/participate/roles-and-responsibilities/#members ) 可以提出改进建议。
38
+ SIG Docs 的[ 成员] ( /zh-cn /docs/contribute/participate/roles-and-responsibilities/#members ) 可以提出改进建议。
38
39
39
40
<!--
40
41
After you've been contributing to the Kubernetes documentation for a while, you
@@ -50,8 +51,8 @@ changes. The quickest way to get answers to questions about how the documentatio
50
51
currently works is to ask in the `#sig-docs` Slack channel on
51
52
[kubernetes.slack.com](https://kubernetes.slack.com)
52
53
-->
53
- 在对 Kubernetes 文档贡献了一段时间后,你可能会对[ 样式指南] ( /zh/docs/contribute/style/style-guide/ ) 、
54
- [ 内容指南] ( /zh/docs/contribute/style/content-guide/ ) 、用于构建文档的工具链、网站样式、
54
+ 在对 Kubernetes 文档贡献了一段时间后,你可能会对[ 样式指南] ( /zh-cn /docs/contribute/style/style-guide/ ) 、
55
+ [ 内容指南] ( /zh-cn /docs/contribute/style/content-guide/ ) 、用于构建文档的工具链、网站样式、
55
56
评审和合并 PR 的流程或者文档的其他方面产生改进的想法。
56
57
为了尽可能透明化,这些提议都需要在 SIG Docs 会议或
57
58
[ kubernetes-sig-docs 邮件列表] ( https://groups.google.com/forum/#!forum/kubernetes-sig-docs ) 上讨论。
@@ -66,18 +67,19 @@ appropriate. For instance, an update to the style guide or the website's
66
67
functionality might involve opening a pull request, while a change related to
67
68
documentation testing might involve working with sig-testing.
68
69
-->
69
- 在进行了讨论并且 SIG 就期望的结果达成一致之后,你就能以最合理的方式处理改进建议了。例如,样式指南或网站功能的更新可能涉及 PR 的新增,而与文档测试相关的更改可能涉及 sig-testing。
70
+ 在进行了讨论并且 SIG 就期望的结果达成一致之后,你就能以最合理的方式处理改进建议了。
71
+ 例如,样式指南或网站功能的更新可能涉及 PR 的新增,而与文档测试相关的更改可能涉及 sig-testing。
70
72
71
73
<!--
72
74
## Coordinate docs for a Kubernetes release
73
75
74
- SIG Docs [approvers](/docs/contribute/participating/ #approvers) can coordinate
75
- docs for a Kubernetes release.
76
+ SIG Docs [approvers](/docs/contribute/participate/roles-and-responsibilities/ #approvers)
77
+ can coordinate docs for a Kubernetes release.
76
78
-->
77
- ## 为 Kubernetes 版本发布协调文档工作
79
+ ## 为 Kubernetes 版本发布协调文档工作 {#coordinate-docs-for-a-kubernetes-release}
78
80
79
- SIG Docs 的[ 批准者(approvers)] ( /zh/docs/contribute/participating/ #approvers ) 可以为
80
- Kubernetes 版本发布协调文档工作。
81
+ SIG Docs 的[ 批准者(approvers)] ( /zh-cn /docs/contribute/participate/roles-and-responsibilities/ #approvers )
82
+ 可以为 Kubernetes 版本发布协调文档工作。
81
83
82
84
<!--
83
85
Each Kubernetes release is coordinated by a team of people participating in the
@@ -129,37 +131,37 @@ rotated among SIG Docs approvers.
129
131
<!--
130
132
## Serve as a New Contributor Ambassador
131
133
132
- SIG Docs [approvers](/docs/contribute/participating/ #approvers) can serve as
133
- New Contributor Ambassadors.
134
+ SIG Docs [approvers](/docs/contribute/participate/roles-and-responsibilities/ #approvers)
135
+ can serve as New Contributor Ambassadors.
134
136
135
- New Contributor Ambassadors work together to welcome new contributors to SIG-Docs,
137
+ New Contributor Ambassadors welcome new contributors to SIG-Docs,
136
138
suggest PRs to new contributors, and mentor new contributors through their first
137
139
few PR submissions.
138
140
139
141
Responsibilities for New Contributor Ambassadors include:
140
142
-->
141
143
142
- ## 担任新的贡献者大使
144
+ ## 担任新的贡献者大使 {#serve-as-a-new-contributor-ambassador}
143
145
144
- SIG Docs [ 批准人(Approvers)] ( /zh/docs/contribute/participating/ #approvers )
146
+ SIG Docs [ 批准人(Approvers)] ( /zh-cn /docs/contribute/participate/roles-and-responsibilities/ #approvers )
145
147
可以担任新的贡献者大使。
146
148
147
- 新的贡献者大使共同努力欢迎 SIG-Docs 的新贡献者,对新贡献者的 PR 提出建议,
149
+ 新的贡献者大使欢迎 SIG-Docs 的新贡献者,对新贡献者的 PR 提出建议,
148
150
以及在前几份 PR 提交中指导新贡献者。
149
151
150
152
新的贡献者大使的职责包括:
151
153
152
154
<!--
153
155
- Being available on the [Kubernetes #sig-docs channel](https://kubernetes.slack.com) to answer questions from new contributors.
154
- - Working with PR wranglers to identify [good first issues](https://kubernetes.dev/docs/guide/help-wanted/#good-first-issue) for new contributors.
155
- - Mentoring new contributors through their first few PRs to the docs repo.
156
+ - Working with PR wranglers to identify [good first issues](https://kubernetes.dev/docs/guide/help-wanted/#good-first-issue) for new contributors.
157
+ - Mentoring new contributors through their first few PRs to the docs repo.
156
158
- Helping new contributors create the more complex PRs they need to become Kubernetes members.
157
- -[Sponsoring contributors](/docs/contribute/advanced/#sponsor-a-new-contributor) on their path to becoming Kubernetes members.
159
+ - [Sponsoring contributors](/docs/contribute/advanced/#sponsor-a-new-contributor) on their path to becoming Kubernetes members.
158
160
- Hosting a monthly meeting to help and mentor new contributors.
159
161
-->
160
162
- 监听 [ Kubernetes #sig-docs 频道] ( https://kubernetes.slack.com ) 上新贡献者的 Issue。
161
- - 与 PR 管理者合作为新参与者寻找[ 合适的第一个 issues] ( https://kubernetes.dev/docs/guide/help-wanted/#good-first-issue ) 。
162
- - 通过前几个 PR 指导新贡献者为文档存储库作贡献。
163
+ - 与 PR 管理者合作为新参与者寻找[ 合适的第一个 issues] ( https://kubernetes.dev/docs/guide/help-wanted/#good-first-issue ) 。
164
+ - 通过前几个 PR 指导新贡献者为文档存储库作贡献。
163
165
- 帮助新的贡献者创建成为 Kubernetes 成员所需的更复杂的 PR。
164
166
- [ 为贡献者提供保荐] ( #sponsor-a-new-contributor ) ,使其成为 Kubernetes 成员。
165
167
- 每月召开一次会议,帮助和指导新的贡献者。
@@ -172,22 +174,23 @@ Current New Contributor Ambassadors are announced at each SIG-Docs meeting and i
172
174
<!--
173
175
## Sponsor a new contributor
174
176
175
- SIG Docs [reviewers](/docs/contribute/participating/ #reviewers) can sponsor
176
- new contributors.
177
+ SIG Docs [reviewers](/docs/contribute/participate/roles-and-responsibilities/ #reviewers)
178
+ can sponsor new contributors.
177
179
-->
178
180
## 为新的贡献者提供保荐 {#sponsor-a-new-contributor}
179
181
180
- SIG Docs 的[ 评审人(Reviewers)] ( /zh/docs/contribute/participating/#reviewers ) 可以为新的贡献者提供保荐。
182
+ SIG Docs 的[ 评审人(Reviewers)] ( /zh-cn/docs/contribute/participate/roles-and-responsibilities/#reviewers )
183
+ 可以为新的贡献者提供保荐。
181
184
182
185
<!--
183
186
After a new contributor has successfully submitted 5 substantive pull requests
184
187
to one or more Kubernetes repositories, they are eligible to apply for
185
- [membership](/docs/contribute/participating #members) in the Kubernetes
186
- organization. The contributor's membership needs to be backed by two sponsors
187
- who are already reviewers.
188
+ [membership](/docs/contribute/participate/roles-and-responsibilities/ #members)
189
+ in the Kubernetes organization. The contributor's membership needs to be
190
+ backed by two sponsors who are already reviewers.
188
191
-->
189
192
新的贡献者针对一个或多个 Kubernetes 项目仓库成功提交了 5 个实质性 PR 之后,
190
- 就有资格申请 Kubernetes 组织的[ 成员身份] ( /zh/docs/contribute/participate/roles-and-responsibilities/#members ) 。
193
+ 就有资格申请 Kubernetes 组织的[ 成员身份] ( /zh-cn /docs/contribute/participate/roles-and-responsibilities/#members ) 。
191
194
贡献者的成员资格需要同时得到两位评审人的保荐。
192
195
193
196
<!--
@@ -212,18 +215,23 @@ can serve a term as a co-chair of SIG Docs.
212
215
213
216
### Prerequisites
214
217
-->
215
- ## 担任 SIG 联合主席
218
+ ## 担任 SIG 联合主席 {#sponsor-a-new-contributor}
216
219
217
- SIG Docs [ 成员(Members)] ( /zh/docs/contribute/participate/roles-and-responsibilities/#members )
220
+ SIG Docs [ 成员(Members)] ( /zh-cn /docs/contribute/participate/roles-and-responsibilities/#members )
218
221
可以担任 SIG Docs 的联合主席。
219
222
220
- ### 前提条件
223
+ ### 前提条件 {#prerequisites}
221
224
222
225
<!--
223
226
A Kubernetes member must meet the following requirements to be a co-chair:
224
227
225
228
- Understand SIG Docs workflows and tooling: git, Hugo, localization, blog subproject
226
- - Understand how other Kubernetes SIGs and repositories affect the SIG Docs workflow, including: [teams in k/org](https://github.com/kubernetes/org/blob/master/config/kubernetes/sig-docs/teams.yaml), the [process in k/community](https://github.com/kubernetes/community/tree/master/sig-docs), plugins in [k/test-infra](https://github.com/kubernetes/test-infra/), and the role of [SIG Architecture](https://github.com/kubernetes/community/tree/master/sig-architecture).
229
+ - Understand how other Kubernetes SIGs and repositories affect the SIG Docs
230
+ workflow, including:
231
+ [teams in k/org](https://github.com/kubernetes/org/blob/master/config/kubernetes/sig-docs/teams.yaml), the
232
+ [process in k/community](https://github.com/kubernetes/community/tree/master/sig-docs),
233
+ plugins in [k/test-infra](https://github.com/kubernetes/test-infra/), and the role of
234
+ [SIG Architecture](https://github.com/kubernetes/community/tree/master/sig-architecture).
227
235
In addition, understand how the [Kubernetes docs release process](/docs/contribute/advanced/#coordinate-docs-for-a-kubernetes-release) works.
228
236
- Approved by the SIG Docs community either directly or via lazy consensus.
229
237
- Commit at least 5 hours per week (and often more) to the role for a minimum of 6 months
@@ -235,8 +243,8 @@ Kubernetes 成员必须满足以下要求才能成为联合主席:
235
243
[ k/org 中的团队] ( https://github.com/kubernetes/org/blob/master/config/kubernetes/sig-docs/teams.yaml ) 、
236
244
[ k/community 中的流程] ( https://github.com/kubernetes/community/tree/master/sig-docs ) 、
237
245
[ k/test-infra] ( https://github.com/kubernetes/test-infra/ ) 中的插件、
238
- [ SIG Architecture] ( https://github.com/kubernetes/community/tree/master/sig-architecture ) 中的角色。
239
- 此外,了解 [ Kubernetes 文档发布流程] ( /docs/contribute/advanced/#coordinate-docs-for-a-kubernetes-release ) 的工作原理。
246
+ [ SIG Architecture] ( https://github.com/kubernetes/community/tree/master/sig-architecture ) 中的角色。
247
+ 此外,了解 [ Kubernetes 文档发布流程] ( /zh-cn/ docs/contribute/advanced/#coordinate-docs-for-a-kubernetes-release ) 的工作原理。
240
248
- 由 SIG Docs 社区直接或通过惰性共识批准。
241
249
- 在至少 6 个月的时段内,确保每周至少投入 5 个小时(通常更多)
242
250
@@ -247,7 +255,7 @@ The role of co-chair is primarily one of service: co-chairs handle process and p
247
255
248
256
Responsibilities include:
249
257
-->
250
- ### 职责范围
258
+ ### 职责范围 {#responsibilities}
251
259
252
260
联合主席主要提供以下服务:
253
261
联合主席负责处理流程和政策、时间安排和召开会议、安排 PR 管理员、以及一些其他人不想做的事情,目的是增长贡献者团队。
@@ -282,7 +290,7 @@ To schedule and run effective meetings, these guidelines show what to do, how to
282
290
283
291
- Hold respectful, inclusive discussions with respectful, inclusive language.
284
292
-->
285
- ### 召开高效的会议
293
+ ### 召开高效的会议 {#running-effective-meetings}
286
294
287
295
为了安排和召开高效的会议,这些指南说明了如何做、怎样做以及原因。
288
296
@@ -332,7 +340,7 @@ For weekly meetings, copypaste the previous week's notes into the "Past meetings
332
340
333
341
**Honor folks' time**:
334
342
335
- - Begin and end meetings punctually
343
+ Begin and end meetings on time.
336
344
-->
337
345
** 根据需要来进行协调** :
338
346
@@ -341,7 +349,7 @@ For weekly meetings, copypaste the previous week's notes into the "Past meetings
341
349
342
350
** 尊重大家的时间** :
343
351
344
- - 准时开始和结束会议
352
+ 按时开始和结束会议
345
353
346
354
<!--
347
355
**Use Zoom effectively**:
@@ -362,12 +370,12 @@ For weekly meetings, copypaste the previous week's notes into the "Past meetings
362
370
### Recording meetings on Zoom
363
371
364
372
When you're ready to start the recording, click Record to Cloud.
365
-
373
+
366
374
When you're ready to stop recording, click Stop.
367
375
368
376
The video uploads automatically to YouTube.
369
377
-->
370
- ### 录制 Zoom 会议
378
+ ### 录制 Zoom 会议 {#recording-meetings-on-zoom}
371
379
372
380
准备开始录制时,请单击“录制到云”。
373
381
0 commit comments