kubernetes-retired / kubernetes-docs-zh Goto Github PK

Let's begin from index : )

Umbrella issue of all kubectl commands translation.

• kubectl
• kubectl annotate
• kubectl api-versions
• kubectl apply
• kubectl attach
• kubectl autoscale
• kubectl cluster-info
• kubectl config
• kubectl create
• kubectl delete
• kubectl describe
• kubectl edit
• kubectl exec
• kubectl expose
• kubectl get
• kubectl label
• kubectl logs
• kubectl namespace
• kubectl patch
• kubectl port-forward
• kubectl proxy
• kubectl replace
• kubectl rolling-update
• kubectl run
• kubectl scale
• kubectl stop
• kubectl version

I already have sent two emails to hanjiayao to apply in the translation group.
I just want to know how long will it takes to get the reply.
Thanks.

Small docs : )

Please refer to PR #3

Start to merge.

it is really a big help to come up with such a repo.

I just want to know what if the original docs updates, what's the way to let us be aware and do the corresponding updates.

As per the email sent to kubernetes-dev[1], please create a SECURITY_CONTACTS
file.

The template for the file can be found in the kubernetes-template repository[2].
A description for the file is in the steering-committee docs[3], you might need
to search that page for "Security Contacts".

Please feel free to ping me on the PR when you make it, otherwise I will see when
you close this issue. :)

Thanks so much, let me know if you have any questions.

(This issue was generated from a tool, apologies for any weirdness.)

[1] https://groups.google.com/forum/#!topic/kubernetes-dev/codeiIoQ6QE
[2] https://github.com/kubernetes/kubernetes-template-project/blob/master/SECURITY_CONTACTS
[3] https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance-template-short.md

The jekyll auto-generated pages and cache files etc are a little annoying, I think they are better being ignored and not committed into the repo.

Need to provide some instructions on how to send a PR to this repo. For some of our volunteers are not familiar with git.

• docs/admin/cluster-management.md
• docs/admin/cluster-components.md
• docs/admin/multi-cluster.md
• docs/admin/cluster-large.md
• docs/admin/high-availability.md

As far, we need to prioritize the articles left to speed up the translation. Here are the principles we had agreement until now:

1. Add a new column including P0-PN in the index table to identify the priorities: P0s are the most urgent tasks, PN can scale from 1-4 (just my opinion). [Owner: TBD]
2. Ignore the auto-generated files at present. Should list all the files. [Owner: TBD]
3. Ignore the articles indicating feature has been deprecated. Should list all the files. [Owner: TBD]

Any suggestions are welcomed!

@hanjiayao @chentao1596 @linyouchong @zhangxiaoyu-zidif @xiangpengzhao @zhouhaibing089 @lichuqiang @markthink

;-)

Such as: Need Review, to align with those in kubernetes/kubernetes.github.io

@hurf 我是否可以帮助你一起负责计划和验证这个git repo的PR？

This is the list i've been working on:

• docs/user-guide/index.md
• docs/user-guide/annotations.md
• docs/user-guide/labels.md
• docs/user-guide/namespaces.md
• docs/user-guide/identifiers.md
• docs/user-guide/pods.md
• docs/user-guide/replication-controller.md
• docs/user-guide/service.md
• docs/user-guide/volumes.md
• docs/user-guide/secrets.md

The items checked are translated already, once i've finished the list above I will send a pull request by the end of the week soon.

1. We need a clear standard for the condition under which a PR could get merged，say a certain number of guys have reviewed and approved.
2. Commit records might need to be squashed before PR get merged, as we do in k8s repo.
3. We may need to add a list to the CI-robot, which includes the guys who are active in the field of translation. Thus, a new PR could be assigned to one of the guys in the list for review automatically or manually.

Please feel free to give your opinions:)

Start to translate

RT

Kubernetes 中英文词汇标准对应表

Kubernetes 中英文词汇标准对应表 的完善分两步走：

第一阶段：在12月31日之前，定一个基础版本的中英文词汇对照表。

先由 @李晶晶-H3C-成都 @宋净超-jimmysong.io @石龙-HandReach-青岛 @时延军-希为科技-北京 @李储强-华为-杭州 @苏楚霖-IBM-深圳 @陈涛-ZTE-三亚 @张琦翔-geniusafc-上海 @邢舟-IBM 一起完善一下中英词汇的标准化，有不同的意见，可以在此留言，默认大家提交的初始化版本，都是采纳状态。

第二阶段：在12月31日之后，新词汇的加入方式

元旦之后，新增的词汇，默认都是未采纳状态，每个新增词汇需通过讨论确定最优的翻译结果。

注：初始词汇的翻译邀请是以前期贡献的顺序排名的..当然未邀请的译者，有兴趣也是可以参与一起完善初始版本的中英文词汇表的，此表并未记名。

我们希望能够保持一份精减，大家容易有岐义的词汇对照表，尽可能给新加入的译者不会造成过多的困惑。

这里会每周同步 Google 词汇表格的更新记录：

kubernetes master node => kubernetes master节点
kubernetes worker node => kubernetes worker节点
load balancer => 负载均衡器
API Server => API 服务器
load balance => 负载均衡
runtime => runtime
cloud provider =>云服务提供商
dns entry => dns 条目
control plane => 控制平面