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 253170c Updated asf-site from main at
c7b9109f7757065d71be18dc0c70f4c26be46059
253170c is described below
commit 253170c84e9b1465df63388cfb6107b068a98c94
Author: jenkins <bui...@apache.org>
AuthorDate: Sat Oct 7 15:37:42 2023 +0000
Updated asf-site from main at c7b9109f7757065d71be18dc0c70f4c26be46059
Built from
https://ci-builds.apache.org/job/Community%20Development/job/site/job/main/68/
---
content/_pagefind/fragment/en_38dce0f.pf_fragment | Bin 0 -> 4323 bytes
content/_pagefind/fragment/en_5e86da8.pf_fragment | Bin 3434 -> 0 bytes
content/_pagefind/index/en_1795bd2.pf_index | Bin 0 -> 36493 bytes
content/_pagefind/index/en_20bb514.pf_index | Bin 36437 -> 0 bytes
content/_pagefind/index/en_29a8f9d.pf_index | Bin 36604 -> 0 bytes
content/_pagefind/index/en_4b9a1a2.pf_index | Bin 41714 -> 0 bytes
content/_pagefind/index/en_54e6357.pf_index | Bin 0 -> 41892 bytes
content/_pagefind/index/en_639297b.pf_index | Bin 0 -> 422 bytes
content/_pagefind/index/en_6a40379.pf_index | Bin 0 -> 36555 bytes
content/_pagefind/index/en_6ba4e2c.pf_index | Bin 0 -> 36727 bytes
content/_pagefind/index/en_a4e34c8.pf_index | Bin 36330 -> 0 bytes
content/_pagefind/index/en_be89d94.pf_index | Bin 39082 -> 0 bytes
content/_pagefind/index/en_ff545af.pf_index | Bin 0 -> 39225 bytes
content/_pagefind/pagefind-entry.json | 2 +-
content/_pagefind/pagefind.en_e1dacce0b9.pf_meta | Bin 1067 -> 0 bytes
content/_pagefind/pagefind.en_f5d18062db.pf_meta | Bin 0 -> 1085 bytes
content/contributors/mailing-lists.html | 60 +++++++++++++++++-----
17 files changed, 49 insertions(+), 13 deletions(-)
diff --git a/content/_pagefind/fragment/en_38dce0f.pf_fragment
b/content/_pagefind/fragment/en_38dce0f.pf_fragment
new file mode 100644
index 0000000..83da7e7
Binary files /dev/null and b/content/_pagefind/fragment/en_38dce0f.pf_fragment
differ
diff --git a/content/_pagefind/fragment/en_5e86da8.pf_fragment
b/content/_pagefind/fragment/en_5e86da8.pf_fragment
deleted file mode 100644
index d7c37b8..0000000
Binary files a/content/_pagefind/fragment/en_5e86da8.pf_fragment and /dev/null
differ
diff --git a/content/_pagefind/index/en_1795bd2.pf_index
b/content/_pagefind/index/en_1795bd2.pf_index
new file mode 100644
index 0000000..93d48e0
Binary files /dev/null and b/content/_pagefind/index/en_1795bd2.pf_index differ
diff --git a/content/_pagefind/index/en_20bb514.pf_index
b/content/_pagefind/index/en_20bb514.pf_index
deleted file mode 100644
index 62efb23..0000000
Binary files a/content/_pagefind/index/en_20bb514.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_29a8f9d.pf_index
b/content/_pagefind/index/en_29a8f9d.pf_index
deleted file mode 100644
index 09afd4d..0000000
Binary files a/content/_pagefind/index/en_29a8f9d.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_4b9a1a2.pf_index
b/content/_pagefind/index/en_4b9a1a2.pf_index
deleted file mode 100644
index 2ed7c3b..0000000
Binary files a/content/_pagefind/index/en_4b9a1a2.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_54e6357.pf_index
b/content/_pagefind/index/en_54e6357.pf_index
new file mode 100644
index 0000000..9664af9
Binary files /dev/null and b/content/_pagefind/index/en_54e6357.pf_index differ
diff --git a/content/_pagefind/index/en_639297b.pf_index
b/content/_pagefind/index/en_639297b.pf_index
new file mode 100644
index 0000000..77d5d9e
Binary files /dev/null and b/content/_pagefind/index/en_639297b.pf_index differ
diff --git a/content/_pagefind/index/en_6a40379.pf_index
b/content/_pagefind/index/en_6a40379.pf_index
new file mode 100644
index 0000000..c35946b
Binary files /dev/null and b/content/_pagefind/index/en_6a40379.pf_index differ
diff --git a/content/_pagefind/index/en_6ba4e2c.pf_index
b/content/_pagefind/index/en_6ba4e2c.pf_index
new file mode 100644
index 0000000..1d2ea31
Binary files /dev/null and b/content/_pagefind/index/en_6ba4e2c.pf_index differ
diff --git a/content/_pagefind/index/en_a4e34c8.pf_index
b/content/_pagefind/index/en_a4e34c8.pf_index
deleted file mode 100644
index d911cb1..0000000
Binary files a/content/_pagefind/index/en_a4e34c8.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_be89d94.pf_index
b/content/_pagefind/index/en_be89d94.pf_index
deleted file mode 100644
index 339dcd8..0000000
Binary files a/content/_pagefind/index/en_be89d94.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_ff545af.pf_index
b/content/_pagefind/index/en_ff545af.pf_index
new file mode 100644
index 0000000..e611315
Binary files /dev/null and b/content/_pagefind/index/en_ff545af.pf_index differ
diff --git a/content/_pagefind/pagefind-entry.json
b/content/_pagefind/pagefind-entry.json
index fb737dd..7150398 100644
--- a/content/_pagefind/pagefind-entry.json
+++ b/content/_pagefind/pagefind-entry.json
@@ -1 +1 @@
-{"version":"0.12.0","languages":{"en":{"hash":"en_e1dacce0b9","wasm":"en","page_count":130}}}
\ No newline at end of file
+{"version":"0.12.0","languages":{"en":{"hash":"en_f5d18062db","wasm":"en","page_count":130}}}
\ No newline at end of file
diff --git a/content/_pagefind/pagefind.en_e1dacce0b9.pf_meta
b/content/_pagefind/pagefind.en_e1dacce0b9.pf_meta
deleted file mode 100644
index 4316efc..0000000
Binary files a/content/_pagefind/pagefind.en_e1dacce0b9.pf_meta and /dev/null
differ
diff --git a/content/_pagefind/pagefind.en_f5d18062db.pf_meta
b/content/_pagefind/pagefind.en_f5d18062db.pf_meta
new file mode 100644
index 0000000..a9a066a
Binary files /dev/null and b/content/_pagefind/pagefind.en_f5d18062db.pf_meta
differ
diff --git a/content/contributors/mailing-lists.html
b/content/contributors/mailing-lists.html
index 5ec05b9..0db919b 100644
--- a/content/contributors/mailing-lists.html
+++ b/content/contributors/mailing-lists.html
@@ -224,7 +224,8 @@ on a level field, regardless of time zone or availability,
whereas
synchronous communication platforms (IRC, Slack, Discord, etc.) benefit
only those who are online, and in the channel, at the time of the
conversation.</p>
-<p>Mailing lists also allow archiving, so that decisions can be understood
+<p>Mailing lists are also <a href="https://lists.apache.org/";>permanently and
publicly archived</a>,
+so that decisions can be understood
by people who were not there at the time - what was decided, why, and by
whom - even years after the fact.</p>
<p>Synchronous communication platforms are great for end-user support,
@@ -236,14 +237,49 @@ to the mailing list so that the whole community can
participate.</p>
<p>This is why we say, at the ASF, <strong>If it didn’t happen on the
mailing
list, it didn’t happen.</strong></p>
<h2 id="mailing-list-etiquette">Mailing list etiquette <a class="headerlink"
title="Permalink" href="#mailing-list-etiquette">¶</a></h2>
-<p><em>To Be Written</em></p>
-<ul>
-<li>Meaningful subject lines</li>
-<li>Inline vs top-posting</li>
-<li>HTML and “rich text” messages</li>
-<li>Clear language, use of colloquialisms and metaphor, etc. (writing for a
-diverse audience)</li>
-</ul>
+<p>What you send to ASF mailing lists is <a
href="https://lists.apache.org/";>archived, publicly, forever</a>. But
+that’s not the only reason for observing basic email etiquette. We
+expect you to conduct yourself politely on our mailing lists, because
+this is where we work, communicate, and build community. Here’s a few
+tips. See also <a
href="https://community.apache.org/contributors/etiquette.html";>general
etiquette tips</a>.</p>
+<h3 id="meaningful-subject-lines">Meaningful subject lines <a
class="headerlink" title="Permalink"
href="#meaningful-subject-lines">¶</a></h3>
+<p>Your subject line largely determines whether anyone reads what you
+write. Try to summarize the topic that you wish to discuss as concisely
+as possible.</p>
+<p>If an email thread starts to diverge <em>substantially</em> from the
original topic, change the
+subject line to reflect the direction that the thread has taken.</p>
+<h3 id="inline-vs-top-posting">Inline vs top-posting <a class="headerlink"
title="Permalink" href="#inline-vs-top-posting">¶</a></h3>
+<p>Most modern email clients default to top-posting - that is, putting the
+entire reply to a message above the quoted body of the message to which
+you are preferring.</p>
+<p>We encourage you, instead, to respond inline - that is, put each
+response after the quoted paragraph to which you are responding, so that
+the resulting message reads like a conversation. This makes it very
+clear which points you are responding to. You can then also delete the
+portions of the message that you are not responding to at all, making
+the resulting message self-contained, and not forcing everyone to
+re-read everything that has gone before in order to understand your
+response.</p>
+<h3 id="html-and-rich-text-messages">HTML and “rich text” messages
<a class="headerlink" title="Permalink"
href="#html-and-rich-text-messages">¶</a></h3>
+<p>ASF communities tend to prefer plaintext email messages, rather than
+HTML or other so-called “rich text”. This makes messages more
+consistently readable on multiple devices, multiple operating systems,
+and multiple screen sizes. It also makes computer-consumption of these
+message easier, for the purpose of translation, screen readers, and
+other automatic ingestion and processing.</p>
+<h3 id="colloquialisms">Colloquialisms <a class="headerlink" title="Permalink"
href="#colloquialisms">¶</a></h3>
+<p>When you speak to your friends and colleagues, you can, and
+usually do, use idioms, slang, colloquialisms, metaphors, and other
+locally-understood figures of speech.</p>
+<p>But when you’re writing to an open source mailing list, your audience
is
+much more diverse, including people all around the world, who are likely
+to not understand these phrases.</p>
+<p>Write clearly, plainly, and without resorting to figures of speech,
+wherever possible. If you use slang or a metaphor, consider linking to a
+definition or explanation. Remember that not everyone reading your
+message speaks your language natively. Including them in the
+conversation is essential to collaboration.</p>
+<p>ASF mailing lists default to English, unless specified otherwise.</p>
<h2 id="mailing-list-configuration">Mailing list configuration <a
class="headerlink" title="Permalink"
href="#mailing-list-configuration">¶</a></h2>
<p>Modern software development tools, including GitHub, your various ticket
trackers, and CI tools, generate a lot of email. This can make your
@@ -364,16 +400,16 @@ If your project is a single-repo project (or for the
other repositories GitHub i
delete_comment_discussion: "Deleted a comment: Discussion
{repository}: {title}"
</code></pre><h3 id="conclusion">Conclusion <a class="headerlink"
title="Permalink" href="#conclusion">¶</a></h3>
<p>The custom templates help make the GitHub content readable on your
-mailinglist it will therefore not feel as overwhelming as with the
+mailinglist. It will therefore not feel as overwhelming as with the
defaults. Moving dependabot to the commits lists, helped reduce the
content with very little information.</p>
<p>We would strongly encourage projects to keep as much of the discussions
on their main mailingslist. If it’s a larger project and still the
-volumne is so high, it’s overwhelming people, think about directing
+volume is so high that it’s overwhelming people, think about directing
some of the content to other lists.</p>
<p>Simply directing all GitHub content to dedicated mailing lists or
lists nobody reads doesn’t help with keeping the community knowledge
-available. Even if it’s “on the list” someweere, it
doesn’t really
+available. Even if it’s “on the list” somewhere, it
doesn’t really
serve the reasoning behind the “If if didn’t happen on the list,
it didn’t happen”.</p>
