airavata-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r824093 - in /websites/staging/airavata/trunk/content: ./ airavata/community/get-involved.html
Date Mon, 02 Jul 2012 15:27:41 GMT
Author: buildbot
Date: Mon Jul  2 15:27:39 2012
New Revision: 824093

Log:
Staging update by buildbot for airavata

Modified:
    websites/staging/airavata/trunk/content/   (props changed)
    websites/staging/airavata/trunk/content/airavata/community/get-involved.html

Propchange: websites/staging/airavata/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jul  2 15:27:39 2012
@@ -1 +1 @@
-1356297
+1356300

Modified: websites/staging/airavata/trunk/content/airavata/community/get-involved.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/community/get-involved.html (original)
+++ websites/staging/airavata/trunk/content/airavata/community/get-involved.html Mon Jul 
2 15:27:39 2012
@@ -118,7 +118,7 @@ is almost certainly a role for you. </p>
 <li>help new users</li>
 <li>recommend the project to others</li>
 <li>test the code and report bugs</li>
-<li>fix bugs</li>
+<li>fix bugs and [submit patches] [5]</li>
 <li>give us feedback on required features</li>
 <li>write and update the software</li>
 <li>create artwork</li>
@@ -157,6 +157,7 @@ consensus</a> model.</p>
 <p>Occasionally a "feel" for consensus is not enough. Sometimes we need to 
 have a measurable consensus. For example, when <a href="/airavata/community/governance/voting.html">voting</a>
in new committers or 
 to approve a release. </p>
+<p>[5] :/airavata/development/submit-patch.html</p>
   </div>
 
   <!--<div id="rightnav">



Mime
View raw message