| Title: |
| Notice: Licensed to the Apache Software Foundation (ASF) under one |
| or more contributor license agreements. See the NOTICE file |
| distributed with this work for additional information |
| regarding copyright ownership. The ASF licenses this file |
| to you under the Apache License, Version 2.0 (the |
| "License"); you may not use this file except in compliance |
| with the License. You may obtain a copy of the License at |
| . |
| http://www.apache.org/licenses/LICENSE-2.0 |
| . |
| Unless required by applicable law or agreed to in writing, |
| software distributed under the License is distributed on an |
| "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY |
| KIND, either express or implied. See the License for the |
| specific language governing permissions and limitations |
| under the License. |
| |
| |
| # Web chat for Apache Taverna |
| |
| Some of the Apache Taverna developers and users hang out on the Gitter |
| web chat **[apache/taverna](https://gitter.im/apache/taverna)** for more |
| informal communications. |
| |
| Feel free to join us! |
| |
| <a class="btn btn-primary" target="_blank" href="https://gitter.im/apache/taverna" role="button">Join Chat</a> |
| |
| Note that the chat service is provided by a third-party and that |
| joining the chat will require either a GitHub or Twitter account. |
| |
| <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 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> |
| |
| ## Decisions happen on the mailing lists |
| |
| > If it didn't happen on the [mailing list](/community/lists), it didn't happen. |
| |
| IRC and web chat channels can be great for informal enquiries like |
| _"Where do I find `ClassB.java`"_, code pastes and |
| and experimentation, particuarly using Gitter's |
| [Markdown support](https://gitter.zendesk.com/hc/en-us/articles/200176682-Markdown-basics)! |
| |
| However by their synchronous nature, chat rooms can |
| fail to include the wider community who might not share your |
| time zone or have the same day/night pattern. |
| |
| In addition some decisions are better taken in a paced conversation; |
| there's usually no rush. Email threads with a good _Subject:_ |
| also make it easier to keep issues separate; as well as later |
| being findable in the |
| [list archive](https://lists.apache.org/list.html?dev@taverna.apache.org). |
| |
| |
| We therefore always |
| use the Taverna [mailing list](/community/lists) |
| *for all project decisions and information purposes*. |
| |
| It's OK if you get a good idea on the chat; just send an email |
| afterwards to the list. To be inclusive, |
| try not to use a form like |
| _"We decided that `Foo` should be replaced with `Bar`"_, |
| but rather use a neutral form like |
| _"One idea is to replace `Foo` with `Bar`"_. |
| |
| ## IRC channel |
| |
| The Taverna community previously used the |
| IRC chat channel [#taverna](irc://irc.freenode.net/%23taverna) |
| on [irc.freenode.net](http://freenode.net/), which public |
| [log](http://wilderness.apache.org/channels/#logs-#taverna) |
| remains available. |
| |
| [Gitter provides an IRC bridge](https://irc.gitter.im/) |
| which should work with most IRC clients to access |
| the `apache/taverna` Gitter room. |