You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by zh...@apache.org on 2022/01/20 10:13:00 UTC
[dolphinscheduler-website] branch master updated: [community] Add how to review issue or PR (#648)
This is an automated email from the ASF dual-hosted git repository.
zhongjiajie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/dolphinscheduler-website.git
The following commit(s) were added to refs/heads/master by this push:
new 1004927 [community] Add how to review issue or PR (#648)
1004927 is described below
commit 1004927d44bb138448771a0e3e0bdf0fb5114e0f
Author: Jiajie Zhong <zh...@hotmail.com>
AuthorDate: Thu Jan 20 18:12:10 2022 +0800
[community] Add how to review issue or PR (#648)
---
community/en-us/join/review.md | 151 +++++++++++++++++++++++++++++++++++++++++
community/en-us/team.md | 83 +++++++++++-----------
community/zh-cn/join/review.md | 139 +++++++++++++++++++++++++++++++++++++
community/zh-cn/team.md | 82 +++++++++++-----------
site_config/community.jsx | 18 +++++
5 files changed, 388 insertions(+), 85 deletions(-)
diff --git a/community/en-us/join/review.md b/community/en-us/join/review.md
new file mode 100644
index 0000000..794bca8
--- /dev/null
+++ b/community/en-us/join/review.md
@@ -0,0 +1,151 @@
+# Community Review
+
+Beside submit Issues and pull requests to the GitHub repository mentioned in [team](../team.md), another important way to
+contribute to DolphinScheduler is reviewing GitHub Issues or Pull Requests. You can not only know the latest new and
+direction of the community, but also understand the good design in others during you reviewing. At the same time, you can
+increase your exposure in the community and accumulate your honor.
+
+Anyone is encouraged to review Issues and Pull Requests. We also raise a Help Wanted email discussion to solicit contributors
+from the community to review them. You could see detail in [mail][mail-review-wanted], we put the results of mail thread
+in [GitHub Discussion][discussion-result-review-wanted].
+
+> Note: It is only users mentioned in the [GitHub Discussion][discussion-result-review-wanted] can review Issues or Pull
+> Requests, Community advocates **Anyone is encouraged to review Issues and Pull Requests**. Users in
+> [GitHub Discussion][discussion-result-review-wanted] show their willing to review when we collect in the mail thread.
+> The advantage of this list is when the community has discussion, in addition to the mention Members in [team](../team.md),
+> you can also find some help in [GitHub Discussion][discussion-result-review-wanted] people. If you want to join the
+> [GitHub Discussion][discussion-result-review-wanted], please comment in that discussion and leave a module you are interested
+> in, and the maintainer will add you to the list.
+
+## How Reviewing
+
+DolphinScheduler receives community contributions through GitHub, and all its Issues and Pull Requests are hosted in GitHub.
+If you want to join community by reviewing, please go to section [review Issues](#issues), if you prefer Pull Requests please
+go to section [review Pull Requests](#pull-requests).
+
+### Issues
+
+Review Issues means discuss [Issues][all-issues] in GitHub and give suggestions on it. Include but are not limited to the following situations
+
+| Situation | Reason | Label | Action |
+| ------ | ------ | ------ | ------ |
+| wont fix | Has been fixed in dev branch | [wontfix][label-wontfix] | Close Issue, inform creator the fixed version if it already release |
+| duplicate issue | Had the same problem before | [duplicate][label-duplicate] | Close issue, inform creator the link of same issue |
+| Description not clearly | Without detail reproduce step | [need more information][label-need-more-information] | Inform creator add more description |
+
+In addition give suggestion, add label for issue is also important during review. The labeled issues can be retrieved
+better, which convenient for further processing. An issue can with more than one label. Common issue categories are:
+
+| Label | Meaning |
+| ------ | ------ |
+| [UI][label-UI] | UI and front-end related |
+| [security][label-security] | Security Issue |
+| [user experience][label-user-experience] | User experience Issue |
+| [development][label-development] | Development Issue |
+| [Python][label-Python] | Python Issue |
+| [plug-in][label-plug-in] | Plug-in Issue |
+| [document][label-document] | Document Issue |
+| [docker][label-docker] | Docker Issue |
+| [need verify][label-need-verify] | Need verify Issue |
+| [e2e][label-e2e] | E2E Issue |
+| [win-os][label-win-os] | windows operating system Issue |
+| [suggestion][label-suggestion] | Give suggestion to us |
+
+Beside classification, label could also set the priority of Issues. The higher the priority, the more attention pay
+in the community, the easier it is to be fixed or implemented. The priority label are as follows
+
+| Label | priority |
+| ------ | ------ |
+| [priority:high][label-priority-high] | High priority |
+| [priority:middle][label-priority-middle] | Middle priority |
+| [priority:low][label-priority-low] | Low priority |
+
+All the labels above in common label. For all labels in this project you could see in [full label list][label-all-list]
+
+Before reading following content, please make sure you have labeled the Issue.
+
+* Remove label [Waiting for reply][label-waiting-for-reply] after replying: Label [Waiting for reply][label-waiting-for-reply]
+ added when [creating an Issue][issue-choose]. It makes positioning un reply issue more convenient, and you should remove
+ this label after you reviewed it. If you do not remove it, will cause others to waste time looking on the same issue.
+* Mark [Waiting for review][label-waiting-for-review] when not sure whether issue is resolved or not: There are two situations
+ when you review issue. One is the problem has been located or resolved, maybe have to [Create PR](../development/submit-code.md)
+ when necessary. Secondly, you are not sure about this issue, you can labeled [Waiting for review][label-waiting-for-review]
+ and mention others to make a second confirmation.
+
+When an Issue need to create Pull Requests, you could also labeled it from below.
+
+| Label | Mean |
+| ------ | ------ |
+| [Chore][label-Chore] | Chore for project |
+| [Good first issue][label-good-first-issue] | Good first issue for new contributor |
+| [easy to fix][label-easy-to-fix] | Easy to fix, harder than `Good first issue` |
+| [help wanted][label-help-wanted] | Help wanted |
+
+> Note: Only members have permission to add or delete label. When you need to add or remove lebals but are not member,
+> you can `@` members to do that. But as long as you have a GitHub account, you can comment on issues and give suggestions.
+> We encourage everyone in the community to comment and answer issues
+
+### Pull Requests
+
+Review Pull mean discussing in [Pull Requests][all-PRs] in GitHub and giving suggestions to it. DolphinScheduler's
+Pull Requests reviewing are the same as [GitHub's reviewing changes in pull requests][gh-review-pr]. You can give your
+suggestions in Pull Requests
+
+* When you think the Pull Request is OK to be merged, you can agree to the Pull Request according to the "Approve" process
+ in [GitHub's reviewing changes in pull requests][gh-review-pr].
+* When you think Pull Request needs to be changed, you can comment it according to the "Comment" process in
+ [GitHub's reviewing changes in pull requests][gh-review-pr]. And when you think issues that must be fixed before they
+ merged, please follow "Request changes" in [GitHub's reviewing changes in pull requests][gh-review-pr] to ask contributors
+ modify it.
+
+Labeled Pull Requests is an important part. Reasonable classification can save a lot of time for reviewers. The good news
+is that the label's name and usage of Pull Requests are the same in [Issues](#issues), which can reduce the memory. For
+example, if there is a Pull Request is related to docker and block deployment. We can label it with [docker][label-docker]
+and [priority:high][label-priority-high].
+
+Pull Requests have some unique labels of it own
+
+| Label | Mean |
+| ------ | ------ |
+| [miss document][label-miss-document] | Pull Requests miss document, and should be add |
+| [first time contributor][label-first-time-contributor] | Pull Requests submit by first time contributor |
+| [don't merge][label-do-not-merge] | Pull Requests have some problem and should not be merged |
+
+> Note: Only members have permission to add or delete label. When you need to add or remove lebals but are not member,
+> you can `@` members to do that. But as long as you have a GitHub account, you can comment on Pull Requests and give suggestions.
+> We encourage everyone in the community to review Pull Requests
+
+[mail-review-wanted]: https://lists.apache.org/thread/9flwlzrp69xjn6v8tdkbytq8glqp2k51
+[discussion-result-review-wanted]: https://github.com/apache/dolphinscheduler/discussions/7545
+[label-wontfix]: https://github.com/apache/dolphinscheduler/labels/wontfix
+[label-duplicate]: https://github.com/apache/dolphinscheduler/labels/duplicate
+[label-need-more-information]: https://github.com/apache/dolphinscheduler/labels/need%20more%20information
+[label-win-os]: https://github.com/apache/dolphinscheduler/labels/win-os
+[label-waiting-for-reply]: https://github.com/apache/dolphinscheduler/labels/Waiting%20for%20reply
+[label-waiting-for-review]: https://github.com/apache/dolphinscheduler/labels/Waiting%20for%20review
+[label-user-experience]: https://github.com/apache/dolphinscheduler/labels/user%20experience
+[label-development]: https://github.com/apache/dolphinscheduler/labels/development
+[label-UI]: https://github.com/apache/dolphinscheduler/labels/UI
+[label-suggestion]: https://github.com/apache/dolphinscheduler/labels/suggestion
+[label-security]: https://github.com/apache/dolphinscheduler/labels/security
+[label-Python]: https://github.com/apache/dolphinscheduler/labels/Python
+[label-plug-in]: https://github.com/apache/dolphinscheduler/labels/plug-in
+[label-document]: https://github.com/apache/dolphinscheduler/labels/document
+[label-docker]: https://github.com/apache/dolphinscheduler/labels/docker
+[label-all-list]: https://github.com/apache/dolphinscheduler/labels
+[label-Chore]: https://github.com/apache/dolphinscheduler/labels/Chore
+[label-good-first-issue]: https://github.com/apache/dolphinscheduler/labels/good%20first%20issue
+[label-help-wanted]: https://github.com/apache/dolphinscheduler/labels/help%20wanted
+[label-easy-to-fix]: https://github.com/apache/dolphinscheduler/labels/easy%20to%20fix
+[label-priority-high]: https://github.com/apache/dolphinscheduler/labels/priority%3Ahigh
+[label-priority-middle]: https://github.com/apache/dolphinscheduler/labels/priority%3Amiddle
+[label-priority-low]: https://github.com/apache/dolphinscheduler/labels/priority%3Alow
+[label-miss-document]: https://github.com/apache/dolphinscheduler/labels/miss%20document
+[label-first-time-contributor]: https://github.com/apache/dolphinscheduler/labels/first%20time%20contributor
+[label-do-not-merge]: https://github.com/apache/dolphinscheduler/labels/don%27t%20merge
+[label-e2e]: https://github.com/apache/dolphinscheduler/labels/e2e
+[label-need-verify]: https://github.com/apache/dolphinscheduler/labels/need%20to%20verify
+[issue-choose]: https://github.com/apache/dolphinscheduler/issues/new/choose
+[all-issues]: https://github.com/apache/dolphinscheduler/issues
+[all-PRs]: https://github.com/apache/dolphinscheduler/pulls
+[gh-review-pr]: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews
diff --git a/community/en-us/team.md b/community/en-us/team.md
index e533c3b..1074b16 100644
--- a/community/en-us/team.md
+++ b/community/en-us/team.md
@@ -4,52 +4,49 @@ The DolphinScheduler team is comprised of Members and Contributors. Members have
## Members
-### PMC
-
-| Public Name | Apache ID | GitHub ID |
-|-------------------| ------------ | -------------- |
-| Furkan Kamaci | kamaci | kamaci |
-| Gang Li | lgcareer | lgcareer |
-| Guo Jiwei | technoboy | Technoboy- |
-| Guo William | guowei | William-GuoWei |
-| Jun Gao | gaojun2048 | gaojun2048 |
-| Kevin Ratnasekera | djkevincr | djkevincr |
-| Leon Bao | leonbao | lenboo,leonbao |
-| Liang Chen | chenliang613 | chenliang613 |
-| Lidong Dai | lidongdai | dailidong |
-| Qiao Zhanwei | journey | qiaozhanwei |
-| Shao Feng Shi | shaofengshi | shaofengshi |
-| Sheng Wu | wusheng | wu-sheng |
-| Wu Baoqi | baoqiwu | Baoqi |
-| Xiaochun Liu | liuxiaochun | khadgarmage |
-| ZijJian Gong | millionfor | millionfor |
-| Calvin Kirs | kirs | CalvinKirs |
-
+| Public Name | Apache ID | GitHub ID |
+|-------------------| ------------ | ---------------------------------------------------- |
+| Furkan Kamaci | kamaci | [@kamaci](https://github.com/kamaci) |
+| Gang Li | lgcareer | [@lgcareer](https://github.com/lgcareer) |
+| Guo Jiwei | technoboy | [@Technoboy-](https://github.com/Technoboy-) |
+| Guo William | guowei | [@William-GuoWei](https://github.com/William-GuoWei) |
+| Jun Gao | gaojun2048 | [@gaojun2048](https://github.com/gaojun2048) |
+| Kevin Ratnasekera | djkevincr | [@djkevincr](https://github.com/djkevincr) |
+| Leon Bao | leonbao | [@lenboo](https://github.com/lenboo) |
+| Liang Chen | chenliang613 | [@chenliang613](https://github.com/chenliang613) |
+| Lidong Dai | lidongdai | [@dailidong](https://github.com/dailidong) |
+| Qiao Zhanwei | journey | [@qiaozhanwei](https://github.com/qiaozhanwei) |
+| Shao Feng Shi | shaofengshi | [@shaofengshi](https://github.com/shaofengshi) |
+| Sheng Wu | wusheng | [@wu-sheng](https://github.com/wu-sheng) |
+| Wu Baoqi | baoqiwu | [@Baoqi](https://github.com/Baoqi) |
+| Xiaochun Liu | liuxiaochun | [@khadgarmage](https://github.com/khadgarmage) |
+| ZijJian Gong | millionfor | [@millionfor](https://github.com/millionfor) |
+| Calvin Kirs | kirs | [@CalvinKirs](https://github.com/CalvinKirs) |
### Committer
-| Public Name | Apache ID | GitHub ID |
-|---------------|--------------|-------------------|
-| BoYi Zhang | zhangboyi | BoYiZhang |
-| Caibiao Xiang | break60 | break60 |
-| Chong Zhuang | kerwin | zhuangchong |
-| Cong Huang | chongchongzi | chongchongzi |
-| Hemin Wen | wenhemin | wen-hemin |
-| Kai Zhu | zhukai | nauu |
-| Kejia Chen | jave | Jave-Chen |
-| Li Huang | eights | Eights-Li |
-| Lin Li | lilin | samz406 |
-| Shang Lou | clay4megtr | clay4444 |
-| Shaojie Wu | gabrywu | gabrywu |
-| Shiwen Cheng | chengshiwen | chengshiwen |
-| Wenhe Li | liwenhe | liwenhe1993 |
-| Xingchun Chen | chenxingchun | xingchun-chen |
-| Yichao Yang | yangyichao | yangyichao-mango |
-| Zongyao Zhang | lfyee | lfyee |
-| Zhenxu Ke | kezhenxu94 | kezhenxu94 |
-| Jiajie Zhong | zhongjiajie | zhongjiajie |
-| Yizhi Wang | wangyizhi | Wangyizhi1 |
-| ShunFeng Cai | caishunfeng | caishunfeng |
+| Public Name | Apache ID | GitHub ID |
+| ------------- | ------------ | -------------------------------------------------------- |
+| BoYi Zhang | zhangboyi | [@BoYiZhang](https://github.com/BoYiZhang) |
+| Caibiao Xiang | break60 | [@break60](https://github.com/break60) |
+| Chong Zhuang | kerwin | [@zhuangchong](https://github.com/zhuangchong) |
+| Cong Huang | chongchongzi | [@chongchongzi](https://github.com/chongchongzi) |
+| Hemin Wen | wenhemin | [@wen-hemin](https://github.com/wen-hemin) |
+| Kai Zhu | zhukai | [@nauu](https://github.com/nauu) |
+| Kejia Chen | jave | [@Jave-Chen](https://github.com/Jave-Chen) |
+| Li Huang | eights | [@Eights-Li](https://github.com/Eights-Li) |
+| Lin Li | lilin | [@samz406](https://github.com/samz406) |
+| Shang Lou | clay4megtr | [@clay4444](https://github.com/clay4444) |
+| Shaojie Wu | gabrywu | [@gabrywu](https://github.com/gabrywu) |
+| Shiwen Cheng | chengshiwen | [@chengshiwen](https://github.com/chengshiwen) |
+| Wenhe Li | liwenhe | [@liwenhe1993](https://github.com/liwenhe1993) |
+| Xingchun Chen | chenxingchun | [@xingchun-chen](https://github.com/xingchun-chen) |
+| Yichao Yang | yangyichao | [@yangyichao-mango](https://github.com/yangyichao-mango) |
+| Zongyao Zhang | lfyee | [@lfyee](https://github.com/lfyee) |
+| Zhenxu Ke | kezhenxu94 | [@kezhenxu94](https://github.com/kezhenxu94) |
+| Jiajie Zhong | zhongjiajie | [@zhongjiajie](https://github.com/zhongjiajie) |
+| Yizhi Wang | wangyizhi | [@Wangyizhi1](https://github.com/Wangyizhi1) |
+| ShunFeng Cai | caishunfeng | [@caishunfeng](https://github.com/caishunfeng) |
## Contributors
diff --git a/community/zh-cn/join/review.md b/community/zh-cn/join/review.md
new file mode 100644
index 0000000..5690873
--- /dev/null
+++ b/community/zh-cn/join/review.md
@@ -0,0 +1,139 @@
+# 参与社区 review
+
+贡献 DolphinScheduler 的方式，除了向 [团队](../team.md) 中提到的 GitHub 仓库提交 Issues 和 pull requests 外，另一非常重要的方式是
+review 社区的 Issues 或者 Pull Requests。通过别人 Issues 和 Pull Requests，你不仅能知道社区的最新进展和发展方向，还能了解别人代码的设
+计思想，同时可以增加自己在社区的曝光、积累自己在社区的荣誉值。
+
+任何人都被鼓励去 review 社区的 Issues 和 Pull Requests。我们还曾经发起过一个 Help Wanted 的邮件讨论，向社区征求贡献者协助 review Issues
+以及 Pull Requests，详见 [邮件][mail-review-wanted]，并将其结果放到了 [GitHub Discussion][discussion-result-review-wanted] 中。
+
+> 注意: 这里并不是说只有 [GitHub Discussion][discussion-result-review-wanted] 中提及的用户才可以协助 review Issue 或者 Pull Requests，
+> 请记住社区的主张是 **任何人都被鼓励去 review 社区的 Issues 和 Pull Requests**。只是那部分用户在邮件列表意见征集的时候，表达了愿意付
+> 出更多的时间，参与社区的 review。另一个好处是，当社区有不确定的问题的时，除了可以找 [团队](../team.md) 中对应的 Members 外，还可以找
+> [GitHub Discussion][discussion-result-review-wanted] 中提及的人解答对应的问题。如果你要想要加入到 [GitHub Discussion][discussion-result-review-wanted]
+> 中，请在该 discussion 中评论并留下你感兴趣的模块，维护者会将你加入到对应的名单中。
+
+## 怎么参与社区 review
+
+DolphinScheduler 主要通过 GitHub 接收社区的贡献，其所有的 Issues 和 Pull Requests 都托管在 GitHub 中，如果你想参与 Issues 的 review
+具体请查看 [review Issues](#issues) 章节，如果你是想要参与 Pull Requests 的 review 具体请查看 [review Pull Requests](#pull-requests)
+章节。
+
+### Issues
+
+Review Issues 是指在 GitHub 中参与 [Issues][all-issues] 的讨论，并在对应的 Issues 给出建议。给出的建议包括但不限于如下的情况
+
+| 情况 | 原因 | 需增加标签 | 需要的动作 |
+| ------ | ------ | ------ | ------ |
+| 不需要修改 | 问题在 dev 分支最新代码中已经修复了 | [wontfix][label-wontfix] | 关闭 Issue，告知提出者将在那个版本发布，如已发布告知版本 |
+| 重复的问题 | 之前已经存在相同的问题 | [duplicate][label-duplicate] | 关闭 Issue，告知提出者相同问题的连接 |
+| 问题描述不清晰 | 没有明确说明问题如何复现 | [need more information][label-need-more-information] | 提醒用户需要增加缺失的描述 |
+
+除了个 issue 建议之外，给 Issue 分类也是非常重要的一个工作。分类后的 Issue 可以更好的被检索，为以后进一步处理提供便利。一个 Issue 可以被打上多个标签，常见的 Issue 分类有
+
+| 标签 | 标签代表的情况 |
+| ------ | ------ |
+| [UI][label-UI] | UI以及前端相关的 Issue |
+| [security][label-security] | 安全相关的 Issue |
+| [user experience][label-user-experience] | 用户体验相关的 Issue |
+| [development][label-development] | 开发者相关的 Issue |
+| [Python][label-Python] | Python相关的 Issue |
+| [plug-in][label-plug-in] | 插件相关的 Issue |
+| [document][label-document] | 文档相关的 Issue |
+| [docker][label-docker] | docker相关的 Issue |
+| [need verify][label-need-verify] | Issue 需要被验证 |
+| [e2e][label-e2e] | e2e相关的 Issue |
+| [win-os][label-win-os] | windows 操作系统相关的 Issue |
+| [suggestion][label-suggestion] | Issue 为项目提出了建议 |
+
+标签除了分类之外，还能区分 Issue 的优先级，优先级越高的标签越重要，越容易被重视，并会尽快被修复或者实现，优先级的标签如下
+
+| 标签 | 优先级 |
+| ------ | ------ |
+| [priority:high][label-priority-high] | 高优先级 |
+| [priority:middle][label-priority-middle] | 中优先级 |
+| [priority:low][label-priority-low] | 低优先级 |
+
+以上是常见的几个标签，更多的标签请查阅项目[全部的标签列表][label-all-list]
+
+在阅读以下内容是，请确保你已经为 Issue 打了标签。
+
+* 回复后及时去掉标签[Waiting for reply][label-waiting-for-reply]：在 [创建 Issue 的时候][issue-choose]，我们会为 Issue 打上特定的标签
+ [Waiting for reply][label-waiting-for-reply]，方便定位还没有被回复的 Issue，所以当你 review 了 Issue 之后，就需要将标签
+ [Waiting for reply][label-waiting-for-reply] 及时的从 Issue 中删除。
+* 打上 [Waiting for review][label-waiting-for-review] 标当你不确定这个 Issue 是否被解决：当你查阅了 Issue 后，会有两个情况出现。一是
+ 问题已经被定位或解决，如果创建 Pull Requests 的话，则参考 [创建PR](../development/submit-code.md)。二是你也不确定这个问题是否真的是
+ 被解决，这时你可以为 Issue 打上 [Waiting for review][label-waiting-for-review] 标签，并在 Issue 中 `@` 对应的人进行二次确认
+
+当 Issue 需要被创建 Pull Requests 解决，也可以视情况打上部分标签
+
+| 标签 | 标签代表的PR |
+| ------ | ------ |
+| [Chore][label-Chore] | 日常维护工作 |
+| [Good first issue][label-good-first-issue] | 适合首次贡献者解决的 Issue |
+| [easy to fix][label-easy-to-fix] | 比较容易解决 |
+| [help wanted][label-help-wanted] | 向社区寻求帮忙 |
+
+> 注意: 上面关于增加和删除标签的操作，目前只有成员可以操作，当你遇到需要增减标签的时候，但是不是成员是，可以 `@` 对应的成员让其帮忙增减。
+> 但只要你有 GitHub 账号就能评论 Issue，并给出建议。我们鼓励社区每人都去评论并为 Issue 给出解答
+
+### Pull Requests
+
+Review Pull 是指在 GitHub 中参与 [Pull Requests][all-PRs] 的讨论，并在对应的 Pull Requests 给出建议。DolphinScheduler review
+Pull Requests 与 [GitHub 的 reviewing changes in pull requests][gh-review-pr] 一样。你可以为 Pull Requests 提出自己的看法，
+
+* 当你认为这个 Pull Requests 没有问题，可以被合并的时候，可以根据 [GitHub 的 reviewing changes in pull requests][gh-review-pr] 的
+ approve 流程同意这个 Pull Requests。
+* 当你觉得这个 Pull Requests 需要被修改时，可以根据 [GitHub 的 reviewing changes in pull requests][gh-review-pr] 的 comment
+ 流程评论这个 Pull Requests。当你认为存在一定要先修复才能合并的问题，请参照 [GitHub 的 reviewing changes in pull requests][gh-review-pr]
+ 的 Request changes 流程要求贡献者修改 Pull Requests 的内容。
+
+为 Pull Requests 打上标签也是非常重要的一个环节，合理的分类能为后来的 reviewer 节省大量的时间。值得高兴的是，Pull Requests 的标签和 [Issues](#issues)
+中提及的标签和用法是一致的，这能减少 reviewer 对标签的记忆。例如这个 Pull Requests 是和 docker 并且直接影响到用户部署的，我们可以为他
+打上 [docker][label-docker] 和 [priority:high][label-priority-high] 的标签。
+
+除了和 Issue 类似的标签外，Pull Requests 还有许多自己特有的标签
+
+| 标签 | 含义 |
+| ------ | ------ |
+| [miss document][label-miss-document] | 该 Pull Requests 缺少文档 需要增加 |
+| [first time contributor][label-first-time-contributor] | 该 Pull Requests 贡献者是第一次贡献项目 |
+| [don't merge][label-do-not-merge] | 该 Pull Requests 有问题 暂时先不要合并 |
+
+> 注意: 上面关于增加和删除标签的操作，目前只有成员可以操作，当你遇到需要增减标签的时候，可以 `@` 对应的成员让其帮忙增减。但只要你有 GitHub
+> 账号就能评论 Pull Requests，并给出建议。我们鼓励社区每人都去评论并为 Pull Requests 给出建议
+
+[mail-review-wanted]: https://lists.apache.org/thread/9flwlzrp69xjn6v8tdkbytq8glqp2k51
+[discussion-result-review-wanted]: https://github.com/apache/dolphinscheduler/discussions/7545
+[label-wontfix]: https://github.com/apache/dolphinscheduler/labels/wontfix
+[label-duplicate]: https://github.com/apache/dolphinscheduler/labels/duplicate
+[label-need-more-information]: https://github.com/apache/dolphinscheduler/labels/need%20more%20information
+[label-win-os]: https://github.com/apache/dolphinscheduler/labels/win-os
+[label-waiting-for-reply]: https://github.com/apache/dolphinscheduler/labels/Waiting%20for%20reply
+[label-waiting-for-review]: https://github.com/apache/dolphinscheduler/labels/Waiting%20for%20review
+[label-user-experience]: https://github.com/apache/dolphinscheduler/labels/user%20experience
+[label-development]: https://github.com/apache/dolphinscheduler/labels/development
+[label-UI]: https://github.com/apache/dolphinscheduler/labels/UI
+[label-suggestion]: https://github.com/apache/dolphinscheduler/labels/suggestion
+[label-security]: https://github.com/apache/dolphinscheduler/labels/security
+[label-Python]: https://github.com/apache/dolphinscheduler/labels/Python
+[label-plug-in]: https://github.com/apache/dolphinscheduler/labels/plug-in
+[label-document]: https://github.com/apache/dolphinscheduler/labels/document
+[label-docker]: https://github.com/apache/dolphinscheduler/labels/docker
+[label-all-list]: https://github.com/apache/dolphinscheduler/labels
+[label-Chore]: https://github.com/apache/dolphinscheduler/labels/Chore
+[label-good-first-issue]: https://github.com/apache/dolphinscheduler/labels/good%20first%20issue
+[label-help-wanted]: https://github.com/apache/dolphinscheduler/labels/help%20wanted
+[label-easy-to-fix]: https://github.com/apache/dolphinscheduler/labels/easy%20to%20fix
+[label-priority-high]: https://github.com/apache/dolphinscheduler/labels/priority%3Ahigh
+[label-priority-middle]: https://github.com/apache/dolphinscheduler/labels/priority%3Amiddle
+[label-priority-low]: https://github.com/apache/dolphinscheduler/labels/priority%3Alow
+[label-miss-document]: https://github.com/apache/dolphinscheduler/labels/miss%20document
+[label-first-time-contributor]: https://github.com/apache/dolphinscheduler/labels/first%20time%20contributor
+[label-do-not-merge]: https://github.com/apache/dolphinscheduler/labels/don%27t%20merge
+[label-e2e]: https://github.com/apache/dolphinscheduler/labels/e2e
+[label-need-verify]: https://github.com/apache/dolphinscheduler/labels/need%20to%20verify
+[issue-choose]: https://github.com/apache/dolphinscheduler/issues/new/choose
+[all-issues]: https://github.com/apache/dolphinscheduler/issues
+[all-PRs]: https://github.com/apache/dolphinscheduler/pulls
+[gh-review-pr]: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews
diff --git a/community/zh-cn/team.md b/community/zh-cn/team.md
index faa6bea..e72313c 100644
--- a/community/zh-cn/team.md
+++ b/community/zh-cn/team.md
@@ -6,51 +6,49 @@ DolphinScheduler 团队由成员和贡献者组成。 成员可以直接访问 D
### PMC
-| Public Name | Apache ID | GitHub ID |
-|-------------------| ------------ | -------------- |
-| Furkan Kamaci | kamaci | kamaci |
-| Gang Li | lgcareer | lgcareer |
-| Guo Jiwei | technoboy | Technoboy- |
-| Guo William | guowei | William-GuoWei |
-| Jun Gao | gaojun2048 | gaojun2048 |
-| Kevin Ratnasekera | djkevincr | djkevincr |
-| Leon Bao | leonbao | lenboo,leonbao |
-| Liang Chen | chenliang613 | chenliang613 |
-| Lidong Dai | lidongdai | dailidong |
-| Qiao Zhanwei | journey | qiaozhanwei |
-| Shao Feng Shi | shaofengshi | shaofengshi |
-| Sheng Wu | wusheng | wu-sheng |
-| Wu Baoqi | baoqiwu | Baoqi |
-| Xiaochun Liu | liuxiaochun | khadgarmage |
-| ZijJian Gong | millionfor | millionfor |
-| Calvin Kirs | kirs | CalvinKirs |
-
+| Public Name | Apache ID | GitHub ID |
+|-------------------| ------------ | ---------------------------------------------------- |
+| Furkan Kamaci | kamaci | [@kamaci](https://github.com/kamaci) |
+| Gang Li | lgcareer | [@lgcareer](https://github.com/lgcareer) |
+| Guo Jiwei | technoboy | [@Technoboy-](https://github.com/Technoboy-) |
+| Guo William | guowei | [@William-GuoWei](https://github.com/William-GuoWei) |
+| Jun Gao | gaojun2048 | [@gaojun2048](https://github.com/gaojun2048) |
+| Kevin Ratnasekera | djkevincr | [@djkevincr](https://github.com/djkevincr) |
+| Leon Bao | leonbao | [@lenboo](https://github.com/lenboo) |
+| Liang Chen | chenliang613 | [@chenliang613](https://github.com/chenliang613) |
+| Lidong Dai | lidongdai | [@dailidong](https://github.com/dailidong) |
+| Qiao Zhanwei | journey | [@qiaozhanwei](https://github.com/qiaozhanwei) |
+| Shao Feng Shi | shaofengshi | [@shaofengshi](https://github.com/shaofengshi) |
+| Sheng Wu | wusheng | [@wu-sheng](https://github.com/wu-sheng) |
+| Wu Baoqi | baoqiwu | [@Baoqi](https://github.com/Baoqi) |
+| Xiaochun Liu | liuxiaochun | [@khadgarmage](https://github.com/khadgarmage) |
+| ZijJian Gong | millionfor | [@millionfor](https://github.com/millionfor) |
+| Calvin Kirs | kirs | [@CalvinKirs](https://github.com/CalvinKirs) |
### Committer
-| Public Name | Apache ID | GitHub ID |
-| ------------- | ------------ | ---------------- |
-| BoYi Zhang | zhangboyi | BoYiZhang |
-| Caibiao Xiang | break60 | break60 |
-| Chong Zhuang | kerwin | zhuangchong |
-| Cong Huang | chongchongzi | chongchongzi |
-| Hemin Wen | wenhemin | wen-hemin |
-| Kai Zhu | zhukai | nauu |
-| Kejia Chen | jave | Jave-Chen |
-| Li Huang | eights | Eights-Li |
-| Lin Li | lilin | samz406 |
-| Shang Lou | clay4megtr | clay4444 |
-| Shaojie Wu | gabrywu | gabrywu |
-| Shiwen Cheng | chengshiwen | chengshiwen |
-| Wenhe Li | liwenhe | liwenhe1993 |
-| Xingchun Chen | chenxingchun | xingchun-chen |
-| Yichao Yang | yangyichao | yangyichao-mango |
-| Zongyao Zhang | lfyee | lfyee |
-| Zhenxu Ke | kezhenxu94 | kezhenxu94 |
-| Jiajie Zhong | zhongjiajie | zhongjiajie |
-| Yizhi Wang | wangyizhi | Wangyizhi1 |
-| ShunFeng Cai | caishunfeng | caishunfeng |
-
+| Public Name | Apache ID | GitHub ID |
+| ------------- | ------------ | -------------------------------------------------------- |
+| BoYi Zhang | zhangboyi | [@BoYiZhang](https://github.com/BoYiZhang) |
+| Caibiao Xiang | break60 | [@break60](https://github.com/break60) |
+| Chong Zhuang | kerwin | [@zhuangchong](https://github.com/zhuangchong) |
+| Cong Huang | chongchongzi | [@chongchongzi](https://github.com/chongchongzi) |
+| Hemin Wen | wenhemin | [@wen-hemin](https://github.com/wen-hemin) |
+| Kai Zhu | zhukai | [@nauu](https://github.com/nauu) |
+| Kejia Chen | jave | [@Jave-Chen](https://github.com/Jave-Chen) |
+| Li Huang | eights | [@Eights-Li](https://github.com/Eights-Li) |
+| Lin Li | lilin | [@samz406](https://github.com/samz406) |
+| Shang Lou | clay4megtr | [@clay4444](https://github.com/clay4444) |
+| Shaojie Wu | gabrywu | [@gabrywu](https://github.com/gabrywu) |
+| Shiwen Cheng | chengshiwen | [@chengshiwen](https://github.com/chengshiwen) |
+| Wenhe Li | liwenhe | [@liwenhe1993](https://github.com/liwenhe1993) |
+| Xingchun Chen | chenxingchun | [@xingchun-chen](https://github.com/xingchun-chen) |
+| Yichao Yang | yangyichao | [@yangyichao-mango](https://github.com/yangyichao-mango) |
+| Zongyao Zhang | lfyee | [@lfyee](https://github.com/lfyee) |
+| Zhenxu Ke | kezhenxu94 | [@kezhenxu94](https://github.com/kezhenxu94) |
+| Jiajie Zhong | zhongjiajie | [@zhongjiajie](https://github.com/zhongjiajie) |
+| Yizhi Wang | wangyizhi | [@Wangyizhi1](https://github.com/Wangyizhi1) |
+| ShunFeng Cai | caishunfeng | [@caishunfeng](https://github.com/caishunfeng) |
## 贡献者
diff --git a/site_config/community.jsx b/site_config/community.jsx
index fc8b19f..758853d 100644
--- a/site_config/community.jsx
+++ b/site_config/community.jsx
@@ -40,6 +40,15 @@ export default {
],
},
{
+ title: 'Join Community',
+ children: [
+ {
+ title: 'Review Issue or Pull Requests',
+ link: '/en-us/community/join/review.html',
+ },
+ ],
+ },
+ {
title: 'Contribution Guide',
children: [
{
@@ -267,6 +276,15 @@ export default {
],
},
{
+ title: '参与社区',
+ children: [
+ {
+ title: 'Review Issue or Pull Requests',
+ link: '/zh-cn/community/join/review.html',
+ },
+ ],
+ },
+ {
title: '提交者指南',
children: [
{