You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@community.apache.org by gi...@apache.org on 2023/04/21 15:25:08 UTC
[comdev-site] branch asf-site updated: Updated asf-site from main at 35cb996d661f4c03dc9f117dbbf2267c7c940165
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 10e1deb Updated asf-site from main at 35cb996d661f4c03dc9f117dbbf2267c7c940165
10e1deb is described below
commit 10e1deb35354518bc94bbcfa3d5ed182d7ae54f3
Author: jenkins <bu...@apache.org>
AuthorDate: Fri Apr 21 15:25:02 2023 +0000
Updated asf-site from main at 35cb996d661f4c03dc9f117dbbf2267c7c940165
Built from https://ci-builds.apache.org/job/Community%20Development/job/site/job/main/17/
---
content/_pagefind/fragment/en_152436f.pf_fragment | Bin 0 -> 829 bytes
content/_pagefind/fragment/en_1b80a68.pf_fragment | Bin 0 -> 2313 bytes
content/_pagefind/fragment/en_56365a8.pf_fragment | Bin 0 -> 1430 bytes
content/_pagefind/fragment/en_5da3d0f.pf_fragment | Bin 0 -> 2060 bytes
content/_pagefind/fragment/en_6683c69.pf_fragment | Bin 0 -> 855 bytes
content/_pagefind/fragment/en_69d5efd.pf_fragment | Bin 0 -> 2623 bytes
content/_pagefind/fragment/en_745d45a.pf_fragment | Bin 2461 -> 0 bytes
content/_pagefind/fragment/en_bfee618.pf_fragment | Bin 0 -> 752 bytes
content/_pagefind/fragment/en_c8daf54.pf_fragment | Bin 0 -> 1585 bytes
content/_pagefind/fragment/en_cb12e4e.pf_fragment | Bin 0 -> 792 bytes
content/_pagefind/fragment/en_e4aa188.pf_fragment | Bin 0 -> 812 bytes
content/_pagefind/index/en_0bb3126.pf_index | Bin 0 -> 42011 bytes
content/_pagefind/index/en_83ce65e.pf_index | Bin 14323 -> 0 bytes
content/_pagefind/index/en_a3ce4a5.pf_index | Bin 0 -> 25507 bytes
content/_pagefind/index/en_a586beb.pf_index | Bin 43706 -> 0 bytes
content/_pagefind/index/en_a6dab55.pf_index | Bin 0 -> 38274 bytes
content/_pagefind/index/en_c0ea44c.pf_index | Bin 39384 -> 0 bytes
content/_pagefind/pagefind-entry.json | 2 +-
content/_pagefind/pagefind.en_61f6b24176.pf_meta | Bin 0 -> 587 bytes
content/_pagefind/pagefind.en_925345e760.pf_meta | Bin 538 -> 0 bytes
.../index.html => contributor-ladder.html} | 172 ++++++++++++---------
content/contributors/index.html | 11 +-
content/contributors/index.xml | 10 ++
.../{index.html => mailing-lists.html} | 119 ++++++--------
content/index.xml | 81 ++++++++++
content/{contributors/index.html => pmc.html} | 122 ++++++---------
.../index.html => pmc/adding-committers.html} | 90 +++--------
.../index.html => pmc/adding-pmc-members.html} | 91 +++--------
.../{contributors/index.html => pmc/chair.html} | 95 +++---------
content/pmc/index.xml | 71 +++++++++
.../index.html => pmc/new-member.html} | 90 +++--------
.../index.html => pmc/reporting.html} | 89 +++--------
.../index.html => pmc/responsibilities.html} | 150 +++++++++---------
content/sitemap.xml | 29 +++-
34 files changed, 577 insertions(+), 645 deletions(-)
diff --git a/content/_pagefind/fragment/en_152436f.pf_fragment b/content/_pagefind/fragment/en_152436f.pf_fragment
new file mode 100644
index 0000000..918c06d
Binary files /dev/null and b/content/_pagefind/fragment/en_152436f.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_1b80a68.pf_fragment b/content/_pagefind/fragment/en_1b80a68.pf_fragment
new file mode 100644
index 0000000..17fc497
Binary files /dev/null and b/content/_pagefind/fragment/en_1b80a68.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_56365a8.pf_fragment b/content/_pagefind/fragment/en_56365a8.pf_fragment
new file mode 100644
index 0000000..032efa1
Binary files /dev/null and b/content/_pagefind/fragment/en_56365a8.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_5da3d0f.pf_fragment b/content/_pagefind/fragment/en_5da3d0f.pf_fragment
new file mode 100644
index 0000000..e11f99f
Binary files /dev/null and b/content/_pagefind/fragment/en_5da3d0f.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_6683c69.pf_fragment b/content/_pagefind/fragment/en_6683c69.pf_fragment
new file mode 100644
index 0000000..80f44a3
Binary files /dev/null and b/content/_pagefind/fragment/en_6683c69.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_69d5efd.pf_fragment b/content/_pagefind/fragment/en_69d5efd.pf_fragment
new file mode 100644
index 0000000..8e1295e
Binary files /dev/null and b/content/_pagefind/fragment/en_69d5efd.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_745d45a.pf_fragment b/content/_pagefind/fragment/en_745d45a.pf_fragment
deleted file mode 100644
index 5b0488d..0000000
Binary files a/content/_pagefind/fragment/en_745d45a.pf_fragment and /dev/null differ
diff --git a/content/_pagefind/fragment/en_bfee618.pf_fragment b/content/_pagefind/fragment/en_bfee618.pf_fragment
new file mode 100644
index 0000000..9e2cc92
Binary files /dev/null and b/content/_pagefind/fragment/en_bfee618.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_c8daf54.pf_fragment b/content/_pagefind/fragment/en_c8daf54.pf_fragment
new file mode 100644
index 0000000..9c17e7f
Binary files /dev/null and b/content/_pagefind/fragment/en_c8daf54.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_cb12e4e.pf_fragment b/content/_pagefind/fragment/en_cb12e4e.pf_fragment
new file mode 100644
index 0000000..a388e2f
Binary files /dev/null and b/content/_pagefind/fragment/en_cb12e4e.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_e4aa188.pf_fragment b/content/_pagefind/fragment/en_e4aa188.pf_fragment
new file mode 100644
index 0000000..4bf8f40
Binary files /dev/null and b/content/_pagefind/fragment/en_e4aa188.pf_fragment differ
diff --git a/content/_pagefind/index/en_0bb3126.pf_index b/content/_pagefind/index/en_0bb3126.pf_index
new file mode 100644
index 0000000..c471dc2
Binary files /dev/null and b/content/_pagefind/index/en_0bb3126.pf_index differ
diff --git a/content/_pagefind/index/en_83ce65e.pf_index b/content/_pagefind/index/en_83ce65e.pf_index
deleted file mode 100644
index e1a67d5..0000000
Binary files a/content/_pagefind/index/en_83ce65e.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_a3ce4a5.pf_index b/content/_pagefind/index/en_a3ce4a5.pf_index
new file mode 100644
index 0000000..3a3b25c
Binary files /dev/null and b/content/_pagefind/index/en_a3ce4a5.pf_index differ
diff --git a/content/_pagefind/index/en_a586beb.pf_index b/content/_pagefind/index/en_a586beb.pf_index
deleted file mode 100644
index 557937e..0000000
Binary files a/content/_pagefind/index/en_a586beb.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_a6dab55.pf_index b/content/_pagefind/index/en_a6dab55.pf_index
new file mode 100644
index 0000000..d640a83
Binary files /dev/null and b/content/_pagefind/index/en_a6dab55.pf_index differ
diff --git a/content/_pagefind/index/en_c0ea44c.pf_index b/content/_pagefind/index/en_c0ea44c.pf_index
deleted file mode 100644
index fb809e9..0000000
Binary files a/content/_pagefind/index/en_c0ea44c.pf_index and /dev/null differ
diff --git a/content/_pagefind/pagefind-entry.json b/content/_pagefind/pagefind-entry.json
index a15ea89..ecd3b78 100644
--- a/content/_pagefind/pagefind-entry.json
+++ b/content/_pagefind/pagefind-entry.json
@@ -1 +1 @@
-{"version":"0.12.0","languages":{"en":{"hash":"en_925345e760","wasm":"en","page_count":53}}}
\ No newline at end of file
+{"version":"0.12.0","languages":{"en":{"hash":"en_61f6b24176","wasm":"en","page_count":62}}}
\ No newline at end of file
diff --git a/content/_pagefind/pagefind.en_61f6b24176.pf_meta b/content/_pagefind/pagefind.en_61f6b24176.pf_meta
new file mode 100644
index 0000000..a15e4c7
Binary files /dev/null and b/content/_pagefind/pagefind.en_61f6b24176.pf_meta differ
diff --git a/content/_pagefind/pagefind.en_925345e760.pf_meta b/content/_pagefind/pagefind.en_925345e760.pf_meta
deleted file mode 100644
index d9f3355..0000000
Binary files a/content/_pagefind/pagefind.en_925345e760.pf_meta and /dev/null differ
diff --git a/content/contributors/index.html b/content/contributor-ladder.html
similarity index 59%
copy from content/contributors/index.html
copy to content/contributor-ladder.html
index 88de78d..7951653 100644
--- a/content/contributors/index.html
+++ b/content/contributor-ladder.html
@@ -6,13 +6,16 @@
<meta name="description" content="Apache Community Development"/>
<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="Contributing to the Apache Software Foundation" />
-<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
-<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/contributors/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+ <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 ¶ 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="" />
+<meta property="article:modified_time" content="2023-04-20T12:01:52-04:00" /><meta property="og:site_name" content="Apache Community Development" />
- <title>Apache Community Development - Contributing to the Apache Software Foundation</title>
+
+ <title>Apache Community Development - ASF Contributor Ladder</title>
<link rel="shortcut icon" href="images/favicon.ico">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
@@ -170,87 +173,108 @@
- <li class="breadcrumb-item"><a href='/contributors'>Contributors</a></li>
+ <li class="breadcrumb-item"><a href='/contributor-ladder.html'>Contributor ladder</a></li>
-
-
-
</ol>
</nav>
<hr>
- <p>This page is for people who are reasonably
-comfortable with open source development models but need a helping hand finding
-their way around the Apache Software Foundation and our way of developing software
-(commonly called “The Apache Way”). For those wishing to start from
-the very beginning, we have a <a href="/newcomers/index.html">newcomers page</a>.</p>
-<h1 id="project-independence-and-policies">Project Independence And Policies <a class="headerlink" title="Permalink" href="#project-independence-and-policies">¶</a></h1>
-<p>While not all ASF projects practice all aspects of the Apache Way in the same way, there are a number of rules that Apache
-projects must follow – things like complying with PMC
-<a href="https://www.apache.org/legal/release-policy.html">release voting</a>, <a href="https://www.apache.org/legal/">legal policy</a>, <a href="https://www.apache.org/foundation/marks/">brand policy</a>,
-using <a href="https://www.apache.org/dev/#mail">mailing lists</a>, etc., which are <a href="https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different">documented in various places</a>.</p>
-<p>One of these invariant rules is that projects are managed
-independently of any commercial interests. The goal is to create an
-environment in which all participants are equal and thus have an equal
-opportunity to contribute to and benefit from our software, regardless
-of motivation or financial objectives. This is discussed in more detail
-in our document <a href="/projectIndependence.html">Project Independence</a>.</p>
-<h1 id="moving-from-contributor-to-committer">Moving From Contributor to Committer <a class="headerlink" title="Permalink" href="#moving-from-contributor-to-committer">¶</a></h1>
-<p>Anyone can be a contributor to an Apache project. Being a contributor simply means
-that you take an interest in the project and contribute in some way, ranging from asking
-sensible questions (which document the project and provide feedback to developers)
-through to providing new features as code patches.</p>
-<p>If you become a valuable contributor to the project, the Project Management Committee (PMC) may invite you to become
-a <em>committer</em>. At the ASF, a committer is someone who is
-committed to a particular project. It brings with it the privilege of write access to
-the project repository and resources. In many projects, committers may also be invited
-to be part of the core group within the project that ensures the project’s vitality, the PMC.
-In a few projects only a subset of committers who have earned even more merit are invited to be a part of the PMC.</p>
-<p>One thing that is sometimes hard to understand, when you are new to the open
-development process used at the ASF, is that we value the community more than
-the code. A strong and healthy community will be respectful and be a fun and
-rewarding place. More importantly, a diverse and healthy community can
-continue to support the code over the longer term, even as individual
-contributors come and go from the field.</p>
-<p>In particular, we have some <a href="/contributors/etiquette">etiquette and behavior expectations</a> when
-you work with Apache communities.</p>
-<p>See also this <a href="/contributors/becomingacommitter.html">detailed advice for how to become a committer</a></p>
-<h2 id="contributing-a-project---copdoc">Contributing A Project - CoPDoC <a class="headerlink" title="Permalink" href="#contributing-a-project---copdoc">¶</a></h2>
-<p>The foundations of an Apache project and how the community contributes to it are
-sometimes referred to by the acronym CoPDoC:</p>
+
+ <p>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.</p>
<ul>
-<li>(Co)mmunity - one must interact with others, and share vision and knowledge</li>
-<li>(P)roject - a clear vision and consensus are needed</li>
-<li>(Do)cumentation - without it, the stuff remains only in the minds of the authors</li>
-<li>(C)ode - discussion goes nowhere without code</li>
+<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>
-<h2 id="anyone-can-become-a-committer">Anyone Can Become A Committer <a class="headerlink" title="Permalink" href="#anyone-can-become-a-committer">¶</a></h2>
-<p>There is nothing at the Apache Software Foundation that says you must write code
-in order to be a committer. Anyone who is supportive of the community and works
-in any of the CoPDoC areas is a likely candidate for committership.</p>
-<p>Apache strives to be meritocratic. That is, once someone has contributed sufficiently to
-any area of CoPDoC they can be voted in as a committer. Being a committer does
-not necessarily mean you commit code; it means you are committed to the project
-and are productively contributing to its success.</p>
-<p>One of the key contributions people can make to the community is through the
-support of a wide user base by assisting users on the user list, writing user-oriented docs and ensuring the developers understand the user viewpoint.
-A main idea behind being a committer is the ability to be a mentor and to work
-cooperatively with your peers.</p>
-<p>Some users of a project’s software become committers in their own right. Some will test code,
-some will write documentation, some will do bug triage and some will write code.</p>
-<p>For more details see “<a href="https://www.apache.org/foundation/how-it-works.html">How it works</a>”. You can also make
-<a href="/newbiefaq.html#websitecms">suggestions for how to update this website</a> you’re reading right now!</p>
-<h2 id="questions-and-feedback">Questions and Feedback <a class="headerlink" title="Permalink" href="#questions-and-feedback">¶</a></h2>
-<p>You can provide feedback and ask questions by subscribing to our mailing
-list: send an email to
-<a href="mailto:dev-subscribe@community.apache.org">dev-subscribe@community.apache.org</a>. Once subscribed, you can send your mail to
-<a href="mailto:dev@community.apache.org">dev@community.apache.org</a>.</p>
+<h2 id="user">User <a class="headerlink" title="Permalink" href="#user">¶</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>
+<p>We encourage you to join the user mailing list to ask questions, and
+make suggestions. Members of the project are there to help out when you
+run into problems. You can find this list (or lists) by looking under the
+project name on <a href="https://lists.apache.org">lists.apache.org</a>.</p>
+<p>As a user, you’re expected to abide by the project’s <a href="https://www.apache.org/foundation/policies/conduct">code of
+conduct</a>, so that
+interactions are polite, friendly, and helpful.</p>
+<p>As you become a power user of the project, you may consider becoming a
+contributor.</p>
+<h2 id="contributor">Contributor <a class="headerlink" title="Permalink" href="#contributor">¶</a></h2>
+<p>While most people think of open source contributors as being coders,
+there are a wider variety of ways that you can contribute to a project.</p>
+<p>Most users’ first contribution will be to open a ticket on the project’s
+issue tracker, or to answer a less experienced user’s questions. These
+actions help shape the future direction of the project, and are
+important contributions.</p>
+<p>We encourage you to join the project’s developer mailing list at this
+time, to engage with the discussions about the direction that the project
+is taking. You can find this list (or lists) by looking under the
+project name on <a href="https://lists.apache.org">lists.apache.org</a>.</p>
+<p>Other contributions may include design, promotion, documentation
+improvements, events, and many other things.</p>
+<p><a href="/contributors/">See more about being a contributor</a>.</p>
+<p>As you become more involved with contributing to the project, you may
+want to work towards <a href="/contributors/becomingacommitter">becoming a
+committer</a>.</p>
+<h2 id="committer">Committer <a class="headerlink" title="Permalink" href="#committer">¶</a></h2>
+<p>After making a number of contributions to a project, its PMC may invite you
+to become a committer. Note that the criteria for inviting a contributor
+to become a committer will vary greatly from one project to another.</p>
+<p>Once you have been invited to become a committer, and have accepted this
+invitation, you are authorized to commit changes directly to the
+project’s source code repository. Note, however, that different projects
+may have different social norms around committing changes.</p>
+<p>Broadly referred to as CTR (Commit Then Review) and RTC (Review Then
+Commit), the exact mechanisms may vary. For example, you may be
+authorized to commit documentation changes without approval, while code
+changes may be submitted as a pull request, for other committers to
+review and approve before they are merged.</p>
+<p><a href="/committers">See more information about being a committer</a>.</p>
+<h2 id="pmc-member">PMC Member <a class="headerlink" title="Permalink" href="#pmc-member">¶</a></h2>
+<p>After being a committer for some time, the project’s PMC may invite you to become a member
+of the project’s Project Management Committee. This group acts as the
+steering committee for the project, making decisions about the project’s
+road map, what features will be added, and other decisions around the
+project.</p>
+<p>The PMC <em>should</em> be conducting all of these conversations on the public
+developer mailing list(s), in the view of the entire community. A PMC
+also has a private mailing list, which is for discussion of topics such
+as the addition of new committers and PMC members, and any other
+sensitive topics.</p>
+<p><a href="/pmc">See more information about being a PMC member</a>.</p>
+<h2 id="foundation-member">Foundation Member <a class="headerlink" title="Permalink" href="#foundation-member">¶</a></h2>
+<p>When someone has been involved at the ASF for a while, they may be
+invited, by the membership, to become a member of the Foundation. This entitles them to vote
+for the Board of Directors, to participate in the members’ mailing list,
+and to invite others to become Foundation members.</p>
+<p><a href="https://apache.org/foundation/governance/members.html">See more about being a Foundation
+member</a></p>
+<h2 id="officers-of-the-foundation">Officers of the Foundation <a class="headerlink" title="Permalink" href="#officers-of-the-foundation">¶</a></h2>
+<p>Officers of the Foundation are responsible for various aspects of the
+day-to-day operation of the Foundation. You can see how these roles are
+broken down in the <a href="https://whimsy.apache.org/foundation/orgchart/board">Foundation organization
+chart</a>.</p>
+<h2 id="board-of-directors">Board of Directors <a class="headerlink" title="Permalink" href="#board-of-directors">¶</a></h2>
+<p>The members of the ASF elect the members of the Board annually for
+one-year terms.</p>
+<p>The Board of Directors is responsible for the governance of the
+Foundation. This includes overseeing projects, to ensure they are
+behaving in accordance with ASF policies and norms.</p>
+<p>The Board also delegates much of the day-to-day operation of the
+Foundation to the President, and various officers and committees.</p>
+<p>You can see the current composition of the Board on the <a href="https://apache.org/foundation/board/">Board
+website</a>.</p>
-
</div>
</main>
diff --git a/content/contributors/index.html b/content/contributors/index.html
index 88de78d..66daacb 100644
--- a/content/contributors/index.html
+++ b/content/contributors/index.html
@@ -188,7 +188,7 @@ comfortable with open source development models but need a helping hand finding
their way around the Apache Software Foundation and our way of developing software
(commonly called “The Apache Way”). For those wishing to start from
the very beginning, we have a <a href="/newcomers/index.html">newcomers page</a>.</p>
-<h1 id="project-independence-and-policies">Project Independence And Policies <a class="headerlink" title="Permalink" href="#project-independence-and-policies">¶</a></h1>
+<h2 id="project-independence-and-policies">Project Independence And Policies <a class="headerlink" title="Permalink" href="#project-independence-and-policies">¶</a></h2>
<p>While not all ASF projects practice all aspects of the Apache Way in the same way, there are a number of rules that Apache
projects must follow – things like complying with PMC
<a href="https://www.apache.org/legal/release-policy.html">release voting</a>, <a href="https://www.apache.org/legal/">legal policy</a>, <a href="https://www.apache.org/foundation/marks/">brand policy</a>,
@@ -199,7 +199,14 @@ environment in which all participants are equal and thus have an equal
opportunity to contribute to and benefit from our software, regardless
of motivation or financial objectives. This is discussed in more detail
in our document <a href="/projectIndependence.html">Project Independence</a>.</p>
-<h1 id="moving-from-contributor-to-committer">Moving From Contributor to Committer <a class="headerlink" title="Permalink" href="#moving-from-contributor-to-committer">¶</a></h1>
+<h2 id="communication-on-mailing-lists">Communication on mailing lists <a class="headerlink" title="Permalink" href="#communication-on-mailing-lists">¶</a></h2>
+<p>Development at the ASF has traditionally been done on mailing lists.
+This is not merely because we’ve always done it this way, but is an
+intentional decision, in order to include a wider community than who
+happens to be on your Slack channel at a particular moment.</p>
+<p>This is why we say, at the ASF, <a href="/contributors/mailing-lists"><strong>If it didn’t happen on the mailing
+list, it didn’t happen</strong></a>.</p>
+<h2 id="moving-from-contributor-to-committer">Moving From Contributor to Committer <a class="headerlink" title="Permalink" href="#moving-from-contributor-to-committer">¶</a></h2>
<p>Anyone can be a contributor to an Apache project. Being a contributor simply means
that you take an interest in the project and contribute in some way, ranging from asking
sensible questions (which document the project and provide feedback to developers)
diff --git a/content/contributors/index.xml b/content/contributors/index.xml
index 4449e91..42b2914 100644
--- a/content/contributors/index.xml
+++ b/content/contributors/index.xml
@@ -25,5 +25,15 @@ Code of Conduct &para; The ASF has adopted a Code of Conduct which covers in
<description>Read the mailing list Contribute code (and other things) End user support Documentation Review PRs and tickets Be visible Test, and vote on releases (non-binding) Give talks Disclaimer &para; Nothing in this post should be construed as a guarantee. You can do everything listed here, for years, and still not become a committer. This is because the decision is made by individuals on the project PMC, who do things for their own reasons.</description>
</item>
+ <item>
+ <title>Mailing lists</title>
+ <link>https://community.apache.org/contributors/mailing-lists.html</link>
+ <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+
+ <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&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.</description>
+ </item>
+
</channel>
</rss>
diff --git a/content/contributors/index.html b/content/contributors/mailing-lists.html
similarity index 62%
copy from content/contributors/index.html
copy to content/contributors/mailing-lists.html
index 88de78d..4233fa9 100644
--- a/content/contributors/index.html
+++ b/content/contributors/mailing-lists.html
@@ -6,13 +6,16 @@
<meta name="description" content="Apache Community Development"/>
<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="Contributing to the Apache Software Foundation" />
-<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
-<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/contributors/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+ <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’ve always done it that way, but is an intentional decision for the health and sustainability of our communities.
+Inclusion and transparency ¶ 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." />
+<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" />
+<meta property="article:modified_time" content="2023-04-20T12:01:52-04:00" /><meta property="og:site_name" content="Apache Community Development" />
- <title>Apache Community Development - Contributing to the Apache Software Foundation</title>
+
+ <title>Apache Community Development - Mailing lists</title>
<link rel="shortcut icon" href="images/favicon.ico">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
@@ -176,6 +179,9 @@
+ <li class="breadcrumb-item"><a href='/contributors/mailing-lists.html'>Mailing lists</a></li>
+
+
</ol>
</nav>
@@ -183,74 +189,47 @@
<hr>
- <p>This page is for people who are reasonably
-comfortable with open source development models but need a helping hand finding
-their way around the Apache Software Foundation and our way of developing software
-(commonly called “The Apache Way”). For those wishing to start from
-the very beginning, we have a <a href="/newcomers/index.html">newcomers page</a>.</p>
-<h1 id="project-independence-and-policies">Project Independence And Policies <a class="headerlink" title="Permalink" href="#project-independence-and-policies">¶</a></h1>
-<p>While not all ASF projects practice all aspects of the Apache Way in the same way, there are a number of rules that Apache
-projects must follow – things like complying with PMC
-<a href="https://www.apache.org/legal/release-policy.html">release voting</a>, <a href="https://www.apache.org/legal/">legal policy</a>, <a href="https://www.apache.org/foundation/marks/">brand policy</a>,
-using <a href="https://www.apache.org/dev/#mail">mailing lists</a>, etc., which are <a href="https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different">documented in various places</a>.</p>
-<p>One of these invariant rules is that projects are managed
-independently of any commercial interests. The goal is to create an
-environment in which all participants are equal and thus have an equal
-opportunity to contribute to and benefit from our software, regardless
-of motivation or financial objectives. This is discussed in more detail
-in our document <a href="/projectIndependence.html">Project Independence</a>.</p>
-<h1 id="moving-from-contributor-to-committer">Moving From Contributor to Committer <a class="headerlink" title="Permalink" href="#moving-from-contributor-to-committer">¶</a></h1>
-<p>Anyone can be a contributor to an Apache project. Being a contributor simply means
-that you take an interest in the project and contribute in some way, ranging from asking
-sensible questions (which document the project and provide feedback to developers)
-through to providing new features as code patches.</p>
-<p>If you become a valuable contributor to the project, the Project Management Committee (PMC) may invite you to become
-a <em>committer</em>. At the ASF, a committer is someone who is
-committed to a particular project. It brings with it the privilege of write access to
-the project repository and resources. In many projects, committers may also be invited
-to be part of the core group within the project that ensures the project’s vitality, the PMC.
-In a few projects only a subset of committers who have earned even more merit are invited to be a part of the PMC.</p>
-<p>One thing that is sometimes hard to understand, when you are new to the open
-development process used at the ASF, is that we value the community more than
-the code. A strong and healthy community will be respectful and be a fun and
-rewarding place. More importantly, a diverse and healthy community can
-continue to support the code over the longer term, even as individual
-contributors come and go from the field.</p>
-<p>In particular, we have some <a href="/contributors/etiquette">etiquette and behavior expectations</a> when
-you work with Apache communities.</p>
-<p>See also this <a href="/contributors/becomingacommitter.html">detailed advice for how to become a committer</a></p>
-<h2 id="contributing-a-project---copdoc">Contributing A Project - CoPDoC <a class="headerlink" title="Permalink" href="#contributing-a-project---copdoc">¶</a></h2>
-<p>The foundations of an Apache project and how the community contributes to it are
-sometimes referred to by the acronym CoPDoC:</p>
+
+ <p>The ASF has a long tradition of using mailing lists as the primary
+communication format in projects. This is not merely because we’ve
+always done it that way, but is an intentional decision for the health
+and sustainability of our communities.</p>
+<h2 id="inclusion-and-transparency">Inclusion and transparency <a class="headerlink" title="Permalink" href="#inclusion-and-transparency">¶</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
+synchronous communication platforms (IRC, Slack, Discord, etc.) benefit
+only those who are online, and in the channel, at the time of the
+conversation.</p>
+<p>Mailing lists also allow archiving, so that decisions can be understood
+by people who were not there at the time - what was decided, why, and by
+whom - even years after the fact.</p>
+<p>Synchronous communication platforms are great for end-user support,
+where an answer is needed quickly, and asking for clarification can be
+done real-time. It’s also good for social interactions, and for quick
+brainstorming.</p>
+<p>But decisions, and important technical discussions, should be taken back
+to the mailing list so that the whole community can participate.</p>
+<p>This is why we say, at the ASF, <strong>If it didn’t happen on the mailing
+list, it didn’t happen.</strong></p>
+<h2 id="mailing-list-etiquette">Mailing list etiquette <a class="headerlink" title="Permalink" href="#mailing-list-etiquette">¶</a></h2>
+<p><em>To Be Written</em></p>
<ul>
-<li>(Co)mmunity - one must interact with others, and share vision and knowledge</li>
-<li>(P)roject - a clear vision and consensus are needed</li>
-<li>(Do)cumentation - without it, the stuff remains only in the minds of the authors</li>
-<li>(C)ode - discussion goes nowhere without code</li>
+<li>Meaningful subject lines</li>
+<li>Inline vs top-posting</li>
+<li>HTML and “rich text” messages</li>
+<li>Clear language, use of colloquialisms and metaphor, etc. (writing for a
+diverse audience)</li>
</ul>
-<h2 id="anyone-can-become-a-committer">Anyone Can Become A Committer <a class="headerlink" title="Permalink" href="#anyone-can-become-a-committer">¶</a></h2>
-<p>There is nothing at the Apache Software Foundation that says you must write code
-in order to be a committer. Anyone who is supportive of the community and works
-in any of the CoPDoC areas is a likely candidate for committership.</p>
-<p>Apache strives to be meritocratic. That is, once someone has contributed sufficiently to
-any area of CoPDoC they can be voted in as a committer. Being a committer does
-not necessarily mean you commit code; it means you are committed to the project
-and are productively contributing to its success.</p>
-<p>One of the key contributions people can make to the community is through the
-support of a wide user base by assisting users on the user list, writing user-oriented docs and ensuring the developers understand the user viewpoint.
-A main idea behind being a committer is the ability to be a mentor and to work
-cooperatively with your peers.</p>
-<p>Some users of a project’s software become committers in their own right. Some will test code,
-some will write documentation, some will do bug triage and some will write code.</p>
-<p>For more details see “<a href="https://www.apache.org/foundation/how-it-works.html">How it works</a>”. You can also make
-<a href="/newbiefaq.html#websitecms">suggestions for how to update this website</a> you’re reading right now!</p>
-<h2 id="questions-and-feedback">Questions and Feedback <a class="headerlink" title="Permalink" href="#questions-and-feedback">¶</a></h2>
-<p>You can provide feedback and ask questions by subscribing to our mailing
-list: send an email to
-<a href="mailto:dev-subscribe@community.apache.org">dev-subscribe@community.apache.org</a>. Once subscribed, you can send your mail to
-<a href="mailto:dev@community.apache.org">dev@community.apache.org</a>.</p>
+<h2 id="mailing-list-configuration">Mailing list configuration <a class="headerlink" title="Permalink" href="#mailing-list-configuration">¶</a></h2>
+<p>Modern software development tools, including GitHub, your various ticket
+trackers, and CI tools, generate a lot of email. This can make your
+development mailing list difficult to approach for new contributors, as
+they appear as a wall of identical subject lines. This makes it hard for
+beginners to break into your project, and find out what’s going on.</p>
+<p>Here’s some configuration tips for your mailing lists to cut through the
+noise and make your project’s lists more approachable and welcoming.</p>
+<p><em>To Be Written</em></p>
-
</div>
</main>
diff --git a/content/index.xml b/content/index.xml
index 6547cfc..9fdcdad 100644
--- a/content/index.xml
+++ b/content/index.xml
@@ -36,6 +36,26 @@ Governance of Provisional Top Level Project &para; Provisional Top Level Pro
Overview &para; The goals of this maturity model are to describe how Apache projects operate in a concise and high-level way, and to provide a basic framework that projects may choose to use to evaluate themselves.</description>
</item>
+ <item>
+ <title>Adding Committers</title>
+ <link>https://community.apache.org/pmc/adding-committers.html</link>
+ <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+
+ <guid>https://community.apache.org/pmc/adding-committers.html</guid>
+ <description>The addition of new committers is essential to the long-term sustainability of an open source project. The PMC is responsible for determining who will be added as a committer.
+Who should be a committer? Vote process What to do when a committer is elected </description>
+ </item>
+
+ <item>
+ <title>Adding PMC members</title>
+ <link>https://community.apache.org/pmc/adding-pmc-members.html</link>
+ <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+
+ <guid>https://community.apache.org/pmc/adding-pmc-members.html</guid>
+ <description>The PMC is responsible for identifying individuals who should be added to the PMC. This is a critical part of the long-term health and sustainability of a project, and ensures that contributors to the project have a voice in the project&rsquo;s roadmap.
+Who should be a PMC member? Nominating, discussion, and voting What to do when a new PMC member is elected </description>
+ </item>
+
<item>
<title>Apache Conferences Calendar</title>
<link>https://community.apache.org/calendars/conferences.html</link>
@@ -102,6 +122,16 @@ In our recent community survey, we heard from a lot of you that you want more in
Code of Conduct &para; The ASF has adopted a Code of Conduct which covers interactions in all the online spaces that ASF projects use - email, issue trackers, wikis, websites, IRC, and the like. ASF projects are made up of volunteers, and we work to ensure that all productive contributions are welcomed.</description>
</item>
+ <item>
+ <title>ASF Contributor Ladder</title>
+ <link>https://community.apache.org/contributor-ladder.html</link>
+ <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+
+ <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 &para; Everything that we do in an ASF project is for the user.</description>
+ </item>
+
<item>
<title>Becoming a committer</title>
<link>https://community.apache.org/contributors/becomingacommitter.html</link>
@@ -266,6 +296,16 @@ Finding Speakers &para; If you are organising an event and looking for speak
Listing yourself as a potential speaker &para; To list yourself as someone interested in being an Apache speaker, there are two steps.</description>
</item>
+ <item>
+ <title>Mailing lists</title>
+ <link>https://community.apache.org/contributors/mailing-lists.html</link>
+ <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+
+ <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&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.</description>
+ </item>
+
<item>
<title>May 2017 Community Newsletter</title>
<link>https://community.apache.org/newsletter/2017-05.html</link>
@@ -345,6 +385,17 @@ Each project has a different approach to managing new committers. This page desc
Guidelines for assessing new candidates for committership Ability to work cooperatively with peers.</description>
</item>
+ <item>
+ <title>New PMC Members</title>
+ <link>https://community.apache.org/pmc/new-member.html</link>
+ <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?
+(There&rsquo;s some info here: https://svn.apache.org/repos/private/foundation/officers/advice-for-new-pmc-chairs.txt
+but it&rsquo;s plain text, fairly terse, and behind a password.) </description>
+ </item>
+
<item>
<title>Pilot Mentoring Programme with India ICFOSS</title>
<link>https://community.apache.org/history/mentoringprogramme-icfoss-pilot.html</link>
@@ -356,6 +407,36 @@ The ASF has been participating in many mentoring initiatives, and it&rsquo;s
The mentoring programme is not here to teach you to write documentation or code.</description>
</item>
+ <item>
+ <title>PMC Chair</title>
+ <link>https://community.apache.org/pmc/chair.html</link>
+ <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 responsibile 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 </description>
+ </item>
+
+ <item>
+ <title>PMC Reporting</title>
+ <link>https://community.apache.org/pmc/reporting.html</link>
+ <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.
+Reporting schedule What goes into a report Tools to help generation of reports </description>
+ </item>
+
+ <item>
+ <title>PMC Responsibilities</title>
+ <link>https://community.apache.org/pmc/responsibilities.html</link>
+ <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 Ensuring project health Adding community members Reporting 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>
+ </item>
+
<item>
<title>Project Independence</title>
<link>https://community.apache.org/projectIndependence.html</link>
diff --git a/content/contributors/index.html b/content/pmc.html
similarity index 62%
copy from content/contributors/index.html
copy to content/pmc.html
index 88de78d..85d352f 100644
--- a/content/contributors/index.html
+++ b/content/pmc.html
@@ -6,13 +6,13 @@
<meta name="description" content="Apache Community Development"/>
<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="Contributing to the Apache Software Foundation" />
+ <meta property="og:title" content="Project Management Committees" />
<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/contributors/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+<meta property="og:url" content="https://community.apache.org/pmc.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
- <title>Apache Community Development - Contributing to the Apache Software Foundation</title>
+ <title>Apache Community Development - Project Management Committees</title>
<link rel="shortcut icon" href="images/favicon.ico">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
@@ -170,85 +170,65 @@
- <li class="breadcrumb-item"><a href='/contributors'>Contributors</a></li>
+ <li class="breadcrumb-item"><a href='/pmc.html'>Pmc</a></li>
-
-
-
</ol>
</nav>
<hr>
- <p>This page is for people who are reasonably
-comfortable with open source development models but need a helping hand finding
-their way around the Apache Software Foundation and our way of developing software
-(commonly called “The Apache Way”). For those wishing to start from
-the very beginning, we have a <a href="/newcomers/index.html">newcomers page</a>.</p>
-<h1 id="project-independence-and-policies">Project Independence And Policies <a class="headerlink" title="Permalink" href="#project-independence-and-policies">¶</a></h1>
-<p>While not all ASF projects practice all aspects of the Apache Way in the same way, there are a number of rules that Apache
-projects must follow – things like complying with PMC
-<a href="https://www.apache.org/legal/release-policy.html">release voting</a>, <a href="https://www.apache.org/legal/">legal policy</a>, <a href="https://www.apache.org/foundation/marks/">brand policy</a>,
-using <a href="https://www.apache.org/dev/#mail">mailing lists</a>, etc., which are <a href="https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different">documented in various places</a>.</p>
-<p>One of these invariant rules is that projects are managed
-independently of any commercial interests. The goal is to create an
-environment in which all participants are equal and thus have an equal
-opportunity to contribute to and benefit from our software, regardless
-of motivation or financial objectives. This is discussed in more detail
-in our document <a href="/projectIndependence.html">Project Independence</a>.</p>
-<h1 id="moving-from-contributor-to-committer">Moving From Contributor to Committer <a class="headerlink" title="Permalink" href="#moving-from-contributor-to-committer">¶</a></h1>
-<p>Anyone can be a contributor to an Apache project. Being a contributor simply means
-that you take an interest in the project and contribute in some way, ranging from asking
-sensible questions (which document the project and provide feedback to developers)
-through to providing new features as code patches.</p>
-<p>If you become a valuable contributor to the project, the Project Management Committee (PMC) may invite you to become
-a <em>committer</em>. At the ASF, a committer is someone who is
-committed to a particular project. It brings with it the privilege of write access to
-the project repository and resources. In many projects, committers may also be invited
-to be part of the core group within the project that ensures the project’s vitality, the PMC.
-In a few projects only a subset of committers who have earned even more merit are invited to be a part of the PMC.</p>
-<p>One thing that is sometimes hard to understand, when you are new to the open
-development process used at the ASF, is that we value the community more than
-the code. A strong and healthy community will be respectful and be a fun and
-rewarding place. More importantly, a diverse and healthy community can
-continue to support the code over the longer term, even as individual
-contributors come and go from the field.</p>
-<p>In particular, we have some <a href="/contributors/etiquette">etiquette and behavior expectations</a> when
-you work with Apache communities.</p>
-<p>See also this <a href="/contributors/becomingacommitter.html">detailed advice for how to become a committer</a></p>
-<h2 id="contributing-a-project---copdoc">Contributing A Project - CoPDoC <a class="headerlink" title="Permalink" href="#contributing-a-project---copdoc">¶</a></h2>
-<p>The foundations of an Apache project and how the community contributes to it are
-sometimes referred to by the acronym CoPDoC:</p>
+ <p>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
+reports quarterly to the Board of Directors.</p>
<ul>
-<li>(Co)mmunity - one must interact with others, and share vision and knowledge</li>
-<li>(P)roject - a clear vision and consensus are needed</li>
-<li>(Do)cumentation - without it, the stuff remains only in the minds of the authors</li>
-<li>(C)ode - discussion goes nowhere without code</li>
+<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="#reporting">Reporting</a></li>
+<li><a href="#adding-committers">Adding committers</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>
-<h2 id="anyone-can-become-a-committer">Anyone Can Become A Committer <a class="headerlink" title="Permalink" href="#anyone-can-become-a-committer">¶</a></h2>
-<p>There is nothing at the Apache Software Foundation that says you must write code
-in order to be a committer. Anyone who is supportive of the community and works
-in any of the CoPDoC areas is a likely candidate for committership.</p>
-<p>Apache strives to be meritocratic. That is, once someone has contributed sufficiently to
-any area of CoPDoC they can be voted in as a committer. Being a committer does
-not necessarily mean you commit code; it means you are committed to the project
-and are productively contributing to its success.</p>
-<p>One of the key contributions people can make to the community is through the
-support of a wide user base by assisting users on the user list, writing user-oriented docs and ensuring the developers understand the user viewpoint.
-A main idea behind being a committer is the ability to be a mentor and to work
-cooperatively with your peers.</p>
-<p>Some users of a project’s software become committers in their own right. Some will test code,
-some will write documentation, some will do bug triage and some will write code.</p>
-<p>For more details see “<a href="https://www.apache.org/foundation/how-it-works.html">How it works</a>”. You can also make
-<a href="/newbiefaq.html#websitecms">suggestions for how to update this website</a> you’re reading right now!</p>
-<h2 id="questions-and-feedback">Questions and Feedback <a class="headerlink" title="Permalink" href="#questions-and-feedback">¶</a></h2>
-<p>You can provide feedback and ask questions by subscribing to our mailing
-list: send an email to
-<a href="mailto:dev-subscribe@community.apache.org">dev-subscribe@community.apache.org</a>. Once subscribed, you can send your mail to
-<a href="mailto:dev@community.apache.org">dev@community.apache.org</a>.</p>
+<h2 id="pmc-responsibilities">PMC Responsibilities <a class="headerlink" title="Permalink" href="#pmc-responsibilities">¶</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
+in community-friendly ways.</p>
+<p>The PMC is also responsibile for voting on releases of their project, to
+ensure that each release is tested, and is an official ASF release
+artifact.</p>
+<p><a href="/pmc/responsibilities">Read more about PMC responsibilities</a></p>
+<h2 id="chair">Chair <a class="headerlink" title="Permalink" href="#chair">¶</a></h2>
+<p>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
+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><a href="/pmc/chair">Read more about the PMC Chair</a></p>
+<h2 id="voting">Voting <a class="headerlink" title="Permalink" href="#voting">¶</a></h2>
+<p>While most actions of a project are decided by discussion and consensus,
+there are a number of situations in which a vote is necessary. You can
+read more about voting on the <a href="https://apache.org/foundation/voting.html">ASF main
+website</a>.</p>
+<h2 id="reporting">Reporting <a class="headerlink" title="Permalink" href="#reporting">¶</a></h2>
+<p>A PMC is required to file a report to the Board of Directors every
+quarter, on a schedule determined by the Board. <a href="/pmc/reporting">Read more about what
+goes into a PMC report</a>.</p>
+<h2 id="adding-committers">Adding committers <a class="headerlink" title="Permalink" href="#adding-committers">¶</a></h2>
+<p>The addition of committers is essential to the long-term
+sustainability of an open source project. The PMC is responsible for
+determining who will be added as a committer. <a href="/pmc/adding-committers">Read more about how new
+committers are added to a project</a>.</p>
+<h2 id="adding-pmc-members">Adding PMC members <a class="headerlink" title="Permalink" href="#adding-pmc-members">¶</a></h2>
+<p>The PMC members identify project participants who they want to be
+members of the PMC. <a href="/pmc/adding-pmc-members">Read more about the process of adding new PMC
+members</a>.</p>
+<h2 id="what-to-do-as-a-new-member">What to do as a new member <a class="headerlink" title="Permalink" href="#what-to-do-as-a-new-member">¶</a></h2>
+<p>If you’ve just been added as a new PMC member, there’s a number of
+things that you’ll need to do to be an effective part of the PMC. <a href="/pmc/new-member">Read
+more about getting started as a new PMC member</a>.</p>
diff --git a/content/contributors/index.html b/content/pmc/adding-committers.html
similarity index 61%
copy from content/contributors/index.html
copy to content/pmc/adding-committers.html
index 88de78d..c5a58cc 100644
--- a/content/contributors/index.html
+++ b/content/pmc/adding-committers.html
@@ -6,13 +6,16 @@
<meta name="description" content="Apache Community Development"/>
<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="Contributing to the Apache Software Foundation" />
-<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
-<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/contributors/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+ <meta property="og:title" content="Adding Committers" />
+<meta property="og:description" content="The addition of new committers is essential to the long-term sustainability of an open source project. The PMC is responsible for determining who will be added as a committer.
+Who should be a committer? Vote process What to do when a committer is elected " />
+<meta property="og:type" content="article" />
+<meta property="og:url" content="https://community.apache.org/pmc/adding-committers.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="pmc" />
+<meta property="article:modified_time" content="2023-04-15T22:01:34-04:00" /><meta property="og:site_name" content="Apache Community Development" />
- <title>Apache Community Development - Contributing to the Apache Software Foundation</title>
+
+ <title>Apache Community Development - Adding Committers</title>
<link rel="shortcut icon" href="images/favicon.ico">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
@@ -170,12 +173,15 @@
- <li class="breadcrumb-item"><a href='/contributors'>Contributors</a></li>
+ <li class="breadcrumb-item"><a href='/pmc'>Pmc</a></li>
+ <li class="breadcrumb-item"><a href='/pmc/adding-committers.html'>Adding committers</a></li>
+
+
</ol>
</nav>
@@ -183,74 +189,16 @@
<hr>
- <p>This page is for people who are reasonably
-comfortable with open source development models but need a helping hand finding
-their way around the Apache Software Foundation and our way of developing software
-(commonly called “The Apache Way”). For those wishing to start from
-the very beginning, we have a <a href="/newcomers/index.html">newcomers page</a>.</p>
-<h1 id="project-independence-and-policies">Project Independence And Policies <a class="headerlink" title="Permalink" href="#project-independence-and-policies">¶</a></h1>
-<p>While not all ASF projects practice all aspects of the Apache Way in the same way, there are a number of rules that Apache
-projects must follow – things like complying with PMC
-<a href="https://www.apache.org/legal/release-policy.html">release voting</a>, <a href="https://www.apache.org/legal/">legal policy</a>, <a href="https://www.apache.org/foundation/marks/">brand policy</a>,
-using <a href="https://www.apache.org/dev/#mail">mailing lists</a>, etc., which are <a href="https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different">documented in various places</a>.</p>
-<p>One of these invariant rules is that projects are managed
-independently of any commercial interests. The goal is to create an
-environment in which all participants are equal and thus have an equal
-opportunity to contribute to and benefit from our software, regardless
-of motivation or financial objectives. This is discussed in more detail
-in our document <a href="/projectIndependence.html">Project Independence</a>.</p>
-<h1 id="moving-from-contributor-to-committer">Moving From Contributor to Committer <a class="headerlink" title="Permalink" href="#moving-from-contributor-to-committer">¶</a></h1>
-<p>Anyone can be a contributor to an Apache project. Being a contributor simply means
-that you take an interest in the project and contribute in some way, ranging from asking
-sensible questions (which document the project and provide feedback to developers)
-through to providing new features as code patches.</p>
-<p>If you become a valuable contributor to the project, the Project Management Committee (PMC) may invite you to become
-a <em>committer</em>. At the ASF, a committer is someone who is
-committed to a particular project. It brings with it the privilege of write access to
-the project repository and resources. In many projects, committers may also be invited
-to be part of the core group within the project that ensures the project’s vitality, the PMC.
-In a few projects only a subset of committers who have earned even more merit are invited to be a part of the PMC.</p>
-<p>One thing that is sometimes hard to understand, when you are new to the open
-development process used at the ASF, is that we value the community more than
-the code. A strong and healthy community will be respectful and be a fun and
-rewarding place. More importantly, a diverse and healthy community can
-continue to support the code over the longer term, even as individual
-contributors come and go from the field.</p>
-<p>In particular, we have some <a href="/contributors/etiquette">etiquette and behavior expectations</a> when
-you work with Apache communities.</p>
-<p>See also this <a href="/contributors/becomingacommitter.html">detailed advice for how to become a committer</a></p>
-<h2 id="contributing-a-project---copdoc">Contributing A Project - CoPDoC <a class="headerlink" title="Permalink" href="#contributing-a-project---copdoc">¶</a></h2>
-<p>The foundations of an Apache project and how the community contributes to it are
-sometimes referred to by the acronym CoPDoC:</p>
+
+ <p>The addition of new committers is essential to the long-term
+sustainability of an open source project. The PMC is responsible for
+determining who will be added as a committer.</p>
<ul>
-<li>(Co)mmunity - one must interact with others, and share vision and knowledge</li>
-<li>(P)roject - a clear vision and consensus are needed</li>
-<li>(Do)cumentation - without it, the stuff remains only in the minds of the authors</li>
-<li>(C)ode - discussion goes nowhere without code</li>
+<li>Who should be a committer?</li>
+<li>Vote process</li>
+<li>What to do when a committer is elected</li>
</ul>
-<h2 id="anyone-can-become-a-committer">Anyone Can Become A Committer <a class="headerlink" title="Permalink" href="#anyone-can-become-a-committer">¶</a></h2>
-<p>There is nothing at the Apache Software Foundation that says you must write code
-in order to be a committer. Anyone who is supportive of the community and works
-in any of the CoPDoC areas is a likely candidate for committership.</p>
-<p>Apache strives to be meritocratic. That is, once someone has contributed sufficiently to
-any area of CoPDoC they can be voted in as a committer. Being a committer does
-not necessarily mean you commit code; it means you are committed to the project
-and are productively contributing to its success.</p>
-<p>One of the key contributions people can make to the community is through the
-support of a wide user base by assisting users on the user list, writing user-oriented docs and ensuring the developers understand the user viewpoint.
-A main idea behind being a committer is the ability to be a mentor and to work
-cooperatively with your peers.</p>
-<p>Some users of a project’s software become committers in their own right. Some will test code,
-some will write documentation, some will do bug triage and some will write code.</p>
-<p>For more details see “<a href="https://www.apache.org/foundation/how-it-works.html">How it works</a>”. You can also make
-<a href="/newbiefaq.html#websitecms">suggestions for how to update this website</a> you’re reading right now!</p>
-<h2 id="questions-and-feedback">Questions and Feedback <a class="headerlink" title="Permalink" href="#questions-and-feedback">¶</a></h2>
-<p>You can provide feedback and ask questions by subscribing to our mailing
-list: send an email to
-<a href="mailto:dev-subscribe@community.apache.org">dev-subscribe@community.apache.org</a>. Once subscribed, you can send your mail to
-<a href="mailto:dev@community.apache.org">dev@community.apache.org</a>.</p>
-
</div>
</main>
diff --git a/content/contributors/index.html b/content/pmc/adding-pmc-members.html
similarity index 61%
copy from content/contributors/index.html
copy to content/pmc/adding-pmc-members.html
index 88de78d..622f703 100644
--- a/content/contributors/index.html
+++ b/content/pmc/adding-pmc-members.html
@@ -6,13 +6,16 @@
<meta name="description" content="Apache Community Development"/>
<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="Contributing to the Apache Software Foundation" />
-<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
-<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/contributors/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+ <meta property="og:title" content="Adding PMC members" />
+<meta property="og:description" content="The PMC is responsible for identifying individuals who should be added to the PMC. This is a critical part of the long-term health and sustainability of a project, and ensures that contributors to the project have a voice in the project’s roadmap.
+Who should be a PMC member? Nominating, discussion, and voting What to do when a new PMC member is elected " />
+<meta property="og:type" content="article" />
+<meta property="og:url" content="https://community.apache.org/pmc/adding-pmc-members.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="pmc" />
+<meta property="article:modified_time" content="2023-04-15T22:01:34-04:00" /><meta property="og:site_name" content="Apache Community Development" />
- <title>Apache Community Development - Contributing to the Apache Software Foundation</title>
+
+ <title>Apache Community Development - Adding PMC members</title>
<link rel="shortcut icon" href="images/favicon.ico">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
@@ -170,12 +173,15 @@
- <li class="breadcrumb-item"><a href='/contributors'>Contributors</a></li>
+ <li class="breadcrumb-item"><a href='/pmc'>Pmc</a></li>
+ <li class="breadcrumb-item"><a href='/pmc/adding-pmc-members.html'>Adding pmc members</a></li>
+
+
</ol>
</nav>
@@ -183,74 +189,17 @@
<hr>
- <p>This page is for people who are reasonably
-comfortable with open source development models but need a helping hand finding
-their way around the Apache Software Foundation and our way of developing software
-(commonly called “The Apache Way”). For those wishing to start from
-the very beginning, we have a <a href="/newcomers/index.html">newcomers page</a>.</p>
-<h1 id="project-independence-and-policies">Project Independence And Policies <a class="headerlink" title="Permalink" href="#project-independence-and-policies">¶</a></h1>
-<p>While not all ASF projects practice all aspects of the Apache Way in the same way, there are a number of rules that Apache
-projects must follow – things like complying with PMC
-<a href="https://www.apache.org/legal/release-policy.html">release voting</a>, <a href="https://www.apache.org/legal/">legal policy</a>, <a href="https://www.apache.org/foundation/marks/">brand policy</a>,
-using <a href="https://www.apache.org/dev/#mail">mailing lists</a>, etc., which are <a href="https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different">documented in various places</a>.</p>
-<p>One of these invariant rules is that projects are managed
-independently of any commercial interests. The goal is to create an
-environment in which all participants are equal and thus have an equal
-opportunity to contribute to and benefit from our software, regardless
-of motivation or financial objectives. This is discussed in more detail
-in our document <a href="/projectIndependence.html">Project Independence</a>.</p>
-<h1 id="moving-from-contributor-to-committer">Moving From Contributor to Committer <a class="headerlink" title="Permalink" href="#moving-from-contributor-to-committer">¶</a></h1>
-<p>Anyone can be a contributor to an Apache project. Being a contributor simply means
-that you take an interest in the project and contribute in some way, ranging from asking
-sensible questions (which document the project and provide feedback to developers)
-through to providing new features as code patches.</p>
-<p>If you become a valuable contributor to the project, the Project Management Committee (PMC) may invite you to become
-a <em>committer</em>. At the ASF, a committer is someone who is
-committed to a particular project. It brings with it the privilege of write access to
-the project repository and resources. In many projects, committers may also be invited
-to be part of the core group within the project that ensures the project’s vitality, the PMC.
-In a few projects only a subset of committers who have earned even more merit are invited to be a part of the PMC.</p>
-<p>One thing that is sometimes hard to understand, when you are new to the open
-development process used at the ASF, is that we value the community more than
-the code. A strong and healthy community will be respectful and be a fun and
-rewarding place. More importantly, a diverse and healthy community can
-continue to support the code over the longer term, even as individual
-contributors come and go from the field.</p>
-<p>In particular, we have some <a href="/contributors/etiquette">etiquette and behavior expectations</a> when
-you work with Apache communities.</p>
-<p>See also this <a href="/contributors/becomingacommitter.html">detailed advice for how to become a committer</a></p>
-<h2 id="contributing-a-project---copdoc">Contributing A Project - CoPDoC <a class="headerlink" title="Permalink" href="#contributing-a-project---copdoc">¶</a></h2>
-<p>The foundations of an Apache project and how the community contributes to it are
-sometimes referred to by the acronym CoPDoC:</p>
+
+ <p>The PMC is responsible for identifying individuals who should be added
+to the PMC. This is a critical part of the long-term health and
+sustainability of a project, and ensures that contributors to the
+project have a voice in the project’s roadmap.</p>
<ul>
-<li>(Co)mmunity - one must interact with others, and share vision and knowledge</li>
-<li>(P)roject - a clear vision and consensus are needed</li>
-<li>(Do)cumentation - without it, the stuff remains only in the minds of the authors</li>
-<li>(C)ode - discussion goes nowhere without code</li>
+<li>Who should be a PMC member?</li>
+<li>Nominating, discussion, and voting</li>
+<li>What to do when a new PMC member is elected</li>
</ul>
-<h2 id="anyone-can-become-a-committer">Anyone Can Become A Committer <a class="headerlink" title="Permalink" href="#anyone-can-become-a-committer">¶</a></h2>
-<p>There is nothing at the Apache Software Foundation that says you must write code
-in order to be a committer. Anyone who is supportive of the community and works
-in any of the CoPDoC areas is a likely candidate for committership.</p>
-<p>Apache strives to be meritocratic. That is, once someone has contributed sufficiently to
-any area of CoPDoC they can be voted in as a committer. Being a committer does
-not necessarily mean you commit code; it means you are committed to the project
-and are productively contributing to its success.</p>
-<p>One of the key contributions people can make to the community is through the
-support of a wide user base by assisting users on the user list, writing user-oriented docs and ensuring the developers understand the user viewpoint.
-A main idea behind being a committer is the ability to be a mentor and to work
-cooperatively with your peers.</p>
-<p>Some users of a project’s software become committers in their own right. Some will test code,
-some will write documentation, some will do bug triage and some will write code.</p>
-<p>For more details see “<a href="https://www.apache.org/foundation/how-it-works.html">How it works</a>”. You can also make
-<a href="/newbiefaq.html#websitecms">suggestions for how to update this website</a> you’re reading right now!</p>
-<h2 id="questions-and-feedback">Questions and Feedback <a class="headerlink" title="Permalink" href="#questions-and-feedback">¶</a></h2>
-<p>You can provide feedback and ask questions by subscribing to our mailing
-list: send an email to
-<a href="mailto:dev-subscribe@community.apache.org">dev-subscribe@community.apache.org</a>. Once subscribed, you can send your mail to
-<a href="mailto:dev@community.apache.org">dev@community.apache.org</a>.</p>
-
</div>
</main>
diff --git a/content/contributors/index.html b/content/pmc/chair.html
similarity index 61%
copy from content/contributors/index.html
copy to content/pmc/chair.html
index 88de78d..05f456f 100644
--- a/content/contributors/index.html
+++ b/content/pmc/chair.html
@@ -6,13 +6,16 @@
<meta name="description" content="Apache Community Development"/>
<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="Contributing to the Apache Software Foundation" />
-<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
-<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/contributors/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+ <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 responsibile 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 " />
+<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/aceu19_1.jpg"/><meta property="article:section" content="pmc" />
+<meta property="article:modified_time" content="2023-04-20T08:27:41-04:00" /><meta property="og:site_name" content="Apache Community Development" />
- <title>Apache Community Development - Contributing to the Apache Software Foundation</title>
+
+ <title>Apache Community Development - PMC Chair</title>
<link rel="shortcut icon" href="images/favicon.ico">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
@@ -170,12 +173,15 @@
- <li class="breadcrumb-item"><a href='/contributors'>Contributors</a></li>
+ <li class="breadcrumb-item"><a href='/pmc'>Pmc</a></li>
+ <li class="breadcrumb-item"><a href='/pmc/chair.html'>Chair</a></li>
+
+
</ol>
</nav>
@@ -183,74 +189,21 @@
<hr>
- <p>This page is for people who are reasonably
-comfortable with open source development models but need a helping hand finding
-their way around the Apache Software Foundation and our way of developing software
-(commonly called “The Apache Way”). For those wishing to start from
-the very beginning, we have a <a href="/newcomers/index.html">newcomers page</a>.</p>
-<h1 id="project-independence-and-policies">Project Independence And Policies <a class="headerlink" title="Permalink" href="#project-independence-and-policies">¶</a></h1>
-<p>While not all ASF projects practice all aspects of the Apache Way in the same way, there are a number of rules that Apache
-projects must follow – things like complying with PMC
-<a href="https://www.apache.org/legal/release-policy.html">release voting</a>, <a href="https://www.apache.org/legal/">legal policy</a>, <a href="https://www.apache.org/foundation/marks/">brand policy</a>,
-using <a href="https://www.apache.org/dev/#mail">mailing lists</a>, etc., which are <a href="https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different">documented in various places</a>.</p>
-<p>One of these invariant rules is that projects are managed
-independently of any commercial interests. The goal is to create an
-environment in which all participants are equal and thus have an equal
-opportunity to contribute to and benefit from our software, regardless
-of motivation or financial objectives. This is discussed in more detail
-in our document <a href="/projectIndependence.html">Project Independence</a>.</p>
-<h1 id="moving-from-contributor-to-committer">Moving From Contributor to Committer <a class="headerlink" title="Permalink" href="#moving-from-contributor-to-committer">¶</a></h1>
-<p>Anyone can be a contributor to an Apache project. Being a contributor simply means
-that you take an interest in the project and contribute in some way, ranging from asking
-sensible questions (which document the project and provide feedback to developers)
-through to providing new features as code patches.</p>
-<p>If you become a valuable contributor to the project, the Project Management Committee (PMC) may invite you to become
-a <em>committer</em>. At the ASF, a committer is someone who is
-committed to a particular project. It brings with it the privilege of write access to
-the project repository and resources. In many projects, committers may also be invited
-to be part of the core group within the project that ensures the project’s vitality, the PMC.
-In a few projects only a subset of committers who have earned even more merit are invited to be a part of the PMC.</p>
-<p>One thing that is sometimes hard to understand, when you are new to the open
-development process used at the ASF, is that we value the community more than
-the code. A strong and healthy community will be respectful and be a fun and
-rewarding place. More importantly, a diverse and healthy community can
-continue to support the code over the longer term, even as individual
-contributors come and go from the field.</p>
-<p>In particular, we have some <a href="/contributors/etiquette">etiquette and behavior expectations</a> when
-you work with Apache communities.</p>
-<p>See also this <a href="/contributors/becomingacommitter.html">detailed advice for how to become a committer</a></p>
-<h2 id="contributing-a-project---copdoc">Contributing A Project - CoPDoC <a class="headerlink" title="Permalink" href="#contributing-a-project---copdoc">¶</a></h2>
-<p>The foundations of an Apache project and how the community contributes to it are
-sometimes referred to by the acronym CoPDoC:</p>
+
+ <p>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
+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>
<ul>
-<li>(Co)mmunity - one must interact with others, and share vision and knowledge</li>
-<li>(P)roject - a clear vision and consensus are needed</li>
-<li>(Do)cumentation - without it, the stuff remains only in the minds of the authors</li>
-<li>(C)ode - discussion goes nowhere without code</li>
+<li>Reporting</li>
+<li>Selecting a new chair
+<ul>
+<li>When</li>
+<li>Who</li>
+</ul>
+</li>
</ul>
-<h2 id="anyone-can-become-a-committer">Anyone Can Become A Committer <a class="headerlink" title="Permalink" href="#anyone-can-become-a-committer">¶</a></h2>
-<p>There is nothing at the Apache Software Foundation that says you must write code
-in order to be a committer. Anyone who is supportive of the community and works
-in any of the CoPDoC areas is a likely candidate for committership.</p>
-<p>Apache strives to be meritocratic. That is, once someone has contributed sufficiently to
-any area of CoPDoC they can be voted in as a committer. Being a committer does
-not necessarily mean you commit code; it means you are committed to the project
-and are productively contributing to its success.</p>
-<p>One of the key contributions people can make to the community is through the
-support of a wide user base by assisting users on the user list, writing user-oriented docs and ensuring the developers understand the user viewpoint.
-A main idea behind being a committer is the ability to be a mentor and to work
-cooperatively with your peers.</p>
-<p>Some users of a project’s software become committers in their own right. Some will test code,
-some will write documentation, some will do bug triage and some will write code.</p>
-<p>For more details see “<a href="https://www.apache.org/foundation/how-it-works.html">How it works</a>”. You can also make
-<a href="/newbiefaq.html#websitecms">suggestions for how to update this website</a> you’re reading right now!</p>
-<h2 id="questions-and-feedback">Questions and Feedback <a class="headerlink" title="Permalink" href="#questions-and-feedback">¶</a></h2>
-<p>You can provide feedback and ask questions by subscribing to our mailing
-list: send an email to
-<a href="mailto:dev-subscribe@community.apache.org">dev-subscribe@community.apache.org</a>. Once subscribed, you can send your mail to
-<a href="mailto:dev@community.apache.org">dev@community.apache.org</a>.</p>
-
</div>
</main>
diff --git a/content/pmc/index.xml b/content/pmc/index.xml
new file mode 100644
index 0000000..f6f37bb
--- /dev/null
+++ b/content/pmc/index.xml
@@ -0,0 +1,71 @@
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
+ <channel>
+ <title>Project Management Committees on Apache Comdev</title>
+ <link>https://community.apache.org/pmc.html</link>
+ <description>Recent content in Project Management Committees on Apache Comdev</description>
+ <generator>Hugo -- gohugo.io</generator>
+ <language>en</language><atom:link href="https://community.apache.org/pmc/index.xml" rel="self" type="application/rss+xml" />
+ <item>
+ <title>Adding Committers</title>
+ <link>https://community.apache.org/pmc/adding-committers.html</link>
+ <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+
+ <guid>https://community.apache.org/pmc/adding-committers.html</guid>
+ <description>The addition of new committers is essential to the long-term sustainability of an open source project. The PMC is responsible for determining who will be added as a committer.
+Who should be a committer? Vote process What to do when a committer is elected </description>
+ </item>
+
+ <item>
+ <title>Adding PMC members</title>
+ <link>https://community.apache.org/pmc/adding-pmc-members.html</link>
+ <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+
+ <guid>https://community.apache.org/pmc/adding-pmc-members.html</guid>
+ <description>The PMC is responsible for identifying individuals who should be added to the PMC. This is a critical part of the long-term health and sustainability of a project, and ensures that contributors to the project have a voice in the project&rsquo;s roadmap.
+Who should be a PMC member? Nominating, discussion, and voting What to do when a new PMC member is elected </description>
+ </item>
+
+ <item>
+ <title>New PMC Members</title>
+ <link>https://community.apache.org/pmc/new-member.html</link>
+ <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?
+(There&rsquo;s some info here: https://svn.apache.org/repos/private/foundation/officers/advice-for-new-pmc-chairs.txt
+but it&rsquo;s plain text, fairly terse, and behind a password.) </description>
+ </item>
+
+ <item>
+ <title>PMC Chair</title>
+ <link>https://community.apache.org/pmc/chair.html</link>
+ <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 responsibile 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 </description>
+ </item>
+
+ <item>
+ <title>PMC Reporting</title>
+ <link>https://community.apache.org/pmc/reporting.html</link>
+ <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.
+Reporting schedule What goes into a report Tools to help generation of reports </description>
+ </item>
+
+ <item>
+ <title>PMC Responsibilities</title>
+ <link>https://community.apache.org/pmc/responsibilities.html</link>
+ <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 Ensuring project health Adding community members Reporting 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>
+ </item>
+
+ </channel>
+</rss>
diff --git a/content/contributors/index.html b/content/pmc/new-member.html
similarity index 61%
copy from content/contributors/index.html
copy to content/pmc/new-member.html
index 88de78d..1e46911 100644
--- a/content/contributors/index.html
+++ b/content/pmc/new-member.html
@@ -6,13 +6,17 @@
<meta name="description" content="Apache Community Development"/>
<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="Contributing to the Apache Software Foundation" />
-<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
-<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/contributors/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+ <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?
+(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.) " />
+<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/aceu19_1.jpg"/><meta property="article:section" content="pmc" />
+<meta property="article:modified_time" content="2023-04-15T22:01:34-04:00" /><meta property="og:site_name" content="Apache Community Development" />
- <title>Apache Community Development - Contributing to the Apache Software Foundation</title>
+
+ <title>Apache Community Development - New PMC Members</title>
<link rel="shortcut icon" href="images/favicon.ico">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
@@ -170,12 +174,15 @@
- <li class="breadcrumb-item"><a href='/contributors'>Contributors</a></li>
+ <li class="breadcrumb-item"><a href='/pmc'>Pmc</a></li>
+ <li class="breadcrumb-item"><a href='/pmc/new-member.html'>New member</a></li>
+
+
</ol>
</nav>
@@ -183,74 +190,15 @@
<hr>
- <p>This page is for people who are reasonably
-comfortable with open source development models but need a helping hand finding
-their way around the Apache Software Foundation and our way of developing software
-(commonly called “The Apache Way”). For those wishing to start from
-the very beginning, we have a <a href="/newcomers/index.html">newcomers page</a>.</p>
-<h1 id="project-independence-and-policies">Project Independence And Policies <a class="headerlink" title="Permalink" href="#project-independence-and-policies">¶</a></h1>
-<p>While not all ASF projects practice all aspects of the Apache Way in the same way, there are a number of rules that Apache
-projects must follow – things like complying with PMC
-<a href="https://www.apache.org/legal/release-policy.html">release voting</a>, <a href="https://www.apache.org/legal/">legal policy</a>, <a href="https://www.apache.org/foundation/marks/">brand policy</a>,
-using <a href="https://www.apache.org/dev/#mail">mailing lists</a>, etc., which are <a href="https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different">documented in various places</a>.</p>
-<p>One of these invariant rules is that projects are managed
-independently of any commercial interests. The goal is to create an
-environment in which all participants are equal and thus have an equal
-opportunity to contribute to and benefit from our software, regardless
-of motivation or financial objectives. This is discussed in more detail
-in our document <a href="/projectIndependence.html">Project Independence</a>.</p>
-<h1 id="moving-from-contributor-to-committer">Moving From Contributor to Committer <a class="headerlink" title="Permalink" href="#moving-from-contributor-to-committer">¶</a></h1>
-<p>Anyone can be a contributor to an Apache project. Being a contributor simply means
-that you take an interest in the project and contribute in some way, ranging from asking
-sensible questions (which document the project and provide feedback to developers)
-through to providing new features as code patches.</p>
-<p>If you become a valuable contributor to the project, the Project Management Committee (PMC) may invite you to become
-a <em>committer</em>. At the ASF, a committer is someone who is
-committed to a particular project. It brings with it the privilege of write access to
-the project repository and resources. In many projects, committers may also be invited
-to be part of the core group within the project that ensures the project’s vitality, the PMC.
-In a few projects only a subset of committers who have earned even more merit are invited to be a part of the PMC.</p>
-<p>One thing that is sometimes hard to understand, when you are new to the open
-development process used at the ASF, is that we value the community more than
-the code. A strong and healthy community will be respectful and be a fun and
-rewarding place. More importantly, a diverse and healthy community can
-continue to support the code over the longer term, even as individual
-contributors come and go from the field.</p>
-<p>In particular, we have some <a href="/contributors/etiquette">etiquette and behavior expectations</a> when
-you work with Apache communities.</p>
-<p>See also this <a href="/contributors/becomingacommitter.html">detailed advice for how to become a committer</a></p>
-<h2 id="contributing-a-project---copdoc">Contributing A Project - CoPDoC <a class="headerlink" title="Permalink" href="#contributing-a-project---copdoc">¶</a></h2>
-<p>The foundations of an Apache project and how the community contributes to it are
-sometimes referred to by the acronym CoPDoC:</p>
+
+ <p>You’ve been invited to join a project PMC? Congratulations! What should
+you do now?</p>
+<p>(There’s some info 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>(Co)mmunity - one must interact with others, and share vision and knowledge</li>
-<li>(P)roject - a clear vision and consensus are needed</li>
-<li>(Do)cumentation - without it, the stuff remains only in the minds of the authors</li>
-<li>(C)ode - discussion goes nowhere without code</li>
+<li>but it’s plain text, fairly terse, and behind a password.)</li>
</ul>
-<h2 id="anyone-can-become-a-committer">Anyone Can Become A Committer <a class="headerlink" title="Permalink" href="#anyone-can-become-a-committer">¶</a></h2>
-<p>There is nothing at the Apache Software Foundation that says you must write code
-in order to be a committer. Anyone who is supportive of the community and works
-in any of the CoPDoC areas is a likely candidate for committership.</p>
-<p>Apache strives to be meritocratic. That is, once someone has contributed sufficiently to
-any area of CoPDoC they can be voted in as a committer. Being a committer does
-not necessarily mean you commit code; it means you are committed to the project
-and are productively contributing to its success.</p>
-<p>One of the key contributions people can make to the community is through the
-support of a wide user base by assisting users on the user list, writing user-oriented docs and ensuring the developers understand the user viewpoint.
-A main idea behind being a committer is the ability to be a mentor and to work
-cooperatively with your peers.</p>
-<p>Some users of a project’s software become committers in their own right. Some will test code,
-some will write documentation, some will do bug triage and some will write code.</p>
-<p>For more details see “<a href="https://www.apache.org/foundation/how-it-works.html">How it works</a>”. You can also make
-<a href="/newbiefaq.html#websitecms">suggestions for how to update this website</a> you’re reading right now!</p>
-<h2 id="questions-and-feedback">Questions and Feedback <a class="headerlink" title="Permalink" href="#questions-and-feedback">¶</a></h2>
-<p>You can provide feedback and ask questions by subscribing to our mailing
-list: send an email to
-<a href="mailto:dev-subscribe@community.apache.org">dev-subscribe@community.apache.org</a>. Once subscribed, you can send your mail to
-<a href="mailto:dev@community.apache.org">dev@community.apache.org</a>.</p>
-
</div>
</main>
diff --git a/content/contributors/index.html b/content/pmc/reporting.html
similarity index 61%
copy from content/contributors/index.html
copy to content/pmc/reporting.html
index 88de78d..609a06e 100644
--- a/content/contributors/index.html
+++ b/content/pmc/reporting.html
@@ -6,13 +6,16 @@
<meta name="description" content="Apache Community Development"/>
<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="Contributing to the Apache Software Foundation" />
-<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
-<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/contributors/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+ <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.
+Reporting schedule What goes into a report Tools to help generation of reports " />
+<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/aceu19_1.jpg"/><meta property="article:section" content="pmc" />
+<meta property="article:modified_time" content="2023-04-15T22:01:34-04:00" /><meta property="og:site_name" content="Apache Community Development" />
- <title>Apache Community Development - Contributing to the Apache Software Foundation</title>
+
+ <title>Apache Community Development - PMC Reporting</title>
<link rel="shortcut icon" href="images/favicon.ico">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
@@ -170,12 +173,15 @@
- <li class="breadcrumb-item"><a href='/contributors'>Contributors</a></li>
+ <li class="breadcrumb-item"><a href='/pmc'>Pmc</a></li>
+ <li class="breadcrumb-item"><a href='/pmc/reporting.html'>Reporting</a></li>
+
+
</ol>
</nav>
@@ -183,74 +189,15 @@
<hr>
- <p>This page is for people who are reasonably
-comfortable with open source development models but need a helping hand finding
-their way around the Apache Software Foundation and our way of developing software
-(commonly called “The Apache Way”). For those wishing to start from
-the very beginning, we have a <a href="/newcomers/index.html">newcomers page</a>.</p>
-<h1 id="project-independence-and-policies">Project Independence And Policies <a class="headerlink" title="Permalink" href="#project-independence-and-policies">¶</a></h1>
-<p>While not all ASF projects practice all aspects of the Apache Way in the same way, there are a number of rules that Apache
-projects must follow – things like complying with PMC
-<a href="https://www.apache.org/legal/release-policy.html">release voting</a>, <a href="https://www.apache.org/legal/">legal policy</a>, <a href="https://www.apache.org/foundation/marks/">brand policy</a>,
-using <a href="https://www.apache.org/dev/#mail">mailing lists</a>, etc., which are <a href="https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different">documented in various places</a>.</p>
-<p>One of these invariant rules is that projects are managed
-independently of any commercial interests. The goal is to create an
-environment in which all participants are equal and thus have an equal
-opportunity to contribute to and benefit from our software, regardless
-of motivation or financial objectives. This is discussed in more detail
-in our document <a href="/projectIndependence.html">Project Independence</a>.</p>
-<h1 id="moving-from-contributor-to-committer">Moving From Contributor to Committer <a class="headerlink" title="Permalink" href="#moving-from-contributor-to-committer">¶</a></h1>
-<p>Anyone can be a contributor to an Apache project. Being a contributor simply means
-that you take an interest in the project and contribute in some way, ranging from asking
-sensible questions (which document the project and provide feedback to developers)
-through to providing new features as code patches.</p>
-<p>If you become a valuable contributor to the project, the Project Management Committee (PMC) may invite you to become
-a <em>committer</em>. At the ASF, a committer is someone who is
-committed to a particular project. It brings with it the privilege of write access to
-the project repository and resources. In many projects, committers may also be invited
-to be part of the core group within the project that ensures the project’s vitality, the PMC.
-In a few projects only a subset of committers who have earned even more merit are invited to be a part of the PMC.</p>
-<p>One thing that is sometimes hard to understand, when you are new to the open
-development process used at the ASF, is that we value the community more than
-the code. A strong and healthy community will be respectful and be a fun and
-rewarding place. More importantly, a diverse and healthy community can
-continue to support the code over the longer term, even as individual
-contributors come and go from the field.</p>
-<p>In particular, we have some <a href="/contributors/etiquette">etiquette and behavior expectations</a> when
-you work with Apache communities.</p>
-<p>See also this <a href="/contributors/becomingacommitter.html">detailed advice for how to become a committer</a></p>
-<h2 id="contributing-a-project---copdoc">Contributing A Project - CoPDoC <a class="headerlink" title="Permalink" href="#contributing-a-project---copdoc">¶</a></h2>
-<p>The foundations of an Apache project and how the community contributes to it are
-sometimes referred to by the acronym CoPDoC:</p>
+
+ <p>A PMC is required to file a report to the Board of Directors every
+quarter, on a schedule determined by the Board.</p>
<ul>
-<li>(Co)mmunity - one must interact with others, and share vision and knowledge</li>
-<li>(P)roject - a clear vision and consensus are needed</li>
-<li>(Do)cumentation - without it, the stuff remains only in the minds of the authors</li>
-<li>(C)ode - discussion goes nowhere without code</li>
+<li>Reporting schedule</li>
+<li>What goes into a report</li>
+<li>Tools to help generation of reports</li>
</ul>
-<h2 id="anyone-can-become-a-committer">Anyone Can Become A Committer <a class="headerlink" title="Permalink" href="#anyone-can-become-a-committer">¶</a></h2>
-<p>There is nothing at the Apache Software Foundation that says you must write code
-in order to be a committer. Anyone who is supportive of the community and works
-in any of the CoPDoC areas is a likely candidate for committership.</p>
-<p>Apache strives to be meritocratic. That is, once someone has contributed sufficiently to
-any area of CoPDoC they can be voted in as a committer. Being a committer does
-not necessarily mean you commit code; it means you are committed to the project
-and are productively contributing to its success.</p>
-<p>One of the key contributions people can make to the community is through the
-support of a wide user base by assisting users on the user list, writing user-oriented docs and ensuring the developers understand the user viewpoint.
-A main idea behind being a committer is the ability to be a mentor and to work
-cooperatively with your peers.</p>
-<p>Some users of a project’s software become committers in their own right. Some will test code,
-some will write documentation, some will do bug triage and some will write code.</p>
-<p>For more details see “<a href="https://www.apache.org/foundation/how-it-works.html">How it works</a>”. You can also make
-<a href="/newbiefaq.html#websitecms">suggestions for how to update this website</a> you’re reading right now!</p>
-<h2 id="questions-and-feedback">Questions and Feedback <a class="headerlink" title="Permalink" href="#questions-and-feedback">¶</a></h2>
-<p>You can provide feedback and ask questions by subscribing to our mailing
-list: send an email to
-<a href="mailto:dev-subscribe@community.apache.org">dev-subscribe@community.apache.org</a>. Once subscribed, you can send your mail to
-<a href="mailto:dev@community.apache.org">dev@community.apache.org</a>.</p>
-
</div>
</main>
diff --git a/content/contributors/index.html b/content/pmc/responsibilities.html
similarity index 61%
copy from content/contributors/index.html
copy to content/pmc/responsibilities.html
index 88de78d..1ff4636 100644
--- a/content/contributors/index.html
+++ b/content/pmc/responsibilities.html
@@ -6,13 +6,16 @@
<meta name="description" content="Apache Community Development"/>
<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="Contributing to the Apache Software Foundation" />
-<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
-<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/contributors/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+ <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 Ensuring project health Adding community members Reporting 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: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/aceu19_1.jpg"/><meta property="article:section" content="pmc" />
+<meta property="article:modified_time" content="2023-04-16T08:33:58-04:00" /><meta property="og:site_name" content="Apache Community Development" />
- <title>Apache Community Development - Contributing to the Apache Software Foundation</title>
+
+ <title>Apache Community Development - PMC Responsibilities</title>
<link rel="shortcut icon" href="images/favicon.ico">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
@@ -170,12 +173,15 @@
- <li class="breadcrumb-item"><a href='/contributors'>Contributors</a></li>
+ <li class="breadcrumb-item"><a href='/pmc'>Pmc</a></li>
+ <li class="breadcrumb-item"><a href='/pmc/responsibilities.html'>Responsibilities</a></li>
+
+
</ol>
</nav>
@@ -183,74 +189,76 @@
<hr>
- <p>This page is for people who are reasonably
-comfortable with open source development models but need a helping hand finding
-their way around the Apache Software Foundation and our way of developing software
-(commonly called “The Apache Way”). For those wishing to start from
-the very beginning, we have a <a href="/newcomers/index.html">newcomers page</a>.</p>
-<h1 id="project-independence-and-policies">Project Independence And Policies <a class="headerlink" title="Permalink" href="#project-independence-and-policies">¶</a></h1>
-<p>While not all ASF projects practice all aspects of the Apache Way in the same way, there are a number of rules that Apache
-projects must follow – things like complying with PMC
-<a href="https://www.apache.org/legal/release-policy.html">release voting</a>, <a href="https://www.apache.org/legal/">legal policy</a>, <a href="https://www.apache.org/foundation/marks/">brand policy</a>,
-using <a href="https://www.apache.org/dev/#mail">mailing lists</a>, etc., which are <a href="https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different">documented in various places</a>.</p>
-<p>One of these invariant rules is that projects are managed
-independently of any commercial interests. The goal is to create an
-environment in which all participants are equal and thus have an equal
-opportunity to contribute to and benefit from our software, regardless
-of motivation or financial objectives. This is discussed in more detail
-in our document <a href="/projectIndependence.html">Project Independence</a>.</p>
-<h1 id="moving-from-contributor-to-committer">Moving From Contributor to Committer <a class="headerlink" title="Permalink" href="#moving-from-contributor-to-committer">¶</a></h1>
-<p>Anyone can be a contributor to an Apache project. Being a contributor simply means
-that you take an interest in the project and contribute in some way, ranging from asking
-sensible questions (which document the project and provide feedback to developers)
-through to providing new features as code patches.</p>
-<p>If you become a valuable contributor to the project, the Project Management Committee (PMC) may invite you to become
-a <em>committer</em>. At the ASF, a committer is someone who is
-committed to a particular project. It brings with it the privilege of write access to
-the project repository and resources. In many projects, committers may also be invited
-to be part of the core group within the project that ensures the project’s vitality, the PMC.
-In a few projects only a subset of committers who have earned even more merit are invited to be a part of the PMC.</p>
-<p>One thing that is sometimes hard to understand, when you are new to the open
-development process used at the ASF, is that we value the community more than
-the code. A strong and healthy community will be respectful and be a fun and
-rewarding place. More importantly, a diverse and healthy community can
-continue to support the code over the longer term, even as individual
-contributors come and go from the field.</p>
-<p>In particular, we have some <a href="/contributors/etiquette">etiquette and behavior expectations</a> when
-you work with Apache communities.</p>
-<p>See also this <a href="/contributors/becomingacommitter.html">detailed advice for how to become a committer</a></p>
-<h2 id="contributing-a-project---copdoc">Contributing A Project - CoPDoC <a class="headerlink" title="Permalink" href="#contributing-a-project---copdoc">¶</a></h2>
-<p>The foundations of an Apache project and how the community contributes to it are
-sometimes referred to by the acronym CoPDoC:</p>
+
+ <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>
<ul>
-<li>(Co)mmunity - one must interact with others, and share vision and knowledge</li>
-<li>(P)roject - a clear vision and consensus are needed</li>
-<li>(Do)cumentation - without it, the stuff remains only in the minds of the authors</li>
-<li>(C)ode - discussion goes nowhere without code</li>
+<li><a href="#conducting-business">Conducting business</a></li>
+<li><a href="#ensuring-project-health">Ensuring project health</a></li>
+<li><a href="#adding-community-members">Adding community members</a></li>
+<li><a href="/pmc/reporting">Reporting</a></li>
</ul>
-<h2 id="anyone-can-become-a-committer">Anyone Can Become A Committer <a class="headerlink" title="Permalink" href="#anyone-can-become-a-committer">¶</a></h2>
-<p>There is nothing at the Apache Software Foundation that says you must write code
-in order to be a committer. Anyone who is supportive of the community and works
-in any of the CoPDoC areas is a likely candidate for committership.</p>
-<p>Apache strives to be meritocratic. That is, once someone has contributed sufficiently to
-any area of CoPDoC they can be voted in as a committer. Being a committer does
-not necessarily mean you commit code; it means you are committed to the project
-and are productively contributing to its success.</p>
-<p>One of the key contributions people can make to the community is through the
-support of a wide user base by assisting users on the user list, writing user-oriented docs and ensuring the developers understand the user viewpoint.
-A main idea behind being a committer is the ability to be a mentor and to work
-cooperatively with your peers.</p>
-<p>Some users of a project’s software become committers in their own right. Some will test code,
-some will write documentation, some will do bug triage and some will write code.</p>
-<p>For more details see “<a href="https://www.apache.org/foundation/how-it-works.html">How it works</a>”. You can also make
-<a href="/newbiefaq.html#websitecms">suggestions for how to update this website</a> you’re reading right now!</p>
-<h2 id="questions-and-feedback">Questions and Feedback <a class="headerlink" title="Permalink" href="#questions-and-feedback">¶</a></h2>
-<p>You can provide feedback and ask questions by subscribing to our mailing
-list: send an email to
-<a href="mailto:dev-subscribe@community.apache.org">dev-subscribe@community.apache.org</a>. Once subscribed, you can send your mail to
-<a href="mailto:dev@community.apache.org">dev@community.apache.org</a>.</p>
+<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>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
+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
+website</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
+platoform(s).</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 delagated to PMC members in this
+respect.</p>
+<p>Projects should operate in a vendor neutral fashion. 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.</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">adding new
+committers</a> and <a href="/pmc/adding-pmc-members">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">rung of the contributor
+ladder</a>.</p>
-
</div>
</main>
diff --git a/content/sitemap.xml b/content/sitemap.xml
index 81f3d48..2c2834c 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -10,6 +10,12 @@
</url><url>
<loc>https://community.apache.org/apache-way/apache-project-maturity-model.html</loc>
<lastmod>2023-04-07T09:01:44+01:00</lastmod>
+ </url><url>
+ <loc>https://community.apache.org/pmc/adding-committers.html</loc>
+ <lastmod>2023-04-15T22:01:34-04:00</lastmod>
+ </url><url>
+ <loc>https://community.apache.org/pmc/adding-pmc-members.html</loc>
+ <lastmod>2023-04-15T22:01:34-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/</loc>
<lastmod>2023-03-29T19:12:27+01:00</lastmod>
@@ -37,6 +43,9 @@
</url><url>
<loc>https://community.apache.org/contributors/etiquette.html</loc>
<lastmod>2023-03-17T12:29:24-05:00</lastmod>
+ </url><url>
+ <loc>https://community.apache.org/contributor-ladder.html</loc>
+ <lastmod>2023-04-20T12:01:52-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/contributors/becomingacommitter.html</loc>
<lastmod>2023-03-30T13:02:33-04:00</lastmod>
@@ -69,7 +78,7 @@
<lastmod>2020-12-10T09:12:00-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/contributors/</loc>
- <lastmod>2023-03-29T11:49:44+02:00</lastmod>
+ <lastmod>2023-04-20T08:27:41-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/committers/decisionMaking.html</loc>
<lastmod>2021-01-15T09:22:16-04:00</lastmod>
@@ -109,6 +118,9 @@
</url><url>
<loc>https://community.apache.org/speakers/speakers.html</loc>
<lastmod>2021-07-05T14:07:56-03:00</lastmod>
+ </url><url>
+ <loc>https://community.apache.org/contributors/mailing-lists.html</loc>
+ <lastmod>2023-04-20T12:01:52-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/newsletter/2017-05.html</loc>
<lastmod>2020-07-20T20:22:04+02:00</lastmod>
@@ -133,15 +145,30 @@
</url><url>
<loc>https://community.apache.org/newcommitter.html</loc>
<lastmod>2023-03-29T19:28:51+01:00</lastmod>
+ </url><url>
+ <loc>https://community.apache.org/pmc/new-member.html</loc>
+ <lastmod>2023-04-15T22:01:34-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/newsletter/</loc>
<lastmod>2023-03-29T11:49:44+02:00</lastmod>
</url><url>
<loc>https://community.apache.org/history/mentoringprogramme-icfoss-pilot.html</loc>
<lastmod>2023-03-17T12:26:02-04:00</lastmod>
+ </url><url>
+ <loc>https://community.apache.org/pmc/chair.html</loc>
+ <lastmod>2023-04-20T08:27:41-04:00</lastmod>
+ </url><url>
+ <loc>https://community.apache.org/pmc/reporting.html</loc>
+ <lastmod>2023-04-15T22:01:34-04:00</lastmod>
+ </url><url>
+ <loc>https://community.apache.org/pmc/responsibilities.html</loc>
+ <lastmod>2023-04-16T08:33:58-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/projectIndependence.html</loc>
<lastmod>2022-01-07T11:22:24-08:00</lastmod>
+ </url><url>
+ <loc>https://community.apache.org/pmc.html</loc>
+ <lastmod>2023-04-20T12:01:52-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/proposals.html</loc>
<lastmod>2020-07-20T20:22:04+02:00</lastmod>