svn commit: r919030 - in /websites/staging/airavata/trunk/content: ./ community/mailing-lists.html

[bu...@apache.org]

Author: buildbot
Date: Mon Aug 11 12:41:32 2014
New Revision: 919030

Log:
Staging update by buildbot for airavata

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

Propchange: websites/staging/airavata/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Aug 11 12:41:32 2014
@@ -1 +1 @@
-1616938
+1617267

Modified: websites/staging/airavata/trunk/content/community/mailing-lists.html
==============================================================================
--- websites/staging/airavata/trunk/content/community/mailing-lists.html (original)
+++ websites/staging/airavata/trunk/content/community/mailing-lists.html Mon Aug 11 12:41:32 2014
@@ -159,7 +159,7 @@
 </li>
 </ul>
 <h3 id="apache-airavata-architecture-mailing-list">Apache Airavata Architecture Mailing List</h3>
-<p>To have the architecture discussion focused, the . This list is used to coordinate activities and ensure we are all pulling in the same direction.</p>
+<p>To have the architecture discussion focused and managable for casual contributors, airavata conducts most of the architecture brainstorming on a architecture mailing list. This list is used to coordinate activities and ensure we are all pulling in the same direction.</p>
 <ul>
 <li>Subscribe: <a href="mailto:architecture-subscribe@airavata.apache.org">architecture-subscribe@airavata.apache.org</a></li>
 <li>Post (after subscription): <a href="mailto:architecture@airavata.apache.org">architecture@airavata.apache.org</a></li>
@@ -170,6 +170,18 @@
 </ul>
 </li>
 </ul>
+<h3 id="apache-airavata-issues-mailing-list">Apache Airavata Issues Mailing List</h3>
+<p>To keep the dev list traffic down from JIRA issues, comments, GitHUB Pull Requests and comments, these are sent to the issues mailing list. Developers are encouraged to subscribe to this list to follow all development roadmaps and code reviews. </p>
+<ul>
+<li>Subscribe: <a href="mailto:issues-subscribe@airavata.apache.org">issues-subscribe@airavata.apache.org</a></li>
+<li>Post (after subscription): <a href="mailto:issues@airavata.apache.org">issues@airavata.apache.org</a></li>
+<li>Unsubscribe: <a href="mailto:issues-unsubscribe@airavata.apache.org">issues-unsubscribe@airavata.apache.org</a></li>
+<li>Archives:<ul>
+<li><a href="http://markmail.org/search/+list:org.apache.airavata.issues">Markmail</a></li>
+<li><a href="http://mail-archives.apache.org/mod_mbox/airavata-issues/">Apache</a></li>
+</ul>
+</li>
+</ul>
 <h3 id="apache-airavata-commit-mailing-list">Apache Airavata Commit Mailing List</h3>
 <p>This is where the community receives automated notifications of 
 any changes to the airavata code and documentation.</p>