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 06d3813d Updated asf-site from main at 
15ac5a90d11b23e3965fd8b24c87fa3741ed3252
06d3813d is described below

commit 06d3813d067ca54226bbe95bb19932d92ba0cccb
Author: jenkins <[email protected]>
AuthorDate: Tue Oct 22 13:39:03 2024 +0000

    Updated asf-site from main at 15ac5a90d11b23e3965fd8b24c87fa3741ed3252
    
    Built from 
https://ci-builds.apache.org/job/Community%20Development/job/site/job/main/145/
---
 content/_pagefind/fragment/en_181c19d.pf_fragment | Bin 0 -> 2009 bytes
 content/_pagefind/fragment/en_24e2cce.pf_fragment | Bin 0 -> 2484 bytes
 content/_pagefind/fragment/en_2a2a624.pf_fragment | Bin 0 -> 2615 bytes
 content/_pagefind/fragment/en_4d122e2.pf_fragment | Bin 2547 -> 0 bytes
 content/_pagefind/fragment/en_4e21bf1.pf_fragment | Bin 1689 -> 0 bytes
 content/_pagefind/fragment/en_4fbda78.pf_fragment | Bin 0 -> 2660 bytes
 content/_pagefind/fragment/en_68e2a1b.pf_fragment | Bin 0 -> 2066 bytes
 content/_pagefind/fragment/en_6d2944a.pf_fragment | Bin 2470 -> 0 bytes
 content/_pagefind/fragment/en_7a1d9fb.pf_fragment | Bin 2600 -> 0 bytes
 content/_pagefind/fragment/en_882c1bf.pf_fragment | Bin 2075 -> 0 bytes
 content/_pagefind/fragment/en_8fdfead.pf_fragment | Bin 1994 -> 0 bytes
 content/_pagefind/fragment/en_aa29e39.pf_fragment | Bin 4802 -> 0 bytes
 content/_pagefind/fragment/en_be5a7a8.pf_fragment | Bin 0 -> 4817 bytes
 content/_pagefind/fragment/en_ca9f9e5.pf_fragment | Bin 0 -> 1705 bytes
 content/_pagefind/fragment/en_cee5dac.pf_fragment | Bin 0 -> 2550 bytes
 content/_pagefind/fragment/en_d8e1ff3.pf_fragment | Bin 2664 -> 0 bytes
 content/_pagefind/index/en_1d75d0c.pf_index       | Bin 0 -> 31216 bytes
 content/_pagefind/index/en_24cc8b7.pf_index       | Bin 0 -> 27590 bytes
 content/_pagefind/index/en_2586531.pf_index       | Bin 31813 -> 0 bytes
 content/_pagefind/index/en_2e4ac61.pf_index       | Bin 27722 -> 0 bytes
 content/_pagefind/index/en_376f43b.pf_index       | Bin 28799 -> 0 bytes
 content/_pagefind/index/en_429825c.pf_index       | Bin 0 -> 29998 bytes
 content/_pagefind/index/en_4a776e6.pf_index       | Bin 30454 -> 0 bytes
 content/_pagefind/index/en_677b61a.pf_index       | Bin 32894 -> 0 bytes
 content/_pagefind/index/en_8945cf1.pf_index       | Bin 0 -> 29837 bytes
 content/_pagefind/index/en_a5f1f59.pf_index       | Bin 31203 -> 0 bytes
 content/_pagefind/index/en_b07cb4b.pf_index       | Bin 29804 -> 0 bytes
 content/_pagefind/index/en_b22ea98.pf_index       | Bin 0 -> 30412 bytes
 content/_pagefind/index/en_bd3aa8a.pf_index       | Bin 29935 -> 0 bytes
 content/_pagefind/index/en_c339f53.pf_index       | Bin 0 -> 32894 bytes
 content/_pagefind/index/en_e431bfa.pf_index       | Bin 0 -> 31796 bytes
 content/_pagefind/index/en_f1bedf1.pf_index       | Bin 0 -> 28771 bytes
 content/_pagefind/pagefind-entry.json             |   2 +-
 content/_pagefind/pagefind.en_90ecbf60d0.pf_meta  | Bin 1318 -> 0 bytes
 content/_pagefind/pagefind.en_f8e5152286.pf_meta  | Bin 0 -> 1322 bytes
 content/contactpoints.html                        |  15 ++++++++++++--
 content/contributor-ladder.html                   |  22 +++++++++++---------
 content/contributors/index.xml                    |   2 +-
 content/contributors/mailing-lists.html           |  22 +++++++++++++++++++-
 content/index.xml                                 |   9 ++++----
 content/pmc/adding-committers.html                |   7 +++++++
 content/pmc/chair.html                            |   9 ++++++++
 content/pmc/community-growth.html                 |  13 +++++++++++-
 content/pmc/index.html                            |  24 ++++++++++++----------
 content/pmc/index.xml                             |   2 +-
 content/pmc/responsibilities.html                 |  16 ++++++++-------
 46 files changed, 103 insertions(+), 40 deletions(-)

