community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r900449 - in /websites/staging/community/trunk/content: ./ projectIndependence.html
Date Fri, 07 Mar 2014 13:02:29 GMT
Author: buildbot
Date: Fri Mar  7 13:02:29 2014
New Revision: 900449

Staging update by buildbot for community

    websites/staging/community/trunk/content/   (props changed)

Propchange: websites/staging/community/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Fri Mar  7 13:02:29 2014
@@ -1 +1 @@

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:02:29
@@ -159,7 +159,8 @@ projects are required to follow – t
 <a href="">release voting</a>, <a href="">legal
policy</a>, <a href="">brand policy</a>,

 using <a href="">mailing lists</a>, etc., which
are <a href="">documented
in various places</a>. </p>
 <p>A community is not merely a set of rules; it is also a set of behaviors 
-that are expressed by the participants there.  While the ASF is happy to host 
+that are expressed by the participants when interacting within that 
+community.  While the ASF is happy to host 
 many different styles of project communities, there are some core behaviors that 
 are expected and required of any Apache project. </p>
 <p>A primary purpose of the basic requirements the ASF places on its 
@@ -170,6 +171,16 @@ in that area. The <a href="http://www.ap
 on a diverse community. This is different from other governance models, 
 like the “benevolent dictator” idea or the often corporate-backed model 
 that Eclipse uses.</p>
+<p><strong>Please Note:</strong> These requirements apply to <em>Apache
projects</em>: that is, 
+to individual committer and PMC behaviors and actions within the context 
+of collaboratively building software products <em>at The Apache 
+Software Foundation</em>.  By definition here, "Apache project" means the collaborative

+activity of building a software release called an "Apache product" here at the ASF.</p>
+<p>The ASF and all Apache projects welcome the public to broadly re-use any released

+Apache products for virtually any purpose. Third party use like this is governed by 
+our permissive <a href="">Apache License</a>
and by our <a href="">formal trademark policy</a>.<br
+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>

View raw message