Author: buildbot
Date: Mon Mar 26 20:01:32 2012
New Revision: 810116
Log:
Staging update by buildbot for rave
Modified:
websites/staging/rave/trunk/content/ (props changed)
websites/staging/rave/trunk/content/apachecon2011-meetup.html
websites/staging/rave/trunk/content/docs/governance/consensusBuilding.html
websites/staging/rave/trunk/content/docs/governance/lazyConsensus.html
websites/staging/rave/trunk/content/get-involved.html
Propchange: websites/staging/rave/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Mar 26 20:01:32 2012
@@ -1 +1 @@
-1305522
+1305526
Modified: websites/staging/rave/trunk/content/apachecon2011-meetup.html
==============================================================================
--- websites/staging/rave/trunk/content/apachecon2011-meetup.html (original)
+++ websites/staging/rave/trunk/content/apachecon2011-meetup.html Mon Mar 26
20:01:32 2012
@@ -72,7 +72,7 @@ place at the ApacheCon venue in Vancouve
<p>This event is FREE to the public, even if you are not attending ApacheCon
And don't forget to check out the <a
href="http://na11.apachecon.com/pages/meetups";>list</a> of other MeetUps @
ApacheCon</p>
<p>Feel free to update this page or send suggestions to the list. If you're
new
-to editing the website, see the <a
href="http://incubator.apache.org/rave/edit-website.html";>help page</a> for how
to get started.</p>
+to editing the website, see the <a href="/edit-website.html">help page</a> for
how to get started.</p>
<h3 id="where-and-when">Where and When</h3>
<p>Wednesday, 9 November, 8-10pm
The Westin Bayshore Vancouver, 1601 Bayshore Drive Vancouver, Canada
Modified:
websites/staging/rave/trunk/content/docs/governance/consensusBuilding.html
==============================================================================
--- websites/staging/rave/trunk/content/docs/governance/consensusBuilding.html
(original)
+++ websites/staging/rave/trunk/content/docs/governance/consensusBuilding.html
Mon Mar 26 20:01:32 2012
@@ -100,7 +100,7 @@ that when someone wants to summarise a d
add up the strength of feeling of the community and decide if there is
consensus
or not.</p>
<p>Once there is a clear consensus members of the community can proceed with
-the work under the <a href="/rave/docs/governance/lazyConsensus.html">lazy
consensus</a> model.</p>
+the work under the <a href="/docs/governance/lazyConsensus.html">lazy
consensus</a> model.</p>
</div>
<div id="footer">
Modified: websites/staging/rave/trunk/content/docs/governance/lazyConsensus.html
==============================================================================
--- websites/staging/rave/trunk/content/docs/governance/lazyConsensus.html
(original)
+++ websites/staging/rave/trunk/content/docs/governance/lazyConsensus.html Mon
Mar 26 20:01:32 2012
@@ -98,7 +98,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="/rave/docs/governance/consensusBuilding.html">express support or
objections</a> and corrections to
+since it allows space and time to <a
href="/docs/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/rave/trunk/content/get-involved.html
==============================================================================
--- websites/staging/rave/trunk/content/get-involved.html (original)
+++ websites/staging/rave/trunk/content/get-involved.html Mon Mar 26 20:01:32
2012
@@ -89,7 +89,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="/rave/mailing-lists.html">mailing lists</a>.</p>
+<a href="/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
@@ -101,19 +101,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="/rave/docs/governance/lazyConsensus.html">Lazy consensus</a> is
the first, and possibly the most important, consensus building
+<p><a href="/docs/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="/rave/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="/rave/docs/governance/lazyConsensus.html">lazy
+<a href="/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="/docs/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="/rave/docs/governance/voting.html">voting</a> in new committers or
+have a measurable consensus. For example, when <a
href="/docs/governance/voting.html">voting</a> in new committers or
to approve a release. </p>
<h2 id="contributing-guidelines">Contributing Guidelines</h2>
<p>We welcome code contributions for both existing and new project issues. If
you wish to contribute a solution to an existing entry in
@@ -121,7 +121,7 @@ to approve a release. </p>
Apache's Jira and selecting the "Grant license to ASF for inclusion" option is
required. Then submit your patch to
the <a href="https://reviews.apache.org";>Apache review system</a> and post a
review request to the Apache Rave developer mailing list.</p>
<p>If you wish to submit a solution to a problem that has not been identified
in Rave's Jira, first create the new issue following our
-<a href="/rave/issue-management.html">guidelines</a> and then submit your
patch to the review system as before.</p>
+<a href="/issue-management.html">guidelines</a> and then submit your patch to
the review system as before.</p>
<p>In either case, the easiest way to create a patch on the command line is by
running the command ''svn diff > Rave-XYZ.patch'' from
the top level Apache Rave directory, where XYZ is the Jira issue number.</p>
</div>