diff --git a/content/_pagefind/fragment/en_181c19d.pf_fragment 
b/content/_pagefind/fragment/en_181c19d.pf_fragment
new file mode 100644
index 00000000..300741b4
Binary files /dev/null and b/content/_pagefind/fragment/en_181c19d.pf_fragment 
differ
diff --git a/content/_pagefind/fragment/en_24e2cce.pf_fragment 
b/content/_pagefind/fragment/en_24e2cce.pf_fragment
new file mode 100644
index 00000000..a832847a
Binary files /dev/null and b/content/_pagefind/fragment/en_24e2cce.pf_fragment 
differ
diff --git a/content/_pagefind/fragment/en_2a2a624.pf_fragment 
b/content/_pagefind/fragment/en_2a2a624.pf_fragment
new file mode 100644
index 00000000..9b8ab5c4
Binary files /dev/null and b/content/_pagefind/fragment/en_2a2a624.pf_fragment 
differ
diff --git a/content/_pagefind/fragment/en_4d122e2.pf_fragment 
b/content/_pagefind/fragment/en_4d122e2.pf_fragment
deleted file mode 100644
index 4744a7ef..00000000
Binary files a/content/_pagefind/fragment/en_4d122e2.pf_fragment and /dev/null 
differ
diff --git a/content/_pagefind/fragment/en_4e21bf1.pf_fragment 
b/content/_pagefind/fragment/en_4e21bf1.pf_fragment
deleted file mode 100644
index fd5440e5..00000000
Binary files a/content/_pagefind/fragment/en_4e21bf1.pf_fragment and /dev/null 
differ
diff --git a/content/_pagefind/fragment/en_4fbda78.pf_fragment 
b/content/_pagefind/fragment/en_4fbda78.pf_fragment
new file mode 100644
index 00000000..3110e7ca
Binary files /dev/null and b/content/_pagefind/fragment/en_4fbda78.pf_fragment 
differ
diff --git a/content/_pagefind/fragment/en_68e2a1b.pf_fragment 
b/content/_pagefind/fragment/en_68e2a1b.pf_fragment
new file mode 100644
index 00000000..0f184781
Binary files /dev/null and b/content/_pagefind/fragment/en_68e2a1b.pf_fragment 
differ
diff --git a/content/_pagefind/fragment/en_6d2944a.pf_fragment 
b/content/_pagefind/fragment/en_6d2944a.pf_fragment
deleted file mode 100644
index b0399128..00000000
Binary files a/content/_pagefind/fragment/en_6d2944a.pf_fragment and /dev/null 
differ
diff --git a/content/_pagefind/fragment/en_7a1d9fb.pf_fragment 
b/content/_pagefind/fragment/en_7a1d9fb.pf_fragment
deleted file mode 100644
index 7cbdd33e..00000000
Binary files a/content/_pagefind/fragment/en_7a1d9fb.pf_fragment and /dev/null 
differ
diff --git a/content/_pagefind/fragment/en_882c1bf.pf_fragment 
b/content/_pagefind/fragment/en_882c1bf.pf_fragment
deleted file mode 100644
index 1459d770..00000000
Binary files a/content/_pagefind/fragment/en_882c1bf.pf_fragment and /dev/null 
differ
diff --git a/content/_pagefind/fragment/en_8fdfead.pf_fragment 
b/content/_pagefind/fragment/en_8fdfead.pf_fragment
deleted file mode 100644
index 612ef33d..00000000
Binary files a/content/_pagefind/fragment/en_8fdfead.pf_fragment and /dev/null 
differ
diff --git a/content/_pagefind/fragment/en_aa29e39.pf_fragment 
b/content/_pagefind/fragment/en_aa29e39.pf_fragment
deleted file mode 100644
index 4c334db8..00000000
Binary files a/content/_pagefind/fragment/en_aa29e39.pf_fragment and /dev/null 
differ
diff --git a/content/_pagefind/fragment/en_be5a7a8.pf_fragment 
b/content/_pagefind/fragment/en_be5a7a8.pf_fragment
new file mode 100644
index 00000000..012151de
Binary files /dev/null and b/content/_pagefind/fragment/en_be5a7a8.pf_fragment 
differ
diff --git a/content/_pagefind/fragment/en_ca9f9e5.pf_fragment 
b/content/_pagefind/fragment/en_ca9f9e5.pf_fragment
new file mode 100644
index 00000000..b39aa364
Binary files /dev/null and b/content/_pagefind/fragment/en_ca9f9e5.pf_fragment 
differ
diff --git a/content/_pagefind/fragment/en_cee5dac.pf_fragment 
b/content/_pagefind/fragment/en_cee5dac.pf_fragment
new file mode 100644
index 00000000..70aed330
Binary files /dev/null and b/content/_pagefind/fragment/en_cee5dac.pf_fragment 
differ
diff --git a/content/_pagefind/fragment/en_d8e1ff3.pf_fragment 
b/content/_pagefind/fragment/en_d8e1ff3.pf_fragment
deleted file mode 100644
index 50a1a8d1..00000000
Binary files a/content/_pagefind/fragment/en_d8e1ff3.pf_fragment and /dev/null 
differ
diff --git a/content/_pagefind/index/en_1d75d0c.pf_index 
b/content/_pagefind/index/en_1d75d0c.pf_index
new file mode 100644
index 00000000..69b4a0c9
Binary files /dev/null and b/content/_pagefind/index/en_1d75d0c.pf_index differ
diff --git a/content/_pagefind/index/en_24cc8b7.pf_index 
b/content/_pagefind/index/en_24cc8b7.pf_index
new file mode 100644
index 00000000..cbf3af09
Binary files /dev/null and b/content/_pagefind/index/en_24cc8b7.pf_index differ
diff --git a/content/_pagefind/index/en_2586531.pf_index 
b/content/_pagefind/index/en_2586531.pf_index
deleted file mode 100644
index 0f91afa1..00000000
Binary files a/content/_pagefind/index/en_2586531.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_2e4ac61.pf_index 
b/content/_pagefind/index/en_2e4ac61.pf_index
deleted file mode 100644
index 75510981..00000000
Binary files a/content/_pagefind/index/en_2e4ac61.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_376f43b.pf_index 
b/content/_pagefind/index/en_376f43b.pf_index
deleted file mode 100644
index fc82a6dc..00000000
Binary files a/content/_pagefind/index/en_376f43b.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_429825c.pf_index 
b/content/_pagefind/index/en_429825c.pf_index
new file mode 100644
index 00000000..7bda7b79
Binary files /dev/null and b/content/_pagefind/index/en_429825c.pf_index differ
diff --git a/content/_pagefind/index/en_4a776e6.pf_index 
b/content/_pagefind/index/en_4a776e6.pf_index
deleted file mode 100644
index c4ba71fc..00000000
Binary files a/content/_pagefind/index/en_4a776e6.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_677b61a.pf_index 
b/content/_pagefind/index/en_677b61a.pf_index
deleted file mode 100644
index 63226ccd..00000000
Binary files a/content/_pagefind/index/en_677b61a.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_8945cf1.pf_index 
b/content/_pagefind/index/en_8945cf1.pf_index
new file mode 100644
index 00000000..a5de2d14
Binary files /dev/null and b/content/_pagefind/index/en_8945cf1.pf_index differ
diff --git a/content/_pagefind/index/en_a5f1f59.pf_index 
b/content/_pagefind/index/en_a5f1f59.pf_index
deleted file mode 100644
index ecd06a25..00000000
Binary files a/content/_pagefind/index/en_a5f1f59.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_b07cb4b.pf_index 
b/content/_pagefind/index/en_b07cb4b.pf_index
deleted file mode 100644
index ca050d60..00000000
Binary files a/content/_pagefind/index/en_b07cb4b.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_b22ea98.pf_index 
b/content/_pagefind/index/en_b22ea98.pf_index
new file mode 100644
index 00000000..5dbd6245
Binary files /dev/null and b/content/_pagefind/index/en_b22ea98.pf_index differ
diff --git a/content/_pagefind/index/en_bd3aa8a.pf_index 
b/content/_pagefind/index/en_bd3aa8a.pf_index
deleted file mode 100644
index 36d0eec3..00000000
Binary files a/content/_pagefind/index/en_bd3aa8a.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_c339f53.pf_index 
b/content/_pagefind/index/en_c339f53.pf_index
new file mode 100644
index 00000000..55bb67b6
Binary files /dev/null and b/content/_pagefind/index/en_c339f53.pf_index differ
diff --git a/content/_pagefind/index/en_e431bfa.pf_index 
b/content/_pagefind/index/en_e431bfa.pf_index
new file mode 100644
index 00000000..d80b8f54
Binary files /dev/null and b/content/_pagefind/index/en_e431bfa.pf_index differ
diff --git a/content/_pagefind/index/en_f1bedf1.pf_index 
b/content/_pagefind/index/en_f1bedf1.pf_index
new file mode 100644
index 00000000..965ad52d
Binary files /dev/null and b/content/_pagefind/index/en_f1bedf1.pf_index differ
diff --git a/content/_pagefind/pagefind-entry.json 
b/content/_pagefind/pagefind-entry.json
index a47d2737..7af8e7cd 100644
--- a/content/_pagefind/pagefind-entry.json
+++ b/content/_pagefind/pagefind-entry.json
@@ -1 +1 @@
-{"version":"1.0.3","languages":{"en":{"hash":"en_90ecbf60d0","wasm":"en","page_count":148}}}
\ No newline at end of file
+{"version":"1.0.3","languages":{"en":{"hash":"en_f8e5152286","wasm":"en","page_count":148}}}
\ No newline at end of file
diff --git a/content/_pagefind/pagefind.en_90ecbf60d0.pf_meta 
b/content/_pagefind/pagefind.en_90ecbf60d0.pf_meta
deleted file mode 100644
index 82b42add..00000000
Binary files a/content/_pagefind/pagefind.en_90ecbf60d0.pf_meta and /dev/null 
differ
diff --git a/content/_pagefind/pagefind.en_f8e5152286.pf_meta 
b/content/_pagefind/pagefind.en_f8e5152286.pf_meta
new file mode 100644
index 00000000..a879929d
Binary files /dev/null and b/content/_pagefind/pagefind.en_f8e5152286.pf_meta 
differ
diff --git a/content/contactpoints.html b/content/contactpoints.html
index 1f5e60bd..5c39de75 100644
--- a/content/contactpoints.html
+++ b/content/contactpoints.html
@@ -9,8 +9,7 @@
   <meta property="og:title" content="Contact points" />
 <meta property="og:description" content="If you have a question about anything 
