You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airavata.apache.org by bu...@apache.org on 2012/09/22 18:56:32 UTC
svn commit: r832766 - in /websites/staging/airavata/trunk/content: ./
community/get-involved.html community/governance/lazyConsensus.html
community/governance/voting.html community/mailing-lists.html
development/roadmap.html
Author: buildbot
Date: Sat Sep 22 16:56:31 2012
New Revision: 832766
Log:
Staging update by buildbot for airavata
Modified:
websites/staging/airavata/trunk/content/ (props changed)
websites/staging/airavata/trunk/content/community/get-involved.html
websites/staging/airavata/trunk/content/community/governance/lazyConsensus.html
websites/staging/airavata/trunk/content/community/governance/voting.html
websites/staging/airavata/trunk/content/community/mailing-lists.html
websites/staging/airavata/trunk/content/development/roadmap.html
Propchange: websites/staging/airavata/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Sep 22 16:56:31 2012
@@ -1 +1 @@
-1388437
+1388843
Modified: websites/staging/airavata/trunk/content/community/get-involved.html
==============================================================================
--- websites/staging/airavata/trunk/content/community/get-involved.html (original)
+++ websites/staging/airavata/trunk/content/community/get-involved.html Sat Sep 22 16:56:31 2012
@@ -127,7 +127,7 @@ therefore welcome and encourage particip
as easy as possible for people to get involved. </p>
<h2 id="mailing-lists">Mailing lists</h2>
<p>Your first engagement with the project should be to subscribe to our
-<a href="/mailing-lists.html">mailing lists</a>.</p>
+<a href="/community/mailing-lists.html">mailing lists</a>.</p>
<h2 id="decision-making">Decision Making</h2>
<p>The most important thing about engaging with any Apache project is that everyone
is equal. All people with an opinion are entitled to express that opinion and, where
Modified: websites/staging/airavata/trunk/content/community/governance/lazyConsensus.html
==============================================================================
--- websites/staging/airavata/trunk/content/community/governance/lazyConsensus.html (original)
+++ websites/staging/airavata/trunk/content/community/governance/lazyConsensus.html Sat Sep 22 16:56:31 2012
@@ -102,7 +102,7 @@
<div id="content">
<h1 class="title">Lazy Consensus</h1>
- <p>The concept of "Lazy Consensus" is very important in our project. Lazy
+ <p>The concept of "Lazy Consensus" is very important in any apache project. Lazy
Consensus means that when you are convinced that you know what the community
would like to see happen you can simply assume that you already have consensus
and get on with the work. You don't have to insist people discuss and/or
@@ -136,7 +136,7 @@ it accounts for different timezones and
<p>In this approach the original proposal is not insisting that there is a discussion
around their proposal, nor are they requesting that the community explicitly
supports their actions. However, this differs from assuming lazy consensus
-since it allows space and time to <a href="/openofficeorg/docs/governance/consensusBuilding.html">express support or objections</a> and corrections to
+since it allows space and time to <a href="/community/governance/consensusBuilding.html">express support or objections</a> and corrections to
the proposal before work begins. </p>
<h2 id="silence-is-consent">Silence is consent</h2>
<p>People may choose to indicate their support for the actions taken with a +1
Modified: websites/staging/airavata/trunk/content/community/governance/voting.html
==============================================================================
--- websites/staging/airavata/trunk/content/community/governance/voting.html (original)
+++ websites/staging/airavata/trunk/content/community/governance/voting.html Sat Sep 22 16:56:31 2012
@@ -109,7 +109,7 @@ release. </p>
<p>Before calling a vote it is important to ensure that the community is given time to
discuss the upcoming vote. This will be done by posting an email to the list
indicating the intention to call a vote and the options available. By the time a
-vote is called there should already be <a href="http://incubator.apache.org/openofficeorg/docs/governance/consensusBuilding.html">consensus in the community</a>. The vote
+vote is called there should already be <a href="/community/governance/consensusBuilding.html">consensus in the community</a>. The vote
itself is, normally, a formality.</p>
<h2 id="calling-a-vote">Calling a Vote</h2>
<p>Once it is time to call the vote a mail is posted with a subject starting with
@@ -181,7 +181,7 @@ and present the results. Everyone has 1
</pre></div>
-<p><a href="http://incubator.apache.org/rave/docs/governance/voting.html">See here for more information</a> <br>
+<p><a href="/community/governance/voting.html">See here for more information</a> <br>
<a href="http://community.apache.org/newcommitter.html">See here for more mail templates</a></p>
</div>
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 Sat Sep 22 16:56:31 2012
@@ -104,8 +104,7 @@
<h1 class="title">Mailing Lists</h1>
<p>We welcome you to join mailing lists and let us know about your thoughts or ideas about Apache Airavata.</p>
<h3 id="apache-airavata-user-mailing-list">Apache Airavata User Mailing List</h3>
-<p>This is where you can ask questions about Airavtaa. This list is used to coordinate
-activities and ensure we are all pulling in the same direction.</p>
+<p>This is where you can ask questions about Airavata. All the developers are subscribed to the list and you may ask questions on how to integrate Airavata into existing frameworks, or how to use Airavata out of the box. If you have a use case you are intending to use Airavata, please convey it to this list.</p>
<ul>
<li>Subscribe: <a href="mailto://users-subscribe@airavata.apache.org">users-subscribe@airavata.apache.org</a></li>
<li>Post (after subscription): <a href="mailto://users@airavata.apache.org">users@airavata.apache.org</a></li>
Modified: websites/staging/airavata/trunk/content/development/roadmap.html
==============================================================================
--- websites/staging/airavata/trunk/content/development/roadmap.html (original)
+++ websites/staging/airavata/trunk/content/development/roadmap.html Sat Sep 22 16:56:31 2012
@@ -102,18 +102,15 @@
<div id="content">
<h1 class="title">Development Roadmap</h1>
- <p>The Apache Airavata project is gearing towards its first incubation release with the following components and features:</p>
-<ul>
-<li>GFac-Axis2: An axis2 web service which can consume user defined command line descriptions and generate axis2 application web services.</li>
-<li>XBaya - A desktop application which lets users to construct, execute and monitor workflow executions. </li>
-<li>XBaya is also used in the first release as a user management, application management and data browser. In the future release we will develop web gadgets to be deployed into containers like Apache Rave.</li>
-<li>Workflow Interpreter: Axis2 wrapper around XBaya dynamic executor. This is a simple and interactive workflow execution engine. Future releases will support Apache ODE in addition to interpreter service. </li>
-<li>WS-Messenger: WS-Eventing/WS-Notification based messaging system.</li>
-<li>Registry-API: A thick client registry API for Airavata to put and get documents. Current JCR implementation is supported by Jack-Rabbit.</li>
-</ul>
-<p>Users will be able to build and deploy the entire suite or selected components with one click maven installation and axis2 deployment.
-The toolkit will enable user management in Jack Rabbit, constructing and executing third party and GFac generated services as workflows,
-monitor progress through events and catalog and browse workflow inputs and outputs. </p>
+ <p>For a detailed feature list, pleas see the release notes for indivual <a href="/about/downloads.html">releases</a>. The Apache Airavata project is gearing towards its 1.0 release. Important componets in active development include
+<em> Generic Factory Service (GFac): An axis2 web service which can consume user defined command line descriptions and generate axis2 application web services.
+</em> XBaya - A desktop application which lets users to construct, execute and monitor workflow executions.
+<em> XBaya is also used in the first release as a user management, application management and data browser. Web interfaces are in active delopment and will be targetted to be deployed into containers like Apache Rave.
+</em> Workflow Interpreter: Axis2 wrapper around XBaya dynamic executor. This is a simple and interactive workflow execution engine. Supporting third party enactment engines like Apache ODE, Taverna, Pegasus have been previously used but are currently not in active development.
+<em> WS-Messenger: WS-Eventing/WS-Notification based messaging system.
+</em> Registry-API: A thick client registry API for Airavata to manage application and workflow descriptions and access provenance data resulting from workflow executions. </p>
+<p>Users will be able to build and deploy the entire suite with one click maven installation and axis2 deployment.
+The toolkit will enable registering applications as web services, constructing and executing third party and GFac generated services as workflows, monitor progress through events and catalog and browse workflow inputs and outputs. </p>
</div>
<!--<div id="rightnav">