Author: buildbot
Date: Sat Dec 30 22:41:49 2017
New Revision: 1023006
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 Sat Dec 30 22:41:49 2017
@@ -1 +1 @@
-1819692
+1819697
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
Sat Dec 30 22:41:49 2017
@@ -191,12 +191,12 @@ list.</p>
<p>Another aspect of decision making in an Apache project is the "veto". Every
Committer has the ability to "veto" a change, for technical reasons, provided
he explains the technical reasons for the veto, describes an alternative
approach, and offers to help implement the alternative approach. Vetos are
quite rare.</p>
</li>
<li>
-<p>There is one disorder of community decision making that is common enough to
warrant a colorful name: <a href="http://bikeshed.com/";>bikeshedding</a>.
Follow the link and read more about this topic.</p>
+<p>There is one disorder of community decision making that is common enough to
warrant a colorful name: <a href="http://bikeshed.com/";>bikeshedding</a>.
Follow the link and read more about this topic.</p>
</li>
</ol>
</li>
<li>
-<p>To apply the above skills, be sure you are subscribed to the project's <a
href="http://openoffice.apache.org/mailing-lists.html#development-mailing-list";>main
mailing list</a>. Keep your eye out for terms like "proposal", "lazy
consensus", "vote" or "veto" and see how they are used in practice. Compare
actual practice to the above descriptions. No, we're 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>
+<p>To apply the above skills, be sure you are subscribed to the project's <a
href="https://openoffice.apache.org/mailing-lists.html#development-mailing-list-public";>main
mailing list</a>. Keep your eye out for terms like "proposal", "lazy
consensus", "vote" or "veto" and see how they are used in practice. Compare
actual practice to the above descriptions. No, we're 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>
</ol>
<p>Congratulations, you have completed this Module!</p>
