svn commit: r998244 - in /websites/staging/taverna/trunk: cgi-bin/ content/ content/community/chat.html content/community/lists.html

[bu...@apache.org]

Author: buildbot
Date: Mon Sep 26 01:49:19 2016
New Revision: 998244

Log:
Staging update by buildbot for taverna

Modified:
    websites/staging/taverna/trunk/cgi-bin/   (props changed)
    websites/staging/taverna/trunk/content/   (props changed)
    websites/staging/taverna/trunk/content/community/chat.html
    websites/staging/taverna/trunk/content/community/lists.html

Propchange: websites/staging/taverna/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Sep 26 01:49:19 2016
@@ -1 +1 @@
-1762249
+1762250

Propchange: websites/staging/taverna/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Sep 26 01:49:19 2016
@@ -1 +1 @@
-1762249
+1762250

Modified: websites/staging/taverna/trunk/content/community/chat.html
==============================================================================
--- websites/staging/taverna/trunk/content/community/chat.html (original)
+++ websites/staging/taverna/trunk/content/community/chat.html Mon Sep 26 01:49:19 2016
@@ -193,9 +193,9 @@ informal communications.</p>
 <p>Note that the chat service is provided by a third-party and that
 joining the chat will require either a GitHub or Twitter account.</p>
 <div id="content"><div class="alert alert-info alert-dismissible" role="alert"><p><span class="glyphicon glyphicon-info-sign" aria-hidden="true"></span><strong> Note:</strong>
-The <code>apache/taverna</code> chat room is <strong>logged publicly</strong>.
-All participants are expected to follow the
-<a href="https://www.apache.org/foundation/policies/conduct.html">Apache Code of Conduct</a>.
+The Taverna chat room is <strong>logged publicly</strong>.
+All participants are expected to follow ASF's
+<a class="alert-link" href="https://www.apache.org/foundation/policies/conduct.html">Code of Conduct</a>.
 </div></div>
 
 <h2 id="decisions-happen-on-the-mailing-lists">Decisions happen on the mailing lists<a class="headerlink" href="#decisions-happen-on-the-mailing-lists" title="Permanent link">&para;</a></h2>
@@ -203,30 +203,35 @@ All participants are expected to follow
 <p>If it didn't happen on the <a href="/community/lists">mailing list</a>, it didn't happen.</p>
 </blockquote>
 <p>IRC and web chat channels can be great for informal enquiries like
-("Where do I find <code>ClassB.java</code>"), code pastes and
-and experimentation.</p>
-<p>However by their synchronous nature chat rooms can
+<em>"Where do I find <code>ClassB.java</code>"</em>, code pastes and
+and experimentation, particuarly using Gitter's
+<a href="https://gitter.zendesk.com/hc/en-us/articles/200176682-Markdown-basics">Markdown support</a>!</p>
+<p>However by their synchronous nature, chat rooms can
 fail to include the wider community who might not share your
-time zone, have the same day/night or work/life balance.</p>
+time zone or have the same day/night pattern.</p>
 <p>In addition some decisions are better taken in a paced conversation;
-there's usually no rush. Email threads also make it easier to keep
-issues separate, and findable later in the
+there's usually no rush. Email threads with a good <em>Subject:</em>
+also make it easier to keep issues separate; as well as later
+being findable in the
 <a href="https://lists.apache.org/list.html?dev@taverna.apache.org">list archive</a>.</p>
-<p>For all project decisions and information we therefore always
-use the Taverna <a href="/community/lists">mailing list</a>.</p>
+<p>We therefore always
+use the Taverna <a href="/community/lists">mailing list</a>
+<em>for all project decisions and information purposes</em>.</p>
 <p>It's OK if you get a good idea on the chat; just send an email
 afterwards to the list. To be inclusive,
-don't use a form like
-<em>"We decided that Foo could be replaced with Bar"</em>,
+try not to use a form like
+<em>"We decided that <code>Foo</code> should be replaced with <code>Bar</code>"</em>,
 but rather use a neutral form like
-<em>"One idea is to replace Foo with Bar"</em>.</p>
+<em>"One idea is to replace <code>Foo</code> with <code>Bar</code>"</em>.</p>
 <h2 id="irc-channel">IRC channel<a class="headerlink" href="#irc-channel" title="Permanent link">&para;</a></h2>
 <p>The Taverna community previously used the
 IRC chat channel <a href="irc://irc.freenode.net/%23taverna">#taverna</a>
-on <a href="http://freenode.net/">irc.freenode.net</a>.</p>
+on <a href="http://freenode.net/">irc.freenode.net</a>, which public
+<a href="http://wilderness.apache.org/channels/#logs-#taverna">log</a>
+remains available.</p>
 <p><a href="https://irc.gitter.im/">Gitter provides an IRC bridge</a>
 which should work with most IRC clients to access
-the apahce/taverna Gitter room.</p></div>
+the <code>apache/taverna</code> Gitter room.</p></div>
 
     </div>
 

Modified: websites/staging/taverna/trunk/content/community/lists.html
==============================================================================
--- websites/staging/taverna/trunk/content/community/lists.html (original)
+++ websites/staging/taverna/trunk/content/community/lists.html Mon Sep 26 01:49:19 2016
@@ -191,17 +191,15 @@ h2:hover > .headerlink, h3:hover > .head
 a say in the future development of Taverna. Anyone using the Taverna APIs in their own code
 would be well advised to join both <em>dev@taverna</em> and <em>users@taverna</em>.
 The <a href="#private">private mailing list</a> is only for information that should not be made public.</p>
+<h2 id="code-of-conduct">Code of conduct<a class="headerlink" href="#code-of-conduct" title="Permanent link">&para;</a></h2>
+<p>All participants on Apache mailing lists are expected to follow Apache Software Foundation's
+<a href="https://www.apache.org/foundation/policies/conduct.html">Code of Conduct</a>.</p>
 <h2 id="public-mailing-lists">Public mailing lists<a class="headerlink" href="#public-mailing-lists" title="Permanent link">&para;</a></h2>
 <div id="content"><div class="alert alert-info alert-dismissible" role="alert"><p><span class="glyphicon glyphicon-info-sign" aria-hidden="true"></span><strong> Note:</strong>
-The mailing lists (except private@taverna) are
-<a href="https://lists.apache.org/list.html?dev@taverna.apache.org">logged publicly</a>.
-All participants are expected to follow the
-<a href="https://www.apache.org/foundation/policies/conduct.html">Apache Code of Conduct</a>.
+All participants are expected to follow ASF's
+<a class="alert-link" href="https://www.apache.org/foundation/policies/conduct.html">Code of Conduct</a>.
 </div></div>
 
-<h1 id="code-of-conduct">Code of conduct<a class="headerlink" href="#code-of-conduct" title="Permanent link">&para;</a></h1>
-<p>All participants on Apache mailing lists are expected to follow the
-<a href="https://www.apache.org/foundation/policies/conduct.html">Apache Code of Conduct</a>.</p>
 <p><a name="users"></a></p>
 <h3 id="userstaverna">users@taverna<a class="headerlink" href="#userstaverna" title="Permanent link">&para;</a></h3>
 <p><a class="btn btn-primary" href="mailto:users-subscribe@taverna.incubator.apache.org" role="button">Subscribe</a>