community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r982199 - in /websites/staging/community/trunk/content: ./ apache-way/apache-project-maturity-model.html
Date Tue, 08 Mar 2016 10:45:49 GMT
Author: buildbot
Date: Tue Mar  8 10:45:49 2016
New Revision: 982199

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 Tue Mar  8 10:45:49 2016
@@ -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
Tue Mar  8 10:45:49 2016
@@ -169,6 +169,8 @@ h2:hover > .headerlink, h3:hover > .head
 <p>This is the first version of this document, as of February 2015.</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
 <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>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>

View raw message