You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@community.apache.org by rb...@apache.org on 2023/04/25 15:12:30 UTC
[comdev-site] branch main updated: Initial prose for several more of these docs
This is an automated email from the ASF dual-hosted git repository.
rbowen 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 dc4b0a9 Initial prose for several more of these docs
new 61d16bd Merge pull request #106 from rbowen/20230424-pmc
dc4b0a9 is described below
commit dc4b0a99cfcc5b66365e8ae8bae33506aeff51c4
Author: Rich Bowen <rb...@rcbowen.com>
AuthorDate: Tue Apr 25 10:41:42 2023 -0400
Initial prose for several more of these docs
---
source/pmc/_index.md | 7 +++--
source/pmc/adding-committers.md | 2 ++
source/pmc/adding-pmc-members.md | 3 ++
source/pmc/chair.md | 64 +++++++++++++++++++++++++++++++++++++---
source/pmc/new-member.md | 49 ++++++++++++++++++++++++++++--
source/pmc/reporting.md | 48 ++++++++++++++++++++++++++++--
6 files changed, 161 insertions(+), 12 deletions(-)
diff --git a/source/pmc/_index.md b/source/pmc/_index.md
index f272834..5fc3987 100644
--- a/source/pmc/_index.md
+++ b/source/pmc/_index.md
@@ -8,6 +8,9 @@ committee for a project. This group determines the roadmap for the
project, decides who will be added as committers and PMC members, 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)
@@ -22,7 +25,7 @@ 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.
-The PMC is also responsibile for voting on releases of their project, to
+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
artifact.
@@ -32,7 +35,7 @@ artifact.
## Chair
The PMC Chair acts as the voice of the project to the board, and is
-responsibile for filing a quarterly report. They are not the project
+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.
diff --git a/source/pmc/adding-committers.md b/source/pmc/adding-committers.md
index 43f5504..6d9e56c 100644
--- a/source/pmc/adding-committers.md
+++ b/source/pmc/adding-committers.md
@@ -10,4 +10,6 @@ determining who will be added as a committer.
* Vote process
* What to do when a committer is elected
+Note: Formal policy/process document is here: https://www.apache.org/dev/pmc.html#committer-management
+
diff --git a/source/pmc/adding-pmc-members.md b/source/pmc/adding-pmc-members.md
index ef681ee..0abe0a5 100644
--- a/source/pmc/adding-pmc-members.md
+++ b/source/pmc/adding-pmc-members.md
@@ -11,4 +11,7 @@ project have a voice in the project's roadmap.
* Nominating, discussion, and voting
* What to do when a new PMC member is elected
+Note: Formal policy/process doc is here: https://www.apache.org/dev/pmc.html#newpmc
+
+
diff --git a/source/pmc/chair.md b/source/pmc/chair.md
index 938c1cd..b1acd55 100644
--- a/source/pmc/chair.md
+++ b/source/pmc/chair.md
@@ -7,8 +7,64 @@ 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.
-* Reporting
-* Selecting a new chair
- * When
- * Who
+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.
+
+The Chair should be familiar with the [assigned
+duties](https://www.apache.org/dev/pmc.html#chair) of the role.
+
+## Secretarial duties
+
+The Chair is responsible for completing the necessary "paperwork" when
+new committers and PMC members are added.
+
+See the [process for adding new
+committers](https://www.apache.org/dev/pmc.html#committer-management),
+and the [process for adding new PMC
+members](https://www.apache.org/dev/pmc.html#newpmc), for details of
+these requirements.
+
+## Reporting
+
+The Chair is also responsible for filing the quarterly project report to
+the board of directors. This is discussed in more detail
+[here](/pmc/reporting).
+
+## Moderating discussion
+
+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.
+
+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.
+
+## Selecting a new Chair
+
+A project may periodically select a new Chair.
+
+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.
+
+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.
+
+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.
+
+## See also:
+
+Newly Chairs are sent [this
+advice](https://svn.apache.org/repos/private/foundation/officers/advice-for-new-pmc-chairs.txt),
+and you're encouraged to read that thoroughly. They should also be
+familiar with [published
+policies](https://www.apache.org/dev/pmc.html#policy) for PMCs.
+
+
diff --git a/source/pmc/new-member.md b/source/pmc/new-member.md
index fba9c62..75ed1e9 100644
--- a/source/pmc/new-member.md
+++ b/source/pmc/new-member.md
@@ -5,8 +5,51 @@ title: New PMC Members
You've been invited to join a project PMC? Congratulations! What should
you do now?
-(There's some info here:
-https://svn.apache.org/repos/private/foundation/officers/advice-for-new-pmc-chairs.txt
-- but it's plain text, fairly terse, and behind a password.)
+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. This is the list on which confidential PMC business is conducted,
+and is also the channel that the Board uses to contact the PMC.
+
+See also [these tips for using the private mailing
+list](https://community.apache.org/pmc/responsibilities.html#conducting-business)
+
+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.
+
+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.
+
+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.
+
+## Read the docs
+
+There are policies and procedures for how the PMC should conduct itself.
+You are expected to [read, understand, and abide by these
+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.
+
+## Ask a lot of questions
+
+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 [beginner's mind](https://en.wikipedia.org/wiki/Shoshin) can offer
+insights that more senior members are blind to.
diff --git a/source/pmc/reporting.md b/source/pmc/reporting.md
index 6c80e6c..8a622e9 100644
--- a/source/pmc/reporting.md
+++ b/source/pmc/reporting.md
@@ -5,7 +5,49 @@ title: PMC Reporting
A PMC is required to file a report to the Board of Directors every
quarter, on a schedule determined by the Board.
-* Reporting schedule
-* What goes into a report
-* Tools to help generation of reports
+You can find your project's reporting schedule on
+[projects.apache.org](https://projects.apache.org/committees.html). 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](https://svn.apache.org/repos/private/committers/board/committee-info.txt)
+(requires password authentication).
+
+## Writing a report
+
+The report to the board is expected to contain certain sections. See the
+[detailed instructions for writing a board
+report](https://www.apache.org/foundation/board/reporting).
+
+You may (but are not required to) use the [reporter
+tool](https://reporter.apache.org) to draft your report. However, do
+**not** 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.
+
+Important things you should mention might include (but are not limited to):
+
+* Changes to technology trends that will influence the direction of your
+ project
+* A very active individual, or company, entering or exiting from the project
+* A merger or acquisition between active participant organizations in
+ your project
+* A boost or decline in your project's momentum, or popularity, that may
+ result in community changes
+
+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 *private*
+tags, as described in the formal documentation above.
+
+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.
+
+The report can be submitted via the [reporter
+tool](https://reporter.apache.org), the [agenda
+tool](https://whimsy.apache.org/board/agenda), or committed directly to
+the [subversion
+repository](https://svn.apache.org/repos/private/foundation/board).