103 lines
8.0 KiB
Markdown
103 lines
8.0 KiB
Markdown
---
|
||
title: Kubernetes 社区 - 2017 年开源排行榜榜首
|
||
date: 2018-04-25
|
||
slug: open-source-charts-2017
|
||
---
|
||
<!--
|
||
---
|
||
title: Kubernetes Community - Top of the Open Source Charts in 2017
|
||
date: 2018-04-25
|
||
slug: open-source-charts-2017
|
||
---
|
||
--->
|
||
|
||
<!--
|
||
2017 was a huge year for Kubernetes, and GitHub’s latest [Octoverse report](https://octoverse.github.com) illustrates just how much attention this project has been getting.
|
||
|
||
Kubernetes, an [open source platform for running application containers](/docs/concepts/overview/what-is-kubernetes/), provides a consistent interface that enables developers and ops teams to automate the deployment, management, and scaling of a wide variety of applications on just about any infrastructure.
|
||
--->
|
||
对于 Kubernetes 来说，2017 年是丰收的一年，GitHub的最新 [Octoverse 报告](https://octoverse.github.com) 说明了该项目获得了多少关注。
|
||
|
||
Kubernetes 是 [用于运行应用程序容器的开源平台](/docs/concepts/overview/what-is-kubernetes/)，它提供了一个统一的界面，使开发人员和操作团队能够自动执行部署、管理和扩展几乎任何基础架构上的各种应用程序。
|
||
|
||
<!--
|
||
Solving these shared challenges by leveraging a wide community of expertise and industrial experience, as Kubernetes does, helps engineers focus on building their own products at the top of the stack, rather than needlessly duplicating work that now exists as a standard part of the “cloud native” toolkit.
|
||
|
||
However, achieving these gains via ad-hoc collective organizing is its own unique challenge, one which makes it increasingly difficult to support open source, community-driven efforts through periods of rapid growth.
|
||
|
||
Read on to find out how the Kubernetes Community has addressed these scaling challenges to reach the top of the charts in GitHub’s 2017 Octoverse report.
|
||
--->
|
||
Kubernetes 所做的，是通过利用广泛的专业知识和行业经验来解决这些共同的挑战，可以帮助工程师专注于在堆栈的顶部构建自己的产品，而不是不必要地进行重复工作，比如现在已经存在的 “云原生” 工具包的标准部分。
|
||
|
||
但是，通过临时的集体组织来实现这些收益是它独有的挑战，这使得支持开源，社区驱动的工作变得越来越困难。
|
||
|
||
继续阅读以了解 Kubernetes 社区如何解决这些挑战，从而在 GitHub 的 2017 Octoverse 报告中位居榜首。
|
||
|
||
<!--
|
||
## Most-Discussed on GitHub
|
||
|
||
The top two most-discussed repos of 2017 are both based on Kubernetes:
|
||
|
||
|
||
|
||
Of all the open source repositories on GitHub, none received more issue comments than [kubernetes/kubernetes](https://github.com/kubernetes/kubernetes/). [OpenShift](http://openshift.com/), a [CNCF certified distribution of Kubernetes](https://www.cncf.io/announcement/2017/11/13/cloud-native-computing-foundation-launches-certified-kubernetes-program-32-conformant-distributions-platforms/), took second place.
|
||
|
||
Open discussion with ample time for community feedback and review helps build shared infrastructure and establish new standards for cloud native computing.
|
||
--->
|
||
## GitHub 上讨论最多的
|
||
|
||
2017 年讨论最多的两个仓库都是基于 Kubernetes 的：
|
||
|
||
！[讨论最多](/images/blog-logging/2018-04-24-open-source-charts-2017/most-discussed.png)
|
||
|
||
在 GitHub 的所有开源存储库中，没有比 [kubernetes/kubernetes](https://github.com/kubernetes/kubernetes/) 收到更多的评论。 [OpenShift](http://openshift.com/)， [CNCF 认证的 Kubernetes 发行版](https://www.cncf.io/announcement/2017/11/13/cloud-native-computing-foundation-launches-certified-kubernetes-program-32-conformant-distributions-platforms/) 排名第二。
|
||
|
||
利用充足时间进行公开讨论来获取社区反馈和审查，有助于建立共享的基础架构并为云原生计算建立新标准。
|
||
|
||
<!--
|
||
## Most Reviewed on GitHub
|
||
|
||
Successfully scaling an open source effort’s communications often leads to better coordination and higher-quality feature delivery. The Kubernetes project’s [Special Interest Group (SIG)](https://github.com/kubernetes/community/blob/master/sig-list.md) structure has helped it become GitHub’s second most reviewed project:
|
||
|
||
|
||
|
||
Using SIGs to segment and standardize mechanisms for community participation helps channel more frequent reviews from better-qualified community members.
|
||
|
||
When managed effectively, active community discussions indicate more than just a highly contentious codebase, or a project with an extensive list of unmet needs.
|
||
--->
|
||
## GitHub 上审阅最多的
|
||
|
||
成功扩展开放源代码工作的通信通常会带来更好的协调和更高质量的功能交付。Kubernetes 项目的 [Special Interest Group（SIG）](https://github.com/kubernetes/community/blob/master/sig-list.md) 结构已使其成为 GitHub 审阅第二多的项目：
|
||
|
||
！[审阅最多](/images/blog-logging/2018-04-24-open-source-charts-2017/most-reviews.png)
|
||
|
||
使用 SIG 对社区参与机制进行细分和标准化有助于从资格更高的社区成员中获得更频繁的审阅。
|
||
|
||
如果得到有效管理，活跃的社区讨论不仅表明代码库存在很大的争议，也可能表明项目包含大量未满足的需求。
|
||
|
||
<!--
|
||
Scaling a project’s capacity to handle issues and community interactions helps to expand the conversation. Meanwhile, large communities come with more diverse use cases and a larger array of support problems to manage. The Kubernetes [SIG organization structure](https://github.com/kubernetes/community#sigs) helps to address the challenges of complex communication at scale.
|
||
|
||
SIG meetings provide focused opportunities for users, maintainers, and specialists from various disciplines to collaborate together in support of this community effort. These investments in organizing help create an environment where it’s easier to prioritize architecture discussion and planning over commit velocity; enabling the project to sustain this kind of scale.
|
||
--->
|
||
扩展项目处理问题和社区互动的能力有助于扩大交流。同时，大型社区具有更多不同的用例和更多的支持问题需要管理。Kubernetes [SIG 组织结构](https://github.com/kubernetes/community#sigs) 帮助应对大规模复杂通信的挑战。
|
||
|
||
SIG 会议为不同学科的用户、维护者和专家提供了重点合作的机会，以共同协作来支持社区的工作。这些在组织上的投资有助于创建一个环境，在这样的环境中，可以更轻松地将架构讨论和规划的优先级排到提交速度前面，并使项目能够维持这种规模。
|
||
|
||
<!--
|
||
## Join the party!
|
||
|
||
You may already be using solutions that are successfully managed and scaled on Kubernetes. For example, GitHub.com, which hosts Kubernetes’ upstream source code, [now runs on Kubernetes](https://githubengineering.com/kubernetes-at-github/) as well!
|
||
|
||
Check out the [Kubernetes Contributors’ guide](https://github.com/kubernetes/community/blob/master/contributors/guide/README.md) for more information on how to get started as a contributor.
|
||
|
||
You can also join the [weekly Kubernetes Community meeting](https://github.com/kubernetes/community/tree/master/communication#weekly-meeting) and consider [joining a SIG or two](https://github.com/kubernetes/community/blob/master/sig-list.md#master-sig-list).
|
||
--->
|
||
## 加入我们！
|
||
|
||
您可能已经在 Kubernetes 上成功使用管理和扩展的解决方案。例如，托管 Kubernetes 上游源代码的 GitHub.com [现在也可以在 Kubernetes 上运行](https://githubengineering.com/kubernetes-at-github/) ！
|
||
|
||
请查看 [Kubernetes 贡献者指南](https://github.com/kubernetes/community/blob/master/contributors/guide/README.md) ，以获取有关如何开始作为贡献者的更多信息。
|
||
|
||
您也可以参加 [每周 Kubernetes 的社区会议](https://github.com/kubernetes/community/tree/master/communication#weekly-meeting) 并考虑 [加入一个或两个 SIG](https://github.com/kubernetes/community/blob/master/sig-list.md#master-sig-list)。
|