Author: buildbot
Date: Fri Mar 7 13:19:39 2014
New Revision: 900451
Log:
Staging update by buildbot for community
Modified:
websites/staging/community/trunk/content/ (props changed)
websites/staging/community/trunk/content/projectIndependence.html
Propchange: websites/staging/community/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Mar 7 13:19:39 2014
@@ -1 +1 @@
-1575251
+1575255
Modified: websites/staging/community/trunk/content/projectIndependence.html
==============================================================================
--- websites/staging/community/trunk/content/projectIndependence.html (original)
+++ websites/staging/community/trunk/content/projectIndependence.html Fri Mar
7 13:19:39 2014
@@ -182,8 +182,18 @@ our permissive <a href="http://www.apach
While many third parties create Apache licensed
software, only software released from the ASF itself is properly called
"Apache software".</p>
<h2 id="apache-projects-are-independent">Apache projects are independent</h2>
-<p>This is implicit in the fact that the Project Management Committee (PMC)
runs the project, and the fact that PMC members are expected to contribute to
the project as individuals, wearing their âPMC hatâ. The concept of hats
means that when a PMC member votes on project matters, they are casting their
vote as an individual acting in the best interests of that PMC, and not as an
employee or representative of some third party. There are also certain
expectations of diversity within a PMC; the board may apply extra scrutiny to
PMCs with low diversity (i.e. PMCs that are dominated by people with a common
employer). Similarly, the ASF does not allow corporations to participate
directly in project management, only individuals.</p>
-<p>There are two important aspects to this independence: project management,
and project use by end users.</p>
+<p>Apache projects are controlled by their Project Management Committee
+(PMC). A PMC represents the consensus view of the individual PMC
+members by discussion and [VOTE]ing on project releases and new committers.
+A PMC's actions within their Apache project community and management of
+their project must be in the interest of that consensus and consistent with<br
/>
+the ASF's mission of producing software for the public good. </p>
+<p>There are also
+certain expectations of diversity within a PMC; the board may apply extra
scrutiny to PMCs
+with low diversity (i.e. PMCs that are dominated by individuals with a common
employer).
+Similarly, the ASF does not allow corporations to participate directly in
+Apache project management or other governance activities at the ASF; only
individuals.</p>
+<p>There are several important aspects to this independence: project
management, project use by end users, and project code availability.</p>
<h2 id="apache-projects-are-managed-independently">Apache projects are managed
independently</h2>
<p>Apache projects must be managed independently, and PMCs must ensure that
they are acting in the best interests of the project as a whole. Note that it
is similarly important that the PMC clearly show this independence within their
project community. The perception of existing and new participants within the
community that the PMC is run independently and without favoring any specific
third parties over others is important, to allow new contributors to feel
comfortable both joining the community and contributing their work. A community
that obviously favors one specific vendor in some exclusive way will often
discourage new contributors from competing vendors, which is an issue for the
long term health of the project.</p>
<h2 id="apache-products-may-be-used-independently">Apache products may be used
independently</h2>
