You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-dev@apache.org by sebb <se...@gmail.com> on 2016/02/26 01:28:10 UTC
Re: svn commit: r1732385 - /infrastructure/site/trunk/content/dev/pmc.mdtext
On 25 February 2016 at 22:02, <cu...@apache.org> wrote:
> Author: curcuru
> Date: Thu Feb 25 22:02:39 2016
> New Revision: 1732385
>
> URL: http://svn.apache.org/viewvc?rev=1732385&view=rev
> Log:
> Clarifications and better explanations of many points; FAQ re: VPs vs Membership
>
> Modified:
> infrastructure/site/trunk/content/dev/pmc.mdtext
>
> Modified: infrastructure/site/trunk/content/dev/pmc.mdtext
> URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/content/dev/pmc.mdtext?rev=1732385&r1=1732384&r2=1732385&view=diff
> ==============================================================================
> --- infrastructure/site/trunk/content/dev/pmc.mdtext (original)
> +++ infrastructure/site/trunk/content/dev/pmc.mdtext Thu Feb 25 22:02:39 2016
> @@ -26,13 +26,13 @@ of PMC members in managing their project
> # Intended Audience # {#audience}
>
> This document is targeted at Apache *PMC members*. A
> -[Project Management Committee](/foundation/how-it-works.html#pmc) (PMC) is responsible for the proper management
> -and oversight of an Apache project, and reports directly to the board.
> +[Project Management Committee](/foundation/how-it-works.html#pmc) (PMC) is responsible for the proper
> +[management and oversight of an Apache project][1], and reports directly to the board.
A PMC might have multiple projects?
> If you are a committer who is not yet a PMC member then you probably want
> to [read the committers guide](committers.html) instead.
>
> -If you are not yet a committer but are interested in joining Apache then
> +If you are not yet a committer but are interested in joining an Apache project then
> please start at the [Contributors Tech Guide](contributors.html).
>
> For more information on how Apache projects are run, see "[What makes Apache
> @@ -50,7 +50,8 @@ Terms in this section as used as per [RF
> PMCs **SHALL** ensure that the work on their project and the code that
> they produce complies with relevant [Legal Affairs Committee](/legal/)
> policies, including appropriately using the Apache License, handling IP and
> -copyrights correctly, and handling cryptography.
> +copyrights correctly, handling cryptography, and
> +[producing official software releases][2] of their products.
>
> ## Comply With Brand Management Policies ## {#brand-policy}
>
> @@ -95,11 +96,11 @@ private list (where *project* is the nam
> ## What Is A PMC? ## {#what-is-a-pmc}
>
> A project management committee (PMC) is a committee of the Apache Software
> -Foundation charged with responsibility for a top level project. The PMC is
> +Foundation charged with [responsibility and governance][3] for their top level project. The PMC is
Surely the PMC is responsible for all its projects, not just the TLPs?
> the vehicle through which decision making power and responsibility for
> oversight is devolved to developers. See also the [Intended Audience](#audience) section for links.
>
> -## We've decided on new committer. Now what? ## {#newcommitter}
> +## How To Invite New Project Committers ## {#newcommitter}
>
> It is the responsibility of each project PMC to guide their new committers,
> ensure that they have access to the proper resources, advise them about
> @@ -161,7 +162,7 @@ needs. In particular, the PMC chair has
> responsibility of** - providing write access to the project's source
> repository.
>
> -## How to grant SVN access to a project source repository ## {#SVNaccess}
> +## How To grant SVN access (karma) to a project source repository ## {#SVNaccess}
>
> Access to SVN directories is controlled by the
> [asf-authorization-template](https://svn.apache.org/repos/infra/infrastructure/trunk/subversion/authorization/asf-authorization-template)
> @@ -212,7 +213,7 @@ podling) then just edit the appropriate
> [asf-authorization-template](https://svn.apache.org/repos/infra/infrastructure/trunk/subversion/authorization/asf-authorization-template)
> file and commit the change. (see below)
>
> -## How to grant karma to podling members ## {#karma-podling}
> +## How To grant karma to podling committers ## {#karma-podling}
>
> Podling Git authorization is managed using the incubator unix group.
> See the previous section (modify_unix_group.pl)
> @@ -261,14 +262,14 @@ have a people.apache.org account and nee
> Once the request has been received, a person with appropriate access will
> extend the karma and reply accordingly.
>
> -## How To access a machine other than people.apache.org. ## {#machine}
> +## How To access other Apache infrastructure servers ## {#machine}
>
> -By default, new accounts are only created on people.apache.org. Access to
> -[other ASF machines](machines.html) are on demand. In order to request an
> +Access to
> +[official ASF servers](machines.html) is on demand. In order to request an
> account, please send your request to *infrastructure at apache.org*.
>
> :::text
> - Account request form (other machines than people.apache.org):
> + Account request form:
>
> To: infrastructure
> Cc: private@<project>.apache.org, committers@email.address
> @@ -285,27 +286,18 @@ The administrator of the machine will th
>
> ## How To add a new PMC member ## {#newpmc}
>
> -According to the current rules, adding a new PMC member requires
> -a notification
> -to the Board's mailing list and the PMC's private mailing list. **Once the notification
> +Adding a new PMC member requires sending an email a notification
> +to the Board's mailing list and the PMC's private mailing list and waiting 72 hours. **Once the notification
> appears in the archives**, an invitation may be sent out 72 hours later
> -(unless a Director objects).
> -
> -Note: The current rules can be found
> +(unless a Director objects to the nomination). The detailed process can be found
> in the [June 2013 board minutes](http://apache.org/foundation/records/minutes/2013/board_minutes_2013_06_19.txt)
> under section "[7 G. Amend the Procedure for PMC Membership Changes](https://whimsy.apache.org/board/minutes/Amend_the_Procedure_for_PMC_Membership_Changes.html)"
>
> **Do NOT send an invite to the potential member before the 72 hour NOTICE period has expired!**
> -It would be very awkard if the invite had to be withdrawn.
> -
> -The notification may be sent by the PMC Chair, or by any other
> -PMC member if they include a link to the formal PMC decision.
> +It would be very awkard if the invite had to be withdrawn if the board objected.
>
> -Please note: e-mail delivery can fail silently. Now that an ACK is no longer required,
> -**it is vital that the PMC Chair checks the board archives to ensure that the NOTICE has
> -actually been delivered to the board.** This can be done by sending a mail to the EZMLM server at
> -`board-index@apache.org` followed by a `board-get.XXX@apache.org` (`XXX` = message number).
> -ASF Members can also access the [board archive](https://mail-search.apache.org/members/private-arch/board/) on the web.
> +This notification may be sent by the PMC Chair, or by any other
> +PMC member if they include a link to the formal PMC decision or vote on their private@ list.
>
> **Ensure the PMC private list is copied - but do not Cc the potential member**. For example:
>
> @@ -320,12 +312,16 @@ ASF Members can also access the [board a
> (include if a vote was held) The vote result is available here: https://mail-search.apache.org/pmc/blah-blah
>
> If the candidate does not (yet) have an Apache account, then please note
> -that fact in the notification email.
> +that fact in the notification email. Use a **separate** e-mail for each candidate
>
> -**Note:** please use a separate e-mail for each candidate.
> +Please note: e-mail delivery can fail silently. Now that an ACK is no longer required,
> +**it is vital that the PMC Chair checks the board archives to ensure that the NOTICE has
> +actually been delivered to the board.** This can be done by sending a mail to the EZMLM server at
> +`board-index@apache.org` followed by a `board-get.XXX@apache.org` (`XXX` = message number).
> +ASF Members can also access the [board archive](https://mail-search.apache.org/members/private-arch/board/) on the web.
>
> -After 72 hours have elapsed without objection, then the candidacy
> -becomes valid and the PMC Chair needs to:
> +After 72 hours have elapsed without objection, then you may formally add the
> +candidate to your PMC - the PMC Chair needs to:
>
> - Formally invite the new PMC member; and if they accept, then:
> - Update **[committee-info.txt](https://svn.apache.org/repos/private/committers/board/committee-info.txt)**
> @@ -337,19 +333,17 @@ Also please sort the entries by first na
> - Update the appropriate {project}-pmc group as described above
> in [Grant SVN access](#SVNaccess). In almost all cases this means updating
> the LDAP group, e.g. **modify_committee.pl {project} --add id**
> -
> -This gives access to the PMC-only parts of SVN for the project. (Note: a
> -few projects do not have a {project}-pmc group)
> + - This gives access to the PMC-only parts of SVN for the project. (Note: a
> +few projects do not have a {project}-pmc group) . The new PMC member should
> +now subscribe to your PMC's private@ mailing list in the normal way.
>
> **Note that the appointment does not become official until the Foundation's records have been updated**
> (see 7G (3) of the board minutes cited above)
>
> -The person should now subscribe to your PMC's private@ mailing list in the normal way.
> -
> -If the individual declines PMC membership or doesn't respond to the invitation, please follow up the original notice to the board to say that
> +If the candidate declines PMC membership or doesn't respond to the invitation, please follow up the original notice to the board to say that
> the change did not happen, and do not update the records.
>
> -The duration of the waiting period is very important, not only in this
> +The duration of the 72 hour waiting period is very important, not only in this
> context but also at a project level. People are in various timezones and
> have busy schedules. As with normal email, we need to provide time for
> people to respond. The ASF experience has shown that at least 72 hours is
> @@ -367,9 +361,7 @@ of the PMC or not (i.e. wishes to resign
> who are inactive but remain on the PMC, or those who were formerly on the PMC and have resigned. Some
> projects have also established guidelines to allow former PMC members to remain on the private PMC list,
> and to allow a PMC member to request reinstatement simply by asking (note that
> -the standard Board notification procedures must still be followed).
> -
> -Note: see previous section for link to board resolution.
> +the standard Board notification procedures must still be followed for reinstatement).
>
> Once the PMC member's resignation is received on a mailing list of
> the Foundation, the resignation is considered effective (however, the
> @@ -424,10 +416,11 @@ See the [definition of PMC and chair](..
> , and be familiar with the [ASF Bylaws](../foundation/bylaws.html) and
> their effect on your project and the position that you hold.
>
> -PMC chairs **SHALL** be subscribed to the board@ mailing
> +### Subscribe to the board@ mailing list ###
> +PMC Chairs **SHALL** be subscribed to the board@ mailing
> lists to ensure that they are aware of Foundation level issues that may affect
> their project. Note that board@ is a privately-archived mailing list; however as
> -an officer of the ASF the PMC chair is allowed to subscribe.
> +an officer of the ASF PMC Chairs are allowed to subscribe.
>
> ### Review board meeting minutes about their project ###
> PMC chairs should monitor the minutes of board meetings that are relevant to their
> @@ -436,27 +429,23 @@ serve as a conduit for any questions bet
>
> ### Ensure the project's quarterly board report is submitted ###
>
> -While the PMC chair is not required to write their report personally, they are
> -responsible for ensuring the report is submitted on time. See the [reporting](../foundation/board/reporting) page for what the reports should contain.
> -(Note that new PMCs are required to report monthly for the first quarter.)
> +While the PMC chair is not required to write their quarterly board report personally, they are
> +responsible for ensuring the report is submitted on time.
>
> -The schedule is listed in [committee-info.txt](https://svn.apache.org/repos/private/committers/board/committee-info.txt), along with the procedure.
> -
> -The report is mainly about the status of the project, together with any community and
> + - The reporting schedule is listed in [committee-info.txt](https://svn.apache.org/repos/private/committers/board/committee-info.txt), along with the procedure.
> + - See the [reporting](../foundation/board/reporting) page for what the reports should contain. (Note that new PMCs are required to report monthly for the first quarter.)
> + - Project reports are about the status of the project, together with any community and
> legal issues or other general impediments. If there are issues requiring board assistance, then make
> that apparent, separate from any general project news.
> -You can seek input from your
> -PMC, but it is mainly your report to the board. The chair does not report
> -to the PMC- the chair reports to the board (i.e. ultimately to the ASF
> -membership).
> -
> -Look at [Board Meetings and
> -Calendar](../foundation/board/calendar.html) for examples of past PMC
> -reports and to find out when the next meetings are due.
> -
> -Remember that, as in any meeting, the chair is a facilitator and their role within the PMC
> -is to ensure that everyone has a chance to be heard and to enable meetings
> -to flow smoothly. There is no concept of "leader" in the Apache way.
> + - You should seek input from your
> +PMC, but it is mainly your report to the board on behalf of your project. The chair does not report
> +to the PMC - the chair reports to the board (and ultimately to the ASF membership).
> + - Examples of past project reports are in the [Board Meetings and Calendar](../foundation/board/calendar.html).
> +
> +Remember that, as in any committee, the chair is a **facilitator** and their role within the PMC
> +is to ensure that everyone has a chance to be heard and to enable meetings and mailing lists
> +to flow smoothly. A well run PMC works together to draw up the information for
> +their board report, but the chair is specifically responsible for getting it to the board. There is no concept of "leader" in the Apache way.
>
> ### Ensure new committer requests are made ###
> After the project has elected new committers and followed the process to
> @@ -481,7 +470,9 @@ Be aware of anything currently in incuba
>
> ## How To change your PMC's chair ## {#newchair}
>
> -**If the chair is being changed** , then at some stage your PMC needs to
> +If a PMC wishes to change their VP / Chair, typically you will hold
> +a vote or otherwise reach a consensus in the PMC as to who you'd like your
> +new Chair to be. Then anyone on the PMC can
> send the board an official resolution for the board to approve (or reject)
> before this change can officially take place. There are lots of examples in
> past board minutes, and there is a template for [change of PMC
> @@ -490,17 +481,25 @@ chair](https://svn.apache.org/repos/priv
> Change VP/chair name at the [foundation](../foundation/) website. See
> [editing tips](infra-site.html) for the top-level websites.
>
> -See FAQ [Why are PMC Chairs officers of the
> +## Is a PMC Chair an officer or Member of the ASF? ##
> +
> +Yes, and no. PMC Chairs are appointed by the board to be both the
> +Vice President of their top level project, as well as to serve as the Chair of their
> +Project Management Committee. [Read an explanation why PMC Chairs are legal officers of the
> corporation?](../foundation/faq.html#why-are-PMC-chairs-officers)
>
> -See also the documents at [Apache
> -Incubator](http://incubator.apache.org/guides/general.html) and [Apache
> -Jakarta Wiki: RoleOfChair](http://wiki.apache.org/jakarta/RoleOfChair)
> +PMC Chairs/VPs are not (necessarily) Members of the ASF. Members of
> +a PMC and the Chair/VP have merit within their project, which is different than
> +the governance of the ASF as a whole Foundation. Members of the Foundation
> +are essentially [shareholders in the legal corporation][4] that hosts our 100's of
> +software projects.
> +
>
> ## How Do We Import Code From An External Source? ## {#import}
>
> Any code which which is not created for Apache needs to be passed through
> -the [incubator](http://incubator.apache.org). The incubator team understand
> +the [incubator](http://incubator.apache.org), or otherwise have a
> +Software Grant Agreement (SGA) or otherwise cleared by the Apache Legal team. The incubator team understand
> Apache policy and legal requirements. They need to ensure that all the
> correct procedures have been followed and record the appropriate documents.
>
> @@ -516,7 +515,7 @@ public. Posts to these lists are conside
> be quoted on public lists without the permission of the author.
>
> PMC members may need to search the archives of their pmc list. ASF members
> -and officers may also need to read various pmc mailing list archives. There
> +and officers may also need to read various PMC mailing list archives. There
> are at least three ways to access our private archives:
>
> * [mail-search.apache.org](https://mail-search.apache.org/)
> @@ -530,7 +529,7 @@ are at least three ways to access our pr
> ## Who Is Allowed To Subscribe To A Project's Private List? ## {#who-can-be-on-private}
>
> All PMC members of a project should be subscribed to their project's private@
> -list. In addition, ASF members may read any project's private list. In general,
> +list. In addition, ASF Members may read any project's private list. In general,
> non-PMC members should not be allowed to subscribe to private@ lists.
>
> There is a [self-subscribe app](https://whimsy.apache.org/committers/subscribe) which can speed up the process.
> @@ -558,4 +557,10 @@ Most projects do their work on their **d
> Some projects also have a **user@** mailing lists for more general or non-technical
> questions, or have a **general@** mailing list in addition. Every project should have
> a clear [Mailing Lists page](http://www.apache.org/foundation/mailinglists.html) that has instructions for subscribing to the list and
> -for reading the archives.
> \ No newline at end of file
> +for reading the archives.
> +
> +
> + [1]: /foundation/governance/pmcs
> + [2]: /dev/release
> + [3]: /foundation/governance/pmcs.html
> + [4]: /foundation/governance/members
> \ No newline at end of file
>
>
Re: svn commit: r1732385 - /infrastructure/site/trunk/content/dev/pmc.mdtext
Posted by sebb <se...@gmail.com>.
On 26 February 2016 at 01:48, Shane Curcuru <as...@shanecurcuru.org> wrote:
> sebb wrote on 2/25/16 7:28 PM:
>> On 25 February 2016 at 22:02, <cu...@apache.org> wrote:
>>> Author: curcuru
>>> Date: Thu Feb 25 22:02:39 2016
>>> New Revision: 1732385
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1732385&view=rev
>>> Log:
>>> Clarifications and better explanations of many points; FAQ re: VPs vs Membership
>>>
>>> Modified:
>>> infrastructure/site/trunk/content/dev/pmc.mdtext
>>>
>>> Modified: infrastructure/site/trunk/content/dev/pmc.mdtext
>>> URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/content/dev/pmc.mdtext?rev=1732385&r1=1732384&r2=1732385&view=diff
>>> ==============================================================================
>>> --- infrastructure/site/trunk/content/dev/pmc.mdtext (original)
>>> +++ infrastructure/site/trunk/content/dev/pmc.mdtext Thu Feb 25 22:02:39 2016
>>> @@ -26,13 +26,13 @@ of PMC members in managing their project
>>> # Intended Audience # {#audience}
>>>
>>> This document is targeted at Apache *PMC members*. A
>>> -[Project Management Committee](/foundation/how-it-works.html#pmc) (PMC) is responsible for the proper management
>>> -and oversight of an Apache project, and reports directly to the board.
>>> +[Project Management Committee](/foundation/how-it-works.html#pmc) (PMC) is responsible for the proper
>>> +[management and oversight of an Apache project][1], and reports directly to the board.
>>
>> A PMC might have multiple projects?
>
> A PMC might have multiple software products. But a PMC is by definition
> a "Project Management Committee", charged with managing the named
> project that the board puts in the resolution.
>
> Feel free to wordsmith, but the distinction between product and project
> is an important one. Or am I missing something?
AIUI a software product is produced by a software project.
As such, there are lots of Apache projects that aren't TLPs - this is
one reason the TL prefix is used.
I don't know how to resolve this, but it seemed wrong to me when I read it.
>>> If you are a committer who is not yet a PMC member then you probably want
>>> to [read the committers guide](committers.html) instead.
>>>
>>> -If you are not yet a committer but are interested in joining Apache then
>>> +If you are not yet a committer but are interested in joining an Apache project then
>>> please start at the [Contributors Tech Guide](contributors.html).
>>>
>>> For more information on how Apache projects are run, see "[What makes Apache
>>> @@ -50,7 +50,8 @@ Terms in this section as used as per [RF
>>> PMCs **SHALL** ensure that the work on their project and the code that
>>> they produce complies with relevant [Legal Affairs Committee](/legal/)
>>> policies, including appropriately using the Apache License, handling IP and
>>> -copyrights correctly, and handling cryptography.
>>> +copyrights correctly, handling cryptography, and
>>> +[producing official software releases][2] of their products.
>>>
>>> ## Comply With Brand Management Policies ## {#brand-policy}
>>>
>>> @@ -95,11 +96,11 @@ private list (where *project* is the nam
>>> ## What Is A PMC? ## {#what-is-a-pmc}
>>>
>>> A project management committee (PMC) is a committee of the Apache Software
>>> -Foundation charged with responsibility for a top level project. The PMC is
>>> +Foundation charged with [responsibility and governance][3] for their top level project. The PMC is
>>
>> Surely the PMC is responsible for all its projects, not just the TLPs?
>
> PMCs only exist for TLPs (and for a few oddball other ones, like
> ComDev). There are no podling PMCs. Discussing the Incubator PMC is
> something best left to document on the Incubator website, if that's what
> you're asking about (which I agree is a complex subject, not one I'm
> ready to tackle yet).
>
> My work here is merely to help make it easier for our volunteer PMCs
> understand how things work, so everyone on this list is free to improve
> the wordsmithing.
>
> - Shane
Re: svn commit: r1732385 -
/infrastructure/site/trunk/content/dev/pmc.mdtext
Posted by Shane Curcuru <as...@shanecurcuru.org>.
sebb wrote on 2/25/16 7:28 PM:
> On 25 February 2016 at 22:02, <cu...@apache.org> wrote:
>> Author: curcuru
>> Date: Thu Feb 25 22:02:39 2016
>> New Revision: 1732385
>>
>> URL: http://svn.apache.org/viewvc?rev=1732385&view=rev
>> Log:
>> Clarifications and better explanations of many points; FAQ re: VPs vs Membership
>>
>> Modified:
>> infrastructure/site/trunk/content/dev/pmc.mdtext
>>
>> Modified: infrastructure/site/trunk/content/dev/pmc.mdtext
>> URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/content/dev/pmc.mdtext?rev=1732385&r1=1732384&r2=1732385&view=diff
>> ==============================================================================
>> --- infrastructure/site/trunk/content/dev/pmc.mdtext (original)
>> +++ infrastructure/site/trunk/content/dev/pmc.mdtext Thu Feb 25 22:02:39 2016
>> @@ -26,13 +26,13 @@ of PMC members in managing their project
>> # Intended Audience # {#audience}
>>
>> This document is targeted at Apache *PMC members*. A
>> -[Project Management Committee](/foundation/how-it-works.html#pmc) (PMC) is responsible for the proper management
>> -and oversight of an Apache project, and reports directly to the board.
>> +[Project Management Committee](/foundation/how-it-works.html#pmc) (PMC) is responsible for the proper
>> +[management and oversight of an Apache project][1], and reports directly to the board.
>
> A PMC might have multiple projects?
A PMC might have multiple software products. But a PMC is by definition
a "Project Management Committee", charged with managing the named
project that the board puts in the resolution.
Feel free to wordsmith, but the distinction between product and project
is an important one. Or am I missing something?
>> If you are a committer who is not yet a PMC member then you probably want
>> to [read the committers guide](committers.html) instead.
>>
>> -If you are not yet a committer but are interested in joining Apache then
>> +If you are not yet a committer but are interested in joining an Apache project then
>> please start at the [Contributors Tech Guide](contributors.html).
>>
>> For more information on how Apache projects are run, see "[What makes Apache
>> @@ -50,7 +50,8 @@ Terms in this section as used as per [RF
>> PMCs **SHALL** ensure that the work on their project and the code that
>> they produce complies with relevant [Legal Affairs Committee](/legal/)
>> policies, including appropriately using the Apache License, handling IP and
>> -copyrights correctly, and handling cryptography.
>> +copyrights correctly, handling cryptography, and
>> +[producing official software releases][2] of their products.
>>
>> ## Comply With Brand Management Policies ## {#brand-policy}
>>
>> @@ -95,11 +96,11 @@ private list (where *project* is the nam
>> ## What Is A PMC? ## {#what-is-a-pmc}
>>
>> A project management committee (PMC) is a committee of the Apache Software
>> -Foundation charged with responsibility for a top level project. The PMC is
>> +Foundation charged with [responsibility and governance][3] for their top level project. The PMC is
>
> Surely the PMC is responsible for all its projects, not just the TLPs?
PMCs only exist for TLPs (and for a few oddball other ones, like
ComDev). There are no podling PMCs. Discussing the Incubator PMC is
something best left to document on the Incubator website, if that's what
you're asking about (which I agree is a complex subject, not one I'm
ready to tackle yet).
My work here is merely to help make it easier for our volunteer PMCs
understand how things work, so everyone on this list is free to improve
the wordsmithing.
- Shane