Apache, the ComDev project is here to help.
 To help us help you, try to direct your question to the right mailing list - 
our volunteer committers do all their work on mailing lists.
-Community Questions &para; Email questions about community or issues across 
multiple Apache projects to [email protected] - or see our detailed 
Mailing List How To page.
-Technical Questions &para; If you have a technical question about this 
website, or one of the tools that the ComDev project builds, email us at 
dev@community." />
+Trademarks Publicity and Marketing Fundraising and Sponsorship Legal Other 
Community Questions &para; Email questions about community or issues across 
multiple Apache projects to [email protected] - or see our detailed 
Mailing List How To page." />
 <meta property="og:type" content="article" />
 <meta property="og:url" 
content="https://community.apache.org/contactpoints.html"; /><meta 
property="og:image" 
content="https://community.apache.org/images/aceu19_1.jpg"/><meta 
property="article:section" content="" />
 
@@ -223,6 +222,18 @@ Technical Questions &para; If you have a technical 
question about this website,
        <p>If you have a question about anything Apache, the ComDev project is 
here to help.<br>
 To help us help you, try to direct your question to the right mailing list - 
our
 volunteer committers do all their work on mailing lists.</p>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#trademarks">Trademarks</a></li>
+    <li><a href="#publicity-and-marketing">Publicity and Marketing</a></li>
+    <li><a href="#fundraising-and-sponsorship">Fundraising and Sponsorship</a>
+      <ul>
+        <li><a href="#legal">Legal</a></li>
+        <li><a href="#other">Other</a></li>
+      </ul>
+    </li>
+  </ul>
+</nav>
 <h1 id="community-questions">Community Questions <a class="headerlink" 
