svn commit: r1819697 - /openoffice/site/trunk/content/orientation/decision-making.mdtext

[ms...@apache.org]

Author: mseidel
Date: Sat Dec 30 22:41:44 2017
New Revision: 1819697

URL: http://svn.apache.org/viewvc?rev=1819697&view=rev
Log:
Fixed 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=1819697&r1=1819696&r2=1819697&view=diff
==============================================================================
--- openoffice/site/trunk/content/orientation/decision-making.mdtext (original)
+++ openoffice/site/trunk/content/orientation/decision-making.mdtext Sat Dec 30 22:41:44 2017
@@ -76,9 +76,9 @@ In the previous Module we read about col
 
 	3. 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.
 
-	4. There is one disorder of community decision making that is common enough to warrant a colorful name:  [bikeshedding](http://bikeshed.com/). Follow the link and read more about this topic.
+	4. There is one disorder of community decision making that is common enough to warrant a colorful name: [bikeshedding](http://bikeshed.com/). Follow the link and read more about this topic.
 
-  5. To apply the above skills, be sure you are subscribed to the project's [main mailing list](http://openoffice.apache.org/mailing-lists.html#development-mailing-list). 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!
+  5. To apply the above skills, be sure you are subscribed to the project's [main mailing list](https://openoffice.apache.org/mailing-lists.html#development-mailing-list-public). 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!
 
 Congratulations, you have completed this Module!