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 c0129309 Updated asf-site from main at
bd0aab324638250bd2b5af725c7695f81cfdcd34
c0129309 is described below
commit c012930903ff3481076b88f3da02cb64426ed0ce
Author: jenkins <[email protected]>
AuthorDate: Wed Aug 13 11:39:19 2025 +0000
Updated asf-site from main at bd0aab324638250bd2b5af725c7695f81cfdcd34
Built from
https://ci-builds.apache.org/job/Community%20Development/job/site/job/main/177/
---
content/_pagefind/fragment/en_22901a6.pf_fragment | Bin 2593 -> 0 bytes
content/_pagefind/fragment/en_26f2284.pf_fragment | Bin 0 -> 2293 bytes
content/_pagefind/fragment/en_2ad07e9.pf_fragment | Bin 0 -> 1756 bytes
content/_pagefind/fragment/en_2afbaeb.pf_fragment | Bin 2022 -> 0 bytes
content/_pagefind/fragment/en_648ebd8.pf_fragment | Bin 0 -> 1902 bytes
content/_pagefind/fragment/en_6a8e895.pf_fragment | Bin 0 -> 2443 bytes
content/_pagefind/fragment/en_8970084.pf_fragment | Bin 2524 -> 0 bytes
content/_pagefind/fragment/en_c464369.pf_fragment | Bin 1983 -> 0 bytes
content/_pagefind/fragment/en_cb4d68f.pf_fragment | Bin 0 -> 2567 bytes
content/_pagefind/fragment/en_ce419bc.pf_fragment | Bin 2461 -> 0 bytes
content/_pagefind/index/en_102d217.pf_index | Bin 0 -> 31340 bytes
content/_pagefind/index/en_2319f24.pf_index | Bin 29008 -> 0 bytes
content/_pagefind/index/en_2b9b361.pf_index | Bin 0 -> 31938 bytes
content/_pagefind/index/en_2d33396.pf_index | Bin 0 -> 30726 bytes
content/_pagefind/index/en_3072102.pf_index | Bin 28345 -> 0 bytes
content/_pagefind/index/en_3362acd.pf_index | Bin 30218 -> 0 bytes
content/_pagefind/index/en_39f1f54.pf_index | Bin 30879 -> 0 bytes
content/_pagefind/index/en_4dffc33.pf_index | Bin 0 -> 29878 bytes
content/_pagefind/index/en_551a8e1.pf_index | Bin 30731 -> 0 bytes
content/_pagefind/index/en_6f6384c.pf_index | Bin 0 -> 28623 bytes
content/_pagefind/index/en_84c561c.pf_index | Bin 0 -> 30110 bytes
content/_pagefind/index/en_9371c6e.pf_index | Bin 0 -> 28338 bytes
content/_pagefind/index/en_a8fb7da.pf_index | Bin 0 -> 30271 bytes
content/_pagefind/index/en_c348b48.pf_index | Bin 30953 -> 0 bytes
content/_pagefind/index/en_d0ec9f8.pf_index | Bin 30066 -> 0 bytes
content/_pagefind/index/en_d81e04c.pf_index | Bin 32210 -> 0 bytes
content/_pagefind/pagefind-entry.json | 2 +-
content/_pagefind/pagefind.en_72d8896571.pf_meta | Bin 1311 -> 0 bytes
content/_pagefind/pagefind.en_85d25e4cec.pf_meta | Bin 0 -> 1315 bytes
content/index.xml | 27 +++---
content/pmc/chair.html | 72 ++++++--------
content/pmc/community-growth.html | 113 +++++++++++-----------
content/pmc/index.xml | 27 +++---
content/pmc/new-member.html | 87 ++++++++---------
content/pmc/reporting.html | 103 +++++++++-----------
content/pmc/responsibilities.html | 111 ++++++++++-----------
36 files changed, 261 insertions(+), 281 deletions(-)
diff --git a/content/_pagefind/fragment/en_22901a6.pf_fragment
b/content/_pagefind/fragment/en_22901a6.pf_fragment
deleted file mode 100644
index 94ff9933..00000000
Binary files a/content/_pagefind/fragment/en_22901a6.pf_fragment and /dev/null
differ
diff --git a/content/_pagefind/fragment/en_26f2284.pf_fragment
b/content/_pagefind/fragment/en_26f2284.pf_fragment
new file mode 100644
index 00000000..953f6395
Binary files /dev/null and b/content/_pagefind/fragment/en_26f2284.pf_fragment
differ
diff --git a/content/_pagefind/fragment/en_2ad07e9.pf_fragment
b/content/_pagefind/fragment/en_2ad07e9.pf_fragment
new file mode 100644
index 00000000..7d847fed
Binary files /dev/null and b/content/_pagefind/fragment/en_2ad07e9.pf_fragment
differ
diff --git a/content/_pagefind/fragment/en_2afbaeb.pf_fragment
b/content/_pagefind/fragment/en_2afbaeb.pf_fragment
deleted file mode 100644
index 558ca570..00000000
Binary files a/content/_pagefind/fragment/en_2afbaeb.pf_fragment and /dev/null
differ
diff --git a/content/_pagefind/fragment/en_648ebd8.pf_fragment
b/content/_pagefind/fragment/en_648ebd8.pf_fragment
new file mode 100644
index 00000000..74f0f328
Binary files /dev/null and b/content/_pagefind/fragment/en_648ebd8.pf_fragment
differ
diff --git a/content/_pagefind/fragment/en_6a8e895.pf_fragment
b/content/_pagefind/fragment/en_6a8e895.pf_fragment
new file mode 100644
index 00000000..9be52e04
Binary files /dev/null and b/content/_pagefind/fragment/en_6a8e895.pf_fragment
differ
diff --git a/content/_pagefind/fragment/en_8970084.pf_fragment
b/content/_pagefind/fragment/en_8970084.pf_fragment
deleted file mode 100644
index c668e59a..00000000
Binary files a/content/_pagefind/fragment/en_8970084.pf_fragment and /dev/null
differ
diff --git a/content/_pagefind/fragment/en_c464369.pf_fragment
b/content/_pagefind/fragment/en_c464369.pf_fragment
deleted file mode 100644
index eb16faf8..00000000
Binary files a/content/_pagefind/fragment/en_c464369.pf_fragment and /dev/null
differ
diff --git a/content/_pagefind/fragment/en_cb4d68f.pf_fragment
b/content/_pagefind/fragment/en_cb4d68f.pf_fragment
new file mode 100644
index 00000000..355e161d
Binary files /dev/null and b/content/_pagefind/fragment/en_cb4d68f.pf_fragment
differ
diff --git a/content/_pagefind/fragment/en_ce419bc.pf_fragment
b/content/_pagefind/fragment/en_ce419bc.pf_fragment
deleted file mode 100644
index 46154a24..00000000
Binary files a/content/_pagefind/fragment/en_ce419bc.pf_fragment and /dev/null
differ
diff --git a/content/_pagefind/index/en_102d217.pf_index
b/content/_pagefind/index/en_102d217.pf_index
new file mode 100644
index 00000000..ba8eb671
Binary files /dev/null and b/content/_pagefind/index/en_102d217.pf_index differ
diff --git a/content/_pagefind/index/en_2319f24.pf_index
b/content/_pagefind/index/en_2319f24.pf_index
deleted file mode 100644
index e9cde021..00000000
Binary files a/content/_pagefind/index/en_2319f24.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_2b9b361.pf_index
b/content/_pagefind/index/en_2b9b361.pf_index
new file mode 100644
index 00000000..41033b8a
Binary files /dev/null and b/content/_pagefind/index/en_2b9b361.pf_index differ
diff --git a/content/_pagefind/index/en_2d33396.pf_index
b/content/_pagefind/index/en_2d33396.pf_index
new file mode 100644
index 00000000..e148dd31
Binary files /dev/null and b/content/_pagefind/index/en_2d33396.pf_index differ
diff --git a/content/_pagefind/index/en_3072102.pf_index
b/content/_pagefind/index/en_3072102.pf_index
deleted file mode 100644
index 268303ba..00000000
Binary files a/content/_pagefind/index/en_3072102.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_3362acd.pf_index
b/content/_pagefind/index/en_3362acd.pf_index
deleted file mode 100644
index 5e0cb564..00000000
Binary files a/content/_pagefind/index/en_3362acd.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_39f1f54.pf_index
b/content/_pagefind/index/en_39f1f54.pf_index
deleted file mode 100644
index 01401948..00000000
Binary files a/content/_pagefind/index/en_39f1f54.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_4dffc33.pf_index
b/content/_pagefind/index/en_4dffc33.pf_index
new file mode 100644
index 00000000..9986ee36
Binary files /dev/null and b/content/_pagefind/index/en_4dffc33.pf_index differ
diff --git a/content/_pagefind/index/en_551a8e1.pf_index
b/content/_pagefind/index/en_551a8e1.pf_index
deleted file mode 100644
index ef97db35..00000000
Binary files a/content/_pagefind/index/en_551a8e1.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_6f6384c.pf_index
b/content/_pagefind/index/en_6f6384c.pf_index
new file mode 100644
index 00000000..a5fdde5b
Binary files /dev/null and b/content/_pagefind/index/en_6f6384c.pf_index differ
diff --git a/content/_pagefind/index/en_84c561c.pf_index
b/content/_pagefind/index/en_84c561c.pf_index
new file mode 100644
index 00000000..d3a15915
Binary files /dev/null and b/content/_pagefind/index/en_84c561c.pf_index differ
diff --git a/content/_pagefind/index/en_9371c6e.pf_index
b/content/_pagefind/index/en_9371c6e.pf_index
new file mode 100644
index 00000000..4ec063e5
Binary files /dev/null and b/content/_pagefind/index/en_9371c6e.pf_index differ
diff --git a/content/_pagefind/index/en_a8fb7da.pf_index
b/content/_pagefind/index/en_a8fb7da.pf_index
new file mode 100644
index 00000000..912a9754
Binary files /dev/null and b/content/_pagefind/index/en_a8fb7da.pf_index differ
diff --git a/content/_pagefind/index/en_c348b48.pf_index
b/content/_pagefind/index/en_c348b48.pf_index
deleted file mode 100644
index a206edee..00000000
Binary files a/content/_pagefind/index/en_c348b48.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_d0ec9f8.pf_index
b/content/_pagefind/index/en_d0ec9f8.pf_index
deleted file mode 100644
index 84f1bed3..00000000
Binary files a/content/_pagefind/index/en_d0ec9f8.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_d81e04c.pf_index
b/content/_pagefind/index/en_d81e04c.pf_index
deleted file mode 100644
index 27fbaec1..00000000
Binary files a/content/_pagefind/index/en_d81e04c.pf_index and /dev/null differ
diff --git a/content/_pagefind/pagefind-entry.json
b/content/_pagefind/pagefind-entry.json
index 8795ba42..ae093ce7 100644
--- a/content/_pagefind/pagefind-entry.json
+++ b/content/_pagefind/pagefind-entry.json
@@ -1 +1 @@
-{"version":"1.0.3","languages":{"en":{"hash":"en_72d8896571","wasm":"en","page_count":148}}}
\ No newline at end of file
+{"version":"1.0.3","languages":{"en":{"hash":"en_85d25e4cec","wasm":"en","page_count":148}}}
\ No newline at end of file
diff --git a/content/_pagefind/pagefind.en_72d8896571.pf_meta
b/content/_pagefind/pagefind.en_72d8896571.pf_meta
deleted file mode 100644
index 8e89849f..00000000
Binary files a/content/_pagefind/pagefind.en_72d8896571.pf_meta and /dev/null
differ
diff --git a/content/_pagefind/pagefind.en_85d25e4cec.pf_meta
b/content/_pagefind/pagefind.en_85d25e4cec.pf_meta
new file mode 100644
index 00000000..c4121e24
Binary files /dev/null and b/content/_pagefind/pagefind.en_85d25e4cec.pf_meta
differ
diff --git a/content/index.xml b/content/index.xml
index 87484b61..d0264afb 100644
--- a/content/index.xml
+++ b/content/index.xml
@@ -539,8 +539,8 @@ Board Resolution Creating the Apache Community Development
Project Establish the
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<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 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.</description>
+ <description>Building a thriving project community requires intentional
effort. This guide provides practical strategies to attract contributors to
your project, and engage them in it.
+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;
While volunteers choose their own contributions, providing direction helps them
find meaningful ways to get involved.</description>
</item>
<item>
@@ -764,9 +764,9 @@ Talk to the project first Make sure it&rsquo;s
wanted/welcome See if there&a
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/pmc/new-member.html</guid>
- <description>You&rsquo;ve been invited to join a project PMC?
Congratulations! What should you do now?
-Being part of an ASF Project Management Committee is more than just an
acknowledgement of your contributions. It&rsquo;s a new level of
responsibility for the project&rsquo;s health and sustainability. The Board
of Directors is relying on you to provide oversight of the project code, and
project community
-Join the conversation &para; If you haven&rsquo;t already, you need to
subscribe to the PMC/Private mailing list.</description>
+ <description>Congratulations on your invitation to join a project PMC!
Here&rsquo;s what you should do next.
+Joining an ASF Project Management Committee represents more than recognition
of your contributions. You take on a new level of responsibility for the
project&rsquo;s health and sustainability. The Board of Directors relies on
you to provide oversight of the project code and community.
+Join the conversation &para; Subscribe to the PMC/Private mailing list if
you haven&rsquo;t already.</description>
</item>
<item>
@@ -786,8 +786,10 @@ The mentoring programme is not here to teach you to write
documentation or code.
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/pmc/chair.html</guid>
- <description>The PMC Chair acts as the voice of the project to the
board, and is responsible for filing a quarterly report. They are not the
project leader, but are a peer of the other PMC members, who has been selected,
for a time, to take the role of secretary and spokesperson.
-The PMC Chair is not the de-facto project leader. While they are usually a
senior, well-respected member of the community, they are a peer, with a few
additional duties.</description>
+ <description>The PMC Chair serves as the project&rsquo;s voice to
the board and handles quarterly reporting.
+While typically a senior, respected community leader, the Chair is not the
project leader but a peer among PMC members, with the same voting rights and
authority as other PMC members, who has accepted additional secretarial and
spokesperson responsibilities.
+The Chair must familiarize themselves with the assigned duties of the role.
+Secretarial duties Reporting Moderating discussion Selecting a new Chair See
also: Secretarial duties &para; The Chair is responsible for completing the
necessary processes when the PMC adds committers and members.</description>
</item>
<item>
@@ -796,10 +798,10 @@ The PMC Chair is not the de-facto project leader. While
they are usually a senio
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/pmc/reporting.html</guid>
- <description>A PMC is required to file a report to the Board of
Directors every quarter, on a schedule determined by the Board.
-You can find your project&rsquo;s reporting schedule on
projects.apache.org. You will also receive a reminder from the Secretary a few
weeks prior to your report&rsquo;s due date.
+ <description>Each PMC must submit a quarterly report to the Board of
Directors according to a schedule set by the Board.
+You can find your project&rsquo;s reporting schedule by visiting the
committee&rsquo;s page on projects.apache.org. You will also receive a
reminder from the Secretary a few weeks prior to your report&rsquo;s due
date.
The official record of PMC reporting schedules is the file committee-info.txt
(requires password authentication).
-Writing a report &para; The report to the board is expected to contain
certain sections.</description>
+Writing a report &para; While you may use the reporter tool to draft your
report, avoid submitting auto-generated content.</description>
</item>
<item>
@@ -808,8 +810,9 @@ Writing a report &para; The report to the board is
expected to contain certa
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/pmc/responsibilities.html</guid>
- <description>The Project Management Committee (PMC) is responsible for
the oversight 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.
-Conducting Business Protecting your brand Making a release Ensuring Project
Health Adding Community Members Conducting Business &para; The PMC is
expected to conduct all of its business on the public developers mailing list,
in the full view of the community.</description>
+ <description>The Project Management Committee (PMC) oversees the
project, including technical decisions, ensuring compliance with ASF standards,
adding new members, and approving releases.
+Conducting Business Protecting your brand Making a release Ensuring Project
Health Adding Community Members Conducting Business &para; The PMC must
conduct all business on the public developers&rsquo; mailing list,
maintaining full community visibility.
+Every PMC has a private@ list reserved for confidential matters such as
discussing proposed committers, potential PMC members, or security
issues.</description>
</item>
<item>
diff --git a/content/pmc/chair.html b/content/pmc/chair.html
index 00b1b278..cddf93c7 100644
--- a/content/pmc/chair.html
+++ b/content/pmc/chair.html
@@ -7,8 +7,10 @@
<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="PMC Chair" />
-<meta property="og:description" content="The PMC Chair acts as the voice of
the project to the board, and is responsible for filing a quarterly report.
They are not the project leader, but are a peer of the other PMC members, who
has been selected, for a time, to take the role of secretary and spokesperson.
-The PMC Chair is not the de-facto project leader. While they are usually a
senior, well-respected member of the community, they are a peer, with a few
additional duties." />
+<meta property="og:description" content="The PMC Chair serves as the
project’s voice to the board and handles quarterly reporting.
+While typically a senior, respected community leader, the Chair is not the
project leader but a peer among PMC members, with the same voting rights and
authority as other PMC members, who has accepted additional secretarial and
spokesperson responsibilities.
+The Chair must familiarize themselves with the assigned duties of the role.
+Secretarial duties Reporting Moderating discussion Selecting a new Chair See
also: Secretarial duties ¶ The Chair is responsible for completing the
necessary processes when the PMC adds committers and members." />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://community.apache.org/pmc/chair.html";
/><meta property="og:image"
content="https://community.apache.org/images/project-logos.webp"/><meta
property="article:section" content="pmc" />
@@ -199,14 +201,13 @@ The PMC Chair is not the de-facto project leader. While
they are usually a senio
<br><br>
- <p>The PMC Chair acts as the voice of the project to the board, and is
-responsible for filing a quarterly report. They are not the project
-leader, but are a peer of the other PMC members, who has been selected,
-for a time, to take the role of secretary and spokesperson.</p>
-<p>The PMC Chair is <strong>not</strong> the de-facto project leader. While
they are
-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
+ <p>The PMC Chair serves as the project’s voice to the board and
handles
+quarterly reporting.</p>
+<p>While typically a senior, respected community leader, the Chair is
+<strong>not</strong> the project leader but a peer among PMC members, with the
same
+voting rights and authority as other PMC members, who has accepted
+additional secretarial and spokesperson responsibilities.</p>
+<p>The Chair must familiarize themselves with the <a
href="https://www.apache.org/dev/pmc.html#chair";>assigned
duties</a> of the role.</p>
<nav id="TableOfContents">
<ul>
@@ -218,46 +219,37 @@ duties</a> of the role.</p>
</ul>
</nav>
<h2 id="secretarial-duties">Secretarial duties <a class="headerlink"
title="Permalink" href="#secretarial-duties">¶</a></h2>
-<p>The Chair is responsible for completing the necessary
“paperwork” when
-new committers and PMC members are added.</p>
+<p>The Chair is responsible for completing the necessary processes when
+the PMC adds committers and members.</p>
<p>See the <a
href="https://www.apache.org/dev/pmc.html#committer-management";>process for
adding new
committers</a>,
and the <a href="https://www.apache.org/dev/pmc.html#newpmcmember";>process for
adding new PMC
members</a>, for details of
these requirements.</p>
<h2 id="reporting">Reporting <a class="headerlink" title="Permalink"
href="#reporting">¶</a></h2>
-<p>The Chair is also responsible for <a href="/pmc/reporting">filing the
quarterly project report</a> to
-the board of directors.</p>
+<p>The Chair <a href="/pmc/reporting">files the quarterly project report</a>
to the
+board of directors.</p>
<h2 id="moderating-discussion">Moderating discussion <a class="headerlink"
title="Permalink" href="#moderating-discussion">¶</a></h2>
-<p>As the name implies, the Chair may occasionally need to step in to
-moderate discussion, to ensure that a community is conducting itself
-with decorum, and not straying into divisive discussion.</p>
-<p>The Chair has been selected because they are a respected member of the
-community, and so should not be hesitant to step in and state what the
-community standards are, and enforce the expectation that community members
-behave in appropriate ways on official communication channels.</p>
+<p>The Chair may need to moderate discussions to ensure the community
+maintains appropriate conduct and avoids divisive conversations.</p>
+<p>Since the Chair has been selected as a respected community member, they
+should model and encourage established community standards and enforce
+expectations for appropriate behavior on official communication
+channels.</p>
<h2 id="selecting-a-new-chair">Selecting a new Chair <a class="headerlink"
title="Permalink" href="#selecting-a-new-chair">¶</a></h2>
-<p>A project may periodically select a new Chair.</p>
-<p>Some projects do this every year or two, while others keep the same Chair
-for many years. A Chair might step down because they no longer have time
-for the role, or simply to give someone else an opportunity.</p>
-<p>Candidates for Chair should be made aware of the work load associated
-with the position, to ensure that they have the availability for the
-role, and clearly understand what they’re getting into.</p>
-<p>The outgoing Chair is encouraged to spend some time mentoring the
-incoming Chair, and familiarizing them with the duties, to ensure their
-success in the role.</p>
+<p>Projects may periodically select a new Chair.</p>
+<p>Some projects rotate Chairs every year or two, while others maintain
+the same Chair for many years. A Chair might step down due to time
+constraints or to provide others with leadership opportunities.</p>
+<p>Inform Chair candidates about the workload to ensure they have
+sufficient availability and understand the role’s requirements.</p>
+<p>The outgoing Chair should mentor the incoming Chair, familiarizing them
+with Chair’s duties to ensure a successful transition.</p>
<h2 id="see-also">See also: <a class="headerlink" title="Permalink"
href="#see-also">¶</a></h2>
-<p>Newly Chairs are sent <a
href="https://svn.apache.org/repos/private/foundation/officers/advice-for-new-pmc-chairs.txt";>this
-advice</a>,
-and you’re encouraged to read that thoroughly. They should also be
-familiar with <a href="https://www.apache.org/dev/pmc.html#policy";>published
+<p>New Chairs receive <a
href="https://svn.apache.org/repos/private/foundation/officers/advice-for-new-pmc-chairs.txt";>this
+advice</a>
+and should read it thoroughly. They should also review <a
href="https://www.apache.org/dev/pmc.html#policy";>published
policies</a> for PMCs.</p>
-<p>(There’s some advice for new chairs here:
-<a
href="https://svn.apache.org/repos/private/foundation/officers/advice-for-new-pmc-chairs.txt";>https://svn.apache.org/repos/private/foundation/officers/advice-for-new-pmc-chairs.txt</a></p>
-<ul>
-<li>but it’s plain text, fairly terse, and behind a password.)</li>
-</ul>
</div>
diff --git a/content/pmc/community-growth.html
b/content/pmc/community-growth.html
index 08cd82b6..ff36e77b 100644
--- a/content/pmc/community-growth.html
+++ b/content/pmc/community-growth.html
@@ -7,8 +7,8 @@
<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="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 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 ¶
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:description" content="Building a thriving project community
requires intentional effort. This guide provides practical strategies to
attract contributors to your project, and engage them in it.
+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 ¶ While
volunteers choose their own contributions, providing direction helps them find
meaningful ways to get involved." />
<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/project-logos.webp"/><meta
property="article:section" content="pmc" />
@@ -202,8 +202,9 @@ Publish a roadmap Periodically publish the open issue list
Clearly document cont
<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>
+ <p>Building a thriving project community requires intentional effort.
+This guide provides practical strategies to attract contributors to your
+project, and engage them in it.</p>
<nav id="TableOfContents">
<ul>
<li><a href="#publish-a-roadmap">Publish a roadmap</a></li>
@@ -216,64 +217,66 @@ suggestions of how to encourage people to get involved in
your project.</p>
</ul>
</nav>
<h2 id="publish-a-roadmap">Publish a roadmap <a class="headerlink"
title="Permalink" href="#publish-a-roadmap">¶</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
-even a wishlist of features or improvements that are desired, can give
-people an idea of where they might be able to get involved.</p>
-<p>This also gives a clear sense that the project has ambitions, and is
-going somewhere, rather than that it is stagnating.</p>
-<p>It can be very challenging to keep a roadmap current. Having a mechanism
-for tagging open issues with <code>proposal</code> or <code>roadmap</code> and
-automatically extracting that into a web page can help with this.</p>
+<p>While volunteers choose their own contributions, providing direction
+helps them find meaningful ways to get involved. Publishing a roadmap
+or wishlist of desired features and improvements gives potential
+contributors clear entry points.</p>
+<p>A roadmap demonstrates that your project has clear goals and
+momentum, signaling growth rather than stagnation.</p>
+<p>Keeping a roadmap current can be challenging. Consider implementing
+a mechanism for tagging open issues with <code>proposal</code> or
<code>roadmap</code>
+labels and automatically extracting them into a web page to
+streamline this process.</p>
<h2 id="periodically-publish-the-open-issue-list">Periodically publish the
open issue list <a class="headerlink" title="Permalink"
href="#periodically-publish-the-open-issue-list">¶</a></h2>
-<p>Your ticket tracker allows you to periodically summarize the open
-issues. Sending this to the dev@ list reminds people that there are
-things to work on, and gives them permission, and encouragement, to do
-so.</p>
+<p>Regularly share summaries of open issues from your ticket tracker
+with the dev@ list. This reminds contributors that work is available
+and encourages them to get involved.</p>
<p>Consider creating <a href="/committers/good-first-issues.html">good first
-issues</a> as a place for new
-contributors to get started.</p>
+issues</a> as entry points for new
+contributors.</p>
<h2 id="clearly-document-contribution-processes">Clearly document contribution
processes <a class="headerlink" title="Permalink"
href="#clearly-document-contribution-processes">¶</a></h2>
-<p>Double-check that your “how to contribute / build / test / submit
PR”
-documentation is super clear and easy to follow. Long-time committers
-on a project often forget all the institutional knowledge they just
-“know”, so ensuring the “getting started” document
actually works
-for newcomers is always worth looking at.</p>
-<p>Encourage newcomers to talk about, and document, their pain points
-during their first contributions, and work towards fixing, or at least
-documenting, those things.</p>
+<p>Ensure your contribution documentation – covering how to contribute,
+build, test, and submit pull requests – is clear and easy to follow.
+Experienced committers often overlook the institutional knowledge
+they take for granted, so regularly review your “getting started”
+documentation from a newcomer’s perspective.</p>
+<p>Encourage new contributors to share and document their pain points
+during their first contributions. Work toward addressing or at least
+documenting these challenges to improve the experience for future
+contributors.</p>
+<p>Do not neglect non-code contributions as you think about where people
+can get involved.</p>
<h2 id="publish-your-contributor-ladder">Publish your contributor ladder <a
class="headerlink" title="Permalink"
href="#publish-your-contributor-ladder">¶</a></h2>
-<p>A <a href="/contributor-ladder.html">contributor ladder</a> is a
description of
-various levels of access and responsibility a contributor can progress
-through in your project. This is typically the path from contributor, to
-committer, to PMC member.</p>
-<p>Explicitly publish your requirements for each step. For example, if you
-require ten non-trivial patches accepted, or perhaps 3 months of
-involvement, document this on your website so that people don’t feel
-that it’s random, or that they are driving in the dark.</p>
-<p>Consider lowering your bar to entry. Remember that while the risk of
-inviting someone “too early” is that they’ll break
something, that’s why
-you have version control - so you can revert those changes. However, the
-risk of inviting someone too late is that they’ll give up and go away
-forever.</p>
+<p>A <a href="/contributor-ladder.html">contributor ladder</a> describes the
+levels of access and responsibility contributors can progress through
+in your project – typically from contributor to committer to PMC
member.</p>
+<p>Clearly document requirements for each level. For example, if you require
+ten substantial patches or three months of involvement, publish these
+criteria on your website. This prevents contributors from feeling the
+process is arbitrary or unclear.</p>
+<p>Consider relaxing your entry conditions. Remember that inviting someone
+“too early” risks temporary issues that version control can fix,
but
+inviting someone too late risks losing them permanently.</p>
<h2 id="engage-with-big-users">Engage with big users <a class="headerlink"
title="Permalink" href="#engage-with-big-users">¶</a></h2>
-<p>If you are aware of companies that rely on your project, encourage them
-to think about what they would do if the project retired. This often
-leads to those companies realizing the value they get “for free”,
and
-starting to contribute in some way.</p>
+<p>Reach out to companies that depend on your project, and encourage them
+to take an active role in the decision-making by getting involved in the
+discussions on the mailing lists, and providing code changes that their
+customers are requesting. Encourage them to think of open source
+collaboration as investing in their supply chain, rather than as
+altruism.</p>
<h2 id="be-transparent-about-project-risk">Be transparent about project risk
<a class="headerlink" title="Permalink"
href="#be-transparent-about-project-risk">¶</a></h2>
-<p>If your project is actually at risk of retiring due to lack of community
-engagement, be transparent about this. Tell your dev and user lists
-about the risk, and tell them specifically where you need help.</p>
-<p>While many users are content to simply consume, when they become aware
-that the project is at risk, it often inspires people to think about
-ways they can get involved.</p>
+<p>If your project faces retirement due to insufficient community engagement,
+communicate this openly. Tell your dev and user lists about the specific
+risks and where you need help. Think about non-code needs that your
+project has, and be specific about how these could be addressed.</p>
+<p>While many users are content to consume your project passively, awareness
+of project risks often motivates them to contribute.</p>
<h2 id="come-talk-to-us">Come talk to us <a class="headerlink"
title="Permalink" href="#come-talk-to-us">¶</a></h2>
-<p>You’re always welcome to come talk to the Community Development
project,
-for advice and resources. We don’t always have all of the answers, but
-we can help you think about the problem, and suggest possible solutions.</p>
-<p>Engage with one of our <a href="/workinggroups/">working groups</a> to help
-implement some of the above advise.</p>
+<p>The Community Development project welcomes discussions about community
growth
+challenges. While we don’t have all the answers, we can help you analyze
+problems and explore potential solutions.</p>
+<p>Join one of our <a href="/workinggroups/">working groups</a> to help
implement these
+strategies.</p>
</div>
diff --git a/content/pmc/index.xml b/content/pmc/index.xml
index ea877246..7fb935d7 100644
--- a/content/pmc/index.xml
+++ b/content/pmc/index.xml
@@ -34,8 +34,8 @@ The Contributor Ladder helps explain different
roles.</description>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<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 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.</description>
+ <description>Building a thriving project community requires intentional
effort. This guide provides practical strategies to attract contributors to
your project, and engage them in it.
+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;
While volunteers choose their own contributions, providing direction helps them
find meaningful ways to get involved.</description>
</item>
<item>
@@ -44,9 +44,9 @@ Publish a roadmap Periodically publish the open issue list
Clearly document cont
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/pmc/new-member.html</guid>
- <description>You&rsquo;ve been invited to join a project PMC?
Congratulations! What should you do now?
-Being part of an ASF Project Management Committee is more than just an
acknowledgement of your contributions. It&rsquo;s a new level of
responsibility for the project&rsquo;s health and sustainability. The Board
of Directors is relying on you to provide oversight of the project code, and
project community
-Join the conversation &para; If you haven&rsquo;t already, you need to
subscribe to the PMC/Private mailing list.</description>
+ <description>Congratulations on your invitation to join a project PMC!
Here&rsquo;s what you should do next.
+Joining an ASF Project Management Committee represents more than recognition
of your contributions. You take on a new level of responsibility for the
project&rsquo;s health and sustainability. The Board of Directors relies on
you to provide oversight of the project code and community.
+Join the conversation &para; Subscribe to the PMC/Private mailing list if
you haven&rsquo;t already.</description>
</item>
<item>
@@ -55,8 +55,10 @@ Join the conversation &para; If you haven&rsquo;t
already, you need to s
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/pmc/chair.html</guid>
- <description>The PMC Chair acts as the voice of the project to the
board, and is responsible for filing a quarterly report. They are not the
project leader, but are a peer of the other PMC members, who has been selected,
for a time, to take the role of secretary and spokesperson.
-The PMC Chair is not the de-facto project leader. While they are usually a
senior, well-respected member of the community, they are a peer, with a few
additional duties.</description>
+ <description>The PMC Chair serves as the project&rsquo;s voice to
the board and handles quarterly reporting.
+While typically a senior, respected community leader, the Chair is not the
project leader but a peer among PMC members, with the same voting rights and
authority as other PMC members, who has accepted additional secretarial and
spokesperson responsibilities.
+The Chair must familiarize themselves with the assigned duties of the role.
+Secretarial duties Reporting Moderating discussion Selecting a new Chair See
also: Secretarial duties &para; The Chair is responsible for completing the
necessary processes when the PMC adds committers and members.</description>
</item>
<item>
@@ -65,10 +67,10 @@ The PMC Chair is not the de-facto project leader. While
they are usually a senio
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/pmc/reporting.html</guid>
- <description>A PMC is required to file a report to the Board of
Directors every quarter, on a schedule determined by the Board.
-You can find your project&rsquo;s reporting schedule on
projects.apache.org. You will also receive a reminder from the Secretary a few
weeks prior to your report&rsquo;s due date.
+ <description>Each PMC must submit a quarterly report to the Board of
Directors according to a schedule set by the Board.
+You can find your project&rsquo;s reporting schedule by visiting the
committee&rsquo;s page on projects.apache.org. You will also receive a
reminder from the Secretary a few weeks prior to your report&rsquo;s due
date.
The official record of PMC reporting schedules is the file committee-info.txt
(requires password authentication).
-Writing a report &para; The report to the board is expected to contain
certain sections.</description>
+Writing a report &para; While you may use the reporter tool to draft your
report, avoid submitting auto-generated content.</description>
</item>
<item>
@@ -77,8 +79,9 @@ Writing a report &para; The report to the board is
expected to contain certa
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/pmc/responsibilities.html</guid>
- <description>The Project Management Committee (PMC) is responsible for
the oversight 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.
-Conducting Business Protecting your brand Making a release Ensuring Project
Health Adding Community Members Conducting Business &para; The PMC is
expected to conduct all of its business on the public developers mailing list,
in the full view of the community.</description>
+ <description>The Project Management Committee (PMC) oversees the
project, including technical decisions, ensuring compliance with ASF standards,
adding new members, and approving releases.
+Conducting Business Protecting your brand Making a release Ensuring Project
Health Adding Community Members Conducting Business &para; The PMC must
conduct all business on the public developers&rsquo; mailing list,
maintaining full community visibility.
+Every PMC has a private@ list reserved for confidential matters such as
discussing proposed committers, potential PMC members, or security
issues.</description>
</item>
</channel>
diff --git a/content/pmc/new-member.html b/content/pmc/new-member.html
index 162d727d..bd4a7bd3 100644
--- a/content/pmc/new-member.html
+++ b/content/pmc/new-member.html
@@ -7,9 +7,9 @@
<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="New PMC Members" />
-<meta property="og:description" content="You’ve been invited to join a
project PMC? Congratulations! What should you do now?
-Being part of an ASF Project Management Committee is more than just an
acknowledgement of your contributions. It’s a new level of responsibility
for the project’s health and sustainability. The Board of Directors is
relying on you to provide oversight of the project code, and project community
-Join the conversation ¶ If you haven’t already, you need to
subscribe to the PMC/Private mailing list." />
+<meta property="og:description" content="Congratulations on your invitation to
join a project PMC! Here’s what you should do next.
+Joining an ASF Project Management Committee represents more than recognition
of your contributions. You take on a new level of responsibility for the
project’s health and sustainability. The Board of Directors relies on you
to provide oversight of the project code and community.
+Join the conversation ¶ Subscribe to the PMC/Private mailing list if you
haven’t already." />
<meta property="og:type" content="article" />
<meta property="og:url"
content="https://community.apache.org/pmc/new-member.html"; /><meta
property="og:image"
content="https://community.apache.org/images/project-logos.webp"/><meta
property="article:section" content="pmc" />
@@ -200,50 +200,49 @@ Join the conversation ¶ If you haven’t
already, you need to subscribe
<br><br>
- <p>You’ve been invited to join a project PMC? Congratulations!
What should
-you do now?</p>
-<p>Being part of an ASF Project Management Committee is more than just an
-acknowledgement of your contributions. It’s a new level of
-responsibility for the project’s health and sustainability. The Board of
-Directors is relying on you to provide oversight of the project code,
-and project community</p>
+ <p>Congratulations on your invitation to join a project PMC!
Here’s what
+you should do next.</p>
+<p>Joining an ASF Project Management Committee represents more than
+recognition of your contributions. You take on a new level of responsibility
+for the project’s health and sustainability. The Board of Directors
+relies on you to provide oversight of the project code and community.</p>
<h2 id="join-the-conversation">Join the conversation <a class="headerlink"
title="Permalink" href="#join-the-conversation">¶</a></h2>
-<p>If you haven’t already, you need to subscribe to the PMC/Private
mailing
-list. This is the list on which confidential PMC business is conducted,
-and is also the channel that the Board uses to contact the PMC.</p>
-<p>To subscribe to the private list, send blank email to the address
-private-subscribe@<strong>PROJECT</strong>.apache.org (replacing
<strong>PROJECT</strong> with
-your specific project name). Alternately, you can visit the private list
-on <a href="https://lists.apache.org";>lists.apache.org</a> (you’ll need
to log in)
-and click the blue “Subscribe to list” button in the left
column.</p>
+<p>Subscribe to the PMC/Private mailing list if you haven’t already. This
+list handles confidential PMC business and serves as the Board’s
+communication channel with the PMC.</p>
+<p>To subscribe to the private list, send a blank email to
+private-subscribe@<strong>PROJECT</strong>.apache.org (replace
<strong>PROJECT</strong> with
+your project name). Alternatively, visit the private list on
+<a href="https://lists.apache.org";>lists.apache.org</a> (login required) and
+click the blue “Subscribe to list” button in the left column.</p>
<p>See also <a
href="https://community.apache.org/pmc/responsibilities.html#conducting-business";>these
tips for using the private mailing
list</a></p>
-<p>We also encourage you to join the developer and user mailing lists, if
-you’re not already on them. This is where the day-to-day business of the
-project happens. It’s also one place where you will interact with your
-users, and understand their pains and needs.</p>
-<p>Take a moment to introduce yourself on the dev list, if you’re not
-already well known there. You might include such information as where
-you are in the world, what portion of the project you’re most engaged
-with, and what communications channel you’re most accessible on.</p>
-<p>This will help developers know when you’re likely to be available, how
-to get in touch with you, and what topics you’re most likely to be able
-to help them with.</p>
-<h2 id="read-the-docs">Read the docs <a class="headerlink" title="Permalink"
href="#read-the-docs">¶</a></h2>
-<p>There are policies and procedures for how the PMC should conduct itself.
-You are expected to <a href="https://www.apache.org/dev/pmc.html#policy";>read,
understand, and abide by these
-policies</a></p>
-<p>Also have a look at the <a
href="https://community.apache.org/pmc/responsibilities.html";>overview of PMC
-responsibilities</a> to
-understand best practices of governing your project. Two other key
-documents are about <a
href="https://apache.org/foundation/policies/conduct";>maintaining project
independence</a>,
-and <a href="https://apache.org/foundation/marks/responsibility";>protecting
your project’s trademarks</a>.</p>
-<h2 id="ask-a-lot-of-questions">Ask a lot of questions <a class="headerlink"
title="Permalink" href="#ask-a-lot-of-questions">¶</a></h2>
-<p>As you get used to your new role on the PMC, be sure to ask lots of
-questions. Don’t be afraid to question the status quo. As why things are
-done the way they are, particularly if you see a chance to improve.
-Your <a href="https://en.wikipedia.org/wiki/Shoshin";>beginner’s mind</a>
can offer
-insights that more senior members are blind to.</p>
+<p>Join the developer and user mailing lists if you’re not already
+subscribed. These lists handle the project’s day-to-day business and
+provide opportunities to interact with users, which will help you
+understand their needs and challenges.</p>
+<p>Introduce yourself on the dev list if you’re not well known there.
+Include information such as your location (and time zone), which parts
+of the project you work on most, and your preferred communication channels.</p>
+<p>This helps developers know when you’re available, how to contact you,
+and which topics you can best assist with.</p>
+<h2 id="read-the-documentation">Read the documentation <a class="headerlink"
title="Permalink" href="#read-the-documentation">¶</a></h2>
+<p>Familiarize yourself with policies and procedures for PMC conduct. You
+must <a href="https://www.apache.org/dev/pmc.html#policy";>read, understand,
and follow these
+policies</a>.</p>
+<p>Review the <a
href="https://community.apache.org/pmc/responsibilities.html";>overview of PMC
+responsibilities</a>
+to understand best practices for governing your project. Two other key
+documents cover <a
href="https://apache.org/foundation/policies/conduct";>maintaining project
+independence</a> and
+<a href="https://apache.org/foundation/marks/responsibility";>protecting your
project’s
+trademarks</a>.</p>
+<h2 id="ask-questions">Ask questions <a class="headerlink" title="Permalink"
href="#ask-questions">¶</a></h2>
+<p>As you adjust to your new PMC role, ask plenty of questions. Don’t
+hesitate to question existing practices. Ask why things are done
+certain ways, especially when you see improvement opportunities. Your
+<a href="https://en.wikipedia.org/wiki/Shoshin";>beginner’s mind</a> can
provide
+insights that experienced members might overlook.</p>
</div>
diff --git a/content/pmc/reporting.html b/content/pmc/reporting.html
index ee659b4d..018e95ad 100644
--- a/content/pmc/reporting.html
+++ b/content/pmc/reporting.html
@@ -7,10 +7,10 @@
<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="PMC Reporting" />
-<meta property="og:description" content="A PMC is required to file a report to
the Board of Directors every quarter, on a schedule determined by the Board.
-You can find your project’s reporting schedule on projects.apache.org.
You will also receive a reminder from the Secretary a few weeks prior to your
report’s due date.
+<meta property="og:description" content="Each PMC must submit a quarterly
report to the Board of Directors according to a schedule set by the Board.
+You can find your project’s reporting schedule by visiting the
committee’s page on projects.apache.org. You will also receive a reminder
from the Secretary a few weeks prior to your report’s due date.
The official record of PMC reporting schedules is the file committee-info.txt
(requires password authentication).
-Writing a report ¶ The report to the board is expected to contain certain
sections." />
+Writing a report ¶ While you may use the reporter tool to draft your
report, avoid submitting auto-generated content." />
<meta property="og:type" content="article" />
<meta property="og:url"
content="https://community.apache.org/pmc/reporting.html"; /><meta
property="og:image"
content="https://community.apache.org/images/project-logos.webp"/><meta
property="article:section" content="pmc" />
@@ -201,9 +201,10 @@ Writing a report ¶ The report to the board is
expected to contain certain s
<br><br>
- <p>A PMC is required to file a report to the Board of Directors every
-quarter, on a schedule determined by the Board.</p>
-<p>You can find your project’s reporting schedule on
+ <p>Each PMC must submit a quarterly report to the Board of Directors
+according to a schedule set by the Board.</p>
+<p>You can find your project’s reporting schedule by visiting the
+committee’s page on
<a href="https://projects.apache.org/committees.html";>projects.apache.org</a>.
You
will also receive a reminder from the Secretary a few weeks prior to
your report’s due date.</p>
@@ -211,73 +212,59 @@ your report’s due date.</p>
<a
href="https://svn.apache.org/repos/private/committers/board/committee-info.txt";>committee-info.txt</a>
(requires password authentication).</p>
<h2 id="writing-a-report">Writing a report <a class="headerlink"
title="Permalink" href="#writing-a-report">¶</a></h2>
-<p>The report to the board is expected to contain certain sections. See the
-<a href="https://www.apache.org/foundation/board/reporting";>detailed
instructions for writing a board
-report</a>.</p>
-<p>You may (but are not required to) use the <a
href="https://reporter.apache.org";>reporter
-tool</a> to draft your report. However, do
-<strong>not</strong> simply submit an auto-generated report. You are expected
to take
-this time to be introspective about your project’s health, short- and
-long-term objectives, and any risks or concerns facing your project.</p>
-<p>Important things you should mention might include (but are not limited
to):</p>
+<p>While you may use the <a href="https://reporter.apache.org";>reporter
tool</a>
+to draft your report, avoid submitting auto-generated content. Instead,
+use this opportunity to reflect thoughtfully on your project’s health,
+objectives, and any challenges it’s facing. Take time to be introspective
+about your project’s short- and long-term goals and identify any risks
or concerns.</p>
+<p>Consider including these important topics in your report:</p>
<ul>
-<li>Changes to technology trends that will influence the direction of your
-project</li>
-<li>A very active individual, or company, entering or exiting from the
project</li>
-<li>A merger or acquisition between active participant organizations in
+<li>Technology trend changes that will influence your project’s
direction</li>
+<li>A very active contributor, or company, joining or leaving the project</li>
+<li>Mergers or acquisitions between active participant organizations in
your project</li>
-<li>A boost or decline in your project’s momentum, or popularity, that
may
-result in community changes</li>
+<li>Notable increases or decreases in your project’s momentum or
popularity
+that may affect the community</li>
</ul>
-<p>Remember that reports are made public once the board minutes are
-approved, and craft your phrasing accordingly. Sections that are
-intended to be Foundation-confidential should be enclosed in <em>private</em>
+<p>While the Board of Directors is your primary audience,
+reports become <a href="https://whimsy.apache.org/board/minutes/";>publicly
available</a>
+once the board minutes are approved. Enclose any
+Foundation-confidential sections in <private>…</private>
tags, as described in the formal documentation above.</p>
-<p>While the Chair can write the report on their own, you are encouraged to
-consult with the entire PMC for input on the report, perhaps even
-drafting it with everyone able to contribute.</p>
-<p>The report can be submitted via the <a
href="https://reporter.apache.org";>reporter
-tool</a>, the <a href="https://whimsy.apache.org/board/agenda";>agenda
-tool</a>, or committed directly to
-the <a href="https://svn.apache.org/repos/private/foundation/board";>subversion
+<p>Consider the secondary audience when writing. For example, if you want
+the press to tell a particular story about your project, tell that story
+in your report, and provide a quote suitable for an article.</p>
+<p>The Chair is responsible for ensuring that the report is filed, but it
+should represent the thoughts of the entire PMC. Consult with the entire PMC as
+you draft the report. Many projects discuss drafts on on the dev list,
+giving the broader community the opportunity to provide input as well.</p>
+<p>Submit your report via the <a href="https://reporter.apache.org";>reporter
tool</a> or
+the <a href="https://whimsy.apache.org/board/agenda";>agenda tool</a>, or
commit it
+directly to the <a
href="https://svn.apache.org/repos/private/foundation/board";>subversion
repository</a>.</p>
<h2 id="what-makes-a-good-board-report">What makes a good board report <a
class="headerlink" title="Permalink"
href="#what-makes-a-good-board-report">¶</a></h2>
-<p>As with anything you write, the most important thing to keep in mind
-when writing your board report is who your audience is.</p>
-<p>The primary audience of your report is, of course, the board of
-directors. They are not, generally, experts on your particular technology.
They are,
-rather, interested in the health and sustainability of the project.
-Questions to consider include:</p>
+<p>When writing your board report, keep your audience in mind.</p>
+<p>The primary audience of your report is the board of directors. While
+board members may not be experts in your specific technology, they focus
+on project health and sustainability.</p>
+<p>Consider these key questions:</p>
<ul>
<li>Do you have enough active participants - both committers and PMC members -
-to respond to urgent bugs or security?</li>
-<li>Have you responded to any questions or comments that the board made on
+to respond to urgent bugs or security? Think about non-technical, as
+well as technical roles.</li>
+<li>Have you addressed any questions or comments that the board made on
your previous report?</li>
-<li>Have you pointed out major achievements, or challenges, encountered in
-the past quarter that an outsider would have missed?</li>
+<li>Have you highlighted major achievements or challenges in the past
+quarter than an outsider might have missed?</li>
</ul>
-<p>The secondary audience of your report is the general public. The minutes
-of board meetings are
-<a href="https://apache.org/foundation/board/calendar.html";>published</a> for
our users,
-sponsors, the press, and the general public to read. Consider that
-audience when writing. For example, if there’s a story that you’d
like
-the press to tell about your project, you might mention it, and provide
-a quote that you’d like to see in an article.</p>
-<p>If there’s something you wish to bring to the attention of the board,
-but isn’t for public consumption, enclose it in <private> tags so
-that it won’t be published in the public minutes.</p>
-<p>For example:</p>
-<pre tabindex="0"><code><private>
-Private tags should be alone on a line
-</private>
-</code></pre><p>The report isn’t just a once-a-quarter box to check
– it’s your
+<p>The report isn’t just a once-a-quarter box to check –
it’s your
opportunity to tell the story of your project,
celebrate your accomplishments, ask for help or advice on challenges
you’re facing, and identify places where new contributors might find
something to work on.</p>
-<p>We encourage you to look at <a
href="https://apache.org/foundation/board/calendar.html";>past board
+<p>We encourage you to review <a
href="https://apache.org/foundation/board/calendar.html";>past board
reports</a> for inspiration from
-other projects’ reports.</p>
+other projects.</p>
<!-- TODO
* Add links to recommended/good reports to emulate.
-->
diff --git a/content/pmc/responsibilities.html
b/content/pmc/responsibilities.html
index 68d049ca..cc33971f 100644
--- a/content/pmc/responsibilities.html
+++ b/content/pmc/responsibilities.html
@@ -7,8 +7,9 @@
<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="PMC Responsibilities" />
-<meta property="og:description" content="The Project Management Committee
(PMC) is responsible for the oversight 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.
-Conducting Business Protecting your brand Making a release Ensuring Project
Health Adding Community Members Conducting Business ¶ The PMC is expected
to conduct all of its business on the public developers mailing list, in the
full view of the community." />
+<meta property="og:description" content="The Project Management Committee
(PMC) oversees the project, including technical decisions, ensuring compliance
with ASF standards, adding new members, and approving releases.
+Conducting Business Protecting your brand Making a release Ensuring Project
Health Adding Community Members Conducting Business ¶ The PMC must conduct
all business on the public developers’ mailing list, maintaining full
community visibility.
+Every PMC has a private@ list reserved for confidential matters such as
discussing proposed committers, potential PMC members, or security issues." />
<meta property="og:type" content="article" />
<meta property="og:url"
content="https://community.apache.org/pmc/responsibilities.html"; /><meta
property="og:image"
content="https://community.apache.org/images/project-logos.webp"/><meta
property="article:section" content="pmc" />
@@ -199,10 +200,9 @@ Conducting Business Protecting your brand Making a release
Ensuring Project Heal
<br><br>
- <p>The Project Management Committee (PMC) is responsible for the
oversight
-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>
+ <p>The Project Management Committee (PMC) oversees the project,
including
+technical decisions, ensuring compliance with ASF standards, adding
+new members, and approving releases.</p>
<nav id="TableOfContents">
<ul>
<li><a href="#conducting-business">Conducting Business</a></li>
@@ -213,25 +213,23 @@ project, and voting on releases.</p>
</ul>
</nav>
<h2 id="conducting-business">Conducting Business <a class="headerlink"
title="Permalink" href="#conducting-business">¶</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>
-<p>Every PMC also has a private@ list, which is for communication about
-private matters, such as discussion of proposed committers, proposed
-new PMC members, or confidential security issues. Do not use it for discussion
-of features, roadmap, or other technical decisions.</p>
-<p>The Board of Directors will occasionally send you comments or queries,
-often related to your quarterly board report. Any PMC member can, and
-should, respond to these. You should not wait for the Chair to respond
-to these queries.</p>
-<p>The PMC is tasked with making decisions on the direction of the project,
-They can, and should, also incorporate the voice of the larger community
-in these decisions. However, if a vote is taken, only the votes of the
-PMC are binding on the outcome. Other community members may vote as
-well, but those votes are advisory only, and not binding.</p>
-<p>A PMC member may veto a technical decision, such as a proposed patch.
-However, they must be able to back this veto up with a technical reason,
-and be willing to discuss possible resolutions to their objection.</p>
-<p>Further discussion of voting may be found on the <a
href="https://www.apache.org/foundation/voting.html";>Foundation
+<p>The PMC must conduct all business on the public developers’ mailing
list,
+maintaining full community visibility.</p>
+<p>Every PMC has a private@ list reserved for confidential matters such as
+discussing proposed committers, potential PMC members, or security issues.
+Do not use the private list to discuss features, roadmap discussions, or other
+technical decisions, as this cuts the community out of the process.</p>
+<p>The Board of Directors occasionally sends comments or queries, often
+regarding your quarterly board report. Any PMC member can and should
+respond to these inquiries – don’t wait for the Chair to handle
them.</p>
+<p>The PMC makes decisions about project direction and should incorporate
+input from the broader community. However, when votes are taken, only
+PMC votes are binding. Community members are encouraged to vote, but
+their votes serve as advisory input only.</p>
+<p>PMC members may veto technical decisions, such as proposed patches, but
+must provide technical justification and engage in discussion to resolve
+their objections.</p>
+<p>For more information about voting procedures, see the <a
href="https://www.apache.org/foundation/voting.html";>Foundation
website</a>.</p>
<h2 id="protecting-your-brand">Protecting your brand <a class="headerlink"
title="Permalink" href="#protecting-your-brand">¶</a></h2>
<p>Apache PMCs are directly responsible for promoting and protecting their
@@ -239,43 +237,38 @@ project’s brand and trademarks while following
Apache Trademark
policies. This is discussed in detail on the <a
href="https://apache.org/foundation/marks/responsibility";>trademarks
site</a>.</p>
<h2 id="making-a-release">Making a release <a class="headerlink"
title="Permalink" href="#making-a-release">¶</a></h2>
-<p>The process for releasing a official Apache software artifact may be
-found on the <a href="https://infra.apache.org/release-publishing.html";>Infra
-website</a>. As a PMC
-member, you are expected to read and understand that process.</p>
-<p>When you vote on a release, it should be an indication that you have
-actually tested that release. In your vote email, rather than merely
-voting +1 or -1, also indicate what you tested, and on what
-platform(s).</p>
+<p>The process for releasing official Apache software artifacts is documented
+on the <a href="https://infra.apache.org/release-publishing.html";>Infra
website</a>.
+As a PMC member, you must read and understand this process.</p>
+<p>When voting on a release, actually test the release candidate. In your vote
+email, specify what you tested and on which platforms, rather than simply
+voting +1 or -1.</p>
<h2 id="ensuring-project-health">Ensuring Project Health <a class="headerlink"
title="Permalink" href="#ensuring-project-health">¶</a></h2>
-<p>The PMC is tasked individually and collectively with ensuring that the
-project is behaving according to ASF policies and norms. In this
-responsibility, PMC members act as individuals, not as representatives
-of their employer, or other third-party interests. The reputation of the
-project, and the ASF in general, is delegated to PMC members in this
-respect.</p>
-<p>Projects should <a
href="https://community.apache.org/projectIndependence.html";>operate in a
vendor neutral fashion</a>. That is to say, any
-project participant has an equal voice, unrelated to the employer or
-lack thereof. Evidence that a project is favoring one company or
-organization over another is a serious offense. For example, if members
-of a particular organization are favored over another, for either
-addition to the committer roll, the PMC, or for acceptance of their
-patches, this is an indication that the employer is exerting undue
-influence over the direction of the project.</p>
-<p>The PMC is also expected to set the tone for conduct and interactions in
-the project. They can, and should, call out behavior that is in conflict
-with ASF norms, such as bullying, racist or sexist discussions, or other
-abusive behavior. PMCs may adopt a specific Code of Conduct, or simply
-follow the <a
href="https://apache.org/foundation/policies/conduct";>ASF’s general Code
of Conduct</a>.</p>
+<p>The PMC is individually and collectively responsible for ensuring the
+project operates according to ASF policies and standards. In this role,
+PMC members act as individuals, not as representatives of their employers
+or other third-party interests. The reputation of both the project and the
+ASF depends on PMC members fulfilling this responsibility.</p>
+<p>Projects must <a
href="https://community.apache.org/projectIndependence.html";>operate in a
vendor-neutral
+fashion</a>. Every project
+participant should have an equal voice, regardless of their employer or
+employment status. Evidence that a project favors one company or organization
+over another constitutes a serious violation. For example, if members of a
+particular organization receive preferential treatment for committer status,
+PMC membership, or patch acceptance, this indicates undue employer influence
+over the project.</p>
+<p>The PMC sets the tone for conduct and interactions within the project.
+Members can and should address behavior that conflicts with ASF standards,
+including bullying, discriminatory discussions, or other abusive behavior.
+PMCs may adopt a specific Code of Conduct or follow the <a
href="https://apache.org/foundation/policies/conduct";>ASF’s general
+Code of Conduct</a>.</p>
<h2 id="adding-community-members">Adding Community Members <a
class="headerlink" title="Permalink"
href="#adding-community-members">¶</a></h2>
-<p>The PMC is also tasked with the sustainability of the project. An
-important part of this is regularly <a
href="/pmc/adding-committers.html">adding new
+<p>The PMC ensures project sustainability by regularly <a
href="/pmc/adding-committers.html">adding
committers</a> and <a href="/pmc/adding-pmc-members.html">new PMC
-members</a>. This is not the sole role of the
-chair. Rather, every PMC member can, and should, regularly look at who
-is participating in the project, and evaluate whether they should be
-invited to the next <a href="/contributor-ladder.html">rung of the contributor
-ladder</a>.</p>
+members</a>. This responsibility extends beyond
+the chair – every PMC member should regularly evaluate project
participants
+and consider whether they should be invited to the next <a
href="/contributor-ladder.html">level of the
+contributor ladder</a>.</p>
</div>
![https://community.apache.org/images/project-logos.webp"/](https://community.apache.org/images/project-logos.webp"/){kind=link}