This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/comdev-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 5fb8650 Updated asf-site from master at
37d37f9084df5025a2d02ded7a034d1f82c746a6 using
https://ci-builds.apache.org/job/Community%20Development/job/site/job/master/191/
5fb8650 is described below
commit 5fb8650cfa63ee345cc4bd8e6e8c6a896f434c2a
Author: jenkins <[email protected]>
AuthorDate: Tue Feb 14 17:50:36 2023 +0000
Updated asf-site from master at 37d37f9084df5025a2d02ded7a034d1f82c746a6
using
https://ci-builds.apache.org/job/Community%20Development/job/site/job/master/191/
---
content/contributors/etiquette.html | 69 ++++++++++++++-----------------------
content/contributors/index.xml | 2 +-
content/index.xml | 2 +-
content/sitemap.xml | 4 +--
4 files changed, 30 insertions(+), 47 deletions(-)
diff --git a/content/contributors/etiquette.html
b/content/contributors/etiquette.html
index 65b1e66..61499ce 100644
--- a/content/contributors/etiquette.html
+++ b/content/contributors/etiquette.html
@@ -7,12 +7,12 @@
<meta name="keywords" content="apache, apache community, community
development, opensource"/>
<meta name="viewport" content="width=device-width, initial-scale=1,
maximum-scale=1" />
<meta property="og:title" content="Apache Community Etiquette Guidelines" />
-<meta property="og:description" content="The Apache Software Foundation (ASF)
and our many Apache projects welcome all participants who are willing to
respect our community guidelines. There are many behavior or etiquette guides
for online communities out there; we have a few Apache-specific tips below.
+<meta property="og:description" content="The Apache Software Foundation (ASF)
and our many Apache projects welcome all participants. Before you begin, it is
important to review and respect our community guidelines. There are many
behavior or etiquette guides for online communities out there; we have a few
Apache-specific tips below.
Code of Conduct The ASF has adopted a Code of Conduct which covers
interactions in all the online spaces that Apache projects use - email, issue
trackers, wikis, websites, IRC, and the like." />
<meta property="og:type" content="article" />
<meta property="og:url"
content="https://community.apache.org/contributors/etiquette.html"; />
<meta property="og:image"
content="https://community.apache.org/images/aceu19_1.jpg"/>
-<meta property="article:modified_time" content="2022-02-20T11:26:22-04:00"
/><meta property="og:site_name" content="Apache Community Development" />
+<meta property="article:modified_time" content="2023-02-13T12:54:55-06:00"
/><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Apache Community Etiquette
Guidelines</title>
@@ -199,7 +199,7 @@ Code of Conduct The ASF has adopted a Code of Conduct which
covers interactions
<hr>
<p>The Apache Software Foundation (ASF) and our many Apache projects
welcome all
-participants who are willing to respect our community guidelines. There are
+participants. Before you begin, it is important to review and respect our
community guidelines. There are
many behavior or etiquette guides for online communities out there; we have a
few
Apache-specific tips below.</p>
<h1 id="coc">Code of Conduct</h1>
@@ -209,62 +209,45 @@ websites, IRC, and the like. Apache projects are made up
of volunteers, and
we work to ensure that all productive contributions are welcomed. Every
Apache PMC is expected to ensure their project’s lists show
proper behavior.</p>
-<h1 id="worldwide">Distributed, Archived, Worldwide Online Communities</h1>
-<p>Apache projects are made up of communities of volunteers from around the
-world. When you are sending email to an Apache project mailing list, there may
-be software developers in this country, marketing managers in that country, and
-homemakers in another country reading your email. They will be reading your
-mail at all hours of the day, at work, at home, and on the go. If you
-want a response to your questions or suggestions, be sure to be polite and
-sensible when writing.</p>
-<p>There are many amazing people helping out on Apache project mailing
-lists - but they are all volunteers. Being respectful of the time and
-culture of others on the list is a key start to making productive
contributions.</p>
-<h1 id="member">One Member’s Participation Guidelines</h1>
+<h1 id="member">Guidelines for Conduct and Etiquette</h1>
<p>The ASF as a corporation is run by several hundred Members, who have deep
and lasting experience
in helping to build and run long-term, successful open source projects here
-at Apache. This is just one member’s take on how to approach
-communicating in any particular Apache project.</p>
-<p><strong>Some General Guidelines</strong></p>
+at Apache. Below are some guidelines to help you communicate with other
volunteers, and get the most out of your communication experience.</p>
+<p><strong>General Communication Guidelines</strong></p>
<ul>
<li>
-<p>Assume that the other party agrees more than disagrees with you. We
-tend to leave out agreements and focus on differences. Sometime this is
-forgotten and escalation becomes absurd for no rational reason.</p>
+<p>Use a thoughtful, respectful tone to communicate your thoughts. Remember,
text is difficult to interpret. There are no body language or voice tones to
help interpret the messenger’s intent. Remember that the person on the
other side of your communication is also a human deserving of understanding and
+respect.</p>
</li>
<li>
-<p>When in doubt, assume that you are interpreting the message wrongly
-and kindly ask for verification that you understood a particular topic
well.</p>
+<p>If you agree with someone, let them know. If you disagree, let them know as
well. Positive and negative feedback are both necessary. Positive
+feedback will help others feel more confident in their ideas, as well as
ensure they know they’re on the right track. Negative feedback, given in
a
+respectable tone, will help to guide the messenger toward a more productive
solution.</p>
</li>
<li>
-<p>When writing, assume that every sentence will be misinterpreted.
-Review and try to reformulate to be as clear as possible.</p>
+<p>Avoid idiomatic and metaphoric language. At the ASF, we have thousands of
volunteers that speak different languages. To avoid miscommunication, it
+is best to avoid this type of language in favor of clear, direct
statements.</p>
</li>
<li>
-<p>Use a submissive tone in all writing. Instead of the strong “In my
-opinion, we must…” or the quite neutral “I think we
should…", try to
-use “Maybe we should consider…” or “Another idea that
we could…”</p>
+<p>Be patient when waiting for responses. Because the ASF is an international
community, there may be some delays in response time. We call these
+“asynchronous responders.” We understand that it can be difficult
and frustrating to wait, but please give these asynchronous responders time to
read
+and address your message. The ASF strives to respond to all messages (email,
slack, etc.) in a timely manner.</p>
</li>
<li>
-<p>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.</p>
+<p>Dealing with Conflict and miscommunication: Here at the ASF, we strive to
make everyone feel welcome and wanted in their roles. With that said, we
+also understand that miscommunications happen, especially in text. If you are
sent a message that you don’t understand, or feel uncomfortable with, a
+good first step would be to ask for clarification. Don’t be afraid to
ask specific questions. Chances are, the person you’re communicating
with has been
+in your position before, and will understand.</p>
</li>
<li>
-<p>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.</p>
+<p>Be forgiving and accept different priorities: Everyone that works on ASF
projects is passsionate about their work, and we love and welcome that
+passion and hope you will bring your own passion to your projects. Please
remember, the ASF currently has over 300 projects, each with their own project
+priorities. If your priorities seem at odds with others, remember that
compromise is essential to progress. Work with the other person to come up
with a
+compromise that takes all project’s priorities into account.</p>
</li>
<li>
-<p>Remember that everyone works on Apache projects as a volunteer.
-People have jobs and lives outside of their Apache projects, and may need
-extra time to even read messages on the list before they are ready to respond.
Be patient.</p>
+<p>Note: Foul, derogaroty, or divisive language in any form, up to and
including threats, harassment, and discriminatory language, is strongly
+prohibited.</p>
</li>
</ul>
<p><strong>Most communities at Apache consists of level-headed, reasonable
people</strong> who
diff --git a/content/contributors/index.xml b/content/contributors/index.xml
index 2c3ce5c..0903752 100644
--- a/content/contributors/index.xml
+++ b/content/contributors/index.xml
@@ -16,7 +16,7 @@
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/contributors/etiquette.html</guid>
- <description>The Apache Software Foundation (ASF) and our many Apache
projects welcome all participants who are willing to respect our community
guidelines. There are many behavior or etiquette guides for online communities
out there; we have a few Apache-specific tips below.
+ <description>The Apache Software Foundation (ASF) and our many Apache
projects welcome all participants. Before you begin, it is important to review
and respect our community guidelines. There are many behavior or etiquette
guides for online communities out there; we have a few Apache-specific tips
below.
Code of Conduct The ASF has adopted a Code of Conduct which covers
interactions in all the online spaces that Apache projects use - email, issue
trackers, wikis, websites, IRC, and the like.</description>
</item>
diff --git a/content/index.xml b/content/index.xml
index 80f7874..ddb857a 100644
--- a/content/index.xml
+++ b/content/index.xml
@@ -37,7 +37,7 @@ Overview The goals of this maturity model are to describe how
Apache projects op
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/contributors/etiquette.html</guid>
- <description>The Apache Software Foundation (ASF) and our many Apache
projects welcome all participants who are willing to respect our community
guidelines. There are many behavior or etiquette guides for online communities
out there; we have a few Apache-specific tips below.
+ <description>The Apache Software Foundation (ASF) and our many Apache
projects welcome all participants. Before you begin, it is important to review
and respect our community guidelines. There are many behavior or etiquette
guides for online communities out there; we have a few Apache-specific tips
below.
Code of Conduct The ASF has adopted a Code of Conduct which covers
interactions in all the online spaces that Apache projects use - email, issue
trackers, wikis, websites, IRC, and the like.</description>
</item>
diff --git a/content/sitemap.xml b/content/sitemap.xml
index c5a4239..e5ed8bf 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -24,7 +24,7 @@
<url>
<loc>https://community.apache.org/contributors/etiquette.html</loc>
- <lastmod>2022-02-20T11:26:22-04:00</lastmod>
+ <lastmod>2023-02-13T12:54:55-06:00</lastmod>
</url>
<url>
@@ -119,7 +119,7 @@
<url>
<loc>https://community.apache.org/contributors.html</loc>
- <lastmod>2022-02-20T11:26:22-04:00</lastmod>
+ <lastmod>2023-02-13T12:54:55-06:00</lastmod>
</url>
<url>
![https://community.apache.org/images/aceu19_1.jpg"/](https://community.apache.org/images/aceu19_1.jpg"/){kind=link}