|
| 1 | +--- |
| 2 | +title: 为 Kubernetes 博客做贡献 |
| 3 | +slug: blog-contribution |
| 4 | +content_type: concept |
| 5 | +weight: 15 |
| 6 | +simple_list: true |
| 7 | +--- |
| 8 | +<!-- |
| 9 | +title: Contributing to Kubernetes blogs |
| 10 | +slug: blog-contribution |
| 11 | +content_type: concept |
| 12 | +weight: 15 |
| 13 | +simple_list: true |
| 14 | +--> |
| 15 | + |
| 16 | +<!-- overview --> |
| 17 | + |
| 18 | +<!-- |
| 19 | +There are two official Kubernetes blogs, and the CNCF has [its own blog](https://www.cncf.io/blog/) where you can cover Kubernetes too. |
| 20 | +For the main Kubernetes blog, we (the Kubernetes project) like to publish articles with different perspectives and special focuses, that have a link to Kubernetes. |
| 21 | +--> |
| 22 | +Kubernetes 有两个官方博客,同时 CNCF 也有[其自己的博客](https://www.cncf.io/blog/), |
| 23 | +你也可以在 CNCF 博客上面撰写 Kubernetes 相关内容。对于 Kubernetes 主博客, |
| 24 | +我们(Kubernetes 项目)希望发布具有不同视角和特定关注点的文章,这些文章需与 Kubernetes 有所关联。 |
| 25 | + |
| 26 | +<!-- |
| 27 | +With only a few special case exceptions, we only publish content that hasn't been submitted or published anywhere else. |
| 28 | +
|
| 29 | +Read the [blog guidelines](/docs/contribute/blog/guidelines/#what-we-publish) for more about that aspect. |
| 30 | +--> |
| 31 | +除极少数特殊情况外,我们只发布未在其他任何地方提交过或发表过的内容。 |
| 32 | + |
| 33 | +参阅[博客指南](/zh-cn/docs/contribute/blog/guidelines/#what-we-publish)了解更多相关要求。 |
| 34 | + |
| 35 | +<!-- |
| 36 | +## Official Kubernetes blogs |
| 37 | +
|
| 38 | +### Main blog |
| 39 | +
|
| 40 | +The main [Kubernetes blog](/blog/) is used by the project to communicate new features, community reports, and any |
| 41 | +news that might be relevant to the Kubernetes community. This includes end users and developers. |
| 42 | +Most of the blog's content is about things happening in the core project, but Kubernetes |
| 43 | +as a project encourages you to submit about things happening elsewhere in the ecosystem too! |
| 44 | +--> |
| 45 | +## Kubernetes 官方博客 {#official-kubernetes-blogs} |
| 46 | + |
| 47 | +### 主博客 {#main-blog} |
| 48 | + |
| 49 | +[Kubernetes 主博客](/zh-cn/blog/)由 Kubernetes 项目组发布新特性、社区报告以及可能与 |
| 50 | +Kubernetes 社区相关的所有新闻。这些内容面向终端用户和开发者。 |
| 51 | +大部分博客的内容围绕核心项目展开,但 Kubernetes 作为一个开源项目,也鼓励大家提交关于生态系统中其他方面的内容! |
| 52 | + |
| 53 | +<!-- |
| 54 | +Anyone can write a blog post and submit it for publication. With only a few special case exceptions, we only publish content that hasn't been submitted or published anywhere else. |
| 55 | +
|
| 56 | +### Contributor blog |
| 57 | +
|
| 58 | +The [Kubernetes contributor blog](https://k8s.dev/blog/) is aimed at an audience of people who |
| 59 | +work **on** Kubernetes more than people who work **with** Kubernetes. The Kubernetes project |
| 60 | +deliberately publishes some articles to both blogs. |
| 61 | +
|
| 62 | +Anyone can write a blog post and submit it for review. |
| 63 | +--> |
| 64 | +任何人都可以撰写博文并提交发布。除极少数特殊情况外,我们仅发布未在其他任何地方提交过或发表过的内容。 |
| 65 | + |
| 66 | +### 贡献者博客 {#contributor-blog} |
| 67 | + |
| 68 | +[Kubernetes 贡献者博客](https://k8s.dev/blog/)面向的是**参与 Kubernetes 的开发者**, |
| 69 | +而非**使用 Kubernetes 的用户**。Kubernetes 项目会有意同时在两个博客上都发布某些文章。 |
| 70 | + |
| 71 | +任何人都可以撰写博文并提交审核。 |
| 72 | + |
| 73 | +<!-- |
| 74 | +## Article updates and maintenance {#maintenance} |
| 75 | +
|
| 76 | +The Kubernetes project does not maintain older articles for its blogs. This means that any |
| 77 | +published article more than one year old will normally **not** be eligible for issues or pull |
| 78 | +requests that ask for changes. To avoid establishing precedent, even technically correct pull |
| 79 | +requests are likely to be rejected. |
| 80 | +--> |
| 81 | +## 文章更新与维护 {#maintenance} |
| 82 | + |
| 83 | +Kubernetes 项目不维护博客中较旧的文章。这意味着, |
| 84 | +任何发布超过一年的文章通常**不**接受提交要求修改的 Issue 或 PR。 |
| 85 | +为了避免形成惯例,这种即使从技术角度看正确的 PR 也可能会被拒绝。 |
| 86 | + |
| 87 | +<!-- |
| 88 | +However, there are exceptions like the following: |
| 89 | +
|
| 90 | +* (updates to) articles marked as [evergreen](#maintenance-evergreen) |
| 91 | +* removing or correcting articles giving advice that is now wrong and dangerous to follow |
| 92 | +* fixes to ensure that an existing article still renders correctly |
| 93 | +
|
| 94 | +For any article that is over a year old and not marked as _evergreen_, the website automatically |
| 95 | +displays a notice that the content may be stale. |
| 96 | +--> |
| 97 | +但以下情况是例外: |
| 98 | + |
| 99 | +* (更新)标记为 [Evergreen](#maintenance-evergreen) 的文章 |
| 100 | +* 移除或更正已被证明错误且可能导致危险操作的文章 |
| 101 | +* 一些修复工作,确保现有文章的渲染仍然正确 |
| 102 | + |
| 103 | +对于超过一年且未标记为 **Evergreen** 的文章,网站会自动显示一条通知,提醒读者内容可能已经过时。 |
| 104 | + |
| 105 | +<!-- |
| 106 | +### Evergreen articles {#maintenance-evergreen} |
| 107 | +
|
| 108 | +You can mark an article as evergreen by setting `evergreen: true` in the front matter. |
| 109 | +
|
| 110 | +We only mark blog articles as maintained (`evergreen: true` in front matter) if the Kubernetes project |
| 111 | +can commit to maintaining them indefinitely. Some blog articles absolutely merit this; for example, the release comms team always marks official release announcements as evergreen. |
| 112 | +--> |
| 113 | +### Evergreen 文章 {#maintenance-evergreen} |
| 114 | + |
| 115 | +你可以在文章的 front matter 中添加 `evergreen: true` 将某篇文章标记为 Evergreen(长期维护)。 |
| 116 | + |
| 117 | +只有当 Kubernetes 项目承诺长期维护某篇博文时,我们才会将其标记为长期维护 |
| 118 | +(即在 front matter 中设置 `evergreen: true`)。 |
| 119 | +有些博文确实值得长期维护,例如 Kubernetes 发布公告通常都会由 Release Comms Team(发布沟通团队)标记为 Evergreen。 |
| 120 | + |
| 121 | +## {{% heading "whatsnext" %}} |
| 122 | + |
| 123 | +<!-- |
| 124 | +* Discover the official blogs: |
| 125 | + * [Kubernetes blog](/blog/) |
| 126 | + * [Kubernetes contributor blog](https://k8s.dev/blog/) |
| 127 | +
|
| 128 | +* Read about [reviewing blog pull requests](/docs/contribute/review/reviewing-prs/#blog) |
| 129 | +--> |
| 130 | +* 了解官方博客: |
| 131 | + * [Kubernetes 主博客](/zh-cn/blog/) |
| 132 | + * [Kubernetes 贡献者博客](https://k8s.dev/blog/) |
| 133 | +* 阅读[评审博客 PR](/zh-cn/docs/contribute/review/reviewing-prs/#blog) |
0 commit comments