community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1021036 - in /websites/staging/community/trunk/content: ./ apache-way/apache-project-maturity-model.html
Date Fri, 17 Nov 2017 21:31:53 GMT
Author: buildbot
Date: Fri Nov 17 21:31:53 2017
New Revision: 1021036

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 Nov 17 21:31:53 2017
@@ -1 +1 @@

Modified: websites/staging/community/trunk/content/apache-way/apache-project-maturity-model.html
--- websites/staging/community/trunk/content/apache-way/apache-project-maturity-model.html
+++ websites/staging/community/trunk/content/apache-way/apache-project-maturity-model.html
Fri Nov 17 21:31:53 2017
@@ -169,47 +169,42 @@
   visibility: hidden;
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
> .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink
{ visibility: visible }</style>
-<h1 id="status">Status<a class="headerlink" href="#status" title="Permanent link">&para;</a></h1>
-<p>This is the first version of this document, as of February 2015.</p>
-<p>Updated October 2016 to add RE50.</p>
-<p>See <a href=""></a>
for the discussions that led to this. And thanks to the many people who provided input!</p>
-<p>Questions and feedback about this model are welcome on the <a href="">comdev
mailing list</a>.</p>
-<p>See the <a href="">Groovy
podling 2015 self-assessment</a> for an example of how to use this
-model to prepare a graduation from the <a href="">Apache
+<p>The <strong>Apache Project Maturity Model</strong> provides a suggested
framework for evaluating the overall maturity of an Apache project community and the codebase
that it maintains.  While this model is specific to Apache projects (i.e. hosted at the ASF)
many of these factors are important for any open source project.</p>
 <h1 id="overview">Overview<a class="headerlink" href="#overview" title="Permanent
-<p>The goal of this maturity model is to describe how Apache projects operate, in a
concise and high-level way.</p>
+<p>The goal of this maturity model is to describe how Apache projects operate, in a
concise and high-level way, and to provide a basic framework that projects may choose to use
to evaluate themselves.</p>
 <p>It is meant to be usable outside of Apache as well, for projects that might want
to adopt some or all of these principles. Projects that envision moving to Apache at some
point might start working towards this to prepare for their move.</p>
 <p>It does not describe all the details of how our projects operate, but aims to capture
the invariants of Apache projects and point to additional information where needed. To keep
the main model as concise as possible we use footnotes for anything that's not part of the
core model.</p>
 <p>Contrary to other maturity models, we do not define staged partial compliance levels.
A mature Apache project complies with all the elements of this model, and other projects are
welcome to pick and choose the elements that suit their goals.</p>
-<p>Note that we try to avoid using the word "must" below. The model describes the state
of a mature project, as opposed to a set of rules. </p>
+<p>Note that we try to avoid using the word "must" below. The model describes the state
of a mature project, as opposed to a set of rules. Newer projects in the Incubator might not
fit into all the parts of this model; however part of the process of Incubation should tend
to move their community behavior to fit the model.</p>
+<p>Questions and feedback about this model are welcome on the <a href="">comdev
mailing list</a>.</p>
 <h1 id="the-apache-project-maturity-model">The Apache Project Maturity Model<a class="headerlink"
href="#the-apache-project-maturity-model" title="Permanent link">&para;</a></h1>
 <p>Each item in the model has a unique ID to allow them to be easily referenced elsewhere.
 <h2 id="code">Code<a class="headerlink" href="#code" title="Permanent link">&para;</a></h2>
+<dt id="CD10">CD10</dt>
 The project produces Open Source software, for distribution to the public at no charge.
 <sup><a href="#fnref-a2e0cd066fd8f45af4e87bcdbf8d9abd3ad40872" id="fndef-a2e0cd066fd8f45af4e87bcdbf8d9abd3ad40872-0">1</a></sup>
+<dt id="CD20">CD20</dt>
 The project's code is easily discoverable and publicly accessible. 
+<dt id="CD30">CD30</dt>
 The code can be built in a reproducible way using widely available standard tools.
+<dt id="CD40">CD40</dt>
 The full history of the project's code is available via a source code 
 control system, in a way that allows any released version to be 
+<dt id="CD50">CD50</dt>
 The provenance of each line of code is established via the source code control system, in
a reliable way based on strong authentication of the 
 committer. When third-party contributions are committed, commit messages provide reliable
