CalvinKirs commented on code in PR #12175:
URL: https://github.com/apache/dolphinscheduler/pull/12175#discussion_r981920768


##########
docs/docs/en/contribute/join/become-a-committer.md:
##########
@@ -1,11 +1,168 @@
-# How to Become DolphinScheduler Committer
+# How to become a committer of Apache Dolphinscheduler
 
-Anyone can be a contributor to an Apache project. Being a contributor simply 
means that you take an interest in the project and contribute in some way, 
ranging from asking sensible questions (which documents the project and 
provides feedback to developers) through to providing new features as patches.
+Dolphinscheduler Project Management Committee (PMC) is responsible for 
assessing the contributions of candidates.
 
-If you become a valuable contributor to the project you may well be invited to 
become a committer. Committer is a term used at the ASF to signify someone who 
is committed to a particular project. It brings with it the privilege of write 
access to the project repository and resources.
+Like many Apache projects, Dolphinscheduler welcome all contributions, 
including code contributions, blog entries, guides for new users, public 
speeches, and enhancement of the project in various ways.
 
-In Dolphinscheduler community, if a committer who have earned even more merit, 
can be invited to be a part of the Project Management Committee (PMC).
+Becoming a committer to get started contributing to Dolphinscheduler, learn 
how to contribute – anyone can submit patches, documentation and examples to 
the project.
 
-One thing that is sometimes hard to understand when you are new to the open 
development process used at the ASF, is that we value the community more than 
the code. A strong and healthy community will be respectful and be a fun and 
rewarding place. More importantly, a diverse and healthy community can continue 
to support the code over the longer term, even as individual companies come and 
go from the field.
+The PMC regularly adds new committers from the active contributors, based on 
their contributions to Dolphinscheduler. The qualifications for new committers 
include:
 
-More details could be found [here](https://community.apache.org/contributors/).
+Sustained contributions to Dolphinscheduler: Committers should have a history 
of major contributions to Dolphinscheduler. An ideal committer will have 
contributed broadly throughout the project, and have contributed at least one 
major component where they have taken an “ownership” role. An ownership role 
means that existing contributors feel that they should run patches for this 
component by this person.
+
+Quality of contributions: Committers more than any other community member 
should submit simple, well-tested, and well-designed patches. In addition, they 
should show sufficient expertise to be able to review patches, including making 
sure they fit within Dolphinscheduler’s engineering practices (testability, 
documentation, API stability, code style, etc). The committership is 
collectively responsible for the software quality and maintainability of 
Dolphinscheduler. Note that contributions to critical parts of 
Dolphinscheduler, like its core modules, will be held to a higher standard when 
assessing quality. Contributors to these areas will face more review of their 
changes.
+
+Community involvement: Committers should have a constructive and friendly 
attitude in all community interactions. They should also be active on the dev 
and user list and help mentor newer contributors and users. In design 
discussions, committers should maintain a professional and diplomatic approach, 
even in the face of disagreement.
+
+## Nominate new committer
+
+In Dolphinscheduler, **new committer nomination** could only be officially 
started by existing PMC members. If a new committer feels that he/she is 
qualified, he/she should contact any existing PMC member and discuss. If this 
is agreed among some members of the PMC, the process will kick off.
+
+The following steps are recommended (to be initiated only by an existing 2PMC 
member):

Review Comment:
   ```suggestion
   The following steps are recommended (to be initiated only by an existing PMC 
member):
   ```



-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to