Author: buildbot
Date: Thu Jun 27 16:46:39 2013
New Revision: 867645
Log:
Staging update by buildbot for openoffice
Modified:
websites/staging/openoffice/trunk/content/ (props changed)
websites/staging/openoffice/trunk/content/orientation/decision-making.html
Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jun 27 16:46:39 2013
@@ -1 +1 @@
-1492384
+1497436
Modified:
websites/staging/openoffice/trunk/content/orientation/decision-making.html
==============================================================================
--- websites/staging/openoffice/trunk/content/orientation/decision-making.html
(original)
+++ websites/staging/openoffice/trunk/content/orientation/decision-making.html
Thu Jun 27 16:46:39 2013
@@ -85,8 +85,7 @@
<h1 id="project-management-pmc">Project Management PMC</h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/";>Project Blog</a></li>
-<li><a href="/pmc-faqs.html">PMC FAQs</a><br />
-</li>
+<li><a href="/pmc-faqs.html">PMC FAQs</a> </li>
</ul>
<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
<ul>
@@ -103,9 +102,6 @@
open source software project, especially one at Apache, then much of this
material will already be familiar to you.</p>
<ol>
<li>
-<p>Please send an email to <a
href="mailto:[email protected]?subject=Starting Decision Making
Module">[email protected]</a> to let us know you are working on this
module.</p>
-</li>
-<li>
<p>In the previous Module we read about collaboration on the mailings lists,
how to do it efficiently and how to avoid the most common pitfalls. We use the
mailing lists for many things,
for asking questions, for sharing information or the like. But one of the
most important uses of the mailing list is for decision making. It is
important to understand
how decisions are made in an Apache community. Here are a few general
principles that you should keep in mind:</p>
@@ -131,8 +127,7 @@ on the mailing list.</p>
<li>
<p>A Committer can also voluntarily invocate a RTC on their own changes. For
example the Committer might be considering a change that of greater
significance. Maybe he would
value additional input, or technical review. Maybe the change is
controversial or require coordination. If CTR is not appropriate then one can
make a proposal and send it to
-the dev mailing list.<br />
-</p>
+the dev mailing list. </p>
</li>
<li>
<p>The convention is to send all proposals in their own new thread. (Don't
hide a proposal 10 posts deep in an existing thread). Put "[PROPOSAL]" in the
subject line or
@@ -171,8 +166,8 @@ Keep your eye out for terms like "propos
not perfect. But we work best and have the most fun when we follow the above
guidelines. And so will you when you apply then in your own list
communications!</p>
</li>
<li>
-<p>Congratulations! You have completed this Module Please send a note to <a
href="mailto:[email protected]?subject=Completed Decision Making
Module">[email protected]</a> so
-we all know. This is also a good opportunity to send along any feedback or
questions you might have on this Orientation Module.</p>
+<p>Congratulations, you have completed this Module! If you have any questions
or feedback on this module,
+please send a note to <a
href="mailto:[email protected]?subject=Comments%20on%20Decision%20Making%20Module";>[email protected]</a>.</p>
</li>
</ol>
</div>
