Author: mseidel Date: Tue Aug 22 22:41:15 2017 New Revision: 1805835 URL: http://svn.apache.org/viewvc?rev=1805835&view=rev Log: Fixed typo in link
Modified: openoffice/site/trunk/content/orientation/decision-making.mdtext Modified: openoffice/site/trunk/content/orientation/decision-making.mdtext URL: http://svn.apache.org/viewvc/openoffice/site/trunk/content/orientation/decision-making.mdtext?rev=1805835&r1=1805834&r2=1805835&view=diff ============================================================================== --- openoffice/site/trunk/content/orientation/decision-making.mdtext (original) +++ openoffice/site/trunk/content/orientation/decision-making.mdtext Tue Aug 22 22:41:15 2017 @@ -27,7 +27,7 @@ In the previous Module we read about col 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. - Terms that you might need to know related to the above are: [JFDI](http://www.urbandictionary.com/define.php?term=JFDI) and ["assuming lazy consensus"](.http://www.apache.org/foundation/glossary.html#LazyConsensus). + Terms that you might need to know related to the above are: [JFDI](http://www.urbandictionary.com/define.php?term=JFDI) and ["assuming lazy consensus"](https://www.apache.org/foundation/glossary.html#LazyConsensus). 2. When is RTC, Review-Then-Commit Used?