[GitHub] [dolphinscheduler] SbloodyS commented on a diff in pull request #12265: [Docs] Change the process in all files to workflow

[GitBox <gi...@apache.org>]

SbloodyS commented on code in PR #12265:
URL: https://github.com/apache/dolphinscheduler/pull/12265#discussion_r990754928


##########
docs/docs/en/contribute/join/become-a-committer.md:
##########
@@ -82,7 +82,7 @@ receive a follow-up message with the next steps for
 establishing you as a committer.
 ```
 
-## Invitation acceptance process
+## Invitation acceptance workflow

Review Comment:
   Same here.



##########
docs/docs/en/contribute/join/become-a-committer.md:
##########
@@ -46,7 +46,7 @@ rather than unnecessary constraints.
 
 Being a committer enables you to more easily make 
 changes without needing to go through the patch 
-submission process. 
+submission workflow. 

Review Comment:
   This should not be modified.



##########
docs/docs/en/contribute/join/become-a-committer.md:
##########
@@ -16,14 +16,14 @@ Community involvement: Committers should have a constructive and friendly attitu
 
 ## 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.
+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 workflow will kick off.

Review Comment:
   Same here.



##########
docs/docs/en/contribute/join/become-a-committer.md:
##########
@@ -150,7 +150,7 @@ The V.P. and chair of the PMC is the secretary, who is responsible for initializ
 
 In most cases, a new PMC member is nominated from the committer team. But it is also possible to become a PMC member directly, so long as the PMC agrees to the nomination and is confident that the candidate is ready. For instance, this can be demonstrated by the fact that he/she has been an Apache member, an Apache officer, or a PMC member of another project.
 
-The new PMC voting process should also follow the `[DISCUSS]`, `[VOTE]` and `[RESULT][VOTE]` procedures using a private mail list, just like the voting process for new committers.
+The new PMC voting workflow should also follow the `[DISCUSS]`, `[VOTE]` and `[RESULT][VOTE]` procedures using a private mail list, just like the voting workflow for new committers.

Review Comment:
   Same here.



##########
docs/docs/en/contribute/join/become-a-committer.md:
##########
@@ -133,8 +133,8 @@ As a committer, you could
 2. Create and push codes to the new branch in the Apache repo.
 3. Prepare a new release. Remember to confirm with the committer team before you prepare, because that it is the right time to create the release.
 
-The PMC hopes that the new committer will take part in the release process as well as release voting, even though their vote will be regarded as `+1 no binding`.
-Being familiar with the release process is key to being promoted to the role of PMC member.
+The PMC hopes that the new committer will take part in the release workflow as well as release voting, even though their vote will be regarded as `+1 no binding`.
+Being familiar with the release workflow is key to being promoted to the role of PMC member.

Review Comment:
   Same here.



-- 
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: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org