The Podling Project Management Committee (PPMC) helps a
Podling learn how to govern itself. It works like a PMC but
reports to the Incubator PMC instead of to the ASF Board.
Initially, it is composed of the Podling's mentors and initial
committers. The PPMC is directly responsible for the oversight
of the podling and it also decides who to add as a PPMC member.
For general information about PMCs, see the PMC FAQ.
A private mail list, named project-private, lets
the PPMC discuss confidential topics.
Most communication should be on the Podling's dev list!
The private list is used only for confidential discussions that
should not be made public, such as the suitability of a
particular individual to become a committer or a member of the
PPMC. See the ASF How it Works section titled Balancing confidentiality and public discussion.
Don't mix private and public lists in posts!
- Don't post to both the dev and private lists.
Each member of the PPMC should be on the dev list, so posting
to dev is sufficient.
- Likewise, don't post to both the Incubator general and
Incubator private lists. Each member of the Incubator PMC is on
the Incubator general list, so posting to general is
sufficient.
Note that the lists used to be named project-ppmc or
pmc@tlp, so you may see those names referenced in other ASF
documentation or in the mail list archives. It was
resolved
that these lists should be named private
to make it clear that they should be used for confidential discussion,
not as a general purpose way to contact (P)PMC members.
On a regular basis, reports from each incubating project are
aggregated and sent to the ASF Board. Watch the Incubator general
mail list for when these become due.
The Incubator reports to the ASF Board monthly and includes
status for a subset of the incubating projects. Currently new
Podlings report to the Incubator monthly for the first three
months, then quarterly thereafter. The
reporting schedule is on the Incubator Wiki, which
is also used for Podlings to provide status.
The PPMC does not have to fill out the report itself; the PPMC
is just responsible for making sure that it gets filled out. In
fact, it is better to discuss the report on the dev list and ask
Podling developers to contribute to it. If Mentors disagree with
the posted report, they should say so; otherwise, the Incubator
PMC will assume that it speaks for the community.
Please add the following items:
- Project name and one-line summary.
- Date of entry to the Incubator.
- Top three items to resolve before graduation.
Here are the points to be addressed:
- Is there anything that the Incubator PMC or ASF Board
specifically needs to address?
- Are there any legal, infrastructure, cross-project or
personal issues that need to be addressed? (Are
there any stumbling blocks that impede the podling?)
- Check that the project's Incubation
Status file up to date.
(Also provide the URL.)
- What has been done (releases, milestones, etc.) since the
last report?
- What are the plans and expectations for the next period?
- Are there any recommendations for how incubation could run more
smoothly for you?
- etc. (your own thoughts on what is important would be
helpful!)
In addition to the quarterly status reports, each Podling has a
page on the Incubator web site that tracks the status
(see the complete
list for examples). Instructions for updating the status page
are in the Incubator web site guide
under Edit
your project status report.
This is the primary source of information about your podling's
status to the Incubator PMC and to the general public. Be sure to
keep it updated as your podling progresses!
If a person has made significant contributions of
high-quality, is interested in continuing to
contribute, and works well with
others under the Apache guidelines, the project might vote to
grant that person
commit access. See the ASF How it Works document,
which explains
meritocracy and
roles.
One of the PPMC members should lead the process of accepting
a new committer. For the purposes of this document, the proposing
PPMC member is referred to as the proposer, and the proposed
committer is referred to as the nominee. Discussion of a
nominee should take place on the podling project's private (PPMC)
list [in a Top Level Project it would take place on the project's
private list]. If there are any concerns raised during the
discussion, these need to be resolved so that there is consensus
among the PPMC members as to the suitability of the nominee for
the project and for Apache. Many projects adopt an approach where,
if there are any concerns, the nomination is delayed
for a few months. Many concerns go away with continued participation
by the nominee in the project.
After vetting the nominee, the vote can be called on either
one of the two places listed below (notice the difference between
private and public lists):
Only votes cast by Incubator PMC members are binding, but votes
by the PPMC are very important. The entire PPMC should show support
for the nominee. If the vote is positive (three or more binding +1
votes and no binding -1 votes), the proposer offers committership
to the nominee. If the nominee accepts the responsibility of being
a committer for the project, the nominee formally becomes an
Apache committer.
The proposer then asks an Incubator PMC member
to follow the documented procedures
to complete the process.
Normally, the Incubator PMC member is a Mentor on the podling's PPMC
but if the Mentors are temporarily unavailable, the proposer can ask
any Incubator PMC member.
- If the nominee is already an Apache committer on another project,
the Incubator PMC member simply updates the authorization file
to include the nominee as a committer on the podling.
- If the nominee is not already an Apache committer, the Incubator
PMC member CC's both the Incubator PMC and the PPMC when sending
the necessary e-mails to root.
The proposer then directs the new committer to the Apache developer's pages,
to the Apache Incubator site
and to the Incubator Committers Guide for important additional
information.
It should be a goal of a podling to have all committers participate
in the PPMC. The PPMC should take an active role in watching
committers develop into community participants, identify those who
are participating at a community level, not just a technical one,
and approach them with an offer of PPMC membership.
Any member of the PPMC can propose a new member of the PPMC. The
proposal should be discussed in private on the PPMC private alias,
with a subject line of [DISCUSS] Joe Bob PPMC membership. If there
is consensus that the proposed member is suitable, then there should
be a formal vote in the PPMC private alias, with the subject line of
[VOTE] Joe Bob PPMC membership. The [VOTE] message should be forwarded
to the IPMC (
private@incubator.apache.org) to notify them that the
vote is underway. If the vote is successful, the proposer should send
a message to the PPMC private alias, with
the subject line of [VOTE][RESULT] Joe Bob PPMC membership. The
message id of the [VOTE][RESULT] message should be preserved for
the message to the Incubator PMC after Joe Bob accepts. Now, Joe Bob
should be invited to join the PPMC, using a sample message like
this.
Once the proposed member has accepted, the moderator for the
PPMC mail alias will accept the new member's subscription request.
The nominating PPMC member should send a message to
the IPMC (
private@incubator.apache.org) with a reference to
the vote results message id of the following form:
to: private@incubator.apache.org
subject: New member of Frizzle PPMC Joe Bob
body: Joe Bob has been voted as a new member of the Frizzle PPMC.
the vote thread is at:
msgid: 23985678912386778989056789659048357@sponsoring.member.org
The new member should be directed to
this page for PPMC membership information.
The nominating member should also update
the PPMC membership list.
|
