clr-apache commented on a change in pull request #52:
URL: https://github.com/apache/comdev-site/pull/52#discussion_r558406527
##########
File path: source/contributors/etiquette.md
##########
@@ -54,45 +51,45 @@ Review and try to reformulate to be as clear as possible.
opinion, we must..." or the quite neutral "I think we should...", try to
use "Maybe we should consider..." or "Another idea that we could..."
- * If you disagree strongly with an email sent, tag it Important, then
-put it aside. Read it half a day later again. Put it aside. Read it again
-next day, and then it is easier to write a balanced and inviting response,
-instead of the initial vitriol that flows through us when we get upset. I
-found that sometimes a response wouldn't be necessary, as the importance
-was actually much lower than originally perceived, and I would be able to
-work "with", instead of "against", a given change.
+ * If you disagree strongly with an email, tag it Important, then
+put it aside. Read it again half a day later. Put it aside. Read it again the
+next day. After that, it will be easier to write a balanced and inviting
response,
+instead of delivering the initial vitriol that flows through us when we get
upset. I have
+found that sometimes a response won't be necessary, as the importance
+was actually much lower than I originally perceived, and I can
+work _with_, instead of _against_, a given change.
* Be forgiving and accept different priorities. The other person is not
out to get you or attack your work. More often than not, it is one of the
-above (a-d) that are failing, or that the other person prioritize some
-aspect higher than you do. Sometimes, this requires compromises, sometimes
-not and the different priorities can co-exist.
+above (a-d) that is failing, or the other person prioritizes some
+aspect higher than you do. Sometimes, this requires compromises; sometimes
+the different priorities can co-exist.
* Remember that everyone works on Apache projects as a volunteer.
People have jobs and lives outside of their Apache projects, and may need
-more time to even read messages on the list or respond. Be patient.
+more time to read and respond to messages on the list. Be patient.
-**Most communities at Apache consists of level-headed, reasonable people**, who
-have a strong vested interest in their Apache project. This interest, often
-passion, is both the source of tension, but it is also what unites the
+**Most communities at Apache consists of level-headed, reasonable people** who
+have a strong, vested interest in their Apache project. This interest, often
+passion, can be a source of tension, but it is also what unites
people within the community. It is easy to forget the vast amount of
agreement that exists, and get upset over relatively small disagreements.
-Ability to put that aside, or downplay the importance, will ensure a
+Ability to put that aside, or downplay the importance of disagreements, will
help ensure a
harmonious project.
**Face-to-Face** is excellent way to eliminate disagreements, but that is often
-not practical. Consider Skype or Google Hangout, just for the social aspect
+not practical. Consider talking things out on Skype, Google Hangout or the
project's Slack channel, just for the social aspect
of being part of this community. It should not be formal, and the
-invitation should go out to everyone, perhaps someone want to make a short
+invitation should go out to everyonek. Perhaps someone will want to make a
short
Review comment:
s/everyonek/everyone/
##########
File path: source/contributors/etiquette.md
##########
@@ -54,45 +51,45 @@ Review and try to reformulate to be as clear as possible.
opinion, we must..." or the quite neutral "I think we should...", try to
use "Maybe we should consider..." or "Another idea that we could..."
- * If you disagree strongly with an email sent, tag it Important, then
-put it aside. Read it half a day later again. Put it aside. Read it again
-next day, and then it is easier to write a balanced and inviting response,
-instead of the initial vitriol that flows through us when we get upset. I
-found that sometimes a response wouldn't be necessary, as the importance
-was actually much lower than originally perceived, and I would be able to
-work "with", instead of "against", a given change.
+ * If you disagree strongly with an email, tag it Important, then
+put it aside. Read it again half a day later. Put it aside. Read it again the
+next day. After that, it will be easier to write a balanced and inviting
response,
+instead of delivering the initial vitriol that flows through us when we get
upset. I have
+found that sometimes a response won't be necessary, as the importance
+was actually much lower than I originally perceived, and I can
+work _with_, instead of _against_, a given change.
* Be forgiving and accept different priorities. The other person is not
out to get you or attack your work. More often than not, it is one of the
-above (a-d) that are failing, or that the other person prioritize some
-aspect higher than you do. Sometimes, this requires compromises, sometimes
-not and the different priorities can co-exist.
+above (a-d) that is failing, or the other person prioritizes some
+aspect higher than you do. Sometimes, this requires compromises; sometimes
+the different priorities can co-exist.
* Remember that everyone works on Apache projects as a volunteer.
People have jobs and lives outside of their Apache projects, and may need
-more time to even read messages on the list or respond. Be patient.
+more time to read and respond to messages on the list. Be patient.
-**Most communities at Apache consists of level-headed, reasonable people**, who
-have a strong vested interest in their Apache project. This interest, often
-passion, is both the source of tension, but it is also what unites the
+**Most communities at Apache consists of level-headed, reasonable people** who
+have a strong, vested interest in their Apache project. This interest, often
+passion, can be a source of tension, but it is also what unites
people within the community. It is easy to forget the vast amount of
agreement that exists, and get upset over relatively small disagreements.
-Ability to put that aside, or downplay the importance, will ensure a
+Ability to put that aside, or downplay the importance of disagreements, will
help ensure a
harmonious project.
**Face-to-Face** is excellent way to eliminate disagreements, but that is often
Review comment:
Perhaps mention Zoom for completeness.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
