Author: orcmid Date: Thu Oct 8 17:48:10 2015 New Revision: 1707590 URL: http://svn.apache.org/viewvc?rev=1707590&view=rev Log: Put public version in a stable location (adapted from 2015-08 list posting)
Added: openoffice/pmc/Policies/RoleOfChair-2015-10.txt (with props) Added: openoffice/pmc/Policies/RoleOfChair-2015-10.txt URL: http://svn.apache.org/viewvc/openoffice/pmc/Policies/RoleOfChair-2015-10.txt?rev=1707590&view=auto ============================================================================== --- openoffice/pmc/Policies/RoleOfChair-2015-10.txt (added) +++ openoffice/pmc/Policies/RoleOfChair-2015-10.txt [UTF-8] Thu Oct 8 17:48:10 2015 @@ -0,0 +1,160 @@ +RoleOfChair-2015-10.txt UTF-8 2015-10-08 + + PRACTICE: ROLE OF CHAIR AND PMC RELATIONSHIP + ============================================ + + APACHE OPEN OFFICE PROJECT MANAGEMENT COMMITTEE + + ******************************* + **** VERSION 2 **** + **** 2015-10-08T17:46Z **** + ******************************* + + <http://svn.apache.org/repos/asf/openoffice/pmc/ + Policies/RoleOfChair-2015-10.txt> + + + This document is an adaptation of a list post made on + 2015-08-26 as part of establishment of a new OpenOffice + PMC Chair. It identifies the approach of that Chair + and also specifies resources that expand on how an ASF + Project is to operate. + + The information is intended for review by PMC Chairs + (who may revise it), PMC members, and the wider public + community for understanding of the relationships of + ASF, PMCs and their Chairs, and how Apache projects + serve the public good. + + CONTENT + + 1. The PMC and How It Operates + 2. The Chair of the PMC + 3. Beyond the Dry Stuff + +It is useful to know some specifics concerning the role of a Project +Management Committee (PMC) Chair and how that fits with the responsibilities +of the PMC and what counts as Project Management for a volunteer-driven +open-source software project. + +**PLEASE NOTE** It might appear in the material below that the Chair is in a +position to be the (benevolent?) dictator of the PMC and the project. + That is not the case. + The technical decisions and detailed work fall to the PMC, the committers, +and, for Apache OpenOffice, the community of contributors all the way out to +end-users who submit bugs, complaints, and requests for assistance in +difficulties of successful use. + You might say that the Chair has oversight on how well that activity is +managed and fits under the umbrella of the Foundation. This is not about +technical direction to the extent there is no collision with over-riding ASF +policy (e.g., in handling of IP). + + 1. THE PMC AND HOW IT OPERATES + +Since the PMC Chair is a member of the PMC, an useful place for that important +context is the "Project Management Committee Guide" at +<http://www.apache.org/dev/pmc.html>. + +The section on "PMC Required Policy" is very brief and to the point. An +aspect of PMC activity that is questioned from time to time is where the PMC +conducts its business. The final section of the required policy establishes +*strict, mandatory* limitation on what PMC deliberations are allowed on +private mailing lists under "Conduct Project Business on Mailing Lists." + +Everyone on the AOO PMC must understand and respect the "PMC Required Policy," +including the Chair. + +Neither the Chair nor the PMC have executive powers. No one can command the +work of others. Discussions on technical direction and technical actions +happen on public lists, with additional information on wikis, forums, and the +repositories. Some technical actions do require PMC approval, and for those, +such as approval of a release, only the PMC members have binding votes. That +is because of the accountability of the PMC for assuring the integrity of the +technical work. In all respects, the objective is to operate with a clear +consensus on all matters. + +Furthermore, all participants on ASF Projects, and those who contribute +via apache.org resources and lists are subject to the Apache Software +Foundation Code of Conduct, +<https://www.apache.org/foundation/policies/conduct.html>. +That applies to the Chair and the PMC along with all other contributors. + + + 2. THE CHAIR OF THE PMC + +For the Chair, the "PMC FAQ" section of the PMC "Committee Guide"provides two +additional explanations about what is expected. + +First, all the way down at "Changing the PMC Chair" there is an important link +to "Why are PMC Chairs officers of the corporation, +<http://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers>. + +Some general duties are described in the earlier "PMC FAQ" section on "What +Are the Duties of the PMC Chair and How To Perform Them?" Beside required +administrative activities, there is this particular guidance: + + "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." + +This section also links to an additional definition of PMC and Chair at +<http://www.apache.org/foundation/how-it-works.html#pmc>. This is important +for understanding the relationship of the Chair to the Board: + + "The chair of the PMC is appointed by the Board and + is an officer of the ASF (Vice President). The + chair has primary responsibility to the Board, and + has the power to establish rules and procedures for + the day to day management of the communities for which + the PMC is responsible, including the composition of + the PMC itself." + +Finally, there is reference to section 6.3 of the Bylaws of +The Foundation. The section is essentially the origin of +the description above, in its final statements: + + "Subject to the direction of the Board of Directors, the + chairman of each Project Management Committee shall be + primarily responsible for project(s) managed by such + committee, and he or she shall establish rules and + procedures for the day to day management of project(s) + for which the committee is responsible. + + "The Board of Directors of the corporation may, by + resolution, terminate a Project Management Committee + at any time." + + + 3. BEYOND THE DRY STUFF + +It might seem that this could be very heavy-handed and dry. + +In practice, the philosophy on establishment of sustainable communities that +produce software in the public interest involves very great patience and +tolerance for how communities come together and ultimately thrive. The idea +is for communities to work out a way of working that achieves the purposes of +the project and the over-arching ASF principles on how the public good is +served, and being able to sustain the project for as long as that remains +important. + +At the ASF, there is no counterpart of the business-world "public hanging" and +those who call for them need to understand this is not how the ASF operates. +Period. These examples, also from the FAQ, may be informative: + + <http://www.mail-archive.com/community@apache.org/msg03961.html> + + <http://www.mail-archive.com/community@apache.org/msg04005.html> + +If there is any question about actions on the part of the Chair, please check +this document and linked source documents. If there is a discrepancy between +this practice and actual conduct, shout out and assist in having the concern +addressed. If it is a personal matter, do not hesitate to communicate to the +PMC private list, <mailto:priv...@openoffice.apache.org>. If the concern is +about conduct of the Chair or the PMC, rely on the Apache Software Foundation +Code of Conduct, <https://www.apache.org/foundation/policies/conduct.html>, +for alternative remedies. + + + *** end of RoleOfChair-2015-10.txt *** Propchange: openoffice/pmc/Policies/RoleOfChair-2015-10.txt ------------------------------------------------------------------------------ svn:eol-style = native Propchange: openoffice/pmc/Policies/RoleOfChair-2015-10.txt ------------------------------------------------------------------------------ svn:mime-type = text/plain;charset=UTF-8