community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r789848 - /websites/staging/community/trunk/content/projectIndependence.html
Date Fri, 20 May 2011 14:03:06 GMT
Author: buildbot
Date: Fri May 20 14:03:06 2011
New Revision: 789848

Log:
Staging update by buildbot

Added:
    websites/staging/community/trunk/content/projectIndependence.html

Added: websites/staging/community/trunk/content/projectIndependence.html
==============================================================================
--- websites/staging/community/trunk/content/projectIndependence.html (added)
+++ websites/staging/community/trunk/content/projectIndependence.html Fri May 20 14:03:06
2011
@@ -0,0 +1,140 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+<html>
+    <head>
+       <META name="description" content="Apache Community Development"/>
+       <META name="keywords" content="apache, apache community, community development,
opensource"/>
+
+    
+     <META http-equiv="Content-Type" content="text/html; charset=utf-8">
+      <LINK rel="stylesheet" href="/style/compressed.css" type="text/css" media="screen,
projection">
+      <LINK rel="stylesheet" href="/style/style.css" type="text/css" media="screen, projection">
+     <style type="text/css">
+.code {
+  border: 1px dashed #3c78b5;
+  font-size: 11px;
+  font-family: Courier;
+  margin: 10px;
+  margin-left: 0px;
+  line-height: 13px;
+}
+.codeHeader {
+  background-color: #f0f0f0;
+  border-bottom: 1px dashed #3c78b5;
+  padding: 3px;
+  text-align: center;
+}
+.codeContent {
+  text-align: left;
+  background-color: #f0f0f0;
+  padding: 3px;
+}
+
+.preformatted {
+  border: 1px dashed #3c78b5;
+  font-size: 11px;
+  font-family: Courier;
+  margin: 10px;
+  line-height: 13px;
+}
+.preformattedHeader {
+  background-color: #f0f0f0;
+  border-bottom: 1px dashed #3c78b5;
+  padding: 3px;
+  text-align: center;
+}
+.preformattedContent {
+  background-color: #f0f0f0;
+  padding: 3px;
+}
+        </style>
+
+        <LINK rel="SHORTCUT ICON" href="/images/favicon.ico">   
+        <TITLE>Apache Community Development - Project Independence</TITLE>
+    </head>
+
+    <body onload="init()">
+      <div class="container">
+      <HR class="space col">
+      <DIV class="block">
+        <DIV class="column span-24">
+            <DIV id="header">
+                <h1>The Apache Software Foundation<BR />
+                <SPAN class="alt"><small>Meritocracy in Action.</small></SPAN></h1>
+             </DIV>
+          </DIV>
+      </DIV>
+      <HR/>
+
+
+        <TABLE border="0" cellpadding="2" cellspacing="0" width="100%">
+            <TR class="topBar">
+                <td align="left" valign="middle" class="topBarDiv" nowrap="true" width="100%">
+                    &nbsp;<a href="/">Home</a>&nbsp;&raquo&nbsp;<a
href="/projectIndependence.html">Project Independence</a>
+                </td>
+                <td align="right" valign="middle" class="topBarDiv" align="left" nowrap="true">
+                    <A href="http://community.apache.org">Apache Community Development</A>
| <A href="http://mail-archives.apache.org/mod_mbox/community-dev/">Mailling List</A>
+                </td>
+            </TR>
+        </TABLE>
+
+        <TABLE border="0" cellpadding="0" width="100%">
+            <TR>
+                <td align="left" valign="top">
+                  <DIV id="PageContent">        
+                     <DIV class="pagecontent">
+                         <DIV class="wiki-content">
+                          <p>While not all aspects of the Apache Way are practiced
the same way by 
+all projects at the ASF, there are a number of rules that Apache 
+projects are required to follow – things like complying with PMC 
+<a href="http://www.apache.org/dev/release.html">release voting</a>, <a href="http://www.apache.org/legal/">legal
policy</a>, <a href="http://www.apache.org/foundation/marks/">brand policy</a>,

+using <a href="http://www.apache.org/dev/#mail">mailing lists</a>, etc., which
are <a href="https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different">documented
in various places</a>. </p>
+<p>A primary purpose of the basic requirements the ASF places on it’s 
+projects are to help ensure long-lived and stable projects by having 
+a broad enough community to maintain the project even in the potential 
+absence of any individual volunteer or any sea change at a major vendor 
+in that area. The Apache project governance model is explicitly based 
+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>
+<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>
+<h2 id="apache_projects_are_managed_independently">Apache projects are managed independently</h2>
+<p>Apache projects should 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>
+<p>All Apache projects must release their code under the <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache
License</a>, which clearly specifies the minimum restrictions that users of Apache software
must agree to. Apache software is all about being able to use it for virtually whatever our
users want: open source, proprietary, secret: we’re happy to have users take our software
(although not our name) for virtually any purpose. While our legal guidelines allow certain
other software licenses to be used for specific dependencies, the software we release always
uses our license.</p>
+<p>Extending this idea, users of Apache software should be able to find our software,
learn how to use it, and actually apply it to all its common use cases solely by going to
the Apache project’s own website. Apache projects should provide sufficient documentation,
install features, basic user help (through mailing lists) and services for the common use
cases to the user, without them having to rely on third parties. It is important that our
users can both make use of our software freely – both in terms of not having to pay for
the software, as well as not having to worry about IP claims or other more restrictive licenses
on either the software or the configurations or other common materials required to actually
use the software.</p>
+<h2 id="apache_projects_are_non-commercial">Apache projects are non-commercial</h2>
+<p>The ASF’s mission is to produce software for the public good. All Apache software
is always available for free, and solely under the Apache License. While our projects manage
the technical implementation of their individual software products independently, Apache software
is released from the ASF, and is always meant to serve the public good.</p>
+<p>We’re happy to have third parties, including for-profit corporations, take
our software and use it for their own purposes – even when in some cases it may technically
compete with Apache software. However it is important in these cases to ensure that the brand
and reputation of the Apache project is not misused by third parties for their own purposes.
It is important for the longevity and community health of our projects that they get the appropriate
credit for producing our freely available software.</p>
+                         </DIV>
+                     </DIV>
+                  </DIV>
+                </td>
+            </TR>
+        </TABLE>
+
+        <DIV class="footer">
+            Copyright © 2003-2011, The Apache Software Foundation&nbsp;&nbsp;
+        </DIV>
+
+    </BODY>
+</HTML>



Mime
View raw message