title="Permalink" href="#community-questions">&para;</a></h1>
 <p>Email questions about community or issues across multiple Apache projects 
to <a 
href="mailto:[email protected]?subject=New-Contact-Question";>[email protected]</a>
 - or see our detailed <a href="//community.apache.org/lists.html">Mailing List 
How To</a> page.</p>
 <h1 id="technical-questions">Technical Questions <a class="headerlink" 
title="Permalink" href="#technical-questions">&para;</a></h1>
diff --git a/content/contributor-ladder.html b/content/contributor-ladder.html
index b2898cb4..52d21580 100644
--- a/content/contributor-ladder.html
+++ b/content/contributor-ladder.html
@@ -8,7 +8,7 @@
   <meta name="viewport" content="width=device-width, initial-scale=1, 
maximum-scale=1" />
   <meta property="og:title" content="ASF Contributor Ladder" />
 <meta property="og:description" content="Projects at the ASF offer a way to 
grow in your responsibilities in the project, from being a user, all the way up 
to being a maintainer of the project. While the specific details may look 
different from one project to another, the rungs of the ladder look mostly the 
same.
-User Contributor Committer PMC Member ASF Member Officers of the Foundation 
Board of Directors User &para; Everything that we do in an ASF project is for 
the user." />
+User Contributor Committer PMC Member Foundation Member Officers of the 
Foundation Board of Directors User &para; Everything that we do in an ASF 
project is for the user." />
 <meta property="og:type" content="article" />
 <meta property="og:url" 
content="https://community.apache.org/contributor-ladder.html"; /><meta 
property="og:image" 
content="https://community.apache.org/images/aceu19_1.jpg"/><meta 
property="article:section" content="" />
 
