This is an automated email from the ASF dual-hosted git repository.
curcuru pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/comdev-site.git
The following commit(s) were added to refs/heads/main by this push:
new b10d4b18 Tweak some of the PMC descriptions and add key links
b10d4b18 is described below
commit b10d4b18e08b295bcc20bf7737a748bbfc929e88
Author: Shane Curcuru <[email protected]>
AuthorDate: Tue Oct 22 09:18:31 2024 -0400
Tweak some of the PMC descriptions and add key links
---
source/pmc/_index.md | 25 ++++++++++++++-----------
source/pmc/new-member.md | 4 +++-
source/pmc/responsibilities.md | 20 +++++++++++---------
3 files changed, 28 insertions(+), 21 deletions(-)
diff --git a/source/pmc/_index.md b/source/pmc/_index.md
index 1256d9aa..159ebce6 100644
--- a/source/pmc/_index.md
+++ b/source/pmc/_index.md
@@ -5,27 +5,30 @@ tags: ["pmc","navigation"]
---
The Project Management Committee, or PMC, is the technical steering
-committee for a project. This group determines the roadmap for the
-project, decides who will be added as committers and PMC members, and
+committee for a project. Each PMC determines the roadmap for their
+project, decides who will be added as committers and PMC members,
+votes on new project software releases, and
reports quarterly to the Board of Directors.
The Board expects all PMCs to understand and comply with [published
policies](https://www.apache.org/dev/pmc.html#policy).
-* [PMC Responsibilities](#pmc-responsibilities)
-* [Chair](#chair)
-* [Voting](#voting)
-* [Reporting](#reporting)
-* [Adding committers](#adding-committers)
-* [Encouraging community growth](#community-growth)
-* [Adding PMC members](#adding-pmc-members)
-* [What to do as a new PMC member](#what-to-do-as-a-new-member)
+- [PMC Responsibilities](#pmc-responsibilities)
+- [Chair](#chair)
+- [Voting](#voting)
+- [Infrastructure services](#infrastructure-services)
+- [Reporting](#reporting)
+- [Adding committers](#adding-committers)
+- [Community growth](#community-growth)
+- [Adding PMC members](#adding-pmc-members)
+- [What to do as a new member](#what-to-do-as-a-new-member)
## PMC Responsibilities
The PMC is responsible for the management of the project. This includes
both the technical decisions and ensuring that the project is operating
-in community-friendly ways.
+in community-friendly ways. PMCs are also responsible for managing
+their project's brand and trademarks.
The PMC is also responsible for voting on releases of their project, to
ensure that each release is tested and is an official ASF release
diff --git a/source/pmc/new-member.md b/source/pmc/new-member.md
index f71714b4..ece3505b 100644
--- a/source/pmc/new-member.md
+++ b/source/pmc/new-member.md
@@ -43,7 +43,9 @@ policies](https://www.apache.org/dev/pmc.html#policy)
Also have a look at the [overview of PMC
responsibilities](https://community.apache.org/pmc/responsibilities.html) to
-understand best practices of governing your project.
+understand best practices of governing your project. Two other key
+documents are about [maintaining project
independence](https://apache.org/foundation/policies/conduct),
+and [protecting your project's
trademarks](https://apache.org/foundation/marks/responsibility).
## Ask a lot of questions
diff --git a/source/pmc/responsibilities.md b/source/pmc/responsibilities.md
index daf8d29e..2e2e3da9 100644
--- a/source/pmc/responsibilities.md
+++ b/source/pmc/responsibilities.md
@@ -8,19 +8,20 @@ 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](#conducting-business)
-* [Ensuring project health](#ensuring-project-health)
-* [Adding community members](#adding-community-members)
-* [Reporting](/pmc/reporting.html)
+- [Conducting Business](#conducting-business)
+- [Protecting your brand](#protecting-your-brand)
+- [Making a release](#making-a-release)
+- [Ensuring Project Health](#ensuring-project-health)
+- [Adding Community Members](#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.
-The private@ list is for communication about private matters, such as
-discussion of proposed committers, proposed new PMC members, and
-communication from the Board of Directors. Do not use it for discussion
+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.
The Board of Directors will occasionally send you comments or queries,
@@ -69,7 +70,7 @@ 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.
-Projects should operate in a vendor neutral fashion. That is to say, any
+Projects should [operate in a vendor neutral
fashion](https://community.apache.org/projectIndependence.html). 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
@@ -81,7 +82,8 @@ influence over the direction of the project.
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.
+abusive behavior. PMCs may adopt a specific Code of Conduct, or simply
+follow the [ASF's general Code of
Conduct](https://apache.org/foundation/policies/conduct).
## Adding Community Members
