Author: buildbot
Date: Tue Aug 22 22:41:20 2017
New Revision: 1017139
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 Tue Aug 22 22:41:20 2017
@@ -1 +1 @@
-1796425
+1805835
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
Tue Aug 22 22:41:20 2017
@@ -132,7 +132,7 @@ h2:hover > .headerlink, h3:hover > .head
<p>The two primary ways of managing product changes go by the names
Commit-Then-Review (CTR) and Review-Then-Commit (RTC). For most cases we
operate in a CTR mode, meaning that our <a
href="http://www.apache.org/foundation/how-it-works.html#committers";>Committers</a>
are able to check in changes as they desire, with no advance approval or
review.</p>
<p>We trust our Committers to do the right thing. By default Committers don't
ask permission before acting. They avoid unnecessary discussion and email
traffic. This is not because they are anti-social. This is because they realize
that in a project of this size it is impossible to discuss every small change
in advance. Discussing too much is both
unnecessary and unproductive. We have a "time machine" called Subversion that
allows us to undo any changes to the product or website. So if a Committer
believes that a change would be uncontroversial, and the change is
reversible, then the default approach is to go ahead make the change.</p>
-<p>Terms that you might need to know related to the above are: <a
href="http://www.urbandictionary.com/define.php?term=JFDI";>JFDI</a> and <a
href=".http://www.apache.org/foundation/glossary.html#LazyConsensus";>"assuming
lazy consensus"</a>.</p>
+<p>Terms that you might need to know related to the above are: <a
href="http://www.urbandictionary.com/define.php?term=JFDI";>JFDI</a> and <a
href="https://www.apache.org/foundation/glossary.html#LazyConsensus";>"assuming
lazy consensus"</a>.</p>
</li>
<li>
<p>When is RTC, Review-Then-Commit Used?</p>