@@ -234,15 +234,17 @@ User Contributor Committer PMC Member ASF Member Officers 
of the Foundation Boar
 project, from being a user, all the way up to being a maintainer of the
 project. While the specific details may look different from one project
 to another, the rungs of the ladder look mostly the same.</p>
-<ul>
-<li><a href="#user">User</a></li>
-<li><a href="#contributor">Contributor</a></li>
-<li><a href="#committer">Committer</a></li>
-<li><a href="#pmc-member">PMC Member</a></li>
-<li><a href="#asf-member">ASF Member</a></li>
-<li><a href="#officers-of-the-foundation">Officers of the Foundation</a></li>
-<li><a href="#board-of-directors">Board of Directors</a></li>
-</ul>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#user">User</a></li>
+    <li><a href="#contributor">Contributor</a></li>
+    <li><a href="#committer">Committer</a></li>
+    <li><a href="#pmc-member">PMC Member</a></li>
+    <li><a href="#foundation-member">Foundation Member</a></li>
+    <li><a href="#officers-of-the-foundation">Officers of the 
Foundation</a></li>
+    <li><a href="#board-of-directors">Board of Directors</a></li>
+  </ul>
+</nav>
 <h2 id="user">User <a class="headerlink" title="Permalink" 
href="#user">&para;</a></h2>
 <p>Everything that we do in an ASF project is for the user. As a user of an
 Apache project, your responsibilities are just to enjoy the software.</p>
diff --git a/content/contributors/index.xml b/content/contributors/index.xml
index dc7753b5..13e03938 100644
--- a/content/contributors/index.xml
+++ b/content/contributors/index.xml
@@ -44,7 +44,7 @@ altay # speaker bdelacretaz # mentor, speaker cdutz # mentor, 
speaker clr # ment
       
       <guid>https://community.apache.org/contributors/mailing-lists.html</guid>
       <description>The ASF has a long tradition of using mailing lists as the 
