Merge pull request #439 from tdnaugle/broken-links1

First Set of Broken Website Links

website/_includes/navbar.html

@@ -90,9 +90,6 @@
                            href="/documentation/developers/">Developer Documentation</a>
                         <a class="dropdown-item"
                            href="/community/coc.html">Code of Conduct</a>
-                        <a class="dropdown-item"
-                           href="/404.html">Partners and Supporters</a>
-<!--                        Maybe make a new page that merges professional support and powered-by-mahout?-->
                     </div>
                 </li>
 

website/about/how-to-contribute.md

@@ -82,7 +82,7 @@ First of all, you need to get the [Mahout source code](/developers/version-contr
 <a name="HowToContribute-MakingChanges"></a>
 ## Making Changes
 
-Before you start, you should send a message to the [Mahout developer mailing list](/general/mailing-lists,-irc-and-archives.html)
+Before you start, you should send a message to the [Mahout developer mailing list](/community/mailing-lists.html)
 (note: you have to subscribe before you can post), or file a ticket in  our [issue tracker](/developers/issue-tracker.html).
 Describe your proposed changes and check that they fit in with what others are doing and have planned for the project.  Be patient, it may take folks a while to understand your requirements.
 

website/community/mailing-lists.md

@@ -63,12 +63,6 @@ committed.
 * [http://mail-archives.apache.org/mod_mbox/mahout-dev/](http://mail-archives.apache.org/mod_mbox/mahout-dev/)
 * [http://mail-archives.apache.org/mod_mbox/mahout-user/](http://mail-archives.apache.org/mod_mbox/mahout-user/)
 
-<a name="MailingLists,IRCandArchives-ExternalArchives"></a>
-## External Archives
-
-* [MarkMail](http://mahout.markmail.org/)
-* [Gmane](http://dir.gmane.org/gmane.comp.apache.mahout.user)
-
 Please note the inclusion of a link to an archive does not imply an
 endorsement of that company by any of the committers of Mahout the Lucene
 PMC or the Apache Software Foundation. Each archive owner is solely

website/documentation/developers/developer-resources.md

@@ -38,7 +38,7 @@ All bugs, improvements, [pull requests](http://mahout.apache.org/developers/gith
 <a name="DeveloperResources-ContinuousIntegration"></a>
 ## Continuous Integration
 
-Mahout is continuously built on an hourly basis on the [Apache Jenkins](https://builds.apache.org/job/Mahout-Quality/)  build system.
+Mahout is continuously built using [Apache Maven](https://github.com/apache/mahout/actions/workflows/mahout.yml).
 
 ## Board reports
 

website/documentation/developers/gsoc.md

@@ -61,5 +61,5 @@ your career.
 ## References
 
  * [GSoC Home](http://code.google.com/soc/) - official GSoC page
- * [GSoC FAQ](http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs) - official FAQ
+ * [GSoC FAQ](https://developers.google.com/open-source/gsoc/faq) - official FAQ
  * [Apache GSoC coordination](http://community.apache.org/gsoc.html) - official Apache GSoC documentation, especially important  if you want to become a mentor

website/documentation/developers/how-to-update-the-website.md

@@ -17,7 +17,7 @@ Committers and contributors are all welcomed and encouraged to update the Mahout
 
 ```git clone http://github.com/apache/mahout```
 
-See [Building from Source](/developers/buildingmahout/#getting-code) for more details.
+See [Building from Source](/developers/buildingmahout.html#getting-code) for more details.
 
 #### Working with Markdown
 
@@ -48,7 +48,7 @@ open your favorite browser and make sure your changes look the way you expect th
 #### Commit code and open a PR
 
 Once you're sure everything is right, you commit your code, push to your github.com account (preferably on a branch other than `trunk`
-then click "OpenPR"). This process closely follows [How To Contribute- Making Changes](/developers/how-to-contribute/#HowToContribute-MakingChanges) with an exception that for _WEBSITE ONLY_ changes we relax the requirement to open a JIRA ticket. That is to say, small
+then click "OpenPR"). This process closely follows [How To Contribute- Making Changes](/developers/how-to-contribute.html#HowToContribute-MakingChanges) with an exception that for _WEBSITE ONLY_ changes we relax the requirement to open a JIRA ticket. That is to say, small
 website changes such as fixing a broken link or typo, do not require a specific JIRA issues, and where you would normally 
 commit with a message like `MAHOUT-XXXX The thing I did` (where `XXXX` is the assosciated JIRA number), you can instead 
 simply create a message like `WEBSITE Typos in how-to-update-the-website.md`.  There's nothing to stop you from making a 

website/documentation/developers/index.md

@@ -45,8 +45,6 @@ By following this Developer's Guide, developers can quickly harness the power of
 
 [Developer Resources](/developers/developer-resources.html)
 
-[Index](/developers/index.html)
-
 [Githubprs](/developers/githubPRs.html)
 
 [Buildingmahout](/developers/buildingmahout.html)
@@ -55,4 +53,4 @@ By following this Developer's Guide, developers can quickly harness the power of
 
 [Issue Tracker](/developers/issue-tracker.html)
 
-[How To Become A Committer](/developers/how-to-become-a-committer.html)
+[How To Become A Committer](/developers/how-to-become-a-committer.html)

website/documentation/developers/issue-tracker.md

@@ -13,7 +13,7 @@ For most changes (apart from trivial stuff) Mahout works according to a review-t
 This means anything that is to be added is first presented as a patch in the issue tracker. All conversations in the issue tracker are automatically
 echoed on the developer mailing list and people tend to respond or continue
 conversations there rather in the issue tracker, so in order to follow an
-issue you also have to read to the <a href="http://mahout.apache.org/general/mailing-lists,-irc-and-archives.html">mailing lists</a>. 
+issue you also have to read to the [mailing lists](/community/mailing-lists.html). 
 
 An issue does not literally have to be an issue. It could be a wish, task,
 bug report, etc. and it does not have to contain a patch.