svn commit: r796303 - in /websites/staging/airavata/trunk/content/airavata: community/get-involved.html development/edit-cms-website.html

[bu...@apache.org]

Author: buildbot
Date: Wed Sep 28 03:23:58 2011
New Revision: 796303

Log:
Staging update by buildbot

Modified:
    websites/staging/airavata/trunk/content/airavata/community/get-involved.html
    websites/staging/airavata/trunk/content/airavata/development/edit-cms-website.html

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 Wed Sep 28 03:23:58 2011
@@ -119,19 +119,19 @@ set of simple processes to ensure things
 official approval for legal or process reasons (e.g. a release or a new committer). 
 Most of the time we work with the consensus building techniques documented below.</p>
 <h3 id="lazy_consensus">Lazy Consensus</h3>
-<p><a href="/airavata/docs/governance/lazyConsensus.html">Lazy consensus</a> is the first, and possibly the most important, consensus building 
+<p><a href="/airavata/community/governance/lazyConsensus.html">Lazy consensus</a> is the first, and possibly the most important, consensus building 
 tool we have. Essentially lazy consensus means that you don't need to get explicit
 approval to proceed, but you need to be prepared to listen if someone objects.</p>
 <h3 id="consensus_building">Consensus Building</h3>
 <p>Sometimes lazy consensus is not appropriate. In such cases it is necessary to
 make a proposal to the mailing list and discuss options. There are mechanisms
 for quickly showing your support or otherwise for a proposal and 
-<a href="/airavata/docs/governance/consensusBuilding.html">building consensus</a> amongst the community.</p>
-<p>Once there is a consensus people can proceed with the work under the <a href="/airavata/docs/governance/lazyConsensus.html">lazy 
+<a href="/airavata/community/governance/consensusBuilding.html">building consensus</a> amongst the community.</p>
+<p>Once there is a consensus people can proceed with the work under the <a href="/airavata/community/governance/lazyConsensus.html">lazy 
 consensus</a> model.</p>
 <h3 id="voting">Voting</h3>
 <p>Occasionally a "feel" for consensus is not enough. Sometimes we need to 
-have a measurable consensus. For example, when <a href="/airavata/docs/governance/voting.html">voting</a> in new committers or 
+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>
   </div>
 

Modified: websites/staging/airavata/trunk/content/airavata/development/edit-cms-website.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/development/edit-cms-website.html (original)
+++ websites/staging/airavata/trunk/content/airavata/development/edit-cms-website.html Wed Sep 28 03:23:58 2011
@@ -89,11 +89,13 @@ and sub-directories.</p>
 <p>The website is hosted in a Content Management System (CMS). You will not edit the
 HTML pages directly. The actual edit is splittup in 2 parts:</p>
 <ol>
-<li>
-<p>First you edit the content which is provided as <a href="http://en.wikipedia.org/wiki/Markdown">Markdown text</a> (mdtext).
+<li>First you edit the content which is provided as <a href="http://en.wikipedia.org/wiki/Markdown">Markdown text</a> (mdtext).
     This will be committed into the staging section (see the SVN commit mail with
     your log message) and automatically build HTML files out of the the mdtext files
-    (see the commit mail with "Staging update by buildbot" as log messge).</p>
+    (see the commit mail with "Staging update by buildbot" as log messge).
+     Before you publish youe changes in next step, you can verify the changes on the staging site<ul>
+<li>http://airavata.staging.apache.org/airavata/index.html. </li>
+</ul>
 </li>
 <li>
 <p>Second you need to publish the staging part to the production section (see the