primary communication format in projects. This is not merely because 
we&amp;rsquo;ve always done it that way, but is an intentional decision for the 
health and sustainability of our communities.
-Inclusion and transparency &amp;para; Mailing lists ensure that all members of 
the community can participate on a level field, regardless of time zone or 
availability, whereas synchronous communication platforms (IRC, Slack, Discord, 
etc.</description>
+Inclusion and transparency Mailing list etiquette Meaningful subject lines 
Inline vs top-posting HTML and &amp;ldquo;rich text&amp;rdquo; messages 
Colloquialisms Mailing list configuration Configuring where to send things 
Configuring the subject lines of the emails being sent Conclusion Inclusion and 
transparency &amp;para; Mailing lists ensure that all members of the community 
can participate on a level field, regardless of time zone or availability, 
whereas synchronous communication pl [...]
     </item>
     
   </channel>
diff --git a/content/contributors/mailing-lists.html 
b/content/contributors/mailing-lists.html
index 3f36a466..89c8ca67 100644
--- a/content/contributors/mailing-lists.html
+++ b/content/contributors/mailing-lists.html
@@ -8,7 +8,7 @@
   <meta name="viewport" content="width=device-width, initial-scale=1, 
maximum-scale=1" />
   <meta property="og:title" content="Mailing lists" />
 <meta property="og:description" content="The ASF has a long tradition of using 
mailing lists as the primary communication format in projects. This is not 
merely because we&rsquo;ve always done it that way, but is an intentional 
decision for the health and sustainability of our communities.
-Inclusion and transparency &para; Mailing lists ensure that all members of the 
community can participate on a level field, regardless of time zone or 
availability, whereas synchronous communication platforms (IRC, Slack, Discord, 
etc." />
+Inclusion and transparency Mailing list etiquette Meaningful subject lines 
Inline vs top-posting HTML and &ldquo;rich text&rdquo; messages Colloquialisms 
Mailing list configuration Configuring where to send things Configuring the 
subject lines of the emails being sent Conclusion Inclusion and transparency 
&para; Mailing lists ensure that all members of the community can participate 
on a level field, regardless of time zone or availability, whereas synchronous 
communication platforms (IRC [...]
 <meta property="og:type" content="article" />
 <meta property="og:url" 
content="https://community.apache.org/contributors/mailing-lists.html"; /><meta 
property="og:image" 
content="https://community.apache.org/images/aceu19_1.jpg"/><meta 
property="article:section" content="contributors" />
 
@@ -231,6 +231,26 @@ Inclusion and transparency &para; Mailing lists ensure 
that all members of the c
 communication format in projects. This is not merely because we&rsquo;ve
 always done it that way, but is an intentional decision for the health
 and sustainability of our communities.</p>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#inclusion-and-transparency">Inclusion and 
transparency</a></li>
+    <li><a href="#mailing-list-etiquette">Mailing list etiquette</a>
+      <ul>
+        <li><a href="#meaningful-subject-lines">Meaningful subject 
lines</a></li>
+        <li><a href="#inline-vs-top-posting">Inline vs top-posting</a></li>
+        <li><a href="#html-and-rich-text-messages">HTML and &ldquo;rich 
text&rdquo; messages</a></li>
+        <li><a href="#colloquialisms">Colloquialisms</a></li>
+      </ul>
+    </li>
+    <li><a href="#mailing-list-configuration">Mailing list configuration</a>
+      <ul>
+        <li><a href="#configuring-where-to-send-things">Configuring where to 
send things</a></li>
+        <li><a 
href="#configuring-the-subject-lines-of-the-emails-being-sent">Configuring the 
subject lines of the emails being sent</a></li>
+        <li><a href="#conclusion">Conclusion</a></li>
+      </ul>
+    </li>
+  </ul>
+</nav>
 <h2 id="inclusion-and-transparency">Inclusion and transparency <a 
class="headerlink" title="Permalink" 
href="#inclusion-and-transparency">&para;</a></h2>
 <p>Mailing lists ensure that all members of the community can participate
 on a level field, regardless of time zone or availability, whereas
diff --git a/content/index.xml b/content/index.xml
index a9937429..1060c17c 100644
--- a/content/index.xml
+++ b/content/index.xml
@@ -449,7 +449,7 @@ Code of Conduct &amp;para; The ASF has adopted a Code of 
Conduct which covers in
       
       <guid>https://community.apache.org/contributor-ladder.html</guid>
       <description>Projects at the ASF offer a way to grow in your 
responsibilities in the project, from being a user, all the way up to being a 
maintainer of the project. While the specific details may look different from 
one project to another, the rungs of the ladder look mostly the same.
-User Contributor Committer PMC Member ASF Member Officers of the Foundation 
Board of Directors User &amp;para; Everything that we do in an ASF project is 
for the user.</description>
+User Contributor Committer PMC Member Foundation Member Officers of the 
Foundation Board of Directors User &amp;para; Everything that we do in an ASF 
project is for the user.</description>
     </item>
     
     <item>
@@ -519,7 +519,7 @@ Board Resolution Creating the Apache Community Development 
Project Establish the
       
       <guid>https://community.apache.org/pmc/community-growth.html</guid>
       <description>Growing your project community takes work. This document 
makes practical suggestions of how to encourage people to get involved in your 
project.
-Publish a roadmap &amp;para; Volunteers can work on whatever they want, and so 
we have a tendency to not want to tell them what to work on. However, 
publishing a roadmap, or even a wishlist of features or improvements that are 
desired, can give people an idea of where they might be able to get 
involved.</description>
+Publish a roadmap Periodically publish the open issue list Clearly document 
contribution processes Publish your contributor ladder Engage with big users Be 
transparent about project risk Come talk to us Publish a roadmap &amp;para; 
Volunteers can work on whatever they want, and so we have a tendency to not 
want to tell them what to work on.</description>
     </item>
     
     <item>
@@ -540,8 +540,7 @@ The pages tagged with speakers or mentoring should provide 
the information that
       <guid>https://community.apache.org/contactpoints.html</guid>
       <description>If you have a question about anything Apache, the ComDev 
project is here to help.
 To help us help you, try to direct your question to the right mailing list - 
our volunteer committers do all their work on mailing lists.
-Community Questions &amp;para; Email questions about community or issues 
across multiple Apache projects to [email protected] - or see our 
detailed Mailing List How To page.
-Technical Questions &amp;para; If you have a technical question about this 
website, or one of the tools that the ComDev project builds, email us at 
dev@community.</description>
+Trademarks Publicity and Marketing Fundraising and Sponsorship Legal Other 
Community Questions &amp;para; Email questions about community or issues across 
multiple Apache projects to [email protected] - or see our detailed 
Mailing List How To page.</description>
     </item>
     
     <item>
@@ -635,7 +634,7 @@ Books &amp;para; Producing Open Source Software - by Karl 
Fogel Blog posts &amp;
       
       <guid>https://community.apache.org/contributors/mailing-lists.html</guid>
       <description>The ASF has a long tradition of using mailing lists as the 
primary communication format in projects. This is not merely because 
we&amp;rsquo;ve always done it that way, but is an intentional decision for the 
health and sustainability of our communities.
-Inclusion and transparency &amp;para; Mailing lists ensure that all members of 
the community can participate on a level field, regardless of time zone or 
availability, whereas synchronous communication platforms (IRC, Slack, Discord, 
etc.</description>
+Inclusion and transparency Mailing list etiquette Meaningful subject lines 
Inline vs top-posting HTML and &amp;ldquo;rich text&amp;rdquo; messages 
Colloquialisms Mailing list configuration Configuring where to send things 
Configuring the subject lines of the emails being sent Conclusion Inclusion and 
transparency &amp;para; Mailing lists ensure that all members of the community 
can participate on a level field, regardless of time zone or availability, 
whereas synchronous communication pl [...]
     </item>
     
     <item>
diff --git a/content/pmc/adding-committers.html 
b/content/pmc/adding-committers.html
index 032f3402..f7173515 100644
--- a/content/pmc/adding-committers.html
+++ b/content/pmc/adding-committers.html
@@ -234,6 +234,13 @@ This page discusses best practices in how to think about 
new committers.</p>
 <p>In addition to the mechanisms for adding committers, give some thought
 to <a href="/pmc/community-growth.html">practical steps you can take to 
attract new
 contributors</a>.</p>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#who-should-be-a-committer">Who should be a 
committer?</a></li>
+    <li><a href="#vote-process">Vote process</a></li>
+    <li><a href="#what-to-do-when-a-committer-is-elected">What to do when a 
committer is elected</a></li>
+  </ul>
+</nav>
 <h2 id="who-should-be-a-committer">Who should be a committer? <a 
class="headerlink" title="Permalink" 
href="#who-should-be-a-committer">&para;</a></h2>
 <p>Each project must decide what is the correct measure for inviting a new
 committer to their project. There are, however, several things that we
diff --git a/content/pmc/chair.html b/content/pmc/chair.html
index 9e90ea18..e5457424 100644
--- a/content/pmc/chair.html
+++ b/content/pmc/chair.html
@@ -233,6 +233,15 @@ usually a senior, well-respected member of the community, 
they are a
 peer, with a few additional duties.</p>
 <p>The Chair should be familiar with the <a 
href="https://www.apache.org/dev/pmc.html#chair";>assigned
 duties</a> of the role.</p>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#secretarial-duties">Secretarial duties</a></li>
+    <li><a href="#reporting">Reporting</a></li>
+    <li><a href="#moderating-discussion">Moderating discussion</a></li>
+    <li><a href="#selecting-a-new-chair">Selecting a new Chair</a></li>
+    <li><a href="#see-also">See also:</a></li>
+  </ul>
+</nav>
 <h2 id="secretarial-duties">Secretarial duties <a class="headerlink" 
title="Permalink" href="#secretarial-duties">&para;</a></h2>
 <p>The Chair is responsible for completing the necessary 
&ldquo;paperwork&rdquo; when
 new committers and PMC members are added.</p>
diff --git a/content/pmc/community-growth.html 
b/content/pmc/community-growth.html
index 4f55898c..5214e43e 100644
--- a/content/pmc/community-growth.html
+++ b/content/pmc/community-growth.html
@@ -8,7 +8,7 @@
   <meta name="viewport" content="width=device-width, initial-scale=1, 
maximum-scale=1" />
   <meta property="og:title" content="Community Growth" />
 <meta property="og:description" content="Growing your project community takes 
work. This document makes practical suggestions of how to encourage people to 
get involved in your project.
-Publish a roadmap &para; Volunteers can work on whatever they want, and so we 
have a tendency to not want to tell them what to work on. However, publishing a 
roadmap, or even a wishlist of features or improvements that are desired, can 
give people an idea of where they might be able to get involved." />
+Publish a roadmap Periodically publish the open issue list Clearly document 
contribution processes Publish your contributor ladder Engage with big users Be 
transparent about project risk Come talk to us Publish a roadmap &para; 
Volunteers can work on whatever they want, and so we have a tendency to not 
want to tell them what to work on." />
 <meta property="og:type" content="article" />
 <meta property="og:url" 
content="https://community.apache.org/pmc/community-growth.html"; /><meta 
property="og:image" 
content="https://community.apache.org/images/aceu19_1.jpg"/><meta 
property="article:section" content="pmc" />
 
@@ -229,6 +229,17 @@ Publish a roadmap &para; Volunteers can work on whatever 
they want, and so we ha
        <br><br>
        <p>Growing your project community takes work. This document makes 
practical
 suggestions of how to encourage people to get involved in your project.</p>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#publish-a-roadmap">Publish a roadmap</a></li>
+    <li><a href="#periodically-publish-the-open-issue-list">Periodically 
publish the open issue list</a></li>
+    <li><a href="#clearly-document-contribution-processes">Clearly document 
contribution processes</a></li>
+    <li><a href="#publish-your-contributor-ladder">Publish your contributor 
ladder</a></li>
+    <li><a href="#engage-with-big-users">Engage with big users</a></li>
+    <li><a href="#be-transparent-about-project-risk">Be transparent about 
project risk</a></li>
+    <li><a href="#come-talk-to-us">Come talk to us</a></li>
+  </ul>
+</nav>
 <h2 id="publish-a-roadmap">Publish a roadmap <a class="headerlink" 
title="Permalink" href="#publish-a-roadmap">&para;</a></h2>
 <p>Volunteers can work on whatever they want, and so we have a tendency to
 not want to tell them what to work on. However, publishing a roadmap, or
diff --git a/content/pmc/index.html b/content/pmc/index.html
index e1b9768e..f4c69506 100644
--- a/content/pmc/index.html
+++ b/content/pmc/index.html
@@ -224,17 +224,19 @@ votes on new project software releases, and
 reports quarterly to the Board of Directors.</p>
 <p>The Board expects all PMCs to understand and comply with <a 
href="https://www.apache.org/dev/pmc.html#policy";>published
 policies</a>.</p>
-<ul>
-<li><a href="#pmc-responsibilities">PMC Responsibilities</a></li>
-<li><a href="#chair">Chair</a></li>
-<li><a href="#voting">Voting</a></li>
-<li><a href="#infrastructure-services">Infrastructure services</a></li>
-<li><a href="#reporting">Reporting</a></li>
-<li><a href="#adding-committers">Adding committers</a></li>
-<li><a href="#community-growth">Community growth</a></li>
-<li><a href="#adding-pmc-members">Adding PMC members</a></li>
-<li><a href="#what-to-do-as-a-new-member">What to do as a new member</a></li>
-</ul>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#pmc-responsibilities">PMC Responsibilities</a></li>
+    <li><a href="#chair">Chair</a></li>
+    <li><a href="#voting">Voting</a></li>
+    <li><a href="#infrastructure-services">Infrastructure services</a></li>
+    <li><a href="#reporting">Reporting</a></li>
+    <li><a href="#adding-committers">Adding committers</a></li>
+    <li><a href="#community-growth">Community growth</a></li>
+    <li><a href="#adding-pmc-members">Adding PMC members</a></li>
+    <li><a href="#what-to-do-as-a-new-member">What to do as a new 
member</a></li>
+  </ul>
+</nav>
 <h2 id="pmc-responsibilities">PMC Responsibilities <a class="headerlink" 
title="Permalink" href="#pmc-responsibilities">&para;</a></h2>
 <p>The PMC is responsible for the management of the project. This includes
 both the technical decisions and ensuring that the project is operating
diff --git a/content/pmc/index.xml b/content/pmc/index.xml
index f4492e56..17b61bf4 100644
--- a/content/pmc/index.xml
+++ b/content/pmc/index.xml
@@ -34,7 +34,7 @@ Who should be a PMC member? Nominating, discussion, and 
voting What to do when a
       
       <guid>https://community.apache.org/pmc/community-growth.html</guid>
       <description>Growing your project community takes work. This document 
makes practical suggestions of how to encourage people to get involved in your 
project.
-Publish a roadmap &amp;para; Volunteers can work on whatever they want, and so 
we have a tendency to not want to tell them what to work on. However, 
publishing a roadmap, or even a wishlist of features or improvements that are 
desired, can give people an idea of where they might be able to get 
involved.</description>
+Publish a roadmap Periodically publish the open issue list Clearly document 
contribution processes Publish your contributor ladder Engage with big users Be 
transparent about project risk Come talk to us Publish a roadmap &amp;para; 
Volunteers can work on whatever they want, and so we have a tendency to not 
want to tell them what to work on.</description>
     </item>
     
     <item>
diff --git a/content/pmc/responsibilities.html 
b/content/pmc/responsibilities.html
index de7052b5..1a3433d5 100644
--- a/content/pmc/responsibilities.html
+++ b/content/pmc/responsibilities.html
@@ -228,13 +228,15 @@ Conducting Business Protecting your brand Making a 
release Ensuring Project Heal
 of the project, including technical decisions, ensuring that the project
 is operating in accordance with ASF norms, adding new members to the
 project, and voting on releases.</p>
-<ul>
-<li><a href="#conducting-business">Conducting Business</a></li>
-<li><a href="#protecting-your-brand">Protecting your brand</a></li>
-<li><a href="#making-a-release">Making a release</a></li>
-<li><a href="#ensuring-project-health">Ensuring Project Health</a></li>
-<li><a href="#adding-community-members">Adding Community Members</a></li>
-</ul>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#conducting-business">Conducting Business</a></li>
+    <li><a href="#protecting-your-brand">Protecting your brand</a></li>
+    <li><a href="#making-a-release">Making a release</a></li>
+    <li><a href="#ensuring-project-health">Ensuring Project Health</a></li>
+    <li><a href="#adding-community-members">Adding Community Members</a></li>
+  </ul>
+</nav>
 <h2 id="conducting-business">Conducting Business <a class="headerlink" 
title="Permalink" href="#conducting-business">&para;</a></h2>
 <p>The PMC is expected to conduct all of its business on the public
 developers mailing list, in the full view of the community.</p>


Reply via email to