information about the code provenance.
@@ -220,29 +215,29 @@ committer. When third-party contribution
 <h2 id="licenses-and-copyright">Licenses and Copyright<a class="headerlink" href="#licenses-and-copyright"
title="Permanent link">&para;</a></h2>
+<dt id="LC10">LC10</dt>
 <dd>The code is released under the Apache License, version 2.0. 
+<dt id="LC20">LC20</dt>
 Libraries that are mandatory dependencies of the project's code do not create more restrictions
than the Apache License does.
 <sup><a href="#fnref-76d333d056757395d9b6eb1d62e91a57dad757fa" id="fndef-76d333d056757395d9b6eb1d62e91a57dad757fa-2">3</a></sup>

 <sup><a href="#fnref-3e4d977daeeb59a808fb0c40477b2cd50e913f2e" id="fndef-3e4d977daeeb59a808fb0c40477b2cd50e913f2e-3">4</a></sup>

+<dt id="LC30">LC30</dt>
 The libraries mentioned in LC20 are available as Open Source software. 
+<dt id="LC40">LC40</dt>
 <dd>Committers are bound by an Individual Contributor Agreement (the <a href="">"Apache
iCLA"</a>) that 
 defines which code they are allowed to commit and how they need to 
 identify code that is not their own. 
+<dt id="LC50">LC50</dt>
 The copyright ownership of everything that the project produces is clearly defined and documented.
 <sup><a href="#fnref-258df7a61c975c67bbef17d3cf7851bafd40b8fb" id="fndef-258df7a61c975c67bbef17d3cf7851bafd40b8fb-4">5</a></sup>
@@ -253,32 +248,32 @@ The copyright ownership of everything th
 <h2 id="releases">Releases<a class="headerlink" href="#releases" title="Permanent
+<dt id="RE10">RE10</dt>
 <dd>Releases consist of source code, distributed using standard and open archive 
 formats that are expected to stay readable in the long term.
 <sup><a href="#fnref-d2389850862fcc9bddabb3c2e23b13922d68e3fc" id="fndef-d2389850862fcc9bddabb3c2e23b13922d68e3fc-5">6</a></sup>

+<dt id="RE20">RE20</dt>
 Releases are approved by the project's PMC (see CS10), in order to make them an act of the
+<dt id="RE30">RE30</dt>
 Releases are signed and/or distributed along with digests that can be reliably used to validate
the downloaded archives. 
+<dt id="RE40">RE40</dt>
 <dd>Convenience binaries can be distributed alongside source code but they are not
 Apache Releases -- they are just a 
 convenience provided with no guarantee. 
+<dt id="RE50">RE50</dt>
 <dd>The release process is documented and repeatable to the extent that
 someone new to the project is able to independently generate the complete
@@ -290,7 +285,7 @@ set of artifacts required for a release.
 <h2 id="quality">Quality<a class="headerlink" href="#quality" title="Permanent link">&para;</a></h2>
+<dt id="QU10">QU10</dt>
 project is open and honest about the quality of its code. Various levels
@@ -298,26 +293,26 @@ project is open and honest about the qua
 as long as they are clearly communicated. 
+<dt id="QU20">QU20</dt>
 The project puts a very high priority on producing secure software.
 <sup><a href="#fnref-89a5257606b929cc5ced2bee207c80b43541d488" id="fndef-89a5257606b929cc5ced2bee207c80b43541d488-6">7</a></sup>

+<dt id="QU30">QU30</dt>
 The project provides a well-documented, secure and private channel to report security issues,
along with a documented way of responding to them.
 <sup><a href="#fnref-7c23a24b04dcf9b4b10423685fbd37f69b2b3783" id="fndef-7c23a24b04dcf9b4b10423685fbd37f69b2b3783-7">8</a></sup>

+<dt id="QU40">QU40</dt>
 <dd>The project puts a high priority on backwards compatibility and aims to document
any incompatible changes and provide tools and documentation to help users transition to new
+<p><dt id="QU50">QU50</dt>
  The project strives to respond to documented bug reports in a timely manner. 
@@ -325,45 +320,45 @@ The project provides a well-documented,
 <h2 id="community">Community<a class="headerlink" href="#community" title="Permanent
+<dt id="CO10">CO10</dt>
 The project has a well-known homepage that points to all the information required to operate
according to this maturity model. 
+<dt id="CO20">CO20</dt>
 The community welcomes contributions from anyone who acts in good faith and
  in a respectful manner and adds value to the project. 
+<dt id="CO30">CO30</dt>
 Contributions include not only source code, but also documentation, constructive bug 
 reports, constructive discussions, marketing and generally anything that
  adds value to the project. 
+<dt id="CO40">CO40</dt>
 The community is meritocratic and over time aims to give more rights and 
 responsibilities to contributors who add value to the project. 
+<dt id="CO50">CO50</dt>
 The way in which contributors can be granted more rights such as commit 
 access or decision power is clearly documented and is the same for all 
+<dt id="CO60">CO60</dt>
 The community operates based on consensus of its members (see CS10) who 
 have decision power. Dictators, benevolent or not, are not welcome in 
 Apache projects. 
+<dt id="CO70">CO70</dt>
 The project strives to answer user questions in a timely manner.
@@ -371,13 +366,13 @@ The project strives to answer user quest
 <h2 id="consensus-building">Consensus Building<a class="headerlink" href="#consensus-building"
title="Permanent link">&para;</a></h2>
+<p><dt id="CS10">CS10</dt>
 project maintains a public list of its contributors who have decision 
 power -- the project's PMC (Project Management Committee) consists of 
 those contributors. 
+<dt id="CS20">CS20</dt>
 Decisions are made by consensus among PMC members
@@ -387,18 +382,18 @@ Community opinions are taken into accoun
  if needed.  
+<p><dt id="CS30">CS30</dt>
  Documented voting rules are used to build consensus when discussion is not sufficient.
  <sup><a href="#fnref-9b0cf71f04bcd81dddbf6199f1c771e27566611e" id="fndef-9b0cf71f04bcd81dddbf6199f1c771e27566611e-9">10</a></sup>

+<p><dt id="CS40">CS40</dt>
  Apache projects, vetoes are only valid for code commits and are 
 justified by a technical explanation, as per the Apache voting rules 
 defined in CS30. 
+<dt id="CS50">CS50</dt>
 All "important" discussions happen asynchronously in written form on the 
@@ -412,19 +407,24 @@ that affect the project are also documen
 <h2 id="independence">Independence<a class="headerlink" href="#independence" title="Permanent
+<dt id="IN10">IN10</dt>
 The project is independent from any corporate or organizational influence.
 <sup><a href="#fnref-764b2c2fd32deb4ff73ea01efa67c8556303c359" id="fndef-764b2c2fd32deb4ff73ea01efa67c8556303c359-11">12</a></sup>

+<dt id="IN20">IN20</dt>
 <dd>Contributors act as themselves as opposed to representatives of a corporation or
-<h1 id="related-efforts-inspiration">Related efforts, inspiration<a class="headerlink"
href="#related-efforts-inspiration" title="Permanent link">&para;</a></h1>
+<h1 id="how-to-use-the-apache-project-maturity-model">How To Use The Apache Project
Maturity Model<a class="headerlink" href="#how-to-use-the-apache-project-maturity-model"
title="Permanent link">&para;</a></h1>
+<p>See the <a href="">Groovy
podling 2015 self-assessment</a> for an example of how to use this
+model to prepare a graduation from the <a href="">Apache
+<p><strong>Remember:</strong> This model is a suggested guide; it is not
a requirements document.  The model shows what generally good behaviors in an Apache project
look like.</p>
+<h2 id="other-open-source-project-models">Other Open Source Project Models<a class="headerlink"
href="#other-open-source-project-models" title="Permanent link">&para;</a></h2>
+<p>See <a href=""></a>
for the discussions that led to this. And thanks to the many people who provided input! The
links below are both inspirations for our model above, and are some of the other ways that
FOSS project participants have tried to quantify ways to measure open source projects.</p>
 <li><a href=""></a></li>
 <li><a href=""></a></li>
@@ -434,7 +434,11 @@ The project is independent from any corp
 <li><a href=""></a></li>
 <li><a href=""></a></li>
-<h1 id="footnotes">Footnotes<a class="headerlink" href="#footnotes" title="Permanent
+<h2 id="status-document-version">Status / Document Version<a class="headerlink"
href="#status-document-version" title="Permanent link">&para;</a></h2>
+<p>v 1.0, February 2015, defined by consensus by Apache Community Development project.</p>
+<p>v 1.1, October 2016 added RE50.</p>
+<p>(November 2017 this document was clarified, but the model was not changed)</p>
+<h3 id="footnotes">Footnotes<a class="headerlink" href="#footnotes" title="Permanent

View raw message