mahout-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rawkintr...@apache.org
Subject [27/29] mahout git commit: ported developers and community md, significantly altered theme
Date Wed, 26 Apr 2017 03:05:09 GMT
http://git-wip-us.apache.org/repos/asf/mahout/blob/7fcf655a/website/community/mahout-benchmarks.md
----------------------------------------------------------------------
diff --git a/website/community/mahout-benchmarks.md b/website/community/mahout-benchmarks.md
new file mode 100644
index 0000000..46af54c
--- /dev/null
+++ b/website/community/mahout-benchmarks.md
@@ -0,0 +1,153 @@
+---
+layout: front_page
+title: Mahout Benchmarks
+theme: 
+    name: mahout2
+---
+
+<a name="MahoutBenchmarks-Introduction"></a>
+# Introduction
+
+Depending on hardware configuration, exact distribution of ratings over users and items YMMV!
+
+<a name="MahoutBenchmarks-Recommenders"></a>
+# Recommenders
+
+<a name="MahoutBenchmarks-ARuleofThumb"></a>
+## A Rule of Thumb
+
+100M preferences are about the data set size where non-distributed
+recommenders will outgrow a normal-sized machine (32-bit, <= 4GB RAM). Your
+mileage will vary significantly with the nature of the data.
+
+<a name="MahoutBenchmarks-Distributedrecommendervs.Wikipedialinks(May272010)"></a>
+## Distributed recommender vs. Wikipedia links (May 27 2010)
+
+From the mailing list:
+
+I just finished running a set of recommendations based on the Wikipedia
+link graph, for book purposes (yeah, it's unconventional). I ran on my
+laptop, but it ought to be crudely representative of how it runs in a real
+cluster.
+
+The input is 1058MB as a text file, and contains, 130M article-article
+associations, from 5.7M articles to 3.8M distinct articles ("users" and
+"items", respectively). I estimate cost based on Amazon's North
+American small Linux-based instance pricing of $0.085/hour. I ran on a
+dual-core laptop with plenty of RAM, allowing 1GB per worker, so this is
+valid.
+
+In this run, I run recommendations for all 5.7M "users". You can certainly
+run for any subset of all users of course.
+
+Phase 1 (Item ID to item index mapping)
+29 minutes CPU time
+$0.05
+60MB output
+
+Phase 2 (Create user vectors)
+88 minutes CPU time
+$0.13
+Output: 1159MB
+
+Phase 3 (Count co-occurrence)
+77 hours CPU time
+$6.54
+Output: 23.6GB
+
+Phase 4 (Partial multiply prep)
+10.5 hours CPU time
+$0.90
+Output: 24.6GB
+
+Phase 5 (Aggregate and recommend)
+about 600 hours
+about $51.00
+about 10GB
+(I estimated these rather than let it run at home for days!)
+
+
+Note that phases 1 and 3 may be run less frequently, and need not be run
+every time. But the cost is dominated by the last step, which is most of
+the work. I've ignored storage costs.
+
+This implies a cost of $0.01 (or about 8 instance-minutes) per 1,000 user
+recommendations. That's not bad if, say, you want to update recs for you
+site's 100,000 daily active users for a dollar.
+
+There are several levers one could pull internally to sacrifice accuracy
+for speed, but it's currently set to pretty normal values. So this is just
+one possibility.
+
+Now that's not terrible, but it is about 8x more computing than would be
+needed by a non-distributed implementation *if* you could fit the whole
+data set into a very large instance's memory, which is still possible at
+this scale but needs a pretty big instance. That's a very apples-to-oranges
+comparison of course; different algorithms, entirely different
+environments. This is about the amount of overhead I'd expect from
+distributing -- interesting to note how non-trivial it is.
+
+<a name="MahoutBenchmarks-Non-distributedrecommendervs.KDDCupdataset(March2011)"></a>
+## Non-distributed recommender vs. KDD Cup data set (March 2011)
+
+(From the user@mahout.apache.org mailing list)
+
+I've been test-driving a simple application of Mahout recommenders (the
+non-distributed kind) on Amazon EC2 on the new Yahoo KDD Cup data set
+(kddcup.yahoo.com).
+
+In the spirit of open-source, like I mentioned, I'm committing the extra
+code to mahout-examples that can be used to run a Recommender on the input
+and output the right format. And, I'd like to publish the rough timings
+too. Find all the source in org.apache.mahout.cf.taste.example.kddcup
+
+<a name="MahoutBenchmarks-Track1"></a>
+### Track 1
+
+* m2.2xlarge instance, 34.2GB RAM / 4 cores
+* Steady state memory consumption: ~19GB
+* Computation time: 30 hours (wall clock-time)
+* CPU time per user: ~0.43 sec
+* Cost on EC2: $34.20 (!)
+
+(Helpful hint on cost I realized after the fact: you can almost surely get
+spot instances for cheaper. The maximum price this sort of instance has
+gone for as a spot instance is about $0.60/hour, vs "retail price" of
+$1.14/hour.)
+
+Resulted in an RMSE of 29.5618 (the rating scale is 0-100), which is only
+good enough for 29th place at the moment. Not terrible for "out of the box"
+performance -- it's just using an item-based recommender with uncentered
+cosine similarity. But not really good in absolute terms. A winning
+solution is going to try to factor in time, and apply more sophisticated
+techniques. The best RMSE so far is about 23.
+
+<a name="MahoutBenchmarks-Track2"></a>
+### Track 2
+
+* c1.xlarge instance: 7GB RAM / 8 cores
+* Steady state memory consumption: ~3.8GB
+* Computation time: 4.1 hours (wall clock-time)
+* CPU time per user: ~1.1 sec
+* Cost on EC2: $3.20
+
+For this I bothered to write a simplistic item-item similarity metric to
+take into account the additional info that is available: track, artist,
+album, genre. The result was comparatively better: 17.92% error rate, good
+enough for 4th place at the moment.
+
+Of course, the next task is to put this through the actual distributed
+processing -- that's really the appropriate solution.
+
+This shows you can still tackle fairly impressive scale with a
+non-distributed solution. These results suggest that the largest instances
+available from EC2 would accomodate almost 1 billion ratings in memory.
+However at that scale running a user's full recommendations would easily be
+measured in seconds, not milliseconds.
+
+<a name="MahoutBenchmarks-Clustering"></a>
+# Clustering
+
+See [MAHOUT-588](https://issues.apache.org/jira/browse/MAHOUT-588)
+
+

http://git-wip-us.apache.org/repos/asf/mahout/blob/7fcf655a/website/community/mahout-benchmarks.mdtext
----------------------------------------------------------------------
diff --git a/website/community/mahout-benchmarks.mdtext b/website/community/mahout-benchmarks.mdtext
deleted file mode 100644
index 60f973e..0000000
--- a/website/community/mahout-benchmarks.mdtext
+++ /dev/null
@@ -1,148 +0,0 @@
-Title: Mahout Benchmarks
-
-<a name="MahoutBenchmarks-Introduction"></a>
-# Introduction
-
-Depending on hardware configuration, exact distribution of ratings over users and items YMMV!
-
-<a name="MahoutBenchmarks-Recommenders"></a>
-# Recommenders
-
-<a name="MahoutBenchmarks-ARuleofThumb"></a>
-## A Rule of Thumb
-
-100M preferences are about the data set size where non-distributed
-recommenders will outgrow a normal-sized machine (32-bit, <= 4GB RAM). Your
-mileage will vary significantly with the nature of the data.
-
-<a name="MahoutBenchmarks-Distributedrecommendervs.Wikipedialinks(May272010)"></a>
-## Distributed recommender vs. Wikipedia links (May 27 2010)
-
-From the mailing list:
-
-I just finished running a set of recommendations based on the Wikipedia
-link graph, for book purposes (yeah, it's unconventional). I ran on my
-laptop, but it ought to be crudely representative of how it runs in a real
-cluster.
-
-The input is 1058MB as a text file, and contains, 130M article-article
-associations, from 5.7M articles to 3.8M distinct articles ("users" and
-"items", respectively). I estimate cost based on Amazon's North
-American small Linux-based instance pricing of $0.085/hour. I ran on a
-dual-core laptop with plenty of RAM, allowing 1GB per worker, so this is
-valid.
-
-In this run, I run recommendations for all 5.7M "users". You can certainly
-run for any subset of all users of course.
-
-Phase 1 (Item ID to item index mapping)
-29 minutes CPU time
-$0.05
-60MB output
-
-Phase 2 (Create user vectors)
-88 minutes CPU time
-$0.13
-Output: 1159MB
-
-Phase 3 (Count co-occurrence)
-77 hours CPU time
-$6.54
-Output: 23.6GB
-
-Phase 4 (Partial multiply prep)
-10.5 hours CPU time
-$0.90
-Output: 24.6GB
-
-Phase 5 (Aggregate and recommend)
-about 600 hours
-about $51.00
-about 10GB
-(I estimated these rather than let it run at home for days!)
-
-
-Note that phases 1 and 3 may be run less frequently, and need not be run
-every time. But the cost is dominated by the last step, which is most of
-the work. I've ignored storage costs.
-
-This implies a cost of $0.01 (or about 8 instance-minutes) per 1,000 user
-recommendations. That's not bad if, say, you want to update recs for you
-site's 100,000 daily active users for a dollar.
-
-There are several levers one could pull internally to sacrifice accuracy
-for speed, but it's currently set to pretty normal values. So this is just
-one possibility.
-
-Now that's not terrible, but it is about 8x more computing than would be
-needed by a non-distributed implementation *if* you could fit the whole
-data set into a very large instance's memory, which is still possible at
-this scale but needs a pretty big instance. That's a very apples-to-oranges
-comparison of course; different algorithms, entirely different
-environments. This is about the amount of overhead I'd expect from
-distributing -- interesting to note how non-trivial it is.
-
-<a name="MahoutBenchmarks-Non-distributedrecommendervs.KDDCupdataset(March2011)"></a>
-## Non-distributed recommender vs. KDD Cup data set (March 2011)
-
-(From the user@mahout.apache.org mailing list)
-
-I've been test-driving a simple application of Mahout recommenders (the
-non-distributed kind) on Amazon EC2 on the new Yahoo KDD Cup data set
-(kddcup.yahoo.com).
-
-In the spirit of open-source, like I mentioned, I'm committing the extra
-code to mahout-examples that can be used to run a Recommender on the input
-and output the right format. And, I'd like to publish the rough timings
-too. Find all the source in org.apache.mahout.cf.taste.example.kddcup
-
-<a name="MahoutBenchmarks-Track1"></a>
-### Track 1
-
-* m2.2xlarge instance, 34.2GB RAM / 4 cores
-* Steady state memory consumption: ~19GB
-* Computation time: 30 hours (wall clock-time)
-* CPU time per user: ~0.43 sec
-* Cost on EC2: $34.20 (!)
-
-(Helpful hint on cost I realized after the fact: you can almost surely get
-spot instances for cheaper. The maximum price this sort of instance has
-gone for as a spot instance is about $0.60/hour, vs "retail price" of
-$1.14/hour.)
-
-Resulted in an RMSE of 29.5618 (the rating scale is 0-100), which is only
-good enough for 29th place at the moment. Not terrible for "out of the box"
-performance -- it's just using an item-based recommender with uncentered
-cosine similarity. But not really good in absolute terms. A winning
-solution is going to try to factor in time, and apply more sophisticated
-techniques. The best RMSE so far is about 23.
-
-<a name="MahoutBenchmarks-Track2"></a>
-### Track 2
-
-* c1.xlarge instance: 7GB RAM / 8 cores
-* Steady state memory consumption: ~3.8GB
-* Computation time: 4.1 hours (wall clock-time)
-* CPU time per user: ~1.1 sec
-* Cost on EC2: $3.20
-
-For this I bothered to write a simplistic item-item similarity metric to
-take into account the additional info that is available: track, artist,
-album, genre. The result was comparatively better: 17.92% error rate, good
-enough for 4th place at the moment.
-
-Of course, the next task is to put this through the actual distributed
-processing -- that's really the appropriate solution.
-
-This shows you can still tackle fairly impressive scale with a
-non-distributed solution. These results suggest that the largest instances
-available from EC2 would accomodate almost 1 billion ratings in memory.
-However at that scale running a user's full recommendations would easily be
-measured in seconds, not milliseconds.
-
-<a name="MahoutBenchmarks-Clustering"></a>
-# Clustering
-
-See [MAHOUT-588](https://issues.apache.org/jira/browse/MAHOUT-588)
-
-

http://git-wip-us.apache.org/repos/asf/mahout/blob/7fcf655a/website/community/mahout-wiki.md
----------------------------------------------------------------------
diff --git a/website/community/mahout-wiki.md b/website/community/mahout-wiki.md
new file mode 100644
index 0000000..10684f2
--- /dev/null
+++ b/website/community/mahout-wiki.md
@@ -0,0 +1,200 @@
+---
+layout: front_page
+title: Mahout Wiki
+theme: 
+    name: mahout2
+---
+
+Apache Mahout is a new Apache TLP project to create scalable, machine
+learning algorithms under the Apache license. 
+
+{toc:style=disc|minlevel=2}
+
+<a name="MahoutWiki-General"></a>
+## General
+[Overview](/community/overview.html)
+ -- Mahout? What's that supposed to be?
+
+[Quickstart](/community/quickstart.html)
+ -- learn how to quickly setup Apache Mahout for your project.
+
+[FAQ](/community/faq.html)
+ -- Frequent questions encountered on the mailing lists.
+
+[Developer Resources](/developer/developer-resources.html)
+ -- overview of the Mahout development infrastructure.
+
+[How To Contribute](/developer/how-to-contribute.html)
+ -- get involved with the Mahout community.
+
+[How To Become A Committer](/developer/how-to-become-a-committer.html)
+ -- become a member of the Mahout development community.
+
+[Hadoop](http://hadoop.apache.org)
+ -- several of our implementations depend on Hadoop.
+
+[Machine Learning Open Source Software](http://mloss.org/software/)
+ -- other projects implementing Open Source Machine Learning libraries.
+
+[Mahout -- The name, history and its pronunciation](mahoutname.html)
+
+<a name="MahoutWiki-Community"></a>
+## Community
+
+[Who we are](who-we-are.html)
+ -- who are the developers behind Apache Mahout?
+
+[Books, Tutorials, Talks, Articles, News, Background Reading, etc. on Mahout](books-tutorials-and-talks.html)
+
+[Issue Tracker](issue-tracker.html)
+ -- see what features people are working on, submit patches and file bugs.
+
+[Source Code (SVN)](https://svn.apache.org/repos/asf/mahout/)
+ -- [Fisheye|http://fisheye6.atlassian.com/browse/mahout]
+ -- download the Mahout source code from svn.
+
+[Mailing lists and IRC](mailing-lists,-irc-and-archives.html)
+ -- links to our mailing lists, IRC channel and archived design and
+algorithm discussions, maybe your questions was answered there already?
+
+[Version Control](version-control.html)
+ -- where we track our code.
+
+[Powered By Mahout](powered-by-mahout.html)
+ -- who is using Mahout in production?
+
+[Professional Support](professional-support.html)
+ -- who is offering professional support for Mahout?
+
+[Mahout and Google Summer of Code](gsoc.html)
+  -- All you need to know about Mahout and GSoC.
+
+
+[Glossary of commonly used terms and abbreviations](glossary.html)
+
+<a name="MahoutWiki-Installation/Setup"></a>
+## Installation/Setup
+
+[System Requirements](system-requirements.html)
+ -- what do you need to run Mahout?
+
+[Quickstart](quickstart.html)
+ -- get started with Mahout, run the examples and get pointers to further
+resources.
+
+[Downloads](downloads.html)
+ -- a list of Mahout releases.
+
+[Download and installation](buildingmahout.html)
+ -- build Mahout from the sources.
+
+[Mahout on Amazon's EC2 Service](mahout-on-amazon-ec2.html)
+ -- run Mahout on Amazon's EC2.
+
+[Mahout on Amazon's EMR](mahout-on-elastic-mapreduce.html)
+ -- Run Mahout on Amazon's Elastic Map Reduce
+
+[Integrating Mahout into an Application](mahoutintegration.html)
+ -- integrate Mahout's capabilities in your application.
+
+<a name="MahoutWiki-Examples"></a>
+## Examples
+
+1. [ASF Email Examples](asfemail.html)
+ -- Examples of recommenders, clustering and classification all using a
+public domain collection of 7 million emails.
+
+<a name="MahoutWiki-ImplementationBackground"></a>
+## Implementation Background
+
+<a name="MahoutWiki-RequirementsandDesign"></a>
+### Requirements and Design
+
+[Matrix and Vector Needs](matrix-and-vector-needs.html)
+ -- requirements for Mahout vectors.
+
+[Collection(De-)Serialization](collection(de-)serialization.html)
+
+<a name="MahoutWiki-CollectionsandAlgorithms"></a>
+### Collections and Algorithms
+
+Learn more about [mahout-collections](mahout-collections.html)
+, containers for efficient storage of primitive-type data and open hash
+tables.
+
+Learn more about the [Algorithms](algorithms.html)
+ discussed and employed by Mahout.
+
+Learn more about the [Mahout recommender implementation](recommender-documentation.html)
+.
+
+<a name="MahoutWiki-Utilities"></a>
+### Utilities
+
+This section describes tools that might be useful for working with Mahout.
+
+[Converting Content](converting-content.html)
+ -- Mahout has some utilities for converting content such as logs to
+formats more amenable for consumption by Mahout.
+[Creating Vectors](creating-vectors.html)
+ -- Mahout's algorithms operate on vectors. Learn more on how to generate
+these from raw data.
+[Viewing Result](viewing-result.html)
+ -- How to visualize the result of your trained algorithms.
+
+<a name="MahoutWiki-Data"></a>
+### Data
+
+[Collections](collections.html)
+ -- To try out and test Mahout's algorithms you need training data. We are
+always looking for new training data collections.
+
+<a name="MahoutWiki-Benchmarks"></a>
+### Benchmarks
+
+[Mahout Benchmarks](mahout-benchmarks.html)
+
+<a name="MahoutWiki-Committer'sResources"></a>
+## Committer's Resources
+
+* [Testing](testing.html)
+ -- Information on test plans and ideas for testing
+
+<a name="MahoutWiki-ProjectResources"></a>
+### Project Resources
+
+* [Dealing with Third Party Dependencies not in Maven](thirdparty-dependencies.html)
+* [How To Update The Website](how-to-update-the-website.html)
+* [Patch Check List](patch-check-list.html)
+* [How To Release](http://cwiki.apache.org/confluence/display/MAHOUT/How+to+release)
+* [Release Planning](release-planning.html)
+* [Sonar Code Quality Analysis](https://analysis.apache.org/dashboard/index/63921)
+
+<a name="MahoutWiki-AdditionalResources"></a>
+### Additional Resources
+
+* [Apache Machine Status](http://monitoring.apache.org/status/)
+ \- Check to see if SVN, other resources are available.
+* [Committer's FAQ](http://www.apache.org/dev/committers.html)
+* [Apache Dev](http://www.apache.org/dev/)
+
+
+<a name="MahoutWiki-HowToEditThisWiki"></a>
+## How To Edit This Wiki
+
+How to edit this Wiki
+
+This Wiki is a collaborative site, anyone can contribute and share:
+
+* Create an account by clicking the "Login" link at the top of any page,
+and picking a username and password.
+* Edit any page by pressing Edit at the top of the page
+
+There are some conventions used on the Mahout wiki:
+
+    * {noformat}+*TODO:*+{noformat} (+*TODO:*+ ) is used to denote sections
+that definitely need to be cleaned up.
+    * {noformat}+*Mahout_(version)*+{noformat} (+*Mahout_0.2*+) is used to
+draw attention to which version of Mahout a feature was (or will be) added
+to Mahout.
+

http://git-wip-us.apache.org/repos/asf/mahout/blob/7fcf655a/website/community/mahout-wiki.mdtext
----------------------------------------------------------------------
diff --git a/website/community/mahout-wiki.mdtext b/website/community/mahout-wiki.mdtext
deleted file mode 100644
index 043ba17..0000000
--- a/website/community/mahout-wiki.mdtext
+++ /dev/null
@@ -1,194 +0,0 @@
-Title: Mahout Wiki
-Apache Mahout is a new Apache TLP project to create scalable, machine
-learning algorithms under the Apache license. 
-
-{toc:style=disc|minlevel=2}
-
-<a name="MahoutWiki-General"></a>
-## General
-[Overview](overview.html)
- -- Mahout? What's that supposed to be?
-
-[Quickstart](quickstart.html)
- -- learn how to quickly setup Apache Mahout for your project.
-
-[FAQ](faq.html)
- -- Frequent questions encountered on the mailing lists.
-
-[Developer Resources](developer-resources.html)
- -- overview of the Mahout development infrastructure.
-
-[How To Contribute](how-to-contribute.html)
- -- get involved with the Mahout community.
-
-[How To Become A Committer](how-to-become-a-committer.html)
- -- become a member of the Mahout development community.
-
-[Hadoop](http://hadoop.apache.org)
- -- several of our implementations depend on Hadoop.
-
-[Machine Learning Open Source Software](http://mloss.org/software/)
- -- other projects implementing Open Source Machine Learning libraries.
-
-[Mahout -- The name, history and its pronunciation](mahoutname.html)
-
-<a name="MahoutWiki-Community"></a>
-## Community
-
-[Who we are](who-we-are.html)
- -- who are the developers behind Apache Mahout?
-
-[Books, Tutorials, Talks, Articles, News, Background Reading, etc. on Mahout](books-tutorials-and-talks.html)
-
-[Issue Tracker](issue-tracker.html)
- -- see what features people are working on, submit patches and file bugs.
-
-[Source Code (SVN)](https://svn.apache.org/repos/asf/mahout/)
- -- [Fisheye|http://fisheye6.atlassian.com/browse/mahout]
- -- download the Mahout source code from svn.
-
-[Mailing lists and IRC](mailing-lists,-irc-and-archives.html)
- -- links to our mailing lists, IRC channel and archived design and
-algorithm discussions, maybe your questions was answered there already?
-
-[Version Control](version-control.html)
- -- where we track our code.
-
-[Powered By Mahout](powered-by-mahout.html)
- -- who is using Mahout in production?
-
-[Professional Support](professional-support.html)
- -- who is offering professional support for Mahout?
-
-[Mahout and Google Summer of Code](gsoc.html)
-  -- All you need to know about Mahout and GSoC.
-
-
-[Glossary of commonly used terms and abbreviations](glossary.html)
-
-<a name="MahoutWiki-Installation/Setup"></a>
-## Installation/Setup
-
-[System Requirements](system-requirements.html)
- -- what do you need to run Mahout?
-
-[Quickstart](quickstart.html)
- -- get started with Mahout, run the examples and get pointers to further
-resources.
-
-[Downloads](downloads.html)
- -- a list of Mahout releases.
-
-[Download and installation](buildingmahout.html)
- -- build Mahout from the sources.
-
-[Mahout on Amazon's EC2 Service](mahout-on-amazon-ec2.html)
- -- run Mahout on Amazon's EC2.
-
-[Mahout on Amazon's EMR](mahout-on-elastic-mapreduce.html)
- -- Run Mahout on Amazon's Elastic Map Reduce
-
-[Integrating Mahout into an Application](mahoutintegration.html)
- -- integrate Mahout's capabilities in your application.
-
-<a name="MahoutWiki-Examples"></a>
-## Examples
-
-1. [ASF Email Examples](asfemail.html)
- -- Examples of recommenders, clustering and classification all using a
-public domain collection of 7 million emails.
-
-<a name="MahoutWiki-ImplementationBackground"></a>
-## Implementation Background
-
-<a name="MahoutWiki-RequirementsandDesign"></a>
-### Requirements and Design
-
-[Matrix and Vector Needs](matrix-and-vector-needs.html)
- -- requirements for Mahout vectors.
-
-[Collection(De-)Serialization](collection(de-)serialization.html)
-
-<a name="MahoutWiki-CollectionsandAlgorithms"></a>
-### Collections and Algorithms
-
-Learn more about [mahout-collections](mahout-collections.html)
-, containers for efficient storage of primitive-type data and open hash
-tables.
-
-Learn more about the [Algorithms](algorithms.html)
- discussed and employed by Mahout.
-
-Learn more about the [Mahout recommender implementation](recommender-documentation.html)
-.
-
-<a name="MahoutWiki-Utilities"></a>
-### Utilities
-
-This section describes tools that might be useful for working with Mahout.
-
-[Converting Content](converting-content.html)
- -- Mahout has some utilities for converting content such as logs to
-formats more amenable for consumption by Mahout.
-[Creating Vectors](creating-vectors.html)
- -- Mahout's algorithms operate on vectors. Learn more on how to generate
-these from raw data.
-[Viewing Result](viewing-result.html)
- -- How to visualize the result of your trained algorithms.
-
-<a name="MahoutWiki-Data"></a>
-### Data
-
-[Collections](collections.html)
- -- To try out and test Mahout's algorithms you need training data. We are
-always looking for new training data collections.
-
-<a name="MahoutWiki-Benchmarks"></a>
-### Benchmarks
-
-[Mahout Benchmarks](mahout-benchmarks.html)
-
-<a name="MahoutWiki-Committer'sResources"></a>
-## Committer's Resources
-
-* [Testing](testing.html)
- -- Information on test plans and ideas for testing
-
-<a name="MahoutWiki-ProjectResources"></a>
-### Project Resources
-
-* [Dealing with Third Party Dependencies not in Maven](thirdparty-dependencies.html)
-* [How To Update The Website](how-to-update-the-website.html)
-* [Patch Check List](patch-check-list.html)
-* [How To Release](http://cwiki.apache.org/confluence/display/MAHOUT/How+to+release)
-* [Release Planning](release-planning.html)
-* [Sonar Code Quality Analysis](https://analysis.apache.org/dashboard/index/63921)
-
-<a name="MahoutWiki-AdditionalResources"></a>
-### Additional Resources
-
-* [Apache Machine Status](http://monitoring.apache.org/status/)
- \- Check to see if SVN, other resources are available.
-* [Committer's FAQ](http://www.apache.org/dev/committers.html)
-* [Apache Dev](http://www.apache.org/dev/)
-
-
-<a name="MahoutWiki-HowToEditThisWiki"></a>
-## How To Edit This Wiki
-
-How to edit this Wiki
-
-This Wiki is a collaborative site, anyone can contribute and share:
-
-* Create an account by clicking the "Login" link at the top of any page,
-and picking a username and password.
-* Edit any page by pressing Edit at the top of the page
-
-There are some conventions used on the Mahout wiki:
-
-    * {noformat}+*TODO:*+{noformat} (+*TODO:*+ ) is used to denote sections
-that definitely need to be cleaned up.
-    * {noformat}+*Mahout_(version)*+{noformat} (+*Mahout_0.2*+) is used to
-draw attention to which version of Mahout a feature was (or will be) added
-to Mahout.
-

http://git-wip-us.apache.org/repos/asf/mahout/blob/7fcf655a/website/community/powered-by-mahout.md
----------------------------------------------------------------------
diff --git a/website/community/powered-by-mahout.md b/website/community/powered-by-mahout.md
new file mode 100644
index 0000000..64d59de
--- /dev/null
+++ b/website/community/powered-by-mahout.md
@@ -0,0 +1,129 @@
+---
+layout: front_page
+title: Powered By Mahout
+theme: 
+    name: mahout2
+---
+
+# Powered by Mahout
+
+Are you using Mahout to do Machine Learning? <a href="https://mahout.apache.org/general/mailing-lists,-irc-and-archives.html">Care to share</a>? Developers of the project always are happy to learn about new happy users with interesting use cases.
+
+*Links here do NOT imply
+endorsement by Mahout, its committers or the Apache Software Foundation and
+are for informational purposes only.*
+
+<a name="PoweredByMahout-CommercialUse"></a>
+## Commercial Use
+
+* <a href="http://nosql.mypopescu.com/post/2082712431/hbase-and-hadoop-at-adobe">Adobe AMP</a> uses Mahout's clustering algorithms to increase video
+consumption by better user targeting. 
+* Accenture uses Mahout as typical example for their [Hadoop Deployment Comparison Study](http://www.accenture.com/SiteCollectionDocuments/PDF/Accenture-Hadoop-Deployment-Comparison-Study.pdf)
+* [AOL](http://www.aol.com)
+ use Mahout for shopping recommendations. See [slide deck](http://www.slideshare.net/kryton/the-data-layer)
+* [Booz Allen Hamilton](http://www.boozallen.com/)
+ uses Mahout's clustering algorithms. See [slide deck](http://www.slideshare.net/ydn/3-biometric-hadoopsummit2010)
+* [Buzzlogic](http://www.buzzlogic.com)
+ uses Mahout's clustering algorithms to improve ad targeting
+* [Cull.tv](http://cull.tv/)
+ uses modified Mahout algorithms for content recommendations
+* ![DatamineLab](http://cdn.dataminelab.com/favicon.ico) [DataMine Lab](http://dataminelab.com)
+ uses Mahout's recommendation and clustering algorithms to improve our
+clients' ad targeting.
+* [Drupal](http://drupal.org/project/recommender)
+ uses Mahout to provide open source content recommendation solutions.
+* [Evolv ](http://www.evolvondemand.com)
+ uses Mahout for its Workforce Predictive Analytics platform.
+* [Foursquare](http://www.foursquare.com)
+ uses Mahout for its [recommendation engine](http://engineering.foursquare.com/2011/03/22/building-a-recommendation-engine-foursquare-style/).
+* [Idealo](http://www.idealo.de)
+ uses Mahout's recommendation engine.
+* [InfoGlutton](http://www.infoglutton.com)
+ uses Mahout's clustering and classification for various consulting
+projects.
+* [Intel](http://mark.chmarny.com/2013/07/thinking-big-about-data-at-intel.html)
+ ships Mahout as part of their Distribution for Apache Hadoop Software.
+* [Intela](http://www.intela.com/)
+ has implementations of Mahout's recommendation algorithms to select new
+offers to send tu customers, as well as to recommend potential customers to
+current offers. We are also working on enhancing our offer categories by
+using the clustering algorithms.
+* ![iOffer](http://ioffer.com/favicon.ico) [iOffer](http://www.ioffer.com)
+ uses Mahout's Frequent Pattern Mining and Collaborative Filtering to
+recommend items to users.
+* ![kau.li](http://kau.li/favicon.ico) [Kauli](http://kau.li/en)
+, one of Japanese Adnetwork, uses Mahout's clustering to handle clickstream
+data for predicting audience's interests and intents.
+* [Linked.In](http://linkedin.com)
+ Historically, we have used R for model training. We have recently started
+experimenting with Mahout for model training and are excited about it - also see
+ <a href="https://www.quora.com/LinkedIn-Recommendations/How-does-LinkedIns-recommendation-system-work?srid=XoeG&share=1">Hadoop World slides</a>
+.
+* [LucidWorks Big Data](http://www.lucidworks.com/products/lucidworks-big-data)
+ uses Mahout for clustering, duplicate document detection, phrase
+extraction and classification.
+* ![Mendeley](http://mendeley.com/favicon.ico) [Mendeley](http://mendeley.com)
+ uses Mahout to power Mendeley Suggest, a research article recommendation
+service.
+* ![Mippin](http://mippin.com/web/favicon.ico) [Mippin](http://mippin.com)
+ uses Mahout's collaborative filtering engine to recommend news feeds
+* [Mobage](http://www.slideshare.net/hamadakoichi/mobage-prmu-2011-mahout-hadoop)
+ uses Mahout in their analysis pipeline
+* ![Myrrix](http://myrrix.com/wp-content/uploads/2012/03/favicon.ico) [Myrrix](http://myrrix.com)
+ is a recommender system product built on Mahout.
+* ![Newscred](http://www.newscred.com/static/img/website/favicon.ico) [NewsCred](http://platform.newscred.com)
+ uses Mahout to generate clusters of news articles and to surface the
+important stories of the day
+* [Next Glass](http://nextglass.co/)
+ uses Mahout
+* [Predixion Software](http://predixionsoftware.com/)
+ uses Mahout’s algorithms to build predictive models on big data
+* <img src="http://www.radoop.eu/wp-content/uploads/favicon.png" width=15> [Radoop](http://radoop.eu)
+ provides a drag-n-drop interface for big data analytics, including Mahout
+clustering and classification algorithms
+* ![Researchgate](https://www.researchgate.net/favicon.ico) [ResearchGate](http://www.researchgate.net/), the professional network for scientists and researchers, uses Mahout's
+recommendation algorithms.
+* [Sematext](http://www.sematext.com/)
+ uses Mahout for its recommendation engine
+* [SpeedDate.com](http://www.speeddate.com)
+ uses Mahout's collaborative filtering engine to recommend member profiles
+* [Twitter](http://twitter.com)
+ uses Mahout's LDA implementation for user interest modeling
+* [Yahoo\!](http://www.yahoo.com)
+ Mail uses Mahout's Frequent Pattern Set Mining.  See [slides](http://www.slideshare.net/hadoopusergroup/mail-antispam)
+* [365Media ](http://365media.com/)
+ uses *Mahout's* Classification and Collaborative Filtering algorithms in
+its Real-time system named [UPTIME](http://uptime.365media.com/)
+ and 365Media/Social
+
+<a name="PoweredByMahout-AcademicUse"></a>
+## Academic Use
+
+* [Dicode](https://www.dicode-project.eu/)
+ project uses Mahout's clustering and classification algorithms on top of
+HBase.
+* The course [Large Scale Data Analysis and Data Mining](http://www.dima.tu-berlin.de/menue/teaching/masterstudium/aim-3/)
+ at TU Berlin uses Mahout to teach students about the parallelization of data
+mining problems with Hadoop and Map/Reduce
+* Mahout is used at Carnegie Mellon University, as a comparable platform to [GraphLab](http://www.graphlab.ml.cmu.edu/)
+
+* The [ROBUST project](http://www.robust-project.eu/)
+, co-funded by the European Commission, employs Mahout in the large scale
+analysis of online community data.
+* Mahout is used for research and data processing at [Nagoya Institute of Technology](http://www.nitech.ac.jp/eng/schools/grad/cse.html)
+, in the context of a large-scale citizen participation platform project,
+funded by the Ministry of Interior of Japan.
+* Several researches within [Digital Enterprise Research Institute](http://www.deri.ie)
+ [NUI Galway](http://www.nuigalway.ie)
+ use Mahout for e.g. topic mining and modelling of large corpora.
+* Mahout is used in the NoTube EU project.
+
+<a name="PoweredByMahout-PoweredByLogos"></a>
+## Powered By Logos
+
+Feel free to use our **Powered By** logos on your site:
+
+![powered by logo](https://mahout.apache.org/images/mahout-logo-poweredby-55.png)
+
+
+![powered by logo](https://mahout.apache.org/images/mahout-logo-poweredby-100.png)
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/mahout/blob/7fcf655a/website/community/powered-by-mahout.mdtext
----------------------------------------------------------------------
diff --git a/website/community/powered-by-mahout.mdtext b/website/community/powered-by-mahout.mdtext
deleted file mode 100644
index a2f686e..0000000
--- a/website/community/powered-by-mahout.mdtext
+++ /dev/null
@@ -1,124 +0,0 @@
-Title: Powered By Mahout
-
-# Powered by Mahout
-
-Are you using Mahout to do Machine Learning? <a href="https://mahout.apache.org/general/mailing-lists,-irc-and-archives.html">Care to share</a>? Developers of the project always are happy to learn about new happy users with interesting use cases.
-
-*Links here do NOT imply
-endorsement by Mahout, its committers or the Apache Software Foundation and
-are for informational purposes only.*
-
-<a name="PoweredByMahout-CommercialUse"></a>
-## Commercial Use
-
-* <a href="http://nosql.mypopescu.com/post/2082712431/hbase-and-hadoop-at-adobe">Adobe AMP</a> uses Mahout's clustering algorithms to increase video
-consumption by better user targeting. 
-* Accenture uses Mahout as typical example for their [Hadoop Deployment Comparison Study](http://www.accenture.com/SiteCollectionDocuments/PDF/Accenture-Hadoop-Deployment-Comparison-Study.pdf)
-* [AOL](http://www.aol.com)
- use Mahout for shopping recommendations. See [slide deck](http://www.slideshare.net/kryton/the-data-layer)
-* [Booz Allen Hamilton](http://www.boozallen.com/)
- uses Mahout's clustering algorithms. See [slide deck](http://www.slideshare.net/ydn/3-biometric-hadoopsummit2010)
-* [Buzzlogic](http://www.buzzlogic.com)
- uses Mahout's clustering algorithms to improve ad targeting
-* [Cull.tv](http://cull.tv/)
- uses modified Mahout algorithms for content recommendations
-* ![DatamineLab](http://cdn.dataminelab.com/favicon.ico) [DataMine Lab](http://dataminelab.com)
- uses Mahout's recommendation and clustering algorithms to improve our
-clients' ad targeting.
-* [Drupal](http://drupal.org/project/recommender)
- uses Mahout to provide open source content recommendation solutions.
-* [Evolv ](http://www.evolvondemand.com)
- uses Mahout for its Workforce Predictive Analytics platform.
-* [Foursquare](http://www.foursquare.com)
- uses Mahout for its [recommendation engine](http://engineering.foursquare.com/2011/03/22/building-a-recommendation-engine-foursquare-style/).
-* [Idealo](http://www.idealo.de)
- uses Mahout's recommendation engine.
-* [InfoGlutton](http://www.infoglutton.com)
- uses Mahout's clustering and classification for various consulting
-projects.
-* [Intel](http://mark.chmarny.com/2013/07/thinking-big-about-data-at-intel.html)
- ships Mahout as part of their Distribution for Apache Hadoop Software.
-* [Intela](http://www.intela.com/)
- has implementations of Mahout's recommendation algorithms to select new
-offers to send tu customers, as well as to recommend potential customers to
-current offers. We are also working on enhancing our offer categories by
-using the clustering algorithms.
-* ![iOffer](http://ioffer.com/favicon.ico) [iOffer](http://www.ioffer.com)
- uses Mahout's Frequent Pattern Mining and Collaborative Filtering to
-recommend items to users.
-* ![kau.li](http://kau.li/favicon.ico) [Kauli](http://kau.li/en)
-, one of Japanese Adnetwork, uses Mahout's clustering to handle clickstream
-data for predicting audience's interests and intents.
-* [Linked.In](http://linkedin.com)
- Historically, we have used R for model training. We have recently started
-experimenting with Mahout for model training and are excited about it - also see
- <a href="https://www.quora.com/LinkedIn-Recommendations/How-does-LinkedIns-recommendation-system-work?srid=XoeG&share=1">Hadoop World slides</a>
-.
-* [LucidWorks Big Data](http://www.lucidworks.com/products/lucidworks-big-data)
- uses Mahout for clustering, duplicate document detection, phrase
-extraction and classification.
-* ![Mendeley](http://mendeley.com/favicon.ico) [Mendeley](http://mendeley.com)
- uses Mahout to power Mendeley Suggest, a research article recommendation
-service.
-* ![Mippin](http://mippin.com/web/favicon.ico) [Mippin](http://mippin.com)
- uses Mahout's collaborative filtering engine to recommend news feeds
-* [Mobage](http://www.slideshare.net/hamadakoichi/mobage-prmu-2011-mahout-hadoop)
- uses Mahout in their analysis pipeline
-* ![Myrrix](http://myrrix.com/wp-content/uploads/2012/03/favicon.ico) [Myrrix](http://myrrix.com)
- is a recommender system product built on Mahout.
-* ![Newscred](http://www.newscred.com/static/img/website/favicon.ico) [NewsCred](http://platform.newscred.com)
- uses Mahout to generate clusters of news articles and to surface the
-important stories of the day
-* [Next Glass](http://nextglass.co/)
- uses Mahout
-* [Predixion Software](http://predixionsoftware.com/)
- uses Mahout’s algorithms to build predictive models on big data
-* <img src="http://www.radoop.eu/wp-content/uploads/favicon.png" width=15> [Radoop](http://radoop.eu)
- provides a drag-n-drop interface for big data analytics, including Mahout
-clustering and classification algorithms
-* ![Researchgate](https://www.researchgate.net/favicon.ico) [ResearchGate](http://www.researchgate.net/), the professional network for scientists and researchers, uses Mahout's
-recommendation algorithms.
-* [Sematext](http://www.sematext.com/)
- uses Mahout for its recommendation engine
-* [SpeedDate.com](http://www.speeddate.com)
- uses Mahout's collaborative filtering engine to recommend member profiles
-* [Twitter](http://twitter.com)
- uses Mahout's LDA implementation for user interest modeling
-* [Yahoo\!](http://www.yahoo.com)
- Mail uses Mahout's Frequent Pattern Set Mining.  See [slides](http://www.slideshare.net/hadoopusergroup/mail-antispam)
-* [365Media ](http://365media.com/)
- uses *Mahout's* Classification and Collaborative Filtering algorithms in
-its Real-time system named [UPTIME](http://uptime.365media.com/)
- and 365Media/Social
-
-<a name="PoweredByMahout-AcademicUse"></a>
-## Academic Use
-
-* [Dicode](https://www.dicode-project.eu/)
- project uses Mahout's clustering and classification algorithms on top of
-HBase.
-* The course [Large Scale Data Analysis and Data Mining](http://www.dima.tu-berlin.de/menue/teaching/masterstudium/aim-3/)
- at TU Berlin uses Mahout to teach students about the parallelization of data
-mining problems with Hadoop and Map/Reduce
-* Mahout is used at Carnegie Mellon University, as a comparable platform to [GraphLab](http://www.graphlab.ml.cmu.edu/)
-
-* The [ROBUST project](http://www.robust-project.eu/)
-, co-funded by the European Commission, employs Mahout in the large scale
-analysis of online community data.
-* Mahout is used for research and data processing at [Nagoya Institute of Technology](http://www.nitech.ac.jp/eng/schools/grad/cse.html)
-, in the context of a large-scale citizen participation platform project,
-funded by the Ministry of Interior of Japan.
-* Several researches within [Digital Enterprise Research Institute](http://www.deri.ie)
- [NUI Galway](http://www.nuigalway.ie)
- use Mahout for e.g. topic mining and modelling of large corpora.
-* Mahout is used in the NoTube EU project.
-
-<a name="PoweredByMahout-PoweredByLogos"></a>
-## Powered By Logos
-
-Feel free to use our **Powered By** logos on your site:
-
-![powered by logo](https://mahout.apache.org/images/mahout-logo-poweredby-55.png)
-
-
-![powered by logo](https://mahout.apache.org/images/mahout-logo-poweredby-100.png)
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/mahout/blob/7fcf655a/website/community/privacy-policy.md
----------------------------------------------------------------------
diff --git a/website/community/privacy-policy.md b/website/community/privacy-policy.md
new file mode 100644
index 0000000..0449b99
--- /dev/null
+++ b/website/community/privacy-policy.md
@@ -0,0 +1,30 @@
+---
+layout: front_page
+title: Privacy Policy
+theme: 
+    name: mahout2
+---
+
+
+Information about your use of this website is collected using server access
+logs and a tracking cookie. The collected information consists of the
+following:
+
+* The IP address from which you access the website;
+* The type of browser and operating system you use to access our site;
+* The date and time you access our site;
+* The pages you visit; and
+* The addresses of pages from where you followed a link to our site.
+
+Part of this information is gathered using a tracking cookie set by the
+Google Analytics service and handled by Google as described in their
+privacy policy. See your browser documentation for instructions on how to
+disable the cookie if you prefer not to share this data with Google.
+
+We use the gathered information to help us make our site more useful to
+visitors and to better understand how and when our site is used. We do not
+track or collect personally identifiable information or associate gathered
+data with any personally identifying information from other sources.
+
+By using this website, you consent to the collection of this data in the
+manner and for the purpose described above.

http://git-wip-us.apache.org/repos/asf/mahout/blob/7fcf655a/website/community/privacy-policy.mdtext
----------------------------------------------------------------------
diff --git a/website/community/privacy-policy.mdtext b/website/community/privacy-policy.mdtext
deleted file mode 100644
index a5af19d..0000000
--- a/website/community/privacy-policy.mdtext
+++ /dev/null
@@ -1,23 +0,0 @@
-Title: Privacy Policy
-Information about your use of this website is collected using server access
-logs and a tracking cookie. The collected information consists of the
-following:
-
-* The IP address from which you access the website;
-* The type of browser and operating system you use to access our site;
-* The date and time you access our site;
-* The pages you visit; and
-* The addresses of pages from where you followed a link to our site.
-
-Part of this information is gathered using a tracking cookie set by the
-Google Analytics service and handled by Google as described in their
-privacy policy. See your browser documentation for instructions on how to
-disable the cookie if you prefer not to share this data with Google.
-
-We use the gathered information to help us make our site more useful to
-visitors and to better understand how and when our site is used. We do not
-track or collect personally identifiable information or associate gathered
-data with any personally identifying information from other sources.
-
-By using this website, you consent to the collection of this data in the
-manner and for the purpose described above.

http://git-wip-us.apache.org/repos/asf/mahout/blob/7fcf655a/website/community/professional-support.md
----------------------------------------------------------------------
diff --git a/website/community/professional-support.md b/website/community/professional-support.md
new file mode 100644
index 0000000..85d5172
--- /dev/null
+++ b/website/community/professional-support.md
@@ -0,0 +1,39 @@
+---
+layout: front_page
+title: Professional Support
+theme: 
+    name: mahout2
+---
+
+<a name="ProfessionalSupport-ProfessionalsupportforMahout"></a>
+# Professional support for Mahout
+
+Add yourself or your company if you are offering support for Mahout
+users. Please keep lists in alphabetical order. An entry here
+is not an endorsement by the Apache Software Foundation nor any of its
+committers.
+
+
+<a name="ProfessionalSupport-Peopleandcompaniesforhire"></a>
+## People and companies for hire
+
+| Name | Contact details | Notes |
+|------|-----------------|-------|
+| Accenture | andrew.musselman@accenture.com | [Consulting services in big data analytics](http://accenture.com) |
+| Boston Predictive Analytics | sray@bostonpredictiveanalytics.com | [http://tutorteddy.com/site/free_statistics_help.php](http://tutorteddy.com/site/free_statistics_help.php) |
+| Frank Scholten | frank.scholten@orange11.nl | |
+| GridLine | [http://www.gridline.nl/contact](http://www.gridline.nl/contact) | Specialised in search and thesauri |
+| Jagdish Nomula | nomulaj@gmail.com | ML, Search, Algorithms, Java [http://www.kosmex.com](http://www.kosmex.com) |
+| LucidWorks | [http://www.lucidworks.com](http://www.lucidworks.com) | Big data platform including Mahout as a service for clustering, classification and more |
+| Sematext International | [http://sematext.com/](http://sematext.com/) | |
+| Ted Dunning | sales@maprtech.com | Full commercial support |
+| Winterwell | daniel@winterwell.com | Business/maths concept development & algorithms [http://winterwell.com](http://winterwell.com) |
+
+<a name="ProfessionalSupport-Talksandpresentations"></a>
+## Talks and presentations
+
+| Name | Contact details | Notes |
+|------|-----------------|-------|
+| Andrew Musselman | akm@apache.org | ["Building a Recommender with Apache Mahout on Amazon Elastic-MapReduce"](https://blogs.aws.amazon.com/bigdata/post/Tx1TDK3HHBD4EZL/Building-a-Recommender-with-Apache-Mahout-on-Amazon-Elastic-MapReduce-EMR) |
+| Frank Scholten | frank@jteam.nl | Mahout/Taste [http://blog.jteam.nl/author/frank/](http://blog.jteam.nl/author/frank/) |
+| Isabel Drost-Fromm | isabel@apache.org | If travel and accommodation costs are covered scheduling a talk is a lot easier. |

http://git-wip-us.apache.org/repos/asf/mahout/blob/7fcf655a/website/community/professional-support.mdtext
----------------------------------------------------------------------
diff --git a/website/community/professional-support.mdtext b/website/community/professional-support.mdtext
deleted file mode 100644
index 87b3ee3..0000000
--- a/website/community/professional-support.mdtext
+++ /dev/null
@@ -1,34 +0,0 @@
-Title: Professional Support
-
-<a name="ProfessionalSupport-ProfessionalsupportforMahout"></a>
-# Professional support for Mahout
-
-Add yourself or your company if you are offering support for Mahout
-users. Please keep lists in alphabetical order. An entry here
-is not an endorsement by the Apache Software Foundation nor any of its
-committers.
-
-
-<a name="ProfessionalSupport-Peopleandcompaniesforhire"></a>
-## People and companies for hire
-
-| Name | Contact details | Notes |
-|------|-----------------|-------|
-| Accenture | andrew.musselman@accenture.com | [Consulting services in big data analytics](http://accenture.com) |
-| Boston Predictive Analytics | sray@bostonpredictiveanalytics.com | [http://tutorteddy.com/site/free_statistics_help.php](http://tutorteddy.com/site/free_statistics_help.php) |
-| Frank Scholten | frank.scholten@orange11.nl | |
-| GridLine | [http://www.gridline.nl/contact](http://www.gridline.nl/contact) | Specialised in search and thesauri |
-| Jagdish Nomula | nomulaj@gmail.com | ML, Search, Algorithms, Java [http://www.kosmex.com](http://www.kosmex.com) |
-| LucidWorks | [http://www.lucidworks.com](http://www.lucidworks.com) | Big data platform including Mahout as a service for clustering, classification and more |
-| Sematext International | [http://sematext.com/](http://sematext.com/) | |
-| Ted Dunning | sales@maprtech.com | Full commercial support |
-| Winterwell | daniel@winterwell.com | Business/maths concept development & algorithms [http://winterwell.com](http://winterwell.com) |
-
-<a name="ProfessionalSupport-Talksandpresentations"></a>
-## Talks and presentations
-
-| Name | Contact details | Notes |
-|------|-----------------|-------|
-| Andrew Musselman | akm@apache.org | ["Building a Recommender with Apache Mahout on Amazon Elastic-MapReduce"](https://blogs.aws.amazon.com/bigdata/post/Tx1TDK3HHBD4EZL/Building-a-Recommender-with-Apache-Mahout-on-Amazon-Elastic-MapReduce-EMR) |
-| Frank Scholten | frank@jteam.nl | Mahout/Taste [http://blog.jteam.nl/author/frank/](http://blog.jteam.nl/author/frank/) |
-| Isabel Drost-Fromm | isabel@apache.org | If travel and accommodation costs are covered scheduling a talk is a lot easier. |

http://git-wip-us.apache.org/repos/asf/mahout/blob/7fcf655a/website/community/who-we-are.md
----------------------------------------------------------------------
diff --git a/website/community/who-we-are.md b/website/community/who-we-are.md
new file mode 100644
index 0000000..af91ac7
--- /dev/null
+++ b/website/community/who-we-are.md
@@ -0,0 +1,64 @@
+---
+layout: front_page
+title: Who we are
+theme: 
+    name: mahout2
+---
+
+
+<a name="WhoWeAre-Whoweare"></a>
+# Who we are
+
+Apache Mahout is maintained by a team of volunteer developers.
+
+<a name="WhoWeAre-CoreCommitters"></a>
+## Core Committers
+
+(Please keep the list below in alphabetical order by first name.)
+
+Name | Mail | PMC | Comment 
+----|---------|------|------|----------
+Anand Avati | avati@... | No | Twitter: @anandavati
+Andrew Musselman | akm@... | Yes | Twitter: @akm
+Andrew Palumbo | apalumbo@... | Yes (Chair) | |
+Benson Margulies | bimargulies@... | Yes | |
+Dan Filimon | dfilimon@... | No | |
+Dmitriy Lyubimov | dlyubimov@... | No (Emeritus) | 
+Drew Farris | drew@... | Yes | |
+Ellen Friedman | ellenf@... | No | Twitter: @Ellen_Friedman 
+Frank Scholten | frankscholten@... | No | |
+Gokhan Capan | gcapan@... | No | <a href="http://www.linkedin.com/in/gokhancapan">LinkedIn Profile</a>
+Grant Ingersoll | gsingers@... | Yes | Twitter: @gsingers
+Isabel Drost-Fromm | isabel@... | Yes | Passion for free software (development, but to some extend also the political and economic implications), interested in agile development and project management, lives in Germany. Follow me on Twitter @MaineC
+Jacob Alexander Mannix | jmannix@... | Yes | |
+Jeff Eastman | jeastman@... | No (Emeritus) |
+Paritosh Ranjan | pranjan@... | Yes | Twitter: @paritoshranjan
+Pat Ferrel | pat@... |  Yes | Twitter: @occam 
+Robin Anil | robinanil@... | Yes | |
+Sean Owen | srowen@... | No (Emeritus) |
+Sebastian Schelter | ssc@... | Yes | |
+Shannon Quinn | squinn@... | No | |
+Stevo Slavić|  sslavic@... | No | Twitter: @sslavic
+Suneel Marthi | smarthi@... | Yes | Twitter: @suneelmarthi
+Ted Dunning | tdunning@... |  Yes | 
+Tom Pierce | tcp@... | No | |
+Trevor Grant | rawkintrevo@... | Yes | Twitter: @rawkintrevo , [Blog](http://rawkintrevo.org)
+
+<a name="WhoWeAre-EmeritusCommitters"></a>
+## Emeritus Committers
+
+* Niranjan Balasubramanian (nbalasub@...)
+* Otis Gospodnetic (otis@...)
+* David Hall (dlwh@...)
+* Erik Hatcher (ehatcher@...)
+* Ozgur Yilmazel (oyilmazel@...)
+* Dawid Weiss (dweiss@...)
+* Karl Wettin (kalle@...)
+* AbdelHakim Deneche (adeneche@...)
+
+Note that the email addresses above end with @apache.org.
+
+<a name="WhoWeAre-Contributors"></a>
+## Contributors
+
+Apache Mahout contributors and their contributions to individual issues can be found at Apache <a href="http://issues.apache.org/jira/browse/MAHOUT">JIRA</a>.
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/mahout/blob/7fcf655a/website/community/who-we-are.mdtext
----------------------------------------------------------------------
diff --git a/website/community/who-we-are.mdtext b/website/community/who-we-are.mdtext
deleted file mode 100644
index a4b57bb..0000000
--- a/website/community/who-we-are.mdtext
+++ /dev/null
@@ -1,57 +0,0 @@
-Title: Who We Are
-
-<a name="WhoWeAre-Whoweare"></a>
-# Who we are
-
-Apache Mahout is maintained by a team of volunteer developers.
-
-<a name="WhoWeAre-CoreCommitters"></a>
-## Core Committers
-
-(Please keep the list below in alphabetical order by first name.)
-
-Name | Mail | PMC | Comment 
-----|---------|------|------|----------
-Anand Avati | avati@... | No | Twitter: @anandavati
-Andrew Musselman | akm@... | Yes | Twitter: @akm
-Andrew Palumbo | apalumbo@... | Yes (Chair) | |
-Benson Margulies | bimargulies@... | Yes | |
-Dan Filimon | dfilimon@... | No | |
-Dmitriy Lyubimov | dlyubimov@... | No (Emeritus) | 
-Drew Farris | drew@... | Yes | |
-Ellen Friedman | ellenf@... | No | Twitter: @Ellen_Friedman 
-Frank Scholten | frankscholten@... | No | |
-Gokhan Capan | gcapan@... | No | <a href="http://www.linkedin.com/in/gokhancapan">LinkedIn Profile</a>
-Grant Ingersoll | gsingers@... | Yes | Twitter: @gsingers
-Isabel Drost-Fromm | isabel@... | Yes | Passion for free software (development, but to some extend also the political and economic implications), interested in agile development and project management, lives in Germany. Follow me on Twitter @MaineC
-Jacob Alexander Mannix | jmannix@... | Yes | |
-Jeff Eastman | jeastman@... | No (Emeritus) |
-Paritosh Ranjan | pranjan@... | Yes | Twitter: @paritoshranjan
-Pat Ferrel | pat@... |  Yes | Twitter: @occam 
-Robin Anil | robinanil@... | Yes | |
-Sean Owen | srowen@... | No (Emeritus) |
-Sebastian Schelter | ssc@... | Yes | |
-Shannon Quinn | squinn@... | No | |
-Stevo Slavić|  sslavic@... | No | Twitter: @sslavic
-Suneel Marthi | smarthi@... | Yes | Twitter: @suneelmarthi
-Ted Dunning | tdunning@... |  Yes | 
-Tom Pierce | tcp@... | No | |
-
-<a name="WhoWeAre-EmeritusCommitters"></a>
-## Emeritus Committers
-
-* Niranjan Balasubramanian (nbalasub@...)
-* Otis Gospodnetic (otis@...)
-* David Hall (dlwh@...)
-* Erik Hatcher (ehatcher@...)
-* Ozgur Yilmazel (oyilmazel@...)
-* Dawid Weiss (dweiss@...)
-* Karl Wettin (kalle@...)
-* AbdelHakim Deneche (adeneche@...)
-
-Note that the email addresses above end with @apache.org.
-
-<a name="WhoWeAre-Contributors"></a>
-## Contributors
-
-Apache Mahout contributors and their contributions to individual issues can be found at Apache <a href="http://issues.apache.org/jira/browse/MAHOUT">JIRA</a>.
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/mahout/blob/7fcf655a/website/developers/github.mdtext
----------------------------------------------------------------------
diff --git a/website/developers/github.mdtext b/website/developers/github.mdtext
deleted file mode 100644
index f28f01d..0000000
--- a/website/developers/github.mdtext
+++ /dev/null
@@ -1,168 +0,0 @@
-Title:
-Notice:    Licensed to the Apache Software Foundation (ASF) under one
-           or more contributor license agreements.  See the NOTICE file
-           distributed with this work for additional information
-           regarding copyright ownership.  The ASF licenses this file
-           to you under the Apache License, Version 2.0 (the
-           "License"); you may not use this file except in compliance
-           with the License.  You may obtain a copy of the License at
-           .
-             http://www.apache.org/licenses/LICENSE-2.0
-           .
-           Unless required by applicable law or agreed to in writing,
-           software distributed under the License is distributed on an
-           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-           KIND, either express or implied.  See the License for the
-           specific language governing permissions and limitations
-           under the License.
-
-# Github Setup and Pull Requests (PRs) #
-
-There are several ways to setup Git for committers and contributors. Contributors can safely setup 
-Git any way they choose but committers should take extra care since they can push new commits to the master at 
-Apache and various policies there make backing out mistakes problematic. Therefore all but very small changes should 
-go through a PR, even for committers. To keep the commit history clean take note of the use of --squash below
-when merging into apache/master.
-
-##Git setup for Committers
-
-This describes setup for one local repo and two remotes. It allows you to push the code on your machine to either your Github repo or to git-wip-us.apache.org. 
-You will want to fork github's apache/mahout to your own account on github, this will enable Pull Requests of your own. 
-Cloning this fork locally will set up "origin" to point to your remote fork on github as the default remote. 
-So if you perform "git push origin master" it will go to github.
-
-To attach to the apache git repo do the following:
-
-    git remote add apache https://git-wip-us.apache.org/repos/asf/mahout.git
-
-To check your remote setup
-
-    git remote -v
-
-you should see something like this:
-
-    origin    https://github.com/your-github-id/mahout.git (fetch)
-    origin    https://github.com/your-github-id/mahout.git (push)
-    apache    https://git-wip-us.apache.org/repos/asf/mahout.git (fetch)
-    apache    https://git-wip-us.apache.org/repos/asf/mahout.git (push)
-
-Now if you want to experiment with a branch everything, by default, points to your github account because 'origin' is default. You can work as normal using only github until you are ready to merge with the apache remote. Some conventions will integrate with Apache Jira ticket numbers.
-
-    git checkout -b mahout-xxxx #xxxx typically is a Jira ticket number
-    #do some work on the branch
-    git commit -a -m "doing some work"
-    git push origin mahout-xxxx # notice pushing to **origin** not **apache**
-
-Once you are ready to commit to the apache remote you can merge and push them directly or better yet create a PR. 
-
-##How to create a PR (committers)
-
-Push your branch to Github:
-
-    git checkout mahout-xxxx
-    git push origin mahout-xxxx
-
-Go to your mahout-xxxx branch on Github. Since you forked it from Github's apache/mahout it will default
-any PR to go to apache/master. 
-
-* Click the green "Compare, review, and create pull request" button. 
-* You can edit the to and from for the PR if it isn't correct. The "base fork" should be apache/mahout unless you are collaborating 
-separately with one of the committers on the list. The "base" will be master. Don't submit a PR to one of the other 
-branches unless you know what you are doing. The "head fork" will be your forked repo and the "compare" will be 
-your mahout-xxxx branch. 
-* Click the "Create pull request" button and name the request "MAHOUT-XXXX" all caps. 
-This will connect the comments of the PR to the mailing list and Jira comments.
-* From now on the PR lives on github's apache/mahout. You use the commenting UI there.  
-* If you are looking for a review or sharing with someone else say so in the comments but don't worry about 
-automated merging of your PR--you will have to do that later. The PR is tied to your branch so you can respond to 
-comments, make fixes, and commit them from your local repo. They will appear on the PR page and be mirrored to Jira 
-and the mailing list. 
-
-When you are satisfied and want to push it to Apache's remote repo proceed with **Merging a PR**
-
-## How to create a PR (contributors)
-
-Create pull requests: \[[1]\]. 
-
-Pull requests are made to apache/mahout repository on Github. In the Github UI you should pick the master 
-branch to target the PR as described for committers. This will be reviewed and commented on so the merge is 
-not automatic. This can be used for discussing a contributions in progress.
-
-## Merging a PR (yours or contributors) 
-
-Start with reading \[[2]\] (merging locally). 
-
-Remember that pull requests are equivalent to a remote github branch with potentially a multitude of commits. 
-In this case it is recommended to squash remote commit history to have one commit per issue, rather 
-than merging in a multitude of contributor's commits. In order to do that, as well as close the PR at the 
-same time, it is recommended to use **squash commits**.
-
-Merging pull requests are equivalent to a "pull" of a contributor's branch:
-
-    git checkout master      # switch to local master branch
-    git pull apache master   # fast-forward to current remote HEAD
-    git pull --squash https://github.com/cuser/mahout cbranch  # merge to master 
-
---squash ensures all PR history is squashed into single commit, and allows committer to use his/her own
-message. Read git help for merge or pull for more information about `--squash` option. In this example we 
-assume that the contributor's Github handle is "cuser" and the PR branch name is "cbranch". 
-Next, resolve conflicts, if any, or ask a contributor to rebase on top of master, if PR went out of sync.
-
-If you are ready to merge your own (committer's) PR you probably only need to merge (not pull), since you have a local copy 
-that you've been working on. This is the branch that you used to create the PR.
-
-    git checkout master      # switch to local master branch
-    git pull apache master   # fast-forward to current remote HEAD
-    git merge --squash mahout-xxxx
-
-Remember to run regular patch checks, build with tests enabled, and change CHANGELOG.
-
-If everything is fine, you now can commit the squashed request along the lines
-
-    git commit --author <contributor_email> -a -m "MAHOUT-XXXX description closes apache/mahout#ZZ"
-
-MAHOUT-XXXX is all caps and where `ZZ` is the pull request number on apache/mahout repository. Including 
-"closes apache/mahout#ZZ" will close the PR automatically. More information is found here \[[3]\].
-
-Next, push to git-wip-us.a.o:
-
-    push apache master
-
-(this will require Apache handle credentials).
-
-The PR, once pushed, will get mirrored to github. To update your github version push there too:
-
-    push origin master
-
-*Note on squashing: Since squash discards remote branch history, repeated PRs from the same remote branch are 
-difficult for merging. The workflow implies that every new PR starts with a new rebased branch. This is more 
-important for contributors to know, rather than for committers, because if new PR is not mergeable, github
-would warn to begin with. Anyway, watch for dupe PRs (based on same source branches). This is a bad practice.*
-     
-## Closing a PR without committing (for committers)
-
-When we want to reject a PR (close without committing), we can just issue an empty commit on master's HEAD 
-*without merging the PR*: 
-
-    git commit --allow-empty -m "closes apache/mahout#ZZ *Won't fix*"
-    git push apache master
-
-that should close PR `ZZ` on github mirror without merging and any code modifications in the master repository.
-
-## Apache/github integration features 
-
-Read \[[4]\]. Comments and PRs with Mahout issue handles should post to mailing lists and Jira.
-Mahout issue handles must in the form MAHOUT-YYYYY (all capitals). Usually it makes sense to 
-file a jira issue first, and then create a PR with description 
-    
-    MAHOUT-YYYY: <jira-issue-description>
-
-
-In this case all subsequent comments will automatically be copied to jira without having to mention 
-jira issue explicitly in each comment of the PR.
-
-
-[1]: https://help.github.com/articles/creating-a-pull-request
-[2]: https://help.github.com/articles/merging-a-pull-request#merging-locally
-[3]: https://help.github.com/articles/closing-issues-via-commit-messages
-[4]: https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/mahout/blob/7fcf655a/website/developers/githubPRs.md
----------------------------------------------------------------------
diff --git a/website/developers/githubPRs.md b/website/developers/githubPRs.md
index 80164f3..a61c123 100644
--- a/website/developers/githubPRs.md
+++ b/website/developers/githubPRs.md
@@ -1,20 +1,10 @@
-Title:
-Notice:    Licensed to the Apache Software Foundation (ASF) under one
-           or more contributor license agreements.  See the NOTICE file
-           distributed with this work for additional information
-           regarding copyright ownership.  The ASF licenses this file
-           to you under the Apache License, Version 2.0 (the
-           "License"); you may not use this file except in compliance
-           with the License.  You may obtain a copy of the License at
-           .
-             http://www.apache.org/licenses/LICENSE-2.0
-           .
-           Unless required by applicable law or agreed to in writing,
-           software distributed under the License is distributed on an
-           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-           KIND, either express or implied.  See the License for the
-           specific language governing permissions and limitations
-           under the License.
+---
+layout: front_page
+title: Github PRs
+theme: 
+    name: mahout2
+---
+
 
 # Handling Github PRs #
 

http://git-wip-us.apache.org/repos/asf/mahout/blob/7fcf655a/website/developers/how-to-become-a-committer.md
----------------------------------------------------------------------
diff --git a/website/developers/how-to-become-a-committer.md b/website/developers/how-to-become-a-committer.md
index b08fa73..69259c8 100644
--- a/website/developers/how-to-become-a-committer.md
+++ b/website/developers/how-to-become-a-committer.md
@@ -1,7 +1,8 @@
 ---
-layout: default
-title: Developer Resources
-theme: mahout
+layout: front_page
+title: How to Become a Commmiter
+theme: 
+    name: mahout2
 ---
 
 # How to Become a Committer

http://git-wip-us.apache.org/repos/asf/mahout/blob/7fcf655a/website/developers/how-to-become-a-committer.mdtext
----------------------------------------------------------------------
diff --git a/website/developers/how-to-become-a-committer.mdtext b/website/developers/how-to-become-a-committer.mdtext
deleted file mode 100644
index 72a1b7d..0000000
--- a/website/developers/how-to-become-a-committer.mdtext
+++ /dev/null
@@ -1,23 +0,0 @@
-Title: How To Become A Committer
-
-# How to become a committer
-
-While there's no exact criteria for becoming a committer, there is a fairly
-obvious path to becoming a committer.
-
-For starters, one should be familiar with the [Apache Way ](http://www.apache.org/foundation/how-it-works.html), especially the part about meritocracy.
-
-Second, participate in the mailing lists, help answer questions when you
-can and do so in a respectful manner.  This is often more important than
-writing amazing code.
-
-Third, write code, add patches, stick with them and be patient.  Add unit
-tests and documentation.  In general, tackling 3 or 4 decent patches is
-where the bar is at, but it depends on the state of the project.  In the
-earlier stages of the project, the bar is a bit lower, so it pays to join
-early!
-
-Finally, it is then up to someone to nominate them to the PMC.	Typically,
-one of the existing committers does this by sending an email to the private
-PMC mailing list (private@m.a.o, where m.a.o is mahout.apache.org) and then
-the PMC votes on it.  Nominations often occur internal to the PMC as well.

http://git-wip-us.apache.org/repos/asf/mahout/blob/7fcf655a/website/developers/how-to-contribute.md
----------------------------------------------------------------------
diff --git a/website/developers/how-to-contribute.md b/website/developers/how-to-contribute.md
index bcc2381..de29f5d 100644
--- a/website/developers/how-to-contribute.md
+++ b/website/developers/how-to-contribute.md
@@ -1,9 +1,11 @@
 ---
-layout: default
-title: How To Contribute
-theme: mahout
+layout: front_page
+title: How to Contribute
+theme: 
+    name: mahout2
 ---
 
+
 # How to Contribute
 
 *Contributing to an Apache project* is about more than just writing code --

http://git-wip-us.apache.org/repos/asf/mahout/blob/7fcf655a/website/developers/how-to-release.md
----------------------------------------------------------------------
diff --git a/website/developers/how-to-release.md b/website/developers/how-to-release.md
new file mode 100644
index 0000000..bddef70
--- /dev/null
+++ b/website/developers/how-to-release.md
@@ -0,0 +1,240 @@
+---
+layout: front_page
+title: How to Release Mahout
+theme: 
+    name: mahout2
+---
+
+
+Title: How To Release
+
+# How To Release Mahout
+
+
+*This page is prepared for Mahout committers. You need committer rights to
+create a new Mahout release.*
+
+<a name="HowToRelease-ReleasePlanning"></a>
+# Release Planning
+
+Start a discussion on mahout-dev about having a release, questions to bring
+up include:
+
+ * Any [Unresolved JIRA issues for the upcoming release ](-https://issues.apache.org/jira/secure/issuenavigator!executeadvanced.jspa?jqlquery=project+%3d+mahout+and+resolution+%3d+unresolved+and+fixversion+%3d+%220.6%22&runquery=true&clear=true.html)
+ * Any [Resolved or Closed JIRA issues missing a "Fix Version" ](-https://issues.apache.org/jira/secure/issuenavigator!executeadvanced.jspa?jqlquery=project+%3d+mahout+and+%28status+%3d+resolved+or+status+%3d+closed%29+and+fixversion+is+null+and+resolution+%3d+fixed&runquery=true&clear=true.html)
+ that should be marked as fixed in this release?
+ * Does any documentation need an update?
+ * Who is going to be the "release engineer"?
+ * What day should be targeted for the release ?  Leave buffer time for a
+code freeze and release candidate testing; make sure at least a few people
+commit to having time to help test the release candidates around the target
+date.
+
+
+<a name="HowToRelease-CodeFreeze"></a>
+# Code Freeze
+
+For 7-14 days prior to the release target date, have a "code freeze" where
+committers agree to only commit things if they:
+
+ * Are documentation improvements (including fixes to eliminate Javadoc
+warnings)
+ * Are new test cases that improve test coverage
+ * Are bug fixes found because of improved test coverage
+ * Are new tests and bug fixes for new bugs encountered by manually testing
+
+<a name="HowToRelease-StepsForReleaseEngineer"></a>
+# Steps For Release Engineer
+
+<a name="HowToRelease-Beforebuildingrelease"></a>
+## Before building release
+1. Check that all tests pass after a clean compile: mvn clean test
+1. Check that there are no remaining unresolved Jira issues with the
+upcoming version number listed as the "Fix" version
+1. Publish any prev. unpublished Third Party Deps: [Thirdparty Dependencies](thirdparty-dependencies.html)
+
+<a name="HowToRelease-PreviewingtheArtifacts"></a>
+## Previewing the Artifacts
+1. To build the artifacts:
+1. # mvn -Pmahout-release,apache-release,hadoop2 package
+
+<a name="HowToRelease-Makingarelease"></a>
+## Making a release
+* Check if documentation needs an update
+* Update the web site's news by updating a working copy of the SVN
+directory at https://svn.apache.org/repos/asf/mahout/site/new_website
+* Commit these changes. It is important to do this prior to the build so
+that it is reflected in the copy of the website included with the release
+for documentation purposes.
+* If this is your first release, add your key to the KEYS file. The KEYS
+file is located on Github at
+https://github.com/apache/mahout/master/distribution/KEYS and copy it
+to the release directory. 
+Make sure you commit your change.
+See http://www.apache.org/dev/release-signing.html.
+* Ensure you have set up standard Apache committer settings in
+ ~/.m2/settings.xml as per [this page](http://maven.apache.org/developers/committer-settings.html)
+.
+* Add a profile to your ~/.m2/settings.xml in the <profiles> section with:
+
+ <blockquote>
+  <profiles>
+    <profile>
+      <id>mahout_release</id>
+      <properties>
+	<gpg.keyname>YOUR PGP KEY NAME</gpg.keyname>
+	<gpg.passphrase>YOUR SIGNING PASSCODE HERE</gpg.passphrase>
+       
+<deploy.altRepository>mahout.releases::default::https://repository.apache.org/service/local/staging/deploy/maven2/</deploy.altRepository>
+	<username>USERNAME</username>
+       
+<deploy.url>https://repository.apache.org/service/local/staging/deploy/maven2/</deploy.url>
+      </properties>
+    </profile>
+  </profiles>
+</blockquote>
+
+* You may also need to add the following to the <servers> section in
+~/.m2/settings.xml in order to upload artifacts (as the -Dusername=
+-Dpassword= didn't work for Grant for 0.8, but this did):
+<blockquote>
+<server>
+  <id>apache.releases.https</id>
+  <username>USERNAME</username>
+  <password>PASSWORD</password>
+</server>
+</blockquote>
+
+* Set environment variable MAVEN_OPTS to -Xmx1024m to ensure the tests can
+run
+* export _JAVA_OPTIONS="-Xmx1g"
+* If you are outside the US, then svn.apache.org may not resolve to the
+main US-based Subversion servers. (Compare the IP address you get for
+svn.apache.org with svn.us.apache.org to see if they are different.) This
+will cause problems during the release since it will create a revision and
+then immediately access, but, there is a replication lag of perhaps a
+minute to the non-US servers. To temporarily force using the US-based
+server, edit your equivalent of /etc/hosts and map the IP address of
+svn.us.apache.org to svn.apache.org.
+* Create the release candidate:
+
+     mvn -Pmahout-release,apache-release,hadoop2 release:prepare release:perform 
+
+  If you have problems authenticating to svn.apache.org, try adding to the command line 
+
+      -Dusername=\[user]\ -Dpassword=\[password\]
+
+ If it screws up, first try doing:
+
+  mvn -Dmahout-release,apache-release,hadoop2 release:rollback. 
+
+ followed by
+
+  mvn -Dmahout-release,apache-release,hadoop2 release:clean
+
+ This will likely save you time and do the right thing. You may also need to delete the tag in source control:
+
+  git tag -d mahout-X.XX.X; git push apache :refs/tags/mahout-X.XX.X
+
+ You may also have to rollback the version numbers in the POM files.
+
+ If you want to skip test cases while rebuilding, use
+
+ mvn -DpreparationGoals="clean compile" release:prepare release:perform
+
+* Review the artifacts, etc. on the Apache Repository (using Sonatype's
+Nexus application) site: https://repository.apache.org/.
+           You will need to login using your ASF SVN credentials and then
+browse to the staging area.
+* Once you have reviewed the artifacts, you will need to "Close" out
+the staging area under Nexus, which then makes the artifacts available for
+others to see.
+     * Log in to Nexus
+     * Click the Staging Repositories link in the left hand menu
+     * Click the Mahout staged one that was just uploaded by the
+release:perform target
+     * Click Close in the toolbar. See
+https://docs.sonatype.org/display/Repository/Closing+a+Staging+Repository
+for a picture
+     * Copy the "Repository URL" link to your email; it should be like
+https://repository.apache.org/content/repositories/orgapachemahout-024/
+* Call a VOTE on dev@mahout.apache.org.  Votes require 3 days before
+passing.  See Apache [release policy|http://www.apache.org/foundation/voting.html#ReleaseVotes]
+ for more info.
+* If there's a problem, you need to unwind the release and start all
+over.
+        <blockquote>
+        mvn -Pmahout-release,apache-release,hadoop2 versions:set -DnewVersion=PREVIOUS_SNAPSHOT
+
+        mvn -Pmahout-release,apache-release,hadoop2 versions:commit
+
+        git commit 
+
+        git push --delete apache <tagname> (deletes the remote tag)
+        git tag -d tagname (deletes the local tag)
+
+* Release the artifact in the Nexus Repository in the same way you
+Closed it earlier.
+* Add your key to the KEYS file at
+http://www.apache.org/dist/mahout/<version>/
+* Copy the assemblies and their supporting files (tar.gz, zip, tar.bz2,
+plus .asc, .md5, .pom, .sha1 files) to the ASF mirrors at:
+people.apache.org:/www/www.apache.org/dist/mahout/<version>/. You should
+make sure the group "mahout" owns the files and that they are read only
+(-r--r--r-- in UNIX-speak). See [Guide To Distributing Existing Releases Through The ASF Mirrors|http://jakarta.apache.org/site/convert-to-mirror.html?Step-By-Step]
+ and the links that are there.
+     * cd /www/www.apache.org/dist/mahout
+     * mkdir <VERSION>
+     * cd <VERSION>
+     * wget -e robots=off --no-check-certificate -np -r
+https://repository.apache.org/content/groups/public/org/apache/mahout/apache-mahout-distribution/<VERSION>/
+     * mv
+repository.apache.org/content/groups/public/org/apache/mahout/mahout-distribution/0.8/*
+.
+     * rm -rf repository.apache.org/
+     * rm index.html
+* Wait 24 hours for release to propagate to mirrors.
+* Clean up JIRA: Bulk close all X.Y JIRA issues.  Mark the Version
+number as being released (see Manage Versions.)  Add the next version
+(X.Y+1) if necessary.
+* Update release version on http://mahout.apache.org/ and
+http://en.wikipedia.org/wiki/Apache_Mahout
+*
+https://cwiki.apache.org/confluence/display/MAHOUT/How+To+Update+The+Website
+* Send announcements to the user and developer lists.
+    
+
+
+See also:
+
+* http://maven.apache.org/developers/release/releasing.html
+*
+http://www.sonatype.com/books/nexus-book/reference/staging-sect-deployment.html
+* http://www.sonatype.com/books/nexus-book/reference/index.html
+    
+
+### Post Release
+## Versioning
+* Create the next version in JIRA (if it doesn't already exist)   
+* Mark the version as "released" in JIRA (noting the release date)
+    
+## Documentation
+* Change wiki to match current best practices (remove/change deprecations,
+etc)
+    
+## Publicity
+* update freshmeat
+* blog away
+* Update MLOSS entry: http://mloss.org/revision/view/387/.  See Grant for
+details.
+    
+## Related Resources
+    
+* http://www.apache.org/dev/#releases
+* http://www.apache.org/dev/#mirror
+    
+# TODO: Things To Cleanup in this document
+         
+* more specifics about things to test before starting or after packaging
+(RAT, run scripts against example, etc...)
+* include info about [Voting | http://www.apache.org/foundation/voting.html#ReleaseVotes]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/mahout/blob/7fcf655a/website/developers/how-to-release.mdtext
----------------------------------------------------------------------
diff --git a/website/developers/how-to-release.mdtext b/website/developers/how-to-release.mdtext
deleted file mode 100644
index 7d84b8f..0000000
--- a/website/developers/how-to-release.mdtext
+++ /dev/null
@@ -1,232 +0,0 @@
-Title: How To Release
-
-# How To Release Mahout
-
-
-*This page is prepared for Mahout committers. You need committer rights to
-create a new Mahout release.*
-
-<a name="HowToRelease-ReleasePlanning"></a>
-# Release Planning
-
-Start a discussion on mahout-dev about having a release, questions to bring
-up include:
-
- * Any [Unresolved JIRA issues for the upcoming release ](-https://issues.apache.org/jira/secure/issuenavigator!executeadvanced.jspa?jqlquery=project+%3d+mahout+and+resolution+%3d+unresolved+and+fixversion+%3d+%220.6%22&runquery=true&clear=true.html)
- * Any [Resolved or Closed JIRA issues missing a "Fix Version" ](-https://issues.apache.org/jira/secure/issuenavigator!executeadvanced.jspa?jqlquery=project+%3d+mahout+and+%28status+%3d+resolved+or+status+%3d+closed%29+and+fixversion+is+null+and+resolution+%3d+fixed&runquery=true&clear=true.html)
- that should be marked as fixed in this release?
- * Does any documentation need an update?
- * Who is going to be the "release engineer"?
- * What day should be targeted for the release ?  Leave buffer time for a
-code freeze and release candidate testing; make sure at least a few people
-commit to having time to help test the release candidates around the target
-date.
-
-
-<a name="HowToRelease-CodeFreeze"></a>
-# Code Freeze
-
-For 7-14 days prior to the release target date, have a "code freeze" where
-committers agree to only commit things if they:
-
- * Are documentation improvements (including fixes to eliminate Javadoc
-warnings)
- * Are new test cases that improve test coverage
- * Are bug fixes found because of improved test coverage
- * Are new tests and bug fixes for new bugs encountered by manually testing
-
-<a name="HowToRelease-StepsForReleaseEngineer"></a>
-# Steps For Release Engineer
-
-<a name="HowToRelease-Beforebuildingrelease"></a>
-## Before building release
-1. Check that all tests pass after a clean compile: mvn clean test
-1. Check that there are no remaining unresolved Jira issues with the
-upcoming version number listed as the "Fix" version
-1. Publish any prev. unpublished Third Party Deps: [Thirdparty Dependencies](thirdparty-dependencies.html)
-
-<a name="HowToRelease-PreviewingtheArtifacts"></a>
-## Previewing the Artifacts
-1. To build the artifacts:
-1. # mvn -Pmahout-release,apache-release,hadoop2 package
-
-<a name="HowToRelease-Makingarelease"></a>
-## Making a release
-* Check if documentation needs an update
-* Update the web site's news by updating a working copy of the SVN
-directory at https://svn.apache.org/repos/asf/mahout/site/new_website
-* Commit these changes. It is important to do this prior to the build so
-that it is reflected in the copy of the website included with the release
-for documentation purposes.
-* If this is your first release, add your key to the KEYS file. The KEYS
-file is located on Github at
-https://github.com/apache/mahout/master/distribution/KEYS and copy it
-to the release directory. 
-Make sure you commit your change.
-See http://www.apache.org/dev/release-signing.html.
-* Ensure you have set up standard Apache committer settings in
- ~/.m2/settings.xml as per [this page](http://maven.apache.org/developers/committer-settings.html)
-.
-* Add a profile to your ~/.m2/settings.xml in the <profiles> section with:
-
- <blockquote>
-  <profiles>
-    <profile>
-      <id>mahout_release</id>
-      <properties>
-	<gpg.keyname>YOUR PGP KEY NAME</gpg.keyname>
-	<gpg.passphrase>YOUR SIGNING PASSCODE HERE</gpg.passphrase>
-       
-<deploy.altRepository>mahout.releases::default::https://repository.apache.org/service/local/staging/deploy/maven2/</deploy.altRepository>
-	<username>USERNAME</username>
-       
-<deploy.url>https://repository.apache.org/service/local/staging/deploy/maven2/</deploy.url>
-      </properties>
-    </profile>
-  </profiles>
-</blockquote>
-
-* You may also need to add the following to the <servers> section in
-~/.m2/settings.xml in order to upload artifacts (as the -Dusername=
--Dpassword= didn't work for Grant for 0.8, but this did):
-<blockquote>
-<server>
-  <id>apache.releases.https</id>
-  <username>USERNAME</username>
-  <password>PASSWORD</password>
-</server>
-</blockquote>
-
-* Set environment variable MAVEN_OPTS to -Xmx1024m to ensure the tests can
-run
-* export _JAVA_OPTIONS="-Xmx1g"
-* If you are outside the US, then svn.apache.org may not resolve to the
-main US-based Subversion servers. (Compare the IP address you get for
-svn.apache.org with svn.us.apache.org to see if they are different.) This
-will cause problems during the release since it will create a revision and
-then immediately access, but, there is a replication lag of perhaps a
-minute to the non-US servers. To temporarily force using the US-based
-server, edit your equivalent of /etc/hosts and map the IP address of
-svn.us.apache.org to svn.apache.org.
-* Create the release candidate:
-
-     mvn -Pmahout-release,apache-release,hadoop2 release:prepare release:perform 
-
-  If you have problems authenticating to svn.apache.org, try adding to the command line 
-
-      -Dusername=\[user]\ -Dpassword=\[password\]
-
- If it screws up, first try doing:
-
-  mvn -Dmahout-release,apache-release,hadoop2 release:rollback. 
-
- followed by
-
-  mvn -Dmahout-release,apache-release,hadoop2 release:clean
-
- This will likely save you time and do the right thing. You may also need to delete the tag in source control:
-
-  git tag -d mahout-X.XX.X; git push apache :refs/tags/mahout-X.XX.X
-
- You may also have to rollback the version numbers in the POM files.
-
- If you want to skip test cases while rebuilding, use
-
- mvn -DpreparationGoals="clean compile" release:prepare release:perform
-
-* Review the artifacts, etc. on the Apache Repository (using Sonatype's
-Nexus application) site: https://repository.apache.org/.
-           You will need to login using your ASF SVN credentials and then
-browse to the staging area.
-* Once you have reviewed the artifacts, you will need to "Close" out
-the staging area under Nexus, which then makes the artifacts available for
-others to see.
-     * Log in to Nexus
-     * Click the Staging Repositories link in the left hand menu
-     * Click the Mahout staged one that was just uploaded by the
-release:perform target
-     * Click Close in the toolbar. See
-https://docs.sonatype.org/display/Repository/Closing+a+Staging+Repository
-for a picture
-     * Copy the "Repository URL" link to your email; it should be like
-https://repository.apache.org/content/repositories/orgapachemahout-024/
-* Call a VOTE on dev@mahout.apache.org.  Votes require 3 days before
-passing.  See Apache [release policy|http://www.apache.org/foundation/voting.html#ReleaseVotes]
- for more info.
-* If there's a problem, you need to unwind the release and start all
-over.
-        <blockquote>
-        mvn -Pmahout-release,apache-release,hadoop2 versions:set -DnewVersion=PREVIOUS_SNAPSHOT
-
-        mvn -Pmahout-release,apache-release,hadoop2 versions:commit
-
-        git commit 
-
-        git push --delete apache <tagname> (deletes the remote tag)
-        git tag -d tagname (deletes the local tag)
-
-* Release the artifact in the Nexus Repository in the same way you
-Closed it earlier.
-* Add your key to the KEYS file at
-http://www.apache.org/dist/mahout/<version>/
-* Copy the assemblies and their supporting files (tar.gz, zip, tar.bz2,
-plus .asc, .md5, .pom, .sha1 files) to the ASF mirrors at:
-people.apache.org:/www/www.apache.org/dist/mahout/<version>/. You should
-make sure the group "mahout" owns the files and that they are read only
-(-r--r--r-- in UNIX-speak). See [Guide To Distributing Existing Releases Through The ASF Mirrors|http://jakarta.apache.org/site/convert-to-mirror.html?Step-By-Step]
- and the links that are there.
-     * cd /www/www.apache.org/dist/mahout
-     * mkdir <VERSION>
-     * cd <VERSION>
-     * wget -e robots=off --no-check-certificate -np -r
-https://repository.apache.org/content/groups/public/org/apache/mahout/apache-mahout-distribution/<VERSION>/
-     * mv
-repository.apache.org/content/groups/public/org/apache/mahout/mahout-distribution/0.8/*
-.
-     * rm -rf repository.apache.org/
-     * rm index.html
-* Wait 24 hours for release to propagate to mirrors.
-* Clean up JIRA: Bulk close all X.Y JIRA issues.  Mark the Version
-number as being released (see Manage Versions.)  Add the next version
-(X.Y+1) if necessary.
-* Update release version on http://mahout.apache.org/ and
-http://en.wikipedia.org/wiki/Apache_Mahout
-*
-https://cwiki.apache.org/confluence/display/MAHOUT/How+To+Update+The+Website
-* Send announcements to the user and developer lists.
-    
-
-
-See also:
-
-* http://maven.apache.org/developers/release/releasing.html
-*
-http://www.sonatype.com/books/nexus-book/reference/staging-sect-deployment.html
-* http://www.sonatype.com/books/nexus-book/reference/index.html
-    
-
-### Post Release
-## Versioning
-* Create the next version in JIRA (if it doesn't already exist)   
-* Mark the version as "released" in JIRA (noting the release date)
-    
-## Documentation
-* Change wiki to match current best practices (remove/change deprecations,
-etc)
-    
-## Publicity
-* update freshmeat
-* blog away
-* Update MLOSS entry: http://mloss.org/revision/view/387/.  See Grant for
-details.
-    
-## Related Resources
-    
-* http://www.apache.org/dev/#releases
-* http://www.apache.org/dev/#mirror
-    
-# TODO: Things To Cleanup in this document
-         
-* more specifics about things to test before starting or after packaging
-(RAT, run scripts against example, etc...)
-* include info about [Voting | http://www.apache.org/foundation/voting.html#ReleaseVotes]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/mahout/blob/7fcf655a/website/developers/how-to-update-the-website.md
----------------------------------------------------------------------
diff --git a/website/developers/how-to-update-the-website.md b/website/developers/how-to-update-the-website.md
index bcf1f9b..5d83014 100644
--- a/website/developers/how-to-update-the-website.md
+++ b/website/developers/how-to-update-the-website.md
@@ -1,7 +1,8 @@
 ---
-layout: default
-title: How To Update The Website
-theme: mahout2
+layout: front_page
+title: How to Update the Website
+theme: 
+    name: mahout2
 ---
 
 # How to update the Mahout Website


Mime
View raw message