You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@inlong.apache.org by gi...@apache.org on 2021/07/29 07:07:22 UTC
[incubator-inlong-website] branch asf-site updated: Automated
deployment: Thu Jul 29 07:07:14 UTC 2021
d09dabb1de02d2d112af6618559fcd637bda8f23
This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-inlong-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 787b86a Automated deployment: Thu Jul 29 07:07:14 UTC 2021 d09dabb1de02d2d112af6618559fcd637bda8f23
787b86a is described below
commit 787b86a22ebcf13e43e89f096858d8e5d0df8c78
Author: gosonzhang <go...@users.noreply.github.com>
AuthorDate: Thu Jul 29 07:07:14 2021 +0000
Automated deployment: Thu Jul 29 07:07:14 UTC 2021 d09dabb1de02d2d112af6618559fcd637bda8f23
---
build/documentation.js | 2 +-
docs/en-us/contact.md | 2 +-
.../en-us/development/how-to-become-a-committer.md | 2 +-
docs/en-us/development/how-to-contribute.md | 14 ++++++-------
docs/en-us/development/how-to-release.md | 2 +-
.../development/how-to-vote-a-committer-ppmc.md | 2 +-
docs/zh-cn/contact.md | 2 +-
.../zh-cn/development/how-to-become-a-committer.md | 2 +-
docs/zh-cn/development/how-to-contribute.md | 24 +++++++++-------------
docs/zh-cn/development/how-to-release.md | 2 +-
.../development/how-to-vote-a-committer-ppmc.md | 2 +-
en-us/docs/contact.html | 2 +-
en-us/docs/contact.json | 2 +-
en-us/docs/contact.md | 2 +-
.../development/how-to-become-a-committer.html | 2 +-
.../development/how-to-become-a-committer.json | 2 +-
.../docs/development/how-to-become-a-committer.md | 2 +-
en-us/docs/development/how-to-contribute.html | 13 ++++++------
en-us/docs/development/how-to-contribute.json | 2 +-
en-us/docs/development/how-to-contribute.md | 14 ++++++-------
en-us/docs/development/how-to-release.html | 2 +-
en-us/docs/development/how-to-release.json | 2 +-
en-us/docs/development/how-to-release.md | 2 +-
.../development/how-to-vote-a-committer-ppmc.html | 2 +-
.../development/how-to-vote-a-committer-ppmc.json | 2 +-
.../development/how-to-vote-a-committer-ppmc.md | 2 +-
zh-cn/docs/contact.html | 2 +-
zh-cn/docs/contact.json | 2 +-
zh-cn/docs/contact.md | 2 +-
.../development/how-to-become-a-committer.html | 2 +-
.../development/how-to-become-a-committer.json | 2 +-
.../docs/development/how-to-become-a-committer.md | 2 +-
zh-cn/docs/development/how-to-contribute.html | 22 +++++++++-----------
zh-cn/docs/development/how-to-contribute.json | 2 +-
zh-cn/docs/development/how-to-contribute.md | 24 +++++++++-------------
zh-cn/docs/development/how-to-release.html | 2 +-
zh-cn/docs/development/how-to-release.json | 2 +-
zh-cn/docs/development/how-to-release.md | 2 +-
.../development/how-to-vote-a-committer-ppmc.html | 2 +-
.../development/how-to-vote-a-committer-ppmc.json | 2 +-
.../development/how-to-vote-a-committer-ppmc.md | 2 +-
41 files changed, 83 insertions(+), 98 deletions(-)
diff --git a/build/documentation.js b/build/documentation.js
index e662b28..eb4c9d7 100644
--- a/build/documentation.js
+++ b/build/documentation.js
@@ -158,4 +158,4 @@ var i="function"==typeof Symbol&&Symbol.for,a=i?Symbol.for("react.element"):6010
* Copyright © 2012-2019 Faisal Salman <f...@faisalman.com>
* Licensed under MIT License
*/
-return"string"==typeof e?e.replace(/[^\d\.]/g,"").split(".")[0]:void 0},trim:function(e){return e.replace(/^[\s\uFEFF\xA0]+|[\s\uFEFF\xA0]+$/g,"")}},m={rgx:function(e,t){for(var n,r,o,i,a,c,s=0;s<t.length&&!a;){var l=t[s],u=t[s+1];for(n=r=0;n<l.length&&!a;)if(a=l[n++].exec(e))for(o=0;o<u.length;o++)c=a[++r],i=u[o],"object"==typeof i&&i.length>0?2==i.length?"function"==typeof i[1]?this[i[0]]=i[1].call(this,c):this[i[0]]=i[1]:3==i.length?"function"!=typeof i[1]||i[1].exec&&i[1].test?this[i [...]
\ No newline at end of file
+return"string"==typeof e?e.replace(/[^\d\.]/g,"").split(".")[0]:void 0},trim:function(e){return e.replace(/^[\s\uFEFF\xA0]+|[\s\uFEFF\xA0]+$/g,"")}},m={rgx:function(e,t){for(var n,r,o,i,a,c,s=0;s<t.length&&!a;){var l=t[s],u=t[s+1];for(n=r=0;n<l.length&&!a;)if(a=l[n++].exec(e))for(o=0;o<u.length;o++)c=a[++r],i=u[o],"object"==typeof i&&i.length>0?2==i.length?"function"==typeof i[1]?this[i[0]]=i[1].call(this,c):this[i[0]]=i[1]:3==i.length?"function"!=typeof i[1]||i[1].exec&&i[1].test?this[i [...]
\ No newline at end of file
diff --git a/docs/en-us/contact.md b/docs/en-us/contact.md
index 7278e92..6e9581f 100644
--- a/docs/en-us/contact.md
+++ b/docs/en-us/contact.md
@@ -12,7 +12,7 @@ Contact us
| [dev@inlong.apache.org](mailto:dev@inlong.apache.org) | Development-related discussions | [Subscribe](mailto:dev-subscribe@inlong.apache.org) | [Unsubscribe](mailto:dev-unsubscribe@inlong.apache.org) | [Archives](http://mail-archives.apache.org/mod_mbox/inlong-dev/) |
- Home page: https://inlong.apache.org
-- Issues: https://issues.apache.org/jira/browse/InLong
+- GitHub Issues: https://github.com/apache/incubator-inlong/issues
diff --git a/docs/en-us/development/how-to-become-a-committer.md b/docs/en-us/development/how-to-become-a-committer.md
index d31d671..7577686 100644
--- a/docs/en-us/development/how-to-become-a-committer.md
+++ b/docs/en-us/development/how-to-become-a-committer.md
@@ -21,7 +21,7 @@ Apache InLong Committer拥有InLong代码库的写权限，可以合并PR，任
- 参与邮件列表中的讨论，一般会有以[DISCUSS]开头的邮件
- 回答用户或开发人员在邮件列表中的提问
- 审查(Review)其他人的工作（包括代码和非代码）并发表你自己的建议
-- 对JIRA上的issue进行审查，维护issue为最新状态，比如：关闭过时的issue、更改issue的错误信息等
+- 对GitHub上的issue进行审查，维护issue为最新状态，比如：关闭过时的issue、更改issue的错误信息等
- 指导新加入的贡献者，熟悉社区流程
- 发表关于InLong的演讲和博客，并将这些添加到InLong的官方网站
- 有利于InLong社区发展的任何贡献
diff --git a/docs/en-us/development/how-to-contribute.md b/docs/en-us/development/how-to-contribute.md
index e798bc1..f112896 100644
--- a/docs/en-us/development/how-to-contribute.md
+++ b/docs/en-us/development/how-to-contribute.md
@@ -10,7 +10,7 @@ We use a review-then-commit workflow in InLong for all contributions.
**For larger contributions or those that affect multiple components:**
-1. **Engage**: We encourage you to work with the InLong community on the [JIRA](https://jira.apache.org/jira/browse/INLONG) and [developer’s mailing list](../contact.html) to identify good areas for contribution.
+1. **Engage**: We encourage you to work with the InLong community on the [GitHub](https://github.com/apache/incubator-inlong/issues) and [developer’s mailing list](../contact.html) to identify good areas for contribution.
2. **Design:** More complicated contributions will likely benefit from some early discussion in order to scope and design them well.
**For all contributions:**
@@ -27,18 +27,16 @@ We look forward to working with you!
We discuss design and implementation issues on the [dev@inlong.apache.org](mailto:dev@inlong.apache.org) mailing list, which is archived [here](https://lists.apache.org/list.html?dev@inlong.apache.org). Join by emailing [`dev-subscribe@inlong.apache.org`](mailto:dev-subscribe@inlong.apache.org).
-### JIRA
+### GitHub Issue
-We are using [JIRA](https://jira.apache.org/jira/browse/INLONG) as the issue tracking
+We are using [GitHub](https://github.com/apache/incubator-inlong/issues) as the issue tracking
and project management tool, as well as a way to communicate among a very diverse and distributed set of contributors. To be able to gather feedback, avoid frustration, and avoid duplicated efforts all InLong related work are being tracked there.
-If you do not already have an JIRA account, sign up [here](https://jira.apache.org/jira/secure/Signup!default.jspa).
+If a quick [search](https://github.com/apache/incubator-inlong/issues) doesn’t turn up an existing GitHub issue for the work you want to contribute, create it. Please discuss your idea with a committer in GitHub or, alternatively, on the developer mailing list.
-If a quick [search](https://jira.apache.org/jira/projects/INLONG/issues) doesn’t turn up an existing JIRA issue for the work you want to contribute, create it. Please discuss your idea with a committer in JIRA or, alternatively, on the developer mailing list.
+If there’s an existing GitHub issue for your intended contribution, please comment about your intended work. Once the work is understood, a committer will assign the issue to you. If an issue is currently assigned, please check with the current assignee before reassigning.
-If there’s an existing JIRA issue for your intended contribution, please comment about your intended work. Once the work is understood, a committer will assign the issue to you. If an issue is currently assigned, please check with the current assignee before reassigning.
-
-For moderate or large contributions, you should not start coding or writing a design document unless there is a corresponding JIRA issue assigned to you for that work. Any change requires an associated JIRA issue.
+For moderate or large contributions, you should not start coding or writing a design document unless there is a corresponding GitHub issue assigned to you for that work. Any change requires an associated GitHub issue.
## Design
diff --git a/docs/en-us/development/how-to-release.md b/docs/en-us/development/how-to-release.md
index 56fde49..64e5227 100644
--- a/docs/en-us/development/how-to-release.md
+++ b/docs/en-us/development/how-to-release.md
@@ -511,7 +511,7 @@ Release Notes: https://inlong.apache.org/en-us/docs/download/${release_version}.
Website: https://inlong.apache.org/
InLong Resources:
-- Issue: https://issues.apache.org/jira/projects/INLONG/issues
+- Issue: https://github.com/apache/incubator-inlong/issues
- Mailing list: dev@inlong.apache.org
Thanks
diff --git a/docs/en-us/development/how-to-vote-a-committer-ppmc.md b/docs/en-us/development/how-to-vote-a-committer-ppmc.md
index 4047269..ea5bb07 100644
--- a/docs/en-us/development/how-to-vote-a-committer-ppmc.md
+++ b/docs/en-us/development/how-to-vote-a-committer-ppmc.md
@@ -38,7 +38,7 @@ title: How to vote a Committer or PPMC - Apache InLong
7. 如果以上内容都以完成，投票发起者还需要做如下2件事情：
- 7.1 向项目负责人申请添加项目组成员，开通jira及apache项目的权限帐号。
+ 7.1 向项目负责人申请添加项目组成员，开通apache项目的权限帐号。
7.2 向dev@inlong.apache.org邮件组发通知邮件：
> [ANNOUNCE] New XXXXXX: YYYYY
diff --git a/docs/zh-cn/contact.md b/docs/zh-cn/contact.md
index 5c32170..228bc1c 100644
--- a/docs/zh-cn/contact.md
+++ b/docs/zh-cn/contact.md
@@ -13,7 +13,7 @@ title: 联系我们 - Apache InLong
| [dev@inlong.apache.org](mailto:dev@inlong.apache.org) | Development-related discussions | [Subscribe](mailto:dev-subscribe@inlong.apache.org) | [Unsubscribe](mailto:dev-unsubscribe@inlong.apache.org) | [Archives](http://mail-archives.apache.org/mod_mbox/inlong-dev/) |
- 项目主页: https://inlong.apache.org
-- 需求与问题: https://issues.apache.org/jira/browse/InLong
+- 需求与问题: https://github.com/apache/incubator-inlong/issues
diff --git a/docs/zh-cn/development/how-to-become-a-committer.md b/docs/zh-cn/development/how-to-become-a-committer.md
index ba7b9e9..f27f3d1 100644
--- a/docs/zh-cn/development/how-to-become-a-committer.md
+++ b/docs/zh-cn/development/how-to-become-a-committer.md
@@ -19,7 +19,7 @@ Apache InLong Committer拥有InLong代码库的写权限，可以合并PR，任
- 参与邮件列表中的讨论，一般会有以[DISCUSS]开头的邮件
- 回答用户或开发人员在邮件列表中的提问
- 审查(Review)其他人的工作（包括代码和非代码）并发表你自己的建议
-- 对JIRA上的issue进行审查，维护issue为最新状态，比如：关闭过时的issue、更改issue的错误信息等
+- 对GitHub上的issue进行审查，维护issue为最新状态，比如：关闭过时的issue、更改issue的错误信息等
- 指导新加入的贡献者，熟悉社区流程
- 发表关于InLong的演讲和博客，并将这些添加到InLong的官方网站
- 有利于InLong社区发展的任何贡献
diff --git a/docs/zh-cn/development/how-to-contribute.md b/docs/zh-cn/development/how-to-contribute.md
index 819f55a..197b63f 100644
--- a/docs/zh-cn/development/how-to-contribute.md
+++ b/docs/zh-cn/development/how-to-contribute.md
@@ -6,10 +6,10 @@ title: 如何参与贡献 - Apache InLong
Apache InLong社区欢迎大家为Apache InLong做贡献，您可以通过很多方式为InLong项目成长贡献一份力量：
- 贡献文档：浏览文档可以加深您对InLong的了解，一旦发现文档写得不清晰或逻辑混乱的地方，可以订正、修改、补充或[联系我们](mailto:dev@inlong.apache.org)
- 贡献代码：欢迎大家为InLong社区贡献代码
- - 欢迎您认领Open状态的[Issues](https://issues.apache.org/jira/projects/INLONG/issues)和未完成的特性，提交PR，成为贡献者之一
+ - 欢迎您认领Open状态的[Issues](https://github.com/apache/incubator-inlong/issues)和未完成的特性，提交PR，成为贡献者之一
- 如果您在使用过程中发现有些功能无法满足您的需求或出现问题，请在Issues中记录
- 参与邮件讨论：您可以参与dev邮件列表的任何讨论，或者发送任何疑问到dev邮件列表
- - 参与Issue讨论：您可以在任一[Issues](https://issues.apache.org/jira/projects/INLONG/issues)下发表您的建议
+ - 参与Issue讨论：您可以在任一[Issues](https://github.com/apache/incubator-inlong/issues)下发表您的建议
- Review代码：您可以在[GitHub](https://github.com/apache/incubator-inlong/pulls)上看到所有贡献者提交的PR，您可以Review他们的代码并发表您的建议
> 欢迎大家提交Bug反馈、改进、新功能及PR，具体参与贡献流程可参考该指引。
@@ -17,22 +17,18 @@ Apache InLong社区欢迎大家为Apache InLong做贡献，您可以通过很多
- 官网：https://inlong.apache.org/
- 代码库：https://github.com/apache/incubator-inlong
- 官网代码库：https://github.com/apache/incubator-inlong-website
-- JRIA任务管理：https://issues.apache.org/jira/projects/INLONG/issues
+- GitHub Issue任务管理：https://github.com/apache/incubator-inlong/issues
## 2. 订阅InLong邮件列表
详见[如何订阅邮件列表](how-to-subscribe.md)
-## 3. 注册Jira账号
+## 3. 提交Bug反馈/特性/改进/文档
-Apache InLong使用Apache官方提供的任务管理平台对InLong相关的任务进行管理，JIRA的使用详见[JIRA使用指南](how-to-use-jira.md)
+> Apache InLong使用GitHub对InLong相关的任务进行管理，详见：https://github.com/apache/incubator-inlong/issues
-## 4. 提交Bug反馈/特性/改进/文档
-
-> Apache InLong使用Apache官方提供的任务管理平台对InLong相关的任务进行管理，详见：https://issues.apache.org/jira/projects/INLONG/issues
-
-### 4.1 创建issue
-详见[JIRA使用指南](how-to-use-jira.md)
-### 4.2 如何提交Bug/特性/改进
+### 3.1 创建issue
+详见[GitHub Issue使用指南](https://github.com/apache/incubator-inlong/issues/new/choose)
+### 3.2 如何提交Bug/特性/改进
在您提交特性/改进前，应该注意以下几点：
- 请先确认该特性/改进是否被其他人已经提交
- 一个通俗易懂的标题来阐述你提交的Bug/提交特性/改进
@@ -46,7 +42,7 @@ Apache InLong使用Apache官方提供的任务管理平台对InLong相关的任
- 如果是比较大的特性/改进，尽量先输出设计文档，供其他人review
- 编码，编码完成后，提交代码，参考：[代码提交指南](how-to-commit.md)
-### 4.3 如何贡献文档
+### 3.3 如何贡献文档
InLong项目的所有文档将在[官网](https://inlong.apache.org/)展示，所有的文档都保存在官网代码库的[docs](https://github.com/apache/incubator-inlong-website/tree/master/docs)文件夹下。
贡献的文档包括：
- 编写与InLong相关的文档
@@ -58,7 +54,7 @@ InLong项目的所有文档将在[官网](https://inlong.apache.org/)展示，
- 创建issue，描述清楚问题, Component请选择：website
- 撰写文档，完成后提交文档，参考：[代码提交指南](how-to-commit.md)
-### 5. 如何认领Bug/特性/改进/文档
+### 4. 如何认领Bug/特性/改进/文档
在InLong的issue列表中，有很多由其他人创建的issue并未被修复，如果你感兴趣的话，可以认领这些issue。认领步骤如下：
- 在该issue下留言，表达想认领该任务的想法
diff --git a/docs/zh-cn/development/how-to-release.md b/docs/zh-cn/development/how-to-release.md
index 9e7720c..669e35d 100644
--- a/docs/zh-cn/development/how-to-release.md
+++ b/docs/zh-cn/development/how-to-release.md
@@ -509,7 +509,7 @@ Release Notes: https://inlong.apache.org/en-us/docs/download/${release_version}.
Website: https://inlong.apache.org/
InLong Resources:
-- Issue: https://issues.apache.org/jira/projects/INLONG/issues
+- Issue: https://github.com/apache/incubator-inlong/issues
- Mailing list: dev@inlong.apache.org
Thanks
diff --git a/docs/zh-cn/development/how-to-vote-a-committer-ppmc.md b/docs/zh-cn/development/how-to-vote-a-committer-ppmc.md
index 6c10efe..1a70f54 100644
--- a/docs/zh-cn/development/how-to-vote-a-committer-ppmc.md
+++ b/docs/zh-cn/development/how-to-vote-a-committer-ppmc.md
@@ -37,7 +37,7 @@ title: 成为InLong Committer 或 PPMC 的投票过程 - Apache InLong
7. 如果以上内容都以完成，投票发起者还需要做如下2件事情：
- 7.1 向项目负责人申请添加项目组成员，开通jira及apache项目的权限帐号。
+ 7.1 向项目负责人申请添加项目组成员，开通apache项目的权限帐号。
7.2 向dev@inlong.apache.org邮件组发通知邮件：
> [ANNOUNCE] New XXXXXX: YYYYY
diff --git a/en-us/docs/contact.html b/en-us/docs/contact.html
index 0309c62..6f15fba 100644
--- a/en-us/docs/contact.html
+++ b/en-us/docs/contact.html
@@ -44,7 +44,7 @@
<p>Home page: <a href="https://inlong.apache.org">https://inlong.apache.org</a></p>
</li>
<li>
-<p>Issues: <a href="https://issues.apache.org/jira/browse/InLong">https://issues.apache.org/jira/browse/InLong</a></p>
+<p>GitHub Issues: <a href="https://github.com/apache/incubator-inlong/issues">https://github.com/apache/incubator-inlong/issues</a></p>
</li>
</ul>
<h2>License</h2>
diff --git a/en-us/docs/contact.json b/en-us/docs/contact.json
index 0670108..1c7ec29 100644
--- a/en-us/docs/contact.json
+++ b/en-us/docs/contact.json
@@ -1,6 +1,6 @@
{
"filename": "contact.md",
- "__html": "<h2>Contact us</h2>\n<ul>\n<li>\n<p>Ask questions on: <a href=\"https://the-asf.slack.com/archives/C01QAG6U00L\">Apache InLong Slack</a></p>\n</li>\n<li>\n<p>Mailing lists:</p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:left\">Name</th>\n<th style=\"text-align:left\">Scope</th>\n<th style=\"text-align:left\"></th>\n<th style=\"text-align:left\"></th>\n<th style=\"text-align:left\"></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td style=\"text-align:left\"><a href=\"mailto:dev@ [...]
+ "__html": "<h2>Contact us</h2>\n<ul>\n<li>\n<p>Ask questions on: <a href=\"https://the-asf.slack.com/archives/C01QAG6U00L\">Apache InLong Slack</a></p>\n</li>\n<li>\n<p>Mailing lists:</p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:left\">Name</th>\n<th style=\"text-align:left\">Scope</th>\n<th style=\"text-align:left\"></th>\n<th style=\"text-align:left\"></th>\n<th style=\"text-align:left\"></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td style=\"text-align:left\"><a href=\"mailto:dev@ [...]
"link": "/en-us/docs/contact.html",
"meta": {
"title": "Contact Us - Apache InLong"
diff --git a/en-us/docs/contact.md b/en-us/docs/contact.md
index 7278e92..6e9581f 100644
--- a/en-us/docs/contact.md
+++ b/en-us/docs/contact.md
@@ -12,7 +12,7 @@ Contact us
| [dev@inlong.apache.org](mailto:dev@inlong.apache.org) | Development-related discussions | [Subscribe](mailto:dev-subscribe@inlong.apache.org) | [Unsubscribe](mailto:dev-unsubscribe@inlong.apache.org) | [Archives](http://mail-archives.apache.org/mod_mbox/inlong-dev/) |
- Home page: https://inlong.apache.org
-- Issues: https://issues.apache.org/jira/browse/InLong
+- GitHub Issues: https://github.com/apache/incubator-inlong/issues
diff --git a/en-us/docs/development/how-to-become-a-committer.html b/en-us/docs/development/how-to-become-a-committer.html
index f584c99..5ce4666 100644
--- a/en-us/docs/development/how-to-become-a-committer.html
+++ b/en-us/docs/development/how-to-become-a-committer.html
@@ -30,7 +30,7 @@ Apache InLong Committer拥有InLong代码库的写权限，可以合并PR，任
<li>参与邮件列表中的讨论，一般会有以[DISCUSS]开头的邮件</li>
<li>回答用户或开发人员在邮件列表中的提问</li>
<li>审查(Review)其他人的工作（包括代码和非代码）并发表你自己的建议</li>
-<li>对JIRA上的issue进行审查，维护issue为最新状态，比如：关闭过时的issue、更改issue的错误信息等</li>
+<li>对GitHub上的issue进行审查，维护issue为最新状态，比如：关闭过时的issue、更改issue的错误信息等</li>
<li>指导新加入的贡献者，熟悉社区流程</li>
<li>发表关于InLong的演讲和博客，并将这些添加到InLong的官方网站</li>
<li>有利于InLong社区发展的任何贡献</li>
diff --git a/en-us/docs/development/how-to-become-a-committer.json b/en-us/docs/development/how-to-become-a-committer.json
index 5138eaf..458a329 100644
--- a/en-us/docs/development/how-to-become-a-committer.json
+++ b/en-us/docs/development/how-to-become-a-committer.json
@@ -1,6 +1,6 @@
{
"filename": "how-to-become-a-committer.md",
- "__html": "<h1>如何成为Apache InLong Committer 和 PPMC</h1>\n<p><font color=\"#dd0000\" size=\"4\">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>\n<blockquote>\n<p>Apache InLong是完全按照Apache的规则来构建社区的，Apache Committer是ASF（Apache软件基金会）中用来表示提交特定项目的人的术语，\nApache InLong Committer拥有InLong代码库的写权限，可以合并PR，任何人只要为社区做出了足够的贡献并获取到足够的信任就可以成为Apache InLong Committer。</p>\n</blockquote>\n<p>任何人只要对InLong项目做了贡献，那你就是官方承认的InLong项目的Contributor了，从Contributor成长为Comm [...]
+ "__html": "<h1>如何成为Apache InLong Committer 和 PPMC</h1>\n<p><font color=\"#dd0000\" size=\"4\">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>\n<blockquote>\n<p>Apache InLong是完全按照Apache的规则来构建社区的，Apache Committer是ASF（Apache软件基金会）中用来表示提交特定项目的人的术语，\nApache InLong Committer拥有InLong代码库的写权限，可以合并PR，任何人只要为社区做出了足够的贡献并获取到足够的信任就可以成为Apache InLong Committer。</p>\n</blockquote>\n<p>任何人只要对InLong项目做了贡献，那你就是官方承认的InLong项目的Contributor了，从Contributor成长为Comm [...]
"link": "/en-us/docs/development/how-to-become-a-committer.html",
"meta": {
"title": "How to Become a Committer - Apache InLong"
diff --git a/en-us/docs/development/how-to-become-a-committer.md b/en-us/docs/development/how-to-become-a-committer.md
index d31d671..7577686 100644
--- a/en-us/docs/development/how-to-become-a-committer.md
+++ b/en-us/docs/development/how-to-become-a-committer.md
@@ -21,7 +21,7 @@ Apache InLong Committer拥有InLong代码库的写权限，可以合并PR，任
- 参与邮件列表中的讨论，一般会有以[DISCUSS]开头的邮件
- 回答用户或开发人员在邮件列表中的提问
- 审查(Review)其他人的工作（包括代码和非代码）并发表你自己的建议
-- 对JIRA上的issue进行审查，维护issue为最新状态，比如：关闭过时的issue、更改issue的错误信息等
+- 对GitHub上的issue进行审查，维护issue为最新状态，比如：关闭过时的issue、更改issue的错误信息等
- 指导新加入的贡献者，熟悉社区流程
- 发表关于InLong的演讲和博客，并将这些添加到InLong的官方网站
- 有利于InLong社区发展的任何贡献
diff --git a/en-us/docs/development/how-to-contribute.html b/en-us/docs/development/how-to-contribute.html
index ad8b9b3..16529f4 100644
--- a/en-us/docs/development/how-to-contribute.html
+++ b/en-us/docs/development/how-to-contribute.html
@@ -17,7 +17,7 @@
<p>We use a review-then-commit workflow in InLong for all contributions.</p>
<p><strong>For larger contributions or those that affect multiple components:</strong></p>
<ol>
-<li><strong>Engage</strong>: We encourage you to work with the InLong community on the <a href="https://jira.apache.org/jira/browse/INLONG">JIRA</a> and <a href="../contact.html">developer’s mailing list</a> to identify good areas for contribution.</li>
+<li><strong>Engage</strong>: We encourage you to work with the InLong community on the <a href="https://github.com/apache/incubator-inlong/issues">GitHub</a> and <a href="../contact.html">developer’s mailing list</a> to identify good areas for contribution.</li>
<li><strong>Design:</strong> More complicated contributions will likely benefit from some early discussion in order to scope and design them well.</li>
</ol>
<p><strong>For all contributions:</strong></p>
@@ -30,13 +30,12 @@
<h2>Engage</h2>
<h3>Mailing list(s)</h3>
<p>We discuss design and implementation issues on the <a href="mailto:dev@inlong.apache.org">dev@inlong.apache.org</a> mailing list, which is archived <a href="https://lists.apache.org/list.html?dev@inlong.apache.org">here</a>. Join by emailing <a href="mailto:dev-subscribe@inlong.apache.org"><code>dev-subscribe@inlong.apache.org</code></a>.</p>
-<h3>JIRA</h3>
-<p>We are using <a href="https://jira.apache.org/jira/browse/INLONG">JIRA</a> as the issue tracking
+<h3>GitHub Issue</h3>
+<p>We are using <a href="https://github.com/apache/incubator-inlong/issues">GitHub</a> as the issue tracking
and project management tool, as well as a way to communicate among a very diverse and distributed set of contributors. To be able to gather feedback, avoid frustration, and avoid duplicated efforts all InLong related work are being tracked there.</p>
-<p>If you do not already have an JIRA account, sign up <a href="https://jira.apache.org/jira/secure/Signup!default.jspa">here</a>.</p>
-<p>If a quick <a href="https://jira.apache.org/jira/projects/INLONG/issues">search</a> doesn’t turn up an existing JIRA issue for the work you want to contribute, create it. Please discuss your idea with a committer in JIRA or, alternatively, on the developer mailing list.</p>
-<p>If there’s an existing JIRA issue for your intended contribution, please comment about your intended work. Once the work is understood, a committer will assign the issue to you. If an issue is currently assigned, please check with the current assignee before reassigning.</p>
-<p>For moderate or large contributions, you should not start coding or writing a design document unless there is a corresponding JIRA issue assigned to you for that work. Any change requires an associated JIRA issue.</p>
+<p>If a quick <a href="https://github.com/apache/incubator-inlong/issues">search</a> doesn’t turn up an existing GitHub issue for the work you want to contribute, create it. Please discuss your idea with a committer in GitHub or, alternatively, on the developer mailing list.</p>
+<p>If there’s an existing GitHub issue for your intended contribution, please comment about your intended work. Once the work is understood, a committer will assign the issue to you. If an issue is currently assigned, please check with the current assignee before reassigning.</p>
+<p>For moderate or large contributions, you should not start coding or writing a design document unless there is a corresponding GitHub issue assigned to you for that work. Any change requires an associated GitHub issue.</p>
<h2>Design</h2>
<p>To avoid potential frustration during the code review cycle, we encourage you to clearly scope and design non-trivial contributions with the InLong community before you start coding.</p>
<p>We are using "InLong Improvement Proposals" for managing major changes to InLong. The list of all proposals is maintained in the InLong wiki at <a href="https://cwiki.apache.org/confluence/display/INLONG/INLONG+Improvement+Proposals">this page</a>.</p>
diff --git a/en-us/docs/development/how-to-contribute.json b/en-us/docs/development/how-to-contribute.json
index 54f5450..84477ad 100644
--- a/en-us/docs/development/how-to-contribute.json
+++ b/en-us/docs/development/how-to-contribute.json
@@ -1,6 +1,6 @@
{
"filename": "how-to-contribute.md",
- "__html": "<h1>How to Contribute</h1>\n<p>The Apache InLong(incubating) community welcomes contributions from anyone with a passion for distributed systems! InLong has many different opportunities for contributions -- write new examples/tutorials, add new user-facing libraries or participate on the documentation effort.</p>\n<p>We use a review-then-commit workflow in InLong for all contributions.</p>\n<p><strong>For larger contributions or those that affect multiple components:</strong [...]
+ "__html": "<h1>How to Contribute</h1>\n<p>The Apache InLong(incubating) community welcomes contributions from anyone with a passion for distributed systems! InLong has many different opportunities for contributions -- write new examples/tutorials, add new user-facing libraries or participate on the documentation effort.</p>\n<p>We use a review-then-commit workflow in InLong for all contributions.</p>\n<p><strong>For larger contributions or those that affect multiple components:</strong [...]
"link": "/en-us/docs/development/how-to-contribute.html",
"meta": {
"title": "How to Contribute - Apache InLong"
diff --git a/en-us/docs/development/how-to-contribute.md b/en-us/docs/development/how-to-contribute.md
index e798bc1..f112896 100644
--- a/en-us/docs/development/how-to-contribute.md
+++ b/en-us/docs/development/how-to-contribute.md
@@ -10,7 +10,7 @@ We use a review-then-commit workflow in InLong for all contributions.
**For larger contributions or those that affect multiple components:**
-1. **Engage**: We encourage you to work with the InLong community on the [JIRA](https://jira.apache.org/jira/browse/INLONG) and [developer’s mailing list](../contact.html) to identify good areas for contribution.
+1. **Engage**: We encourage you to work with the InLong community on the [GitHub](https://github.com/apache/incubator-inlong/issues) and [developer’s mailing list](../contact.html) to identify good areas for contribution.
2. **Design:** More complicated contributions will likely benefit from some early discussion in order to scope and design them well.
**For all contributions:**
@@ -27,18 +27,16 @@ We look forward to working with you!
We discuss design and implementation issues on the [dev@inlong.apache.org](mailto:dev@inlong.apache.org) mailing list, which is archived [here](https://lists.apache.org/list.html?dev@inlong.apache.org). Join by emailing [`dev-subscribe@inlong.apache.org`](mailto:dev-subscribe@inlong.apache.org).
-### JIRA
+### GitHub Issue
-We are using [JIRA](https://jira.apache.org/jira/browse/INLONG) as the issue tracking
+We are using [GitHub](https://github.com/apache/incubator-inlong/issues) as the issue tracking
and project management tool, as well as a way to communicate among a very diverse and distributed set of contributors. To be able to gather feedback, avoid frustration, and avoid duplicated efforts all InLong related work are being tracked there.
-If you do not already have an JIRA account, sign up [here](https://jira.apache.org/jira/secure/Signup!default.jspa).
+If a quick [search](https://github.com/apache/incubator-inlong/issues) doesn’t turn up an existing GitHub issue for the work you want to contribute, create it. Please discuss your idea with a committer in GitHub or, alternatively, on the developer mailing list.
-If a quick [search](https://jira.apache.org/jira/projects/INLONG/issues) doesn’t turn up an existing JIRA issue for the work you want to contribute, create it. Please discuss your idea with a committer in JIRA or, alternatively, on the developer mailing list.
+If there’s an existing GitHub issue for your intended contribution, please comment about your intended work. Once the work is understood, a committer will assign the issue to you. If an issue is currently assigned, please check with the current assignee before reassigning.
-If there’s an existing JIRA issue for your intended contribution, please comment about your intended work. Once the work is understood, a committer will assign the issue to you. If an issue is currently assigned, please check with the current assignee before reassigning.
-
-For moderate or large contributions, you should not start coding or writing a design document unless there is a corresponding JIRA issue assigned to you for that work. Any change requires an associated JIRA issue.
+For moderate or large contributions, you should not start coding or writing a design document unless there is a corresponding GitHub issue assigned to you for that work. Any change requires an associated GitHub issue.
## Design
diff --git a/en-us/docs/development/how-to-release.html b/en-us/docs/development/how-to-release.html
index 82a3503..d4a12ec 100644
--- a/en-us/docs/development/how-to-release.html
+++ b/en-us/docs/development/how-to-release.html
@@ -477,7 +477,7 @@ Release Notes: https://inlong.apache.org/en-us/docs/download/${release_version}.
Website: https://inlong.apache.org/
InLong Resources:
-- Issue: https://issues.apache.org/jira/projects/INLONG/issues
+- Issue: https://github.com/apache/incubator-inlong/issues
- Mailing list: dev@inlong.apache.org
Thanks
diff --git a/en-us/docs/development/how-to-release.json b/en-us/docs/development/how-to-release.json
index fbc1b7b..a8e4f97 100644
--- a/en-us/docs/development/how-to-release.json
+++ b/en-us/docs/development/how-to-release.json
@@ -1,6 +1,6 @@
{
"filename": "how-to-release.md",
- "__html": "<h1>如何发布版本</h1>\n<p><font color=\"#dd0000\" size=\"4\">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>\n<blockquote>\n<p>本文主要介绍了Release Manager如何按照Apache的流程发布版本，</p>\n</blockquote>\n<h2>0. 前言</h2>\n<p>Source Release是Apache关注的重点，也是发布的必须内容；\nBinary Release是可选项，InLong可以选择是否发布二进制包到Apache仓库或者发布到Maven中央仓库。</p>\n<p>请参考以下链接，找到更多关于ASF的发布指南:</p>\n<p><a href=\"https://incubator.apache.org/guides/releasemanagement.html\">Apache Release [...]
+ "__html": "<h1>如何发布版本</h1>\n<p><font color=\"#dd0000\" size=\"4\">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>\n<blockquote>\n<p>本文主要介绍了Release Manager如何按照Apache的流程发布版本，</p>\n</blockquote>\n<h2>0. 前言</h2>\n<p>Source Release是Apache关注的重点，也是发布的必须内容；\nBinary Release是可选项，InLong可以选择是否发布二进制包到Apache仓库或者发布到Maven中央仓库。</p>\n<p>请参考以下链接，找到更多关于ASF的发布指南:</p>\n<p><a href=\"https://incubator.apache.org/guides/releasemanagement.html\">Apache Release [...]
"link": "/en-us/docs/development/how-to-release.html",
"meta": {
"title": "How to Release - Apache InLong"
diff --git a/en-us/docs/development/how-to-release.md b/en-us/docs/development/how-to-release.md
index 56fde49..64e5227 100644
--- a/en-us/docs/development/how-to-release.md
+++ b/en-us/docs/development/how-to-release.md
@@ -511,7 +511,7 @@ Release Notes: https://inlong.apache.org/en-us/docs/download/${release_version}.
Website: https://inlong.apache.org/
InLong Resources:
-- Issue: https://issues.apache.org/jira/projects/INLONG/issues
+- Issue: https://github.com/apache/incubator-inlong/issues
- Mailing list: dev@inlong.apache.org
Thanks
diff --git a/en-us/docs/development/how-to-vote-a-committer-ppmc.html b/en-us/docs/development/how-to-vote-a-committer-ppmc.html
index 0a02e33..bd6c606 100644
--- a/en-us/docs/development/how-to-vote-a-committer-ppmc.html
+++ b/en-us/docs/development/how-to-vote-a-committer-ppmc.html
@@ -54,7 +54,7 @@
</li>
<li>
<p>如果以上内容都以完成，投票发起者还需要做如下2件事情：
-7.1 向项目负责人申请添加项目组成员，开通jira及apache项目的权限帐号。</p>
+7.1 向项目负责人申请添加项目组成员，开通apache项目的权限帐号。</p>
<p>7.2 向dev@inlong.apache.org邮件组发通知邮件：</p>
<blockquote>
<pre><code> [ANNOUNCE] New XXXXXX: YYYYY
diff --git a/en-us/docs/development/how-to-vote-a-committer-ppmc.json b/en-us/docs/development/how-to-vote-a-committer-ppmc.json
index 4574849..103ba38 100644
--- a/en-us/docs/development/how-to-vote-a-committer-ppmc.json
+++ b/en-us/docs/development/how-to-vote-a-committer-ppmc.json
@@ -1,6 +1,6 @@
{
"filename": "how-to-vote-a-committer-ppmc.md",
- "__html": "<h1>成为InLong Committer 或 PPMC 的投票过程</h1>\n<p><font color=\"#dd0000\" size=\"4\">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>\n<ol>\n<li>\n<p>InLong的PPMC成员发现社区贡献者任何有价值的贡献并取得候选人本人同意后，在InLong的private邮件列表发起讨论；</p>\n<blockquote>\n<p>[DISCUSS] YYYYY as a InLong XXXXXX</p>\n</blockquote>\n<p>邮件里要把对方的贡献，可以查看的出处说清楚，便于大家讨论分析；讨论邮件将持续至少72个小时，项目组成员，包括mentor们会针对提议邮件充分发表自己的看法；</p>\n</li>\n<li>\n<p>不管有没有分歧，在讨论邮件过后，投票发起者需要在在InLong的private [...]
+ "__html": "<h1>成为InLong Committer 或 PPMC 的投票过程</h1>\n<p><font color=\"#dd0000\" size=\"4\">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>\n<ol>\n<li>\n<p>InLong的PPMC成员发现社区贡献者任何有价值的贡献并取得候选人本人同意后，在InLong的private邮件列表发起讨论；</p>\n<blockquote>\n<p>[DISCUSS] YYYYY as a InLong XXXXXX</p>\n</blockquote>\n<p>邮件里要把对方的贡献，可以查看的出处说清楚，便于大家讨论分析；讨论邮件将持续至少72个小时，项目组成员，包括mentor们会针对提议邮件充分发表自己的看法；</p>\n</li>\n<li>\n<p>不管有没有分歧，在讨论邮件过后，投票发起者需要在在InLong的private [...]
"link": "/en-us/docs/development/how-to-vote-a-committer-ppmc.html",
"meta": {
"title": "How to vote a Committer or PPMC - Apache InLong"
diff --git a/en-us/docs/development/how-to-vote-a-committer-ppmc.md b/en-us/docs/development/how-to-vote-a-committer-ppmc.md
index 4047269..ea5bb07 100644
--- a/en-us/docs/development/how-to-vote-a-committer-ppmc.md
+++ b/en-us/docs/development/how-to-vote-a-committer-ppmc.md
@@ -38,7 +38,7 @@ title: How to vote a Committer or PPMC - Apache InLong
7. 如果以上内容都以完成，投票发起者还需要做如下2件事情：
- 7.1 向项目负责人申请添加项目组成员，开通jira及apache项目的权限帐号。
+ 7.1 向项目负责人申请添加项目组成员，开通apache项目的权限帐号。
7.2 向dev@inlong.apache.org邮件组发通知邮件：
> [ANNOUNCE] New XXXXXX: YYYYY
diff --git a/zh-cn/docs/contact.html b/zh-cn/docs/contact.html
index ef05c35..eaca09b 100644
--- a/zh-cn/docs/contact.html
+++ b/zh-cn/docs/contact.html
@@ -44,7 +44,7 @@
<p>项目主页: <a href="https://inlong.apache.org">https://inlong.apache.org</a></p>
</li>
<li>
-<p>需求与问题: <a href="https://issues.apache.org/jira/browse/InLong">https://issues.apache.org/jira/browse/InLong</a></p>
+<p>需求与问题: <a href="https://github.com/apache/incubator-inlong/issues">https://github.com/apache/incubator-inlong/issues</a></p>
</li>
</ul>
<h2>版权</h2>
diff --git a/zh-cn/docs/contact.json b/zh-cn/docs/contact.json
index 565503f..a4f9b8d 100644
--- a/zh-cn/docs/contact.json
+++ b/zh-cn/docs/contact.json
@@ -1,6 +1,6 @@
{
"filename": "contact.md",
- "__html": "<h2>联系我们</h2>\n<ul>\n<li>\n<p>Slack在线交流: <a href=\"https://the-asf.slack.com/archives/C01QAG6U00L\">Apache InLong Slack</a></p>\n</li>\n<li>\n<p>邮件列表:</p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:left\">Name</th>\n<th style=\"text-align:left\">Scope</th>\n<th style=\"text-align:left\"></th>\n<th style=\"text-align:left\"></th>\n<th style=\"text-align:left\"></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td style=\"text-align:left\"><a href=\"mailto:dev@inlong.apache.org\">de [...]
+ "__html": "<h2>联系我们</h2>\n<ul>\n<li>\n<p>Slack在线交流: <a href=\"https://the-asf.slack.com/archives/C01QAG6U00L\">Apache InLong Slack</a></p>\n</li>\n<li>\n<p>邮件列表:</p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:left\">Name</th>\n<th style=\"text-align:left\">Scope</th>\n<th style=\"text-align:left\"></th>\n<th style=\"text-align:left\"></th>\n<th style=\"text-align:left\"></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td style=\"text-align:left\"><a href=\"mailto:dev@inlong.apache.org\">de [...]
"link": "/zh-cn/docs/contact.html",
"meta": {
"title": "联系我们 - Apache InLong"
diff --git a/zh-cn/docs/contact.md b/zh-cn/docs/contact.md
index 5c32170..228bc1c 100644
--- a/zh-cn/docs/contact.md
+++ b/zh-cn/docs/contact.md
@@ -13,7 +13,7 @@ title: 联系我们 - Apache InLong
| [dev@inlong.apache.org](mailto:dev@inlong.apache.org) | Development-related discussions | [Subscribe](mailto:dev-subscribe@inlong.apache.org) | [Unsubscribe](mailto:dev-unsubscribe@inlong.apache.org) | [Archives](http://mail-archives.apache.org/mod_mbox/inlong-dev/) |
- 项目主页: https://inlong.apache.org
-- 需求与问题: https://issues.apache.org/jira/browse/InLong
+- 需求与问题: https://github.com/apache/incubator-inlong/issues
diff --git a/zh-cn/docs/development/how-to-become-a-committer.html b/zh-cn/docs/development/how-to-become-a-committer.html
index 28b8ead..f40652e 100644
--- a/zh-cn/docs/development/how-to-become-a-committer.html
+++ b/zh-cn/docs/development/how-to-become-a-committer.html
@@ -29,7 +29,7 @@ Apache InLong Committer拥有InLong代码库的写权限，可以合并PR，任
<li>参与邮件列表中的讨论，一般会有以[DISCUSS]开头的邮件</li>
<li>回答用户或开发人员在邮件列表中的提问</li>
<li>审查(Review)其他人的工作（包括代码和非代码）并发表你自己的建议</li>
-<li>对JIRA上的issue进行审查，维护issue为最新状态，比如：关闭过时的issue、更改issue的错误信息等</li>
+<li>对GitHub上的issue进行审查，维护issue为最新状态，比如：关闭过时的issue、更改issue的错误信息等</li>
<li>指导新加入的贡献者，熟悉社区流程</li>
<li>发表关于InLong的演讲和博客，并将这些添加到InLong的官方网站</li>
<li>有利于InLong社区发展的任何贡献</li>
diff --git a/zh-cn/docs/development/how-to-become-a-committer.json b/zh-cn/docs/development/how-to-become-a-committer.json
index 0c52f31..eb81b89 100644
--- a/zh-cn/docs/development/how-to-become-a-committer.json
+++ b/zh-cn/docs/development/how-to-become-a-committer.json
@@ -1,6 +1,6 @@
{
"filename": "how-to-become-a-committer.md",
- "__html": "<h1>如何成为InLong Committer 和 PPMC</h1>\n<blockquote>\n<p>Apache InLong是完全按照Apache的规则来构建社区的，Apache Committer是ASF（Apache软件基金会）中用来表示提交特定项目的人的术语，\nApache InLong Committer拥有InLong代码库的写权限，可以合并PR，任何人只要为社区做出了足够的贡献并获取到足够的信任就可以成为Apache InLong Committer。</p>\n</blockquote>\n<p>任何人只要对InLong项目做了贡献，那你就是官方承认的InLong项目的Contributor了，从Contributor成长为Committer并没有一个确切的标准，\n也没有任何预期的时间表，但是Committer的候选人一般都是长期活跃的贡献者，成为Committer并没有要求必须有巨大的架构改进贡献，\n或者多少行的代码贡献，贡献代码、贡献文档、参与邮件列表的讨论、帮助回答问题等等都提升自己影响力的方式。</p>\ [...]
+ "__html": "<h1>如何成为InLong Committer 和 PPMC</h1>\n<blockquote>\n<p>Apache InLong是完全按照Apache的规则来构建社区的，Apache Committer是ASF（Apache软件基金会）中用来表示提交特定项目的人的术语，\nApache InLong Committer拥有InLong代码库的写权限，可以合并PR，任何人只要为社区做出了足够的贡献并获取到足够的信任就可以成为Apache InLong Committer。</p>\n</blockquote>\n<p>任何人只要对InLong项目做了贡献，那你就是官方承认的InLong项目的Contributor了，从Contributor成长为Committer并没有一个确切的标准，\n也没有任何预期的时间表，但是Committer的候选人一般都是长期活跃的贡献者，成为Committer并没有要求必须有巨大的架构改进贡献，\n或者多少行的代码贡献，贡献代码、贡献文档、参与邮件列表的讨论、帮助回答问题等等都提升自己影响力的方式。</p>\ [...]
"link": "/zh-cn/docs/development/how-to-become-a-committer.html",
"meta": {
"title": "如何成为Committer - Apache InLong"
diff --git a/zh-cn/docs/development/how-to-become-a-committer.md b/zh-cn/docs/development/how-to-become-a-committer.md
index ba7b9e9..f27f3d1 100644
--- a/zh-cn/docs/development/how-to-become-a-committer.md
+++ b/zh-cn/docs/development/how-to-become-a-committer.md
@@ -19,7 +19,7 @@ Apache InLong Committer拥有InLong代码库的写权限，可以合并PR，任
- 参与邮件列表中的讨论，一般会有以[DISCUSS]开头的邮件
- 回答用户或开发人员在邮件列表中的提问
- 审查(Review)其他人的工作（包括代码和非代码）并发表你自己的建议
-- 对JIRA上的issue进行审查，维护issue为最新状态，比如：关闭过时的issue、更改issue的错误信息等
+- 对GitHub上的issue进行审查，维护issue为最新状态，比如：关闭过时的issue、更改issue的错误信息等
- 指导新加入的贡献者，熟悉社区流程
- 发表关于InLong的演讲和博客，并将这些添加到InLong的官方网站
- 有利于InLong社区发展的任何贡献
diff --git a/zh-cn/docs/development/how-to-contribute.html b/zh-cn/docs/development/how-to-contribute.html
index a965298..27845ae 100644
--- a/zh-cn/docs/development/how-to-contribute.html
+++ b/zh-cn/docs/development/how-to-contribute.html
@@ -18,12 +18,12 @@
<li>贡献文档：浏览文档可以加深您对InLong的了解，一旦发现文档写得不清晰或逻辑混乱的地方，可以订正、修改、补充或<a href="mailto:dev@inlong.apache.org">联系我们</a></li>
<li>贡献代码：欢迎大家为InLong社区贡献代码
<ul>
-<li>欢迎您认领Open状态的<a href="https://issues.apache.org/jira/projects/INLONG/issues">Issues</a>和未完成的特性，提交PR，成为贡献者之一</li>
+<li>欢迎您认领Open状态的<a href="https://github.com/apache/incubator-inlong/issues">Issues</a>和未完成的特性，提交PR，成为贡献者之一</li>
<li>如果您在使用过程中发现有些功能无法满足您的需求或出现问题，请在Issues中记录</li>
</ul>
</li>
<li>参与邮件讨论：您可以参与dev邮件列表的任何讨论，或者发送任何疑问到dev邮件列表</li>
-<li>参与Issue讨论：您可以在任一<a href="https://issues.apache.org/jira/projects/INLONG/issues">Issues</a>下发表您的建议</li>
+<li>参与Issue讨论：您可以在任一<a href="https://github.com/apache/incubator-inlong/issues">Issues</a>下发表您的建议</li>
<li>Review代码：您可以在<a href="https://github.com/apache/incubator-inlong/pulls">GitHub</a>上看到所有贡献者提交的PR，您可以Review他们的代码并发表您的建议</li>
</ul>
<blockquote>
@@ -34,19 +34,17 @@
<li>官网：<a href="https://inlong.apache.org/">https://inlong.apache.org/</a></li>
<li>代码库：<a href="https://github.com/apache/incubator-inlong">https://github.com/apache/incubator-inlong</a></li>
<li>官网代码库：<a href="https://github.com/apache/incubator-inlong-website">https://github.com/apache/incubator-inlong-website</a></li>
-<li>JRIA任务管理：<a href="https://issues.apache.org/jira/projects/INLONG/issues">https://issues.apache.org/jira/projects/INLONG/issues</a></li>
+<li>GitHub Issue任务管理：<a href="https://github.com/apache/incubator-inlong/issues">https://github.com/apache/incubator-inlong/issues</a></li>
</ul>
<h2>2. 订阅InLong邮件列表</h2>
<p>详见<a href="how-to-subscribe.md">如何订阅邮件列表</a></p>
-<h2>3. 注册Jira账号</h2>
-<p>Apache InLong使用Apache官方提供的任务管理平台对InLong相关的任务进行管理，JIRA的使用详见<a href="how-to-use-jira.md">JIRA使用指南</a></p>
-<h2>4. 提交Bug反馈/特性/改进/文档</h2>
+<h2>3. 提交Bug反馈/特性/改进/文档</h2>
<blockquote>
-<p>Apache InLong使用Apache官方提供的任务管理平台对InLong相关的任务进行管理，详见：<a href="https://issues.apache.org/jira/projects/INLONG/issues">https://issues.apache.org/jira/projects/INLONG/issues</a></p>
+<p>Apache InLong使用GitHub对InLong相关的任务进行管理，详见：<a href="https://github.com/apache/incubator-inlong/issues">https://github.com/apache/incubator-inlong/issues</a></p>
</blockquote>
-<h3>4.1 创建issue</h3>
-<p>详见<a href="how-to-use-jira.md">JIRA使用指南</a></p>
-<h3>4.2 如何提交Bug/特性/改进</h3>
+<h3>3.1 创建issue</h3>
+<p>详见<a href="https://github.com/apache/incubator-inlong/issues/new/choose">GitHub Issue使用指南</a></p>
+<h3>3.2 如何提交Bug/特性/改进</h3>
<p>在您提交特性/改进前，应该注意以下几点：</p>
<ul>
<li>请先确认该特性/改进是否被其他人已经提交</li>
@@ -62,7 +60,7 @@
<li>如果是比较大的特性/改进，尽量先输出设计文档，供其他人review</li>
<li>编码，编码完成后，提交代码，参考：<a href="how-to-commit.md">代码提交指南</a></li>
</ul>
-<h3>4.3 如何贡献文档</h3>
+<h3>3.3 如何贡献文档</h3>
<p>InLong项目的所有文档将在<a href="https://inlong.apache.org/">官网</a>展示，所有的文档都保存在官网代码库的<a href="https://github.com/apache/incubator-inlong-website/tree/master/docs">docs</a>文件夹下。
贡献的文档包括：</p>
<ul>
@@ -76,7 +74,7 @@
<li>创建issue，描述清楚问题, Component请选择：website</li>
<li>撰写文档，完成后提交文档，参考：<a href="how-to-commit.md">代码提交指南</a></li>
</ul>
-<h3>5. 如何认领Bug/特性/改进/文档</h3>
+<h3>4. 如何认领Bug/特性/改进/文档</h3>
<p>在InLong的issue列表中，有很多由其他人创建的issue并未被修复，如果你感兴趣的话，可以认领这些issue。认领步骤如下：</p>
<ul>
<li>在该issue下留言，表达想认领该任务的想法</li>
diff --git a/zh-cn/docs/development/how-to-contribute.json b/zh-cn/docs/development/how-to-contribute.json
index f586057..10ecdc1 100644
--- a/zh-cn/docs/development/how-to-contribute.json
+++ b/zh-cn/docs/development/how-to-contribute.json
@@ -1,6 +1,6 @@
{
"filename": "how-to-contribute.md",
- "__html": "<h1>如何参与贡献</h1>\n<p>Apache InLong社区欢迎大家为Apache InLong做贡献，您可以通过很多方式为InLong项目成长贡献一份力量：</p>\n<ul>\n<li>贡献文档：浏览文档可以加深您对InLong的了解，一旦发现文档写得不清晰或逻辑混乱的地方，可以订正、修改、补充或<a href=\"mailto:dev@inlong.apache.org\">联系我们</a></li>\n<li>贡献代码：欢迎大家为InLong社区贡献代码\n<ul>\n<li>欢迎您认领Open状态的<a href=\"https://issues.apache.org/jira/projects/INLONG/issues\">Issues</a>和未完成的特性，提交PR，成为贡献者之一</li>\n<li>如果您在使用过程中发现有些功能无法满足您的需求或出现问题，请在Issues中记录</li>\n</ul>\n</li>\n<li>参与邮件讨论：您可以参与dev邮件列表的任何讨论，或者发送任何疑问到dev邮件列表</li [...]
+ "__html": "<h1>如何参与贡献</h1>\n<p>Apache InLong社区欢迎大家为Apache InLong做贡献，您可以通过很多方式为InLong项目成长贡献一份力量：</p>\n<ul>\n<li>贡献文档：浏览文档可以加深您对InLong的了解，一旦发现文档写得不清晰或逻辑混乱的地方，可以订正、修改、补充或<a href=\"mailto:dev@inlong.apache.org\">联系我们</a></li>\n<li>贡献代码：欢迎大家为InLong社区贡献代码\n<ul>\n<li>欢迎您认领Open状态的<a href=\"https://github.com/apache/incubator-inlong/issues\">Issues</a>和未完成的特性，提交PR，成为贡献者之一</li>\n<li>如果您在使用过程中发现有些功能无法满足您的需求或出现问题，请在Issues中记录</li>\n</ul>\n</li>\n<li>参与邮件讨论：您可以参与dev邮件列表的任何讨论，或者发送任何疑问到dev邮件列表</li>\n< [...]
"link": "/zh-cn/docs/development/how-to-contribute.html",
"meta": {
"title": "如何参与贡献 - Apache InLong"
diff --git a/zh-cn/docs/development/how-to-contribute.md b/zh-cn/docs/development/how-to-contribute.md
index 819f55a..197b63f 100644
--- a/zh-cn/docs/development/how-to-contribute.md
+++ b/zh-cn/docs/development/how-to-contribute.md
@@ -6,10 +6,10 @@ title: 如何参与贡献 - Apache InLong
Apache InLong社区欢迎大家为Apache InLong做贡献，您可以通过很多方式为InLong项目成长贡献一份力量：
- 贡献文档：浏览文档可以加深您对InLong的了解，一旦发现文档写得不清晰或逻辑混乱的地方，可以订正、修改、补充或[联系我们](mailto:dev@inlong.apache.org)
- 贡献代码：欢迎大家为InLong社区贡献代码
- - 欢迎您认领Open状态的[Issues](https://issues.apache.org/jira/projects/INLONG/issues)和未完成的特性，提交PR，成为贡献者之一
+ - 欢迎您认领Open状态的[Issues](https://github.com/apache/incubator-inlong/issues)和未完成的特性，提交PR，成为贡献者之一
- 如果您在使用过程中发现有些功能无法满足您的需求或出现问题，请在Issues中记录
- 参与邮件讨论：您可以参与dev邮件列表的任何讨论，或者发送任何疑问到dev邮件列表
- - 参与Issue讨论：您可以在任一[Issues](https://issues.apache.org/jira/projects/INLONG/issues)下发表您的建议
+ - 参与Issue讨论：您可以在任一[Issues](https://github.com/apache/incubator-inlong/issues)下发表您的建议
- Review代码：您可以在[GitHub](https://github.com/apache/incubator-inlong/pulls)上看到所有贡献者提交的PR，您可以Review他们的代码并发表您的建议
> 欢迎大家提交Bug反馈、改进、新功能及PR，具体参与贡献流程可参考该指引。
@@ -17,22 +17,18 @@ Apache InLong社区欢迎大家为Apache InLong做贡献，您可以通过很多
- 官网：https://inlong.apache.org/
- 代码库：https://github.com/apache/incubator-inlong
- 官网代码库：https://github.com/apache/incubator-inlong-website
-- JRIA任务管理：https://issues.apache.org/jira/projects/INLONG/issues
+- GitHub Issue任务管理：https://github.com/apache/incubator-inlong/issues
## 2. 订阅InLong邮件列表
详见[如何订阅邮件列表](how-to-subscribe.md)
-## 3. 注册Jira账号
+## 3. 提交Bug反馈/特性/改进/文档
-Apache InLong使用Apache官方提供的任务管理平台对InLong相关的任务进行管理，JIRA的使用详见[JIRA使用指南](how-to-use-jira.md)
+> Apache InLong使用GitHub对InLong相关的任务进行管理，详见：https://github.com/apache/incubator-inlong/issues
-## 4. 提交Bug反馈/特性/改进/文档
-
-> Apache InLong使用Apache官方提供的任务管理平台对InLong相关的任务进行管理，详见：https://issues.apache.org/jira/projects/INLONG/issues
-
-### 4.1 创建issue
-详见[JIRA使用指南](how-to-use-jira.md)
-### 4.2 如何提交Bug/特性/改进
+### 3.1 创建issue
+详见[GitHub Issue使用指南](https://github.com/apache/incubator-inlong/issues/new/choose)
+### 3.2 如何提交Bug/特性/改进
在您提交特性/改进前，应该注意以下几点：
- 请先确认该特性/改进是否被其他人已经提交
- 一个通俗易懂的标题来阐述你提交的Bug/提交特性/改进
@@ -46,7 +42,7 @@ Apache InLong使用Apache官方提供的任务管理平台对InLong相关的任
- 如果是比较大的特性/改进，尽量先输出设计文档，供其他人review
- 编码，编码完成后，提交代码，参考：[代码提交指南](how-to-commit.md)
-### 4.3 如何贡献文档
+### 3.3 如何贡献文档
InLong项目的所有文档将在[官网](https://inlong.apache.org/)展示，所有的文档都保存在官网代码库的[docs](https://github.com/apache/incubator-inlong-website/tree/master/docs)文件夹下。
贡献的文档包括：
- 编写与InLong相关的文档
@@ -58,7 +54,7 @@ InLong项目的所有文档将在[官网](https://inlong.apache.org/)展示，
- 创建issue，描述清楚问题, Component请选择：website
- 撰写文档，完成后提交文档，参考：[代码提交指南](how-to-commit.md)
-### 5. 如何认领Bug/特性/改进/文档
+### 4. 如何认领Bug/特性/改进/文档
在InLong的issue列表中，有很多由其他人创建的issue并未被修复，如果你感兴趣的话，可以认领这些issue。认领步骤如下：
- 在该issue下留言，表达想认领该任务的想法
diff --git a/zh-cn/docs/development/how-to-release.html b/zh-cn/docs/development/how-to-release.html
index de40f48..aa9ae59 100644
--- a/zh-cn/docs/development/how-to-release.html
+++ b/zh-cn/docs/development/how-to-release.html
@@ -475,7 +475,7 @@ Release Notes: https://inlong.apache.org/en-us/docs/download/${release_version}.
Website: https://inlong.apache.org/
InLong Resources:
-- Issue: https://issues.apache.org/jira/projects/INLONG/issues
+- Issue: https://github.com/apache/incubator-inlong/issues
- Mailing list: dev@inlong.apache.org
Thanks
diff --git a/zh-cn/docs/development/how-to-release.json b/zh-cn/docs/development/how-to-release.json
index 5ca0167..0446cb9 100644
--- a/zh-cn/docs/development/how-to-release.json
+++ b/zh-cn/docs/development/how-to-release.json
@@ -1,6 +1,6 @@
{
"filename": "how-to-release.md",
- "__html": "<h1>如何发布版本</h1>\n<blockquote>\n<p>本文主要介绍了Release Manager如何按照Apache的流程发布版本，</p>\n</blockquote>\n<p>Source Release是Apache关注的重点，也是发布的必须内容；\nBinary Release是可选项，InLong可以选择是否发布二进制包到Apache仓库或者发布到Maven中央仓库。</p>\n<p>请参考以下链接，找到更多关于ASF的发布指南:</p>\n<p><a href=\"https://incubator.apache.org/guides/releasemanagement.html\">Apache Release Guide</a></p>\n<p><a href=\"https://incubator.apache.org/\">Apache incubator 官网</a></p>\n<h2>1. 添加GPG KEY</h2>\n<blockquote>\n<p>本章节主要参考：<a href=\"https:/ [...]
+ "__html": "<h1>如何发布版本</h1>\n<blockquote>\n<p>本文主要介绍了Release Manager如何按照Apache的流程发布版本，</p>\n</blockquote>\n<p>Source Release是Apache关注的重点，也是发布的必须内容；\nBinary Release是可选项，InLong可以选择是否发布二进制包到Apache仓库或者发布到Maven中央仓库。</p>\n<p>请参考以下链接，找到更多关于ASF的发布指南:</p>\n<p><a href=\"https://incubator.apache.org/guides/releasemanagement.html\">Apache Release Guide</a></p>\n<p><a href=\"https://incubator.apache.org/\">Apache incubator 官网</a></p>\n<h2>1. 添加GPG KEY</h2>\n<blockquote>\n<p>本章节主要参考：<a href=\"https:/ [...]
"link": "/zh-cn/docs/development/how-to-release.html",
"meta": {
"title": "如何发布版本- Apache InLong"
diff --git a/zh-cn/docs/development/how-to-release.md b/zh-cn/docs/development/how-to-release.md
index 9e7720c..669e35d 100644
--- a/zh-cn/docs/development/how-to-release.md
+++ b/zh-cn/docs/development/how-to-release.md
@@ -509,7 +509,7 @@ Release Notes: https://inlong.apache.org/en-us/docs/download/${release_version}.
Website: https://inlong.apache.org/
InLong Resources:
-- Issue: https://issues.apache.org/jira/projects/INLONG/issues
+- Issue: https://github.com/apache/incubator-inlong/issues
- Mailing list: dev@inlong.apache.org
Thanks
diff --git a/zh-cn/docs/development/how-to-vote-a-committer-ppmc.html b/zh-cn/docs/development/how-to-vote-a-committer-ppmc.html
index f8b080d..3c96109 100644
--- a/zh-cn/docs/development/how-to-vote-a-committer-ppmc.html
+++ b/zh-cn/docs/development/how-to-vote-a-committer-ppmc.html
@@ -53,7 +53,7 @@
</li>
<li>
<p>如果以上内容都以完成，投票发起者还需要做如下2件事情：
-7.1 向项目负责人申请添加项目组成员，开通jira及apache项目的权限帐号。</p>
+7.1 向项目负责人申请添加项目组成员，开通apache项目的权限帐号。</p>
<p>7.2 向dev@inlong.apache.org邮件组发通知邮件：</p>
<blockquote>
<pre><code> [ANNOUNCE] New XXXXXX: YYYYY
diff --git a/zh-cn/docs/development/how-to-vote-a-committer-ppmc.json b/zh-cn/docs/development/how-to-vote-a-committer-ppmc.json
index 53acfd8..224bb8a 100644
--- a/zh-cn/docs/development/how-to-vote-a-committer-ppmc.json
+++ b/zh-cn/docs/development/how-to-vote-a-committer-ppmc.json
@@ -1,6 +1,6 @@
{
"filename": "how-to-vote-a-committer-ppmc.md",
- "__html": "<h1>成为InLong Committer 或 PPMC 的投票过程</h1>\n<ol>\n<li>\n<p>TubeMQ的PPMC成员发现社区贡献者任何有价值的贡献并取得候选人本人同意后，在InLong的private邮件列表发起讨论；</p>\n<blockquote>\n<p>[DISCUSS] YYYYY as a InLong XXXXXX</p>\n</blockquote>\n<p>邮件里要把对方的贡献，可以查看的出处说清楚，便于大家讨论分析；讨论邮件将持续至少72个小时，项目组成员，包括mentor们会针对提议邮件充分发表自己的看法；</p>\n</li>\n<li>\n<p>不管有没有分歧，在讨论邮件过后，投票发起者需要在在InLong的private邮件列表发起Committer或PPMC的选举投票；</p>\n<blockquote>\n<p>[VOTE] YYYYY as a InLong XXXXXX</p>\n</blockquote>\n<p>投票邮件至少持续72小时，至少要3票+1通过，如果0票或者有1票-1 [...]
+ "__html": "<h1>成为InLong Committer 或 PPMC 的投票过程</h1>\n<ol>\n<li>\n<p>TubeMQ的PPMC成员发现社区贡献者任何有价值的贡献并取得候选人本人同意后，在InLong的private邮件列表发起讨论；</p>\n<blockquote>\n<p>[DISCUSS] YYYYY as a InLong XXXXXX</p>\n</blockquote>\n<p>邮件里要把对方的贡献，可以查看的出处说清楚，便于大家讨论分析；讨论邮件将持续至少72个小时，项目组成员，包括mentor们会针对提议邮件充分发表自己的看法；</p>\n</li>\n<li>\n<p>不管有没有分歧，在讨论邮件过后，投票发起者需要在在InLong的private邮件列表发起Committer或PPMC的选举投票；</p>\n<blockquote>\n<p>[VOTE] YYYYY as a InLong XXXXXX</p>\n</blockquote>\n<p>投票邮件至少持续72小时，至少要3票+1通过，如果0票或者有1票-1 [...]
"link": "/zh-cn/docs/development/how-to-vote-a-committer-ppmc.html",
"meta": {
"title": "成为InLong Committer 或 PPMC 的投票过程 - Apache InLong"
diff --git a/zh-cn/docs/development/how-to-vote-a-committer-ppmc.md b/zh-cn/docs/development/how-to-vote-a-committer-ppmc.md
index 6c10efe..1a70f54 100644
--- a/zh-cn/docs/development/how-to-vote-a-committer-ppmc.md
+++ b/zh-cn/docs/development/how-to-vote-a-committer-ppmc.md
@@ -37,7 +37,7 @@ title: 成为InLong Committer 或 PPMC 的投票过程 - Apache InLong
7. 如果以上内容都以完成，投票发起者还需要做如下2件事情：
- 7.1 向项目负责人申请添加项目组成员，开通jira及apache项目的权限帐号。
+ 7.1 向项目负责人申请添加项目组成员，开通apache项目的权限帐号。
7.2 向dev@inlong.apache.org邮件组发通知邮件：
> [ANNOUNCE] New XXXXXX: YYYYY