Fix Mahout Website links after pages moved to new locations (#490)

niallkp · Niall Pemberton · web-flow · commit cd323d2c68ff · 2025-01-27T10:26:24.000-06:00
The following pages moved from "/developers" to "/documentation/developers"
    - buildingmahout.html
    - developer-resources.html
    - github.html
    - githubPRs.html
    - gsoc.html
    - how-to-become-a-committer.html
    - how-to-release.html
    - how-to-update-the-website.html
    - issue-tracker.html
    - patch-check-list.html
    - thirdparty-dependencies.html
    - version-control.html

The following page moved from "/developers" to "/about"
    - how-to-contribute.html

The following page moved from "/general" to "/download"
    - downloads.html

The following pages moved from "/general" to "/community"
    - mailing-lists.html
    - who-we-are.html

Co-authored-by: Niall Pemberton &lt;niallp@apache.org&gt;
diff --git a/doap_Mahout.rdf b/doap_Mahout.rdf
@@ -29,8 +29,8 @@
     <asfext:pmc rdf:resource="http://mahout.apache.org" />
     <shortdesc>Scalable machine learning library</shortdesc>
     <bug-database rdf:resource="https://issues.apache.org/jira/browse/MAHOUT" />
-    <mailing-list rdf:resource="https://mahout.apache.org/general/mailing-lists,-irc-and-archives.html" />
-    <download-page rdf:resource="http://mahout.apache.org/general/downloads.html" />
+    <mailing-list rdf:resource="https://mahout.apache.org/community/mailing-lists.html" />
+    <download-page rdf:resource="http://mahout.apache.org/download/downloads.html" />
     <programming-language>Java</programming-language>
     <programming-language>Scala</programming-language>
     <category rdf:resource="http://projects.apache.org/category/library" />
diff --git a/website/_posts/2017-12-20-new-website.md b/website/_posts/2017-12-20-new-website.md
@@ -10,4 +10,4 @@ We've launced a new website, (a HUUUGE special thanks to David Miller from [Star
 It looks great but there's lots to do as we migrate and clean up content from the old site. If you see anything broken, 
 please let us know via either:
 - send an email to dev@mahout.apache.org
-- fix it yourself and [open a PR](/developers/githubPRs)! 
+- fix it yourself and [open a PR](/documentation/developers/githubPRs)! 
diff --git a/website/about/how-to-contribute.md b/website/about/how-to-contribute.md
@@ -12,7 +12,7 @@ of ways to contribute!
 <a name="HowToContribute-BeInvolved"></a>
 ## Get Involved
 
-Discussions at Apache happen on the mailing list. To get involved, you should join the [Mahout mailing lists](/general/mailing-lists.html).  In particular:
+Discussions at Apache happen on the mailing list. To get involved, you should join the [Mahout mailing lists](/community/mailing-lists.html).  In particular:
 
 * The **user list** (to help others)
 * The **development list** (to join discussions of changes)  -- This is the best place
@@ -50,7 +50,7 @@ to this website, and we have a [guide for making website updates][2].
 We also have a [wide variety of books and slides][3] for learning more about 
 machine learning algorithms. 
 
-If you are interested in working towards being a committer, [general guidelines are available online](/developers/how-to-become-a-committer.html).
+If you are interested in working towards being a committer, [general guidelines are available online](/documentation/developers/how-to-become-a-committer.html).
 
 <a name="HowToContribute-ContributingCode(Features,BigFixes,Tests,etc...)"></a>
 ## Contributing Code (Features, Big Fixes, Tests, etc...)
@@ -76,14 +76,14 @@ and possibly improve it.
 <a name="HowToContribute-Gettingthesourcecode"></a>
 ## Getting the source code
 
-First of all, you need to get the [Mahout source code](/developers/version-control.html). Most development is done on the "trunk".  Mahout mirrors its codebase on [GitHub](https://github.com/apache/mahout). The first step to making a contribution is to fork Mahout's master branch to your GitHub repository.  
+First of all, you need to get the [Mahout source code](/documentation/developers/version-control.html). Most development is done on the "trunk".  Mahout mirrors its codebase on [GitHub](https://github.com/apache/mahout). The first step to making a contribution is to fork Mahout's master branch to your GitHub repository.  
 
 
 <a name="HowToContribute-MakingChanges"></a>
 ## Making Changes
 
 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).
+(note: you have to subscribe before you can post), or file a ticket in  our [issue tracker](/documentation/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.
 
  1. Create a JIRA Issue (if one does not already exist or you haven't already) 
@@ -144,9 +144,9 @@ for improvement (more tests, better javadocs, etc...) then make the changes on y
 thumbs up, that's a good sign for committers when deciding if it's worth spending time to review it -- and if other people have already put in
 effort to improve the docs/tests for an issue, that helps even more.
 
-For more information see [Handling GitHub PRs](http://mahout.apache.org/developers/github.html).
+For more information see [Handling GitHub PRs](http://mahout.apache.org/documentation/developers/github.html).
 
 
   [1]: http://www.apache.org/dev/contrib-email-tips
-  [2]: http://mahout.apache.org/developers/how-to-update-the-website.html
+  [2]: http://mahout.apache.org/documentation/developers/how-to-update-the-website.html
   [3]: http://mahout.apache.org/general/books-tutorials-and-talks.html
diff --git a/website/docs/latest/algorithms/map-reduce/clustering/cluster-dumper.md b/website/docs/latest/algorithms/map-reduce/clustering/cluster-dumper.md
@@ -63,7 +63,7 @@ executed the [synthetic control example ](clustering-of-synthetic-control-data.h
 
 ### Standalone Java Program                                          
 
-Run the clusterdump utility as follows as a standalone Java Program through Eclipse. <!-- - if you are using eclipse, setup mahout-utils as a project as specified in [Working with Maven in Eclipse](../../developers/buildingmahout.html). -->
+Run the clusterdump utility as follows as a standalone Java Program through Eclipse. <!-- - if you are using eclipse, setup mahout-utils as a project as specified in [Working with Maven in Eclipse](/documentation/developers/buildingmahout.html). -->
     To execute ClusterDumper.java,
     
 * Under mahout-utils, Right-Click on ClusterDumper.java
diff --git a/website/documentation/developers/buildingmahout.md b/website/documentation/developers/buildingmahout.md
@@ -158,7 +158,7 @@ The following profiles are available for building optional components:
 			<td>Build all modules</td>
 		<tr>
 			<td><code>apache-release</code></td>
-			<td>Used for releasing Apache Mahout. See <a href="http://mahout.apache.org/developers/how-to-release">How To Release</a> for more information.</td>
+			<td>Used for releasing Apache Mahout. See <a href="how-to-release.html">How To Release</a> for more information.</td>
 		</tr>
 		<tr>
 			<td><code>flink-batch</code></td>
diff --git a/website/documentation/developers/developer-resources.md b/website/documentation/developers/developer-resources.md
@@ -9,13 +9,13 @@ title: Developer Resources
 ## Making a Contribution
 
 Mahout is always looking for contributions, especially in the areas of
-documentation. See our [How to contribute](/developers/how-to-contribute.html) page for details.
+documentation. See our [How to contribute](/about/how-to-contribute.html) page for details.
 
 
 <a name="DeveloperResources-SourceCode"></a>
 ## Source Code
 
-The source files are stored using Git, our page on [version control](/developers/version-control.html) has details on how to access the sourcecode.
+The source files are stored using Git, our page on [version control](/documentation/developers/version-control.html) has details on how to access the sourcecode.
 
 
 <a name="DeveloperResources-Documentation"></a>
@@ -33,7 +33,7 @@ Javadoc and Scaladoc documentation is available online by module:
 <a name="DeveloperResources-Issues"></a>
 ## Issues
 
-All bugs, improvements, [pull requests](http://mahout.apache.org/developers/github.html), etc. should be logged in our [issue tracker](/developers/issue-tracker.html).
+All bugs, improvements, [pull requests](github.html), etc. should be logged in our [issue tracker](issue-tracker.html).
 
 <a name="DeveloperResources-ContinuousIntegration"></a>
 ## Continuous Integration
diff --git a/website/documentation/developers/gsoc.md b/website/documentation/developers/gsoc.md
@@ -26,7 +26,7 @@ opportunities for you.
 of how we rate proposals.  Having a good idea is just one part of the
 process.  You must show you can communicate and work within the community
 parameters.   You might even consider putting up a patch or two that shows
-you get how things work.  See [How To Contribute](how-to-contribute.html).
+you get how things work.  See [How To Contribute](/about/how-to-contribute.html).
 * Since Machine Learning is fairly academic, be sure to cite your sources
 in your proposal.
 * Provide a realistic timeline.  Be sure you indicate what other
diff --git a/website/documentation/developers/how-to-update-the-website.md b/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.html#getting-code) for more details.
+See [Building from Source](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.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
+then click "OpenPR"). This process closely follows [How To Contribute- Making Changes](/about/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 
diff --git a/website/documentation/developers/index.md b/website/documentation/developers/index.md
@@ -31,26 +31,26 @@ By following this Developer's Guide, developers can quickly harness the power of
 
 ## Index
 
-[Patch Check List](/developers/patch-check-list.html)
+[Patch Check List](patch-check-list.html)
 
-[How To Release](/developers/how-to-release.html)
+[How To Release](how-to-release.html)
 
-[Version Control](/developers/version-control.html)
+[Version Control](version-control.html)
 
-[Gsoc](/developers/gsoc.html)
+[Gsoc](gsoc.html)
 
-[Github](/developers/github.html)
+[Github](github.html)
 
-[How To Update The Website](/developers/how-to-update-the-website.html)
+[How To Update The Website](how-to-update-the-website.html)
 
-[Developer Resources](/developers/developer-resources.html)
+[Developer Resources](developer-resources.html)
 
-[Githubprs](/developers/githubPRs.html)
+[Githubprs](githubPRs.html)
 
-[Buildingmahout](/developers/buildingmahout.html)
+[Buildingmahout](buildingmahout.html)
 
-[Thirdparty Dependencies](/developers/thirdparty-dependencies.html)
+[Thirdparty Dependencies](thirdparty-dependencies.html)
 
-[Issue Tracker](/developers/issue-tracker.html)
+[Issue Tracker](issue-tracker.html)
 
-[How To Become A Committer](/developers/how-to-become-a-committer.html)
+[How To Become A Committer](how-to-become-a-committer.html)
diff --git a/website/documentation/developers/issue-tracker.md b/website/documentation/developers/issue-tracker.md
@@ -32,7 +32,7 @@ Quote only what it is you are responding to in comments.
 
 Patches should be created at trunk or trunk parent level and if possible be
 a single uncompressed text file so it is easy to inspect the patch in a web
-browser. (See [Patch Check List](/developers/patch-check-list.html)
+browser. (See [Patch Check List](patch-check-list.html)
 .)
 
 Use the issue identity when referring to an issue in any discussion.
diff --git a/website/documentation/developers/patch-check-list.md b/website/documentation/developers/patch-check-list.md
@@ -20,7 +20,7 @@ know you are working on it.
   - Before committing, make sure you add any new documents to your local Git repo.  
   - Run all unit tests, verify that all tests pass.
  
-After the above steps are verified and completed, and the contribution is ready to merge, follow the steps in the "Merging a PR" section in: [Handling Github PRs](http://mahout.apache.org/developers/github.html).
+After the above steps are verified and completed, and the contribution is ready to merge, follow the steps in the "Merging a PR" section in: [Handling Github PRs](github.html).
 
  - Remember to update the issue status in JIRA when you have completed it.
 
diff --git a/website/documentation/developers/version-control.md b/website/documentation/developers/version-control.md
@@ -27,4 +27,4 @@ The Git URL for committers is [https://git-wip-us.apache.org/repos/asf/mahout.gi
 <a name="VersionControl-Issues"></a>
 ## Issues
 
-All bugs, improvements, [pull requests](http://mahout.apache.org/developers/github.html), etc. should be logged in our [issue tracker](https://mahout.apache.org/developers/issue-tracker.html).
+All bugs, improvements, [pull requests](github.html), etc. should be logged in our [issue tracker](issue-tracker.html).
diff --git a/website/documentation/tutorials/map-reduce/classification/twenty-newsgroups.md b/website/documentation/tutorials/map-reduce/classification/twenty-newsgroups.md
@@ -21,7 +21,7 @@ the 20 newsgroups.
 <a name="TwentyNewsgroups-Prerequisites"></a>
 ### Prerequisites
 
-* Mahout has been downloaded ([instructions here](https://mahout.apache.org/general/downloads.html))
+* Mahout has been downloaded ([instructions here](https://mahout.apache.org/download/downloads.html))
 * Maven is available
 * Your environment has the following variables:
      * **HADOOP_HOME** Environment variables refers to where Hadoop lives 
diff --git a/website/documentation/tutorials/map-reduce/clustering/clustering-of-synthetic-control-data.md b/website/documentation/tutorials/map-reduce/clustering/clustering-of-synthetic-control-data.md
@@ -20,7 +20,7 @@ We need to do some initial setup before we are able to run the example.
 
   1. Start out by downloading the dataset to be clustered from the UCI Machine Learning Repository: [http://archive.ics.uci.edu/ml/databases/synthetic_control/synthetic_control.data](http://archive.ics.uci.edu/ml/databases/synthetic_control/synthetic_control.data).
 
-  2. Download the [latest release of Mahout](/general/downloads.html).
+  2. Download the [latest release of Mahout](/download//downloads.html).
 
   3. Unpack the release binary and switch to the *mahout-distribution-0.x* folder
 
diff --git a/website/documentation/tutorials/map-reduce/recommender/intro-als-hadoop.md b/website/documentation/tutorials/map-reduce/recommender/intro-als-hadoop.md
@@ -92,5 +92,5 @@ Based on the output feature matrices from step 3, we could make recommendations
 The input user file is a sequence file, the sequence record key is user id and value is the user's rated item ids which will be removed from recommendation. The output file generated in our simple example will be a text file giving the recommended item ids for each user. 
 Remember to translate the Mahout ids back into your application specific ids. 
 
-There exist a variety of parameters for Mahout’s ALS recommender to accommodate custom business requirements; exploring and testing various configurations to suit your needs will doubtless lead to additional questions. Feel free to ask such questions on the [mailing list](https://mahout.apache.org/general/mailing-lists,-irc-and-archives.html).
+There exist a variety of parameters for Mahout’s ALS recommender to accommodate custom business requirements; exploring and testing various configurations to suit your needs will doubtless lead to additional questions. Feel free to ask such questions on the [mailing list](https://mahout.apache.org/community/mailing-lists,-irc-and-archives.html).
 
diff --git a/website/documentation/tutorials/map-reduce/recommender/intro-itembased-hadoop.md b/website/documentation/tutorials/map-reduce/recommender/intro-itembased-hadoop.md
@@ -51,4 +51,4 @@ Running the command will execute a series of jobs the final product of which wil
 
 **Step 4: Making use of the output and doing more with Mahout**
 
-The output file generated in our simple example can be transformed using your tool of choice and consumed by downstream applications. There exist a variety of configuration options for Mahout’s item based recommender to accommodate custom business requirements; exploring and testing various configurations to suit your needs will doubtless lead to additional questions. Our user community is accessible via our [mailing list](https://mahout.apache.org/general/mailing-lists,-irc-and-archives.html) and the book *Mahout In Action* is a fantastic (but slightly outdated) starting point. 
+The output file generated in our simple example can be transformed using your tool of choice and consumed by downstream applications. There exist a variety of configuration options for Mahout’s item based recommender to accommodate custom business requirements; exploring and testing various configurations to suit your needs will doubtless lead to additional questions. Our user community is accessible via our [mailing list](https://mahout.apache.org/community/mailing-lists.html) and the book *Mahout In Action* is a fantastic (but slightly outdated) starting point. 
diff --git a/website/documentation/tutorials/misc/how-to-build-an-app.md b/website/documentation/tutorials/misc/how-to-build-an-app.md
@@ -15,7 +15,7 @@ In order to build and run the CooccurrenceDriver you need to install the follow
 * Install the Java 7 JDK from Oracle. Mac users look here: [Java SE Development Kit 7u72](http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html).
 * Install sbt (simple build tool) 0.13.x for [Mac](http://www.scala-sbt.org/release/tutorial/Installing-sbt-on-Mac.html), [Linux](http://www.scala-sbt.org/release/tutorial/Installing-sbt-on-Linux.html) or [manual instalation](http://www.scala-sbt.org/release/tutorial/Manual-Installation.html).
 * Install [Spark 1.1.1](https://spark.apache.org/docs/1.1.1/spark-standalone.html). Don't forget to setup SPARK_HOME
-* Install [Mahout 0.10.0](http://mahout.apache.org/general/downloads.html). Don't forget to setup MAHOUT_HOME and MAHOUT_LOCAL
+* Install [Mahout 0.10.0](http://mahout.apache.org/download/downloads.html). Don't forget to setup MAHOUT_HOME and MAHOUT_LOCAL
 
 Why install if you are only using them as a library? Certain binaries and scripts are required by the libraries to get information about the environment like discovering where jars are located.
 
diff --git a/website/documentation/users/basics/creating-vectors-from-text.md b/website/documentation/users/basics/creating-vectors-from-text.md
@@ -29,7 +29,7 @@ index.	For those wanting to use just Lucene, see the [Lucene website](http://luc
  or check out _Lucene In Action_ by Erik Hatcher, Otis Gospodnetic and Mike
 McCandless.
 
-To get started, make sure you get a fresh copy of Mahout from [GitHub](http://mahout.apache.org/developers/buildingmahout.html)
+To get started, make sure you get a fresh copy of Mahout from [GitHub](/documentation/developers/buildingmahout.html)
  and are comfortable building it. It defines interfaces and implementations
 for efficiently iterating over a data source (it only supports Lucene
 currently, but should be extensible to databases, Solr, etc.) and produces
diff --git a/website/documentation/users/classification/twenty-newsgroups.md b/website/documentation/users/classification/twenty-newsgroups.md
@@ -21,7 +21,7 @@ the 20 newsgroups.
 <a name="TwentyNewsgroups-Prerequisites"></a>
 ### Prerequisites
 
-* Mahout has been downloaded ([instructions here](https://mahout.apache.org/general/downloads.html))
+* Mahout has been downloaded ([instructions here](https://mahout.apache.org/download/downloads.html))
 * Maven is available
 * Your environment has the following variables:
      * **HADOOP_HOME** Environment variables refers to where Hadoop lives 
diff --git a/website/documentation/users/clustering/cluster-dumper.md b/website/documentation/users/clustering/cluster-dumper.md
@@ -63,7 +63,7 @@ executed the [synthetic control example ](clustering-of-synthetic-control-data.h
 
 ### Standalone Java Program                                          
 
-Run the clusterdump utility as follows as a standalone Java Program through Eclipse. <!-- - if you are using eclipse, setup mahout-utils as a project as specified in [Working with Maven in Eclipse](../../developers/buildingmahout.html). -->
+Run the clusterdump utility as follows as a standalone Java Program through Eclipse. <!-- - if you are using eclipse, setup mahout-utils as a project as specified in [Working with Maven in Eclipse](/documentation/developers/buildingmahout.html). -->
     To execute ClusterDumper.java,
     
 * Under mahout-utils, Right-Click on ClusterDumper.java
diff --git a/website/documentation/users/clustering/clustering-of-synthetic-control-data.md b/website/documentation/users/clustering/clustering-of-synthetic-control-data.md
@@ -20,7 +20,7 @@ We need to do some initial setup before we are able to run the example.
 
   1. Start out by downloading the dataset to be clustered from the UCI Machine Learning Repository: [http://archive.ics.uci.edu/ml/databases/synthetic_control/synthetic_control.data](http://archive.ics.uci.edu/ml/databases/synthetic_control/synthetic_control.data).
 
-  2. Download the [latest release of Mahout](/general/downloads.html).
+  2. Download the [latest release of Mahout](/download/downloads.html).
 
   3. Unpack the release binary and switch to the *mahout-distribution-0.x* folder
 
diff --git a/website/documentation/users/environment/how-to-build-an-app.md b/website/documentation/users/environment/how-to-build-an-app.md
diff --git a/website/documentation/users/recommender/intro-als-hadoop.md b/website/documentation/users/recommender/intro-als-hadoop.md
diff --git a/website/documentation/users/recommender/intro-itembased-hadoop.md b/website/documentation/users/recommender/intro-itembased-hadoop.md
diff --git a/website/download/downloads.md b/website/download/downloads.md
diff --git a/website/download/quickstart.md b/website/download/quickstart.md
diff --git a/website/general/faq.md b/website/general/faq.md
diff --git a/website/general/mahout-wiki.md b/website/general/mahout-wiki.md
diff --git a/website/general/powered-by-mahout.md b/website/general/powered-by-mahout.md
diff --git a/website/release-notes/Apache-Mahout-0.10.0-Release-Notes.pdf b/website/release-notes/Apache-Mahout-0.10.0-Release-Notes.pdf

Original file line number	Diff line number	Diff line change
`@@ -51,4 +51,4 @@ Running the command will execute a series of jobs the final product of which wil`
`51`	`51`
`52`	`52`	`Step 4: Making use of the output and doing more with Mahout`
`53`	`53`
`54`		-The output file generated in our simple example can be transformed using your tool of choice and consumed by downstream applications. There exist a variety of configuration options for Mahout’s item based recommender to accommodate custom business requirements; exploring and testing various configurations to suit your needs will doubtless lead to additional questions. Our user community is accessible via our [mailing list](https://mahout.apache.org/general/mailing-lists,-irc-and-archives.html) and the book Mahout In Action is a fantastic (but slightly outdated) starting point.
	`54`	+The output file generated in our simple example can be transformed using your tool of choice and consumed by downstream applications. There exist a variety of configuration options for Mahout’s item based recommender to accommodate custom business requirements; exploring and testing various configurations to suit your needs will doubtless lead to additional questions. Our user community is accessible via our [mailing list](https://mahout.apache.org/community/mailing-lists.html) and the book Mahout In Action is a fantastic (but slightly outdated) starting point.