This is an automated email from the ASF dual-hosted git repository.
zhangyonglun pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-shenyu-website.git
The following commit(s) were added to refs/heads/main by this push:
new 365c1ed update update-committer (#483)
365c1ed is described below
commit 365c1edb17d75e3d0dbc11633dc8234f75a3bea4
Author: xiaoyu <[email protected]>
AuthorDate: Wed Mar 16 18:56:30 2022 +0800
update update-committer (#483)
---
community/4-committer.md | 23 ++++++---------------
.../current/4-committer.md | 24 ++++++----------------
2 files changed, 12 insertions(+), 35 deletions(-)
diff --git a/community/4-committer.md b/community/4-committer.md
index 9c7f9e3..12e5038 100644
--- a/community/4-committer.md
+++ b/community/4-committer.md
@@ -18,24 +18,13 @@ After you have made a lot of contributions, the community
will nominate. Become
## Committer Responsibilities {#committer-responsibilities}
-* Develop new features;
-* Refactor codes;
-* Review pull requests reliably and in time;
-* Consider and accept feature requests;
-* Answer questions;
-* Update documentation and example;
-* Improve processes and tools;
-* Guide new contributors join community.
+* Solving issue problems.
+* Mentoring contributors to the community.
-## Committer Routine {#committer-routine}
+## Pull Request
-1. A committer needs to review every day the Pull Request and issue list to be
processed by the community, and assign a suitable committer, that is, Assignee.
+* Give sound advice where possible.
+* AThe pull request should be marked `shenyu Lable` and the schedule must be
set.
+* Once the merge is complete, you need to check that the associated `issueNo`
is closed.
-2. After a committer is assigned with an issue, the following work is required:
-
-* Estimate whether it is a long-term issue. If it is, please label it as
pending;
-* Add issue labels, such as bug, enhancement, discussion, etc;
-* Add milestone.
-
-**Notice**: Whether it is a community issue or not, there must be Assignee
until the issue is completed.
diff --git
a/i18n/zh/docusaurus-plugin-content-docs-community/current/4-committer.md
b/i18n/zh/docusaurus-plugin-content-docs-community/current/4-committer.md
index e180c52..5f9afff 100755
--- a/i18n/zh/docusaurus-plugin-content-docs-community/current/4-committer.md
+++ b/i18n/zh/docusaurus-plugin-content-docs-community/current/4-committer.md
@@ -19,25 +19,13 @@ cover: "/img/architecture/shenyu-framework.png"
## 提交者责任
-- 开发新功能；
-- 代码重构；
-- 及时和可靠的评审Pull Request；
-- 思考和接纳新特性请求；
-- 解答问题；
-- 维护文档和代码示例；
-- 改进流程和工具；
-- 引导新的参与者融入社区。
+- 解答issue问题。
+- 指导贡献者加入社区。
-## 日常工作
+## 评审Pull Request
-1. committer需要每天查看社区待处理的Pull Request和issue列表，指定给合适的committer，即assignee。
+* 尽可能给出合理的建议。
-2. assignee在被分配issue后，需要进行如下判断：
+* pull request 应该标有 `shenyu Lable` 并且必须设置进度表。
-- 判断是否是长期issue，如是，则标记为pending。
-- 判断issue类型，如：bug，enhancement，discussion等。
-- 判断Milestone，并标记。
-
-**注意**
-
-无论是否是社区issue，都必须有assignee，直到issue完成。
+* 合并完成后，需要检查关联的 `issueNo` 是否关闭。
