yangjf2019 commented on a change in pull request #268: URL: https://github.com/apache/flink-web/pull/268#discussion_r426215023
########## File path: contributing/contribute-code.zh.md ########## @@ -136,91 +136,91 @@ Apache Flink is maintained, improved, and extended by code contributions of volu <a name="consensus"></a> -### 1. Create Jira Ticket and Reach Consensus +### 1. 创建 Jira 工单并达成共识。 -The first step for making a contribution to Apache Flink is to reach consensus with the Flink community. This means agreeing on the scope and implementation approach of a change. +向 Apache Flink 做出贡献的第一步是与 Flink 社区达成共识，这意味着需要一起商定更改的范围和实现的方法。 -In most cases, the discussion should happen in [Flink's bug tracker: Jira](https://issues.apache.org/jira/projects/FLINK/summary). +在大多数情况下，我们应该在 [Flink 的 Bug 追踪器：Jira](https://issues.apache.org/jira/projects/FLINK/summary) 中进行讨论。 -The following types of changes require a `[DISCUSS]` thread on the dev@flink.a.o Flink mailing list: +以下类型的更改需要向 Flink 的 d...@flink.apache.org 邮件列表发一封以 `[DISCUSS]` 开头的邮件: - - big changes (major new feature; big refactorings, involving multiple components) - - potentially controversial changes or issues - - changes with very unclear approaches or multiple equal approaches + - 重大变化（主要新功能、大重构和涉及多个组件） + - 可能存在争议的改动或问题 + - 采用非常不明确的方法或有多种实现方法 - Do not open a Jira ticket for these types of changes before the discussion has come to a conclusion. - Jira tickets based on a dev@ discussion need to link to that discussion and should summarize the outcome. + 在讨论未达成一致之前,不要为这些类型的更改打开 Jira 工单。 Review comment: 已统一修改。 ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
