mahout-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From isa...@apache.org
Subject svn commit: r1538467 [3/20] - in /mahout/site/mahout_cms: ./ cgi-bin/ content/ content/css/ content/developers/ content/general/ content/images/ content/js/ content/users/ content/users/basics/ content/users/classification/ content/users/clustering/ co...
Date Sun, 03 Nov 2013 21:36:27 GMT
Added: mahout/site/mahout_cms/content/css/bootstrap.min.css
URL: http://svn.apache.org/viewvc/mahout/site/mahout_cms/content/css/bootstrap.min.css?rev=1538467&view=auto
==============================================================================
--- mahout/site/mahout_cms/content/css/bootstrap.min.css (added)
+++ mahout/site/mahout_cms/content/css/bootstrap.min.css Sun Nov  3 21:36:23 2013
@@ -0,0 +1,9 @@
+/*!
+ * Bootstrap v2.3.1
+ *
+ * Copyright 2012 Twitter, Inc
+ * Licensed under the Apache License v2.0
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Designed and built with all the love in the world @twitter by @mdo and @fat.

[... 2 lines stripped ...]
Added: mahout/site/mahout_cms/content/css/global.css
URL: http://svn.apache.org/viewvc/mahout/site/mahout_cms/content/css/global.css?rev=1538467&view=auto
==============================================================================
--- mahout/site/mahout_cms/content/css/global.css (added)
+++ mahout/site/mahout_cms/content/css/global.css Sun Nov  3 21:36:23 2013
@@ -0,0 +1,887 @@
+/********************************** 
+ The Apache Software Foundation
+
+ 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.
+*********************************/
+
+/* Derived from: Open for Business Project Website */
+
+html, body, div, span, applet, object, iframe,
+h1, h2, h2, h4, h5, h6, p, blockquote, pre,
+a, abbr, acronym, address, big, cite, code,
+del, dfn, em, font, img, ins, kbd, q, s, samp,
+small, strike, strong, sub, sup, tt, var,
+b, u, i, center,
+dl, dt, dd, ol, ul, li,
+fieldset, form, label, legend,
+table, caption, tbody, tfoot, thead, tr, th, td {
+  border:0;
+  margin:0;
+  outline:0;
+  padding:0;
+  background:transparent;
+  vertical-align: baseline;
+}
+
+blockquote, q {
+  quotes: none;
+}
+
+a, address, body, caption, cite, code, dfn, em, strong, th, var {
+  font-style: normal;
+  font-weight: normal;
+  text-decoration: none;
+}
+
+a img {
+  border: none;
+}
+
+ol, ul {
+  list-style: none;
+}
+
+table {
+  border-collapse: collapse;
+  border-spacing: 0;
+}
+
+* {margin:0;padding:0;}
+
+html, body, #wrap {height: 100%;}
+
+body > #wrap {height: auto; min-height: 100%;}
+
+body {
+  font: 13px/ 165% sans-serif;
+  line-height: 1.7em;
+  color: #555;
+  margin: 0;
+  padding: 0;
+  background: url(../images/bg.png) top left repeat-x #A6A6A6;
+  text-align: center;
+  font-family: Opensans , "Helvetica Neue", Helvetica, Arial, "Lucida Grande", sans-serif;
+}
+
+.clearfix:after {
+  content: ".";
+  display: block;
+  height: 0;
+  clear: both;
+  visibility: hidden;
+}
+
+.clearfix {
+  display: inline-block;
+}
+
+html[xmlns] .clearfix {
+  display: block;
+}
+
+* html .clearfix {
+  height: 1%;
+}
+
+.clearfix {
+  display: block;
+}
+
+.clearLeft {
+  clear:left;
+}
+
+a,a:active,a:link {
+  text-decoration: none;
+  color: #304c90;
+}
+
+a:visited {
+  text-decoration: none;
+}
+
+a:hover {
+  color: #304c90;
+}
+
+h1,h2,h2 {
+  font-family: Opensans , "Helvetica Neue", Helvetica, Arial, "Lucida Grande", sans-serif;
+  font-weight: 300;
+  color: #555;
+  line-height: 130%;
+}
+
+h1 {
+  font-size: 200%;
+  color: #895F30;
+  padding: 20px 10px 5px 10px;
+  margin: 0;
+}
+
+h2 {
+  font-size: 1.5em;
+  font-weight: normal;
+  padding: 20px 10px 5px 10px;
+  margin: 0;
+}
+
+p,dl {
+  padding: 10px;
+  margin: 0;
+}
+
+ul{
+  margin: 10px 10px;
+  padding: 0 0 0 10px;
+}
+
+ul {
+  list-style: none;
+}
+
+ol {
+  margin: 10px 30px;
+  padding: 0;
+}
+
+dt {
+  font-weight: bold;
+  color: #b13f1a;
+}
+
+dd {
+  padding-left: 25px;
+}
+
+img {
+  border: none;
+}
+
+p img {
+  background: #fafafa;
+  border: 1px solid #dcdcdc;
+  padding: 5px;
+  margin:0 10px 0 0;
+}
+
+img.float-right {
+  margin: 5px 0 10px 10px;
+}
+
+img.float-left {
+  margin: 5px 10px 10px 0;
+}
+
+code {
+  margin: 5px 0;
+  padding: 15px;
+  text-align: left;
+  display: block;
+  overflow: auto;
+  font: 1em/ 1.5em 'Lucida Console', 'courier new', monospace;
+  border: 1px solid #ECF8FE;
+  background: #ECF8FE;
+}
+
+acronym {
+  cursor: help;
+  border-bottom: 1px dotted #895F30;
+}
+
+blockquote {
+  margin: 15px 10px;
+  padding: 10px 10px 10px 35px;
+  border: 1px solid #ECF8FE;
+  background: #ECF8FE no-repeat 10px 10px;
+  font-weight: normal;
+  font-size: 1.5em;
+  line-height: 1.5em;
+  font-style: italic;
+  font-family: sans-serif;
+  color: #976957;
+}
+
+table {
+  border-collapse: collapse;
+  margin: 15px 10px;
+}
+
+th {
+  background: #d14b1f repeat-x 0 -100px;
+  height: 38px;
+  padding-left: 12px;
+  padding-right: 12px;
+  color: #fff;
+  text-align: left;
+  border-left: 1px solid #d14b1f;
+  border-bottom: solid 2px #fff;
+}
+
+tr {
+  height: 34px;
+}
+
+td {
+  padding-left: 11px;
+  padding-right: 11px;
+}
+
+input,select {
+  padding: 4px;
+  font-size: 1em;
+  font-weight: 300;
+  font-family: Opensans , "Helvetica Neue", Helvetica, Arial, "Lucida Grande", sans-serif;
+  color: #555;
+}
+
+input[type="search"] {
+  width: 220px;
+}
+
+#sidebar-wrap {
+  background: #fff url(../images/sidebar.png) top left repeat-y;
+  padding: 0 0 0 15px;
+}
+
+#sidebar ul.sidemenu {
+  text-align: left;
+  margin: 0 5px 8px 0;
+  padding: 5px 0 0 0;
+  text-decoration: none;
+}
+
+#sidebar ul.sidemenu li {
+  list-style: none;
+  background: repeat-x left bottom;
+  padding: 4px 10px;
+  margin: 0;
+}
+
+* html body #sidebar ul.sidemenu li {
+  height: 1%;
+}
+
+#sidebar ul.sidemenu li a {
+  text-decoration: none;
+  background-image: none;
+  background-color: transparent;
+  border: none;
+  color: #304c90;
+  font-size: 1em;
+  font-weight: 300;
+  font-family: Opensans , "Helvetica Neue", Helvetica, Arial, "Lucida Grande", sans-serif;
+  color: #555;
+  background: #fff;
+}
+
+textarea {
+  width: 400px;
+  padding: 4px;
+  font-size: 1em;
+  font-weight: 300;
+  font-family: Opensans , "Helvetica Neue", Helvetica, Arial, "Lucida Grande", sans-serif;
+  height: 100px;
+  display: block;
+  color: #555;
+}
+
+input,textarea,select {
+  background: #fff;
+  border-width: 1px;
+  border-style: solid;
+  border-color: #D4D4D4 #ebebeb #ebebeb #d4d4d4;
+}
+
+input.button {
+  font-size: 13px;
+  font-weight: 500;
+  font-family: Opensans , "Helvetica Neue", Helvetica, Arial, "Lucida Grande", sans-serif;
+  height: 30px;
+  margin: 0;
+  padding: 2px 3px;
+  color: #555;
+  background: #E6E6E6;
+  border-width: 1px;
+  border-style: solid;
+  border-color: #ebebeb #d4d4d4 #d4d4d4 #ebebeb;
+}
+
+.float-left {
+  float: left;
+}
+
+.float-right {
+  float: right;
+}
+
+.align-left {
+  text-align: left;
+}
+
+.align-right {
+  text-align: right;
+}
+
+.clearer {
+  clear: both;
+}
+
+#wrap{
+  background: #fff url(../images/wrapper.jpg) top center no-repeat;
+  width: 1400px;
+  margin: 0 auto;
+  text-align:left;
+}
+
+#content-wrap  {
+  width:1400px;
+  margin:0 auto;
+  padding-bottom: 42px;
+}
+
+#content {
+  width:500px;
+  float:left;
+  padding:30px 0 25px 0;
+}
+
+#footer {
+  background: bottom center no-repeat;
+  position: relative;
+  margin: -50px auto 0 auto;
+  height: 50px;
+  clear:both;
+  font-size:12px;
+  width:1400px;
+  border-top: 1px solid #eee;
+  background-color: #E2E2E2;
+  padding: 20px 0;
+}
+
+#foot {
+  text-align:left;
+  position:relative;
+  top:5px;
+  left:30px;
+}
+
+#header {
+  position: relative;
+  width: 945px;
+  height: 100px;
+  padding: 0;
+  margin: 0 auto;
+  background: transparent;
+}
+
+#header #logo {
+  position: absolute;
+  top: 5px;
+  left: 20px;
+  height: 42px;
+  width: 405px;
+}
+
+#header #logo a,img {
+  background: none;
+  border: none;
+}
+
+#header #controls {
+  position: absolute;
+  top: 60px;
+  right: 32px;
+  height: 42px;
+  color: #1b78d7;
+  font-size: 13px;
+  background: top right no-repeat;
+  padding-right: 20px;
+  text-align: right;
+}
+
+#header #controls a {
+  position: relative;
+  top: -2px;
+}
+
+#header #language {
+  position: absolute;
+  top: 10px;
+  right: 32px;
+  height: 42px;
+  color: #797c7e;
+  text-align: right;
+}
+
+#search {
+  position:absolute;
+  top:0;
+  right:0;
+  background:url(../images/search.gif) center left no-repeat;
+  padding:5px;
+  padding-top:4px;
+  padding-left:33px;
+  background-color:#444;
+  width: 360px;
+}
+
+.hintText {
+  display: none;
+}
+
+.fieldWithHint {
+  color: #001f2f;
+}
+
+#nav {
+  position: absolute;
+  clear: both;
+  margin: 0;
+  padding: 0;
+  padding-right:5px;
+  padding-left:5px;
+  right:0;
+  height: 34px;
+  top: 84px;
+  z-index: 99999;
+  background-color:#444;
+}
+
+#nav ul {
+  float: left;
+  list-style: none;
+  height: 34px;
+  margin: 0;
+  padding: 0;
+  display: inline;
+}
+
+#nav ul li {
+  display: inline;
+  margin: 0;
+  padding: 0;
+}
+
+#nav ul li a {
+  float: left;
+  margin: 0 0 0 0;
+  padding: 0 15px 0 15px;
+  text-decoration: none;
+  color: #fff;
+  border-right:1px inset #888;
+  font-size: 14px;
+  padding-top: 6px;
+  font-weight: 300;
+  height: 28px;
+}
+
+#nav ul li a.last {
+  border:none;
+}
+
+#nav ul li a:hover,#nav ul li a:active {
+  color: #111;
+  background-image: url(../images/header_hot.jpg);
+}
+
+#nav ul li#current a {
+  color: #333333;
+  background-image: url(../images/header_hot.jpg);
+}
+
+#main {
+  float: left;
+  width: 960px;
+  padding: 0;
+  margin: 0 0 0 20px;
+  display: inline;
+}
+
+#main h1 {
+  padding-bottom: 3px;
+  margin-top: 15px;
+  color: #333;
+  text-transform: none;
+  border-bottom: 1px solid #ebebeb;
+  font-size: 2em;
+  font-weight: 300;
+  font-family: Opensans , "Helvetica Neue", Helvetica, Arial, "Lucida Grande", sans-serif;
+}
+
+#main h1 a {
+  color: #333;
+  text-decoration: none;
+  background: none;
+  border: none;
+}
+
+#main ul li {
+  list-style-image: url(../images/bullet.gif);
+}
+
+#col1 {
+  float: left;
+  width: 260px;
+  padding: 0;
+  margin: 20px 0 0 20px;
+  display: inline;
+}
+
+#col2 {
+  float: left;
+  width: 260px;
+  padding: 0;
+  margin: 20px 0 0 20px;
+  display: inline;
+}
+
+#col1 h1, #col2 h1 {
+  padding-bottom: 3px;
+  margin-top: 15px;
+  font-size: 2em;
+  font-weight: 300;
+  font-family: Opensans , "Helvetica Neue", Helvetica, Arial, "Lucida Grande", sans-serif;
+  color: #555;
+  text-transform: none;
+  border-bottom: 1px solid #ebebeb;
+}
+
+#main #col1 h1, #main #col2 h1 {
+  border-bottom: 1px solid #ebebeb;
+  color:#304C70;
+  padding-bottom: 3px;
+  text-transform: none;
+  font-size:30px;
+}
+
+.feature {
+  margin:0;
+  padding:0;
+  height:435px;
+}
+
+.screen {
+  margin:10px 0 5px 0;
+  padding:0;
+  background:#fff;
+  border:1px solid #eee;
+  width:255px;
+  height:200px;
+  overflow:hidden;
+}
+
+#main .hero {
+  margin:10px 0 5px 0;
+  padding:0;
+  background:#fff;
+  border:1px solid #eee;
+  width:555px;
+}
+
+#main .highlights {
+  float:right;
+  width:400px;
+  background:#dfe9ef;
+  border:1px solid #eee;
+  margin:0 10px 0 10px;
+  display:inline;
+  padding: 15px;
+}
+
+#main .highlights ul li {
+  list-style-image: url(../images/highlight-bullet.gif);
+}
+
+#main .highlights h4 {
+  padding:5px 5px 0 5px;
+  font-size: 13px;
+}
+
+#sidebar {
+  float: right;
+  width: 380px;
+  padding: 0;
+  margin: 15px 20px 0 0;
+  display: inline;
+}
+
+#sidebar h2 {
+  margin-top: 10px;
+  padding: 15px 5px 0px 10px;
+  font-size: 1.5em;
+  font-weight: 300;
+  font-family: Opensans , "Helvetica Neue", Helvetica, Arial, "Lucida Grande", sans-serif;
+  color: #333;
+}
+
+#sidebar ul.sidemenu {
+  text-align: left;
+  margin: 0 5px 8px 0;
+  padding: 5px 0 0 0;
+  text-decoration: none;
+  background: repeat-x left top;
+}
+
+#sidebar ul.sidemenu li {
+  list-style: none;
+  background: repeat-x left bottom;
+  padding: 4px 10px;
+  margin: 0;
+}
+
+* html body #sidebar ul.sidemenu li {
+  height: 1%;
+}
+
+#sidebar ul.sidemenu li a {
+  text-decoration: none;
+  background-image: none;
+  background-color: transparent;
+  border: none;
+  color: #304c90;
+  font-weight: 300;
+  font-size: 14px;
+}
+
+#sidebar ul.sidemenu li a span {
+  color: #989898;
+  font-family: serif;
+  font-style: italic;
+  font-weight: normal;
+  font-size: .8em;
+}
+
+#sidebar ul.sidemenu li a:hover {
+  color: #555;
+}
+
+#sidebar ul.sidemenu ul {
+  margin: 0 0 0 5px;
+  padding: 0;
+}
+
+#sidebar ul.sidemenu ul li {
+  background: none;
+}
+
+#sidebar .indentfirst {
+  margin-left:0;
+}
+
+#sidebar .indentsecond {
+  margin-left:20px;
+}
+
+.postmeta {
+  padding: 5px;
+  margin: 20px 10px 15px 10px;
+  font-size: 1em;
+  color: #777;
+  border: 1px solid #ECF8FE;
+  background: #ECF8FE;
+}
+
+.postmeta .date {
+  margin: 0 10px 0 5px;
+}
+
+.postmeta a.comments {
+  margin: 0 10px 0 5px;
+}
+
+.postmeta a.readmore {
+  margin: 0 10px 0 5px;
+}
+
+.post-info {
+  font-size: .95em;
+  padding-top: 3px;
+  margin-left: 5px;
+  color: #bababa;
+}
+
+p.thumbs {
+  padding: 12px 0 0 10px;
+}
+
+.thumbs img {
+  position: relative;
+  border: 1px solid #ebebeb;
+  background: none;
+  padding: 4px;
+  margin: 5px;
+}
+
+.thumbs img:hover {
+  border: 1px solid #c5c5c5;
+  background: none;
+}
+
+.thumbs a:hover {
+  background-color: transparent;
+  border: none
+}
+
+body#home #wrap {
+  position: relative;
+  background: #fff url(../images/home-wrapper-v2.png) top center no-repeat;
+  width: 1400px;
+  margin: 0 auto;
+  text-align: left;
+}
+
+body#home #header {
+  position: relative;
+  width: 1400px;
+  height: 403px;
+  padding: 0;
+  margin: 0 auto;
+  background: transparent;
+}
+
+body#home #header #slides {
+  position: absolute;
+  top: 128px;
+  left: 10px;
+  width: 1363px;
+  height: 260px;
+}
+
+body#home #header #slides .slideshow {
+  width:1363px;
+  height:260px;
+  margin:0;
+  padding:0;
+}
+
+body#home #header #slides .callout {
+  position: absolute;
+  top: 35px;
+  left: 30px;
+  font-size: 30px;
+  line-height: 30px;
+  color: #2b1f48;
+}
+
+body#home #header #slides .description {
+  position: absolute;
+  top: 190px;
+  left: 30px;
+  font-size: 14px;
+  line-height: 1.2em;
+  color: #e0e0e0;
+  width: 640px;
+}
+
+body#home #header #slides .controls {
+  width: 100px;
+  position: absolute;
+  top: 15px;
+  left: 900px;
+  height:30px;
+}
+
+body#home #header #slides .controls a {
+  border: none;
+  position:absolute;
+  height:30px;
+  line-height:24px;
+  padding:5px;
+  text-indent:-9999px;
+  outline:none;
+}
+
+body#home #header #slides .controls a.previous {
+  background: url(../images/backward.gif) top center no-repeat;
+  left:0;
+  height:30px;
+  width:16px;
+}
+
+body#home #header #slides .controls a.next {
+  background: url(../images/forward.gif) top center no-repeat;
+  left:60px;
+  height:30px;
+  width:16px;
+}
+
+body#home #header #slides .controls a.stop {
+  background: url(../images/pause.gif) top center no-repeat;
+  left:30px;
+  height:30px;
+  width:16px;
+}
+
+body#home #header #slides .controls a.start {
+  background: url(../images/start.gif) top center no-repeat;
+  left:30px;
+  height:30px;
+  width:16px;
+}
+
+body#home #header #slides .controls a img {
+  background: none;
+  border: none;
+  cursor: pointer;
+}
+
+body#home #header #slides .mantle{
+  position:absolute;
+  top:58px;
+  left:585px;
+}
+
+body#home #col1 {
+  float: left;
+  width: 260px;
+  padding: 0;
+  margin: 5px 0 0 0;
+  display: inline;
+}
+
+body#home #col2 {
+  float: left;
+  width: 260px;
+  padding: 0;
+  margin: 5px 0 0 20px;
+  display: inline;
+}
+
+.downloadNow {
+  margin:30px 0 10px 20px;
+}
+
+.downloadLinks span.docs {
+  float:left;
+  margin:0;
+  display:inline;
+}
+
+.downloadLinks span.previousVersions {
+  float:right;
+  margin:0 20px 0 0;
+  display:inline;
+}
+
+body#full #wrap {
+  position: relative;
+  background: #fff top center no-repeat;
+  width: 1400px;
+  margin: 0 auto;
+  text-align: left;
+}

Added: mahout/site/mahout_cms/content/css/main.css
URL: http://svn.apache.org/viewvc/mahout/site/mahout_cms/content/css/main.css?rev=1538467&view=auto
==============================================================================
--- mahout/site/mahout_cms/content/css/main.css (added)
+++ mahout/site/mahout_cms/content/css/main.css Sun Nov  3 21:36:23 2013
@@ -0,0 +1,4 @@
+.feather {
+	background-image:url('http://www.apache.org/images/feather-small.gif');
+	background-repeat:no-repeat;
+}
\ No newline at end of file

Added: mahout/site/mahout_cms/content/developers/buildingmahout.mdtext
URL: http://svn.apache.org/viewvc/mahout/site/mahout_cms/content/developers/buildingmahout.mdtext?rev=1538467&view=auto
==============================================================================
--- mahout/site/mahout_cms/content/developers/buildingmahout.mdtext (added)
+++ mahout/site/mahout_cms/content/developers/buildingmahout.mdtext Sun Nov  3 21:36:23 2013
@@ -0,0 +1,306 @@
+Title: BuildingMahout
+<a name="BuildingMahout-PrerequisitesforBuildingMahout"></a>
+# Prerequisites for Building Mahout
+
+* Java JDK *1.6*
+* Maven *2.2* or higher ([http://maven.apache.org/](http://maven.apache.org/)
+).  Use *3.x* to build from SVN.
+
+<a name="BuildingMahout-GettheSourceCode"></a>
+# Get the Source Code
+
+<a name="BuildingMahout-Latest(Recommended)"></a>
+## Latest (Recommended)
+
+Use [Subversion](http://subversion.tigris.org)
+ to check out the code:
+
+    svn co http://svn.apache.org/repos/asf/mahout/trunk
+
+
+<a name="BuildingMahout-Release"></a>
+## Release
+
+[Download source ](http://www.apache.org/dyn/closer.cgi/mahout/)
+Maven artifacts should be in the usual place: [http://repo2.maven.org/maven2/org/apache/mahout/](http://repo2.maven.org/maven2/org/apache/mahout/)
+
+<a name="BuildingMahout-Compiling"></a>
+# Compiling
+
+* change directory to the checked out directory
+* mvn install
+
+{note:title=Important}
+
+If you are Compiling under Windows, make sure you installed Cygwin
+correctly. Here is a [good tutorial](http://hayesdavis.net/2008/06/14/running-hadoop-on-windows/)
+ on installing and configuring a Hadoop cluster on Windows, and it points
+out at antoher great tutorial about installing Cygwin. Here is another [good tutorial |http://ebiquity.umbc.edu/Tutorials/Hadoop/00%20-%20Intro.html]
+ for setting up Hadoop on Windows (via Cygwin) along with the corresponding
+Eclipse plugin for easier Map-Reduce development and deployment.
+Also if your Windows' Account name contains spaces (for example 'my
+account') some of the tests wont pass and the build will fail.
+The easiest solution is to create a new Windows' Account that contains no
+spaces (for example 'myaccount'), and use that account when Compiling.
+{note}This will run the default targets, which builds both the core and the
+examples, and also packages them.
+
+<a name="BuildingMahout-CompileCore"></a>
+## Compile Core
+
+* change to the core directory
+* mvn compile
+
+<a name="BuildingMahout-InstallCore"></a>
+## Install Core
+
+Note, you can do install instead of compile.
+
+* change to the core directory
+* mvn install
+
+<a name="BuildingMahout-CompileExamples"></a>
+## Compile Examples
+
+*You must "mvn install" the core before you can build the examples.  For
+some reason Maven doesn't know how to build sibling modules that are
+dependencies.*
+
+* change to the examples directory
+* mvn compile
+
+
+<a name="BuildingMahout-WorkingWithMaveninEclipse{anchor:mahout_maven_eclipse}"></a>
+## Working With Maven in Eclipse {anchor:mahout_maven_eclipse}
+
+We've used Eclipse Galileo and m2eclipse 0.9 and the 'import maven
+projects' feature. Check out the mahout sources into your workspace
+directory, do a full build on the command-line and then fire up the import
+in Eclipse from File > Import > Maven Projects. Point it at the mahout root
+directory. You are then given the opportunity to choose which sub-modules
+to import. You don't need to import them all, only the projects you are
+interested in working with.
+
+This sets up one Eclipse project for each of the mahout sub-modules you
+chose. Inter-project dependencies are automatically resolved. For example,
+if mahout-core and mahout-math are both open the m2eclipse plugin will
+automatically set up a project dependency on mahout-math in mahout-core. If
+you close mahout-math, the plugin will automatically revert to a jar
+dependency for mahout-math.
+
+If you are importing mahout-collections/mahout-math you will have to add
+the target/generated-sources directories to your build path manually and do
+a refresh on the dependent projects. Alternatively just avoid importing
+these (or close them) and they will be treated as a regular jar dependency.
+This works much better than doing the checkout into Eclipse directly via
+the m2eclipse 'check out maven projects from scm' importer.
+
+<a name="BuildingMahout-ForEclipseusersonMacOSXLeopard"></a>
+## For Eclipse users on Mac OS X Leopard
+
+These instructions work on  Mac OSX Leopard 10.5.6 and Eclipse 3.3.2
+1. Get the [source code](#get-the-source-code.html)
+. You can use [Subclipse plugin|http://subclipse.tigris.org/servlets/ProjectProcess?pageID=p4wYuA]
+ for Eclipse
+1. Install Maven plugin for eclipse through the update site present in [M2Eclipse](http://m2eclipse.codehaus.org/)
+1. JDK 1.6
+Since hadoop requires jdk 1.6, Mahout also needs jdk 1.6 and you would have
+to make sure JRE 1.6 is added to Eclipse.
+To use JRE 1.6 for Mahout, go to Preferences --> Java --> Installed JREs
+\--> Click Add and specify
+1. # JRE type as "standard VM"
+1. # JRE Name as "JVM 1.6" and
+1. # JRE home directory as
+/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home and click
+Ok
+1. # Select this new JVM (JVM 1.6) and click Ok
+1. Building Mahout - Right-click on the mahout project and choose "run as"
+\--> "maven project"
+
+<a name="BuildingMahout-CommonproblemsbuildingMahout"></a>
+## Common problems building Mahout
+
+Sometimes the compilation may fail. Depending on the error type the tips
+below may help.
+
+* Type 1: "artifact not found, please download and install it manually"
+\--> clean maven repository and try again
+
+    rm -rf ~/.m2/
+
+
+* Type 2: "build failed because of a single test - 1 test failed, Failures:
+1"  \--> retry compilation from clean (you may need to clean the \~/.m2
+directory above)
+
+    mvn clean install
+
+
+* Type 3 (MacOSX only): Wrong Java Version
+
+Problem: There is an error 'javac: invalid target release: 1.6' even though
+Java 6 is set to be the default in the Java Preferences. Even on the
+command line, 'java \-version' showed 1.6 as the version number. However,
+this did not carry over to Maven, as 'mvn \-v' confirmed.
+
+Solution: Explicitly set the 'JAVA_HOME' environment variable. Strangely
+enough, this does not happen automatically when changing the Java
+Preferences.  In my case, I set it via 'export
+JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home/'
+
+If you don't want to hard-code which java version you use, you can use
+this:
+
+export JAVA_HOME=$(/usr/libexec/java_home)
+
+This makes use of whatever version of Java you have set on the Java control
+panel.
+
+
+* Type 4: Out of Memory when compiling
+
+Problem: 'java.lang.OutOfMemoryError: Java heap space' when compiling the
+core module of a current svn checkout of Mahout (not the release).
+
+Solution: Set the environment variable 'MAVEN_OPTS' to allow for more
+memory via 'export MAVEN_OPTS=-Xmx1024m'
+
+
+
+<a name="BuildingMahout-BuildingMahoutwiththeIBMJVM"></a>
+## Building Mahout with the IBM JVM
+Due to Hadoop using some Sun proprietary API's in version  0.20.203.0 (the
+version of Hadoop used by version of Mahout in trunk), some care must be
+taken when building Mahout from source. 
+
+To build Mahout: 
+
+1. using [Subversion](http://subversion.tigris.org)
+, check out the trunk:
+
+    svn co http://svn.apache.org/repos/asf/mahout/trunk
+
+Using trunk is required due to a failing unit test under the IBM JVM in
+Mahout .5.
+
+1. Set the environment variable JAVA_HOME to the correct location.
+1. Update the pom.xml in the project root directory to use Hadoop version
+0.20.2 by 
+ setting the version number for the Hadoop to the following:
+
+    <groupId>org.apache.hadoop</groupId>
+           <artifactId>hadoop-core</artifactId>				    
+           <version> 0.20.2</version>  
+
+1. mvn install will now build and test your Mahout distribution.
+ 
+
+
+
+
+<a name="BuildingMahout-Sometipstospeedupinstallationbyskippingtesting"></a>
+## Some tips to speed up installation by skipping testing
+
+Although we love testing and running the tests is strongly recommended for
+the first installation, there are instances when you may want to skip
+testing altogether, or only include a subset of them. This can shorten the
+lengthy installation time of nearly 15 minutes to a matter of 10 to 15
+seconds. Assuming MAHOUT_HOME is the directory of Mahout, to achieve fast
+installation you have the following options depending on your requirements:
+
+<a name="BuildingMahout-Avoidtestingcompletely."></a>
+### Avoid testing completely.
+
+This is useful when you've made changes to files which are NOT under the
+tests directory (MAHOUT_HOME/core/src/test/... or
+MAHOUT_HOME/math/src/test/...), or you have added new code under
+MAHOUT_HOME/core/src/main/ or MAHOUT_HOME/math/src/main/ and want to see if
+it compiles. Change to the MAHOUT_HOME directory, and type:
+
+
+    mvn -DskipTests install
+
+
+This will compile and install Mahout's classes, including your new code,
+and skip ALL tests.
+
+<a name="BuildingMahout-Runningonlyafewtests:MethodI"></a>
+### Running only a few tests: Method I
+
+Let's say you have implemented a new feature by making changes to a source
+file called MyNewFeature, and you have written some corresponding unit
+tests for it in the file called "TestMyNewFeature" under the tests
+directory. To only run the tests of TestMyNewFeature class, from the
+MAHOUT_HOME directory, type:
+
+
+    mvn -Dtest=TestMyNewFeature install
+
+
+The TestMyNewFeature class should be passed as an argument to Maven's mvn
+command without any path information. Just the class name is needed.
+
+To run multiple test classes, you can do:
+
+
+    mvn -Dtest=TestMyNewFeature,TestAnotherNewFeature install
+
+
+<a name="BuildingMahout-Runningonlyafewtests:MethodII"></a>
+### Running only a few tests: Method II
+
+The pom.xml file present in the MAHOUT_HOME directory contains all the
+information needed by the mvn (Maven) command to compile, test, install,
+package etc. It is one place from where you can control testing as well.
+Maven uses the Surefire plugin to run JUnit tests, so to modify the default
+testing behavior of running all tests, you can modify the pom.xml to
+<include> only the tests of TestMyNewFeature class, which was used as an
+example above. Open the pom.xml present in MAHOUT_HOME in your favorite
+editor, and find the following lines:
+
+
+    <plugin>
+    	<groupId>org.apache.maven.plugins</groupId>
+    	<artifactId>maven-surefire-plugin</artifactId>
+    	<configuration>
+    	  <forkMode>once</forkMode>
+    	  <argLine>-Xms256m -Xmx512m</argLine>
+    	  <testFailureIgnore>false</testFailureIgnore>
+    	  <redirectTestOutputToFile>true</redirectTestOutputToFile>	    
+    	</configuration>
+    </plugin>
+
+
+Modify these lines to include only the TestMyNewFeature class while
+testing, by using the <includes> and <include> tags:
+
+
+    <plugin>
+    	<groupId>org.apache.maven.plugins</groupId>
+    	<artifactId>maven-surefire-plugin</artifactId>
+    	<configuration>
+    	  <forkMode>once</forkMode>
+    	  <argLine>-Xms256m -Xmx512m</argLine>
+    	  <testFailureIgnore>false</testFailureIgnore>
+    	  <redirectTestOutputToFile>true</redirectTestOutputToFile>
+    	  <includes>
+    	    <include>**/TestMyNewFeature.java</include>
+    	  </includes>
+    	</configuration>
+    </plugin>
+
+
+Next, save the modified pom.xml file and from the MAHOUT_HOME directory
+type:
+
+
+    mvn install
+
+
+This will only run the tests in the TestMyNewFeature class and install
+Mahout for you. Note that now you don't have to mention
+-Dtest=TestMyNewFeature on the command line.
+
+
+ 
+

Added: mahout/site/mahout_cms/content/developers/developer-resources.mdtext
URL: http://svn.apache.org/viewvc/mahout/site/mahout_cms/content/developers/developer-resources.mdtext?rev=1538467&view=auto
==============================================================================
--- mahout/site/mahout_cms/content/developers/developer-resources.mdtext (added)
+++ mahout/site/mahout_cms/content/developers/developer-resources.mdtext Sun Nov  3 21:36:23 2013
@@ -0,0 +1,42 @@
+Title: Developer Resources
+<a name="DeveloperResources-MakingaContribution"></a>
+## Making a Contribution
+
+Mahout is always looking for contributions, especially in the areas of
+documentation. See this Wiki for details on contributing: [How to contribute](https://cwiki.apache.org/confluence/display/MAHOUT/How+To+Contribute)
+
+We provide a list of items in JIRA that are aimed at new contributors and
+should be fairly easy to start on, these are labeled with [MAHOUT_INTRO_CONTRIBUTE](https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels%20%3D%20MAHOUT_INTRO_CONTRIBUTE)
+.
+
+<a name="DeveloperResources-SourceCode"></a>
+## Source Code
+
+The source files are now stored using Subversion (see [http://subversion.tigris.org/](http://subversion.tigris.org/)
+ and [http://svnbook.red-bean.com/]
+).
+
+svn checkout [http://svn.apache.org/repos/asf/mahout/trunk](http://svn.apache.org/repos/asf/mahout/trunk)
+ mahout/trunk
+
+<a name="DeveloperResources-Documentation"></a>
+## Documentation
+
+Javadoc documentation is available online in our code reports:
+
+* [Latest Javadoc](https://builds.apache.org/hudson/job/Mahout-Quality/javadoc/)
+* [Data Formats](https://cwiki.apache.org/confluence/display/MAHOUT/Data+Formats)
+* [File Format Integrations](https://cwiki.apache.org/confluence/display/MAHOUT/File+Format+Integrations)
+* [Database Integrations](https://cwiki.apache.org/confluence/display/MAHOUT/Database+Integrations)
+
+<a name="DeveloperResources-Issues"></a>
+## Issues
+
+All bugs, improvements, patches, etc. should be logged in [JIRA](https://issues.apache.org/jira/browse/MAHOUT)
+.
+
+<a name="DeveloperResources-ContinuousIntegration"></a>
+## Continuous Integration
+
+Mahout is continuously built on an hourly basis on the Apache [Jenkins](https://builds.apache.org/job/Mahout-Quality/)
+ build system.

Added: mahout/site/mahout_cms/content/developers/gsoc.mdtext
URL: http://svn.apache.org/viewvc/mahout/site/mahout_cms/content/developers/gsoc.mdtext?rev=1538467&view=auto
==============================================================================
--- mahout/site/mahout_cms/content/developers/gsoc.mdtext (added)
+++ mahout/site/mahout_cms/content/developers/gsoc.mdtext Sun Nov  3 21:36:23 2013
@@ -0,0 +1,66 @@
+Title: GSOC
+<a name="GSOC-Introduction"></a>
+# Introduction
+
+Mahout has been mentoring students in Google Summer of Code for as long as
+the project has existed.  To help students better understand what is
+expected of them, this page lays out common advice, links and other tips
+and tricks for successfully creating a GSOC proposal for Mahout.
+
+Be warned, however, that GSOC, particularly at the Apache Software
+Foundation (ASF), is fairly competitive.  Not only are you competing
+against others within Mahout, but Mahout is competing with other projects
+in the ASF.  Therefore, it is very important that proposals be well
+referenced and well thought out.  Even if you don't get selected, consider
+sticking around.  Open source is great career builder and can open up many
+opportunities for you.
+
+<a name="GSOC-TipsonGoodProposals"></a>
+# Tips on Good Proposals
+
+* Interact with the community before proposal time.  This is actually part
+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)
+.
+* 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
+obligations you have during the summer.  It may seem worthwhile to lie
+here, but we have failed students mid-term in the past because they did not
+participate as they said they would.  Failing mid-term means not getting
+paid.
+* Do not mail mentors off list privately unless it is something truly
+personal (most things are not).  This will likely decrease your chances of
+being selected, not increase them.
+* DO NOT BITE OFF MORE THAN YOU CAN CHEW.  Every year, there are a few
+students who propose to implement 3-5 machine learning algorithms on
+Map/Reduce, all in a two month period.	They NEVER get selected.   Be
+realistic.  All successful projects to date follow, more or less, the
+following formula:  Implement algorithm on Map/Reduce.	Write Unit Tests. 
+Do some bigger scale tests.  Write 1 or 2 examples.  Write Wiki
+documentation.	That's it.  Trust us, it takes a summer to do these things.
+*
+http://www.lucidimagination.com/search/document/2acd6fd380feec3/thoughts_on_gsoc
+
+
+<a name="GSOC-Whattoexpectonceselected"></a>
+# What to expect once selected
+
+* Just as in the proposals, almost all interaction should take place on the
+mailing lists.	Only personal matters related to your whereabouts or your
+evaluation will take place privately.
+* Show up.  Ask questions.  Be engaged.  We don't care if you know it all
+about what you are implementing.  We care about you contributing to open
+source.  You learn.  We learn.	Win-win.
+* Enjoy it!  Contributing to open source can open some amazing doors for
+your career.  
+<a name="GSOC-References"></a>
+# References
+
+[Mahout Mail Archives about GSOC](http://www.lucidimagination.com/search/?q=GSOC#/p:mahout)
+
+[GSOC Home](http://code.google.com/soc/)
+
+[GSOC FAQ](http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs)

Added: mahout/site/mahout_cms/content/developers/how-to-become-a-committer.mdtext
URL: http://svn.apache.org/viewvc/mahout/site/mahout_cms/content/developers/how-to-become-a-committer.mdtext?rev=1538467&view=auto
==============================================================================
--- mahout/site/mahout_cms/content/developers/how-to-become-a-committer.mdtext (added)
+++ mahout/site/mahout_cms/content/developers/how-to-become-a-committer.mdtext Sun Nov  3 21:36:23 2013
@@ -0,0 +1,21 @@
+Title: 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.

Added: mahout/site/mahout_cms/content/developers/how-to-contribute.mdtext
URL: http://svn.apache.org/viewvc/mahout/site/mahout_cms/content/developers/how-to-contribute.mdtext?rev=1538467&view=auto
==============================================================================
--- mahout/site/mahout_cms/content/developers/how-to-contribute.mdtext (added)
+++ mahout/site/mahout_cms/content/developers/how-to-contribute.mdtext Sun Nov  3 21:36:23 2013
@@ -0,0 +1,240 @@
+Title: How To Contribute
+"Contributing" to an Apache project is about more than just writing code --
+it's about doing what you can to make the project better.  There are lots
+of ways to contribute....
+
+{toc:style=disc|indent=20px}
+
+
+<a name="HowToContribute-BeInvolved"></a>
+## Be Involved
+
+Contributors should join the [Mahout mailing lists](https://cwiki.apache.org/confluence/display/MAHOUT/Mailing+Lists%2C+IRC+and+Archives)
+.  In particular:
+* The user list (to help others)
+* The commit list (to see changes as they are made)
+* The dev list (to join discussions of changes)  -- This is the best place
+to understand where we are headed.
+
+Please keep discussions about Mahout on list so that everyone benefits. 
+Emailing individual committers with questions about specific Mahout issues
+is discouraged.  See [http://people.apache.org/~hossman/#private_q](http://people.apache.org/~hossman/#private_q)
+.
+
+You can also [track issues that you've raised](https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=resolution+%3D+Unresolved+AND+reporter+%3D+currentUser%28%29)
+ in JIRA.
+
+<a name="HowToContribute-WhattoWorkOn?"></a>
+## What to Work On?
+
+What do you like to work on?  There are a ton of things in Mahout that we
+would love to have contributions for.  Data ingestion, data visualization,
+documentation, new algorithms, performance improvements, better tests, etc.
+ The best place to start is by looking in JIRA under the Mahout project and
+seeing what bugs have been reported and seeing if any look like you could
+take them on.  Small, well written, well tested patches are a great way to
+get your feet wet.  It could be something as simple as fixing a typo.  The
+more important piece is you are showing you understand the necessary steps
+for making changes to the code.  Mahout is a pretty big beast at this
+point, so changes, especially from non-committers, need to be evolutionary
+not revolutionary since it is often very difficult to evaluate the merits
+of a very large patch.	Think small, at least to start\!
+
+Beyond JIRA, hang out on the dev@ mailing list.  That's where we discuss
+what we are working on in the internals and where you can get a sense of
+where people are working.
+
+Also, documentation is a great way to familiarize yourself with the code
+and is always a welcome addition to the codebase and to this Wiki.
+
+Also, check out the [MAHOUT_INTRO_CONTRIBUTE](https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+MAHOUT_INTRO_CONTRIBUTE)
+ items in JIRA, as these have been deemed to be fairly easy to start on.
+
+Also feel free to jump in on the [backlog](https://issues.apache.org/jira/browse/MAHOUT/fixforversion/12318886--juststartingtobefilledin)
+ or on a the [next version|https://issues.apache.org/jira/browse/MAHOUT/fixforversion/12316364]
+
+If you are interested in working towards being a committer, [general guidelines are available online](https://cwiki.apache.org/confluence/display/MAHOUT/How+To+Become+A+Committer)
+.
+
+<a name="HowToContribute-ContributingCode(Features,BigFixes,Tests,etc...)"></a>
+## Contributing Code (Features, Big Fixes, Tests, etc...)
+
+This section identifies the ''optimal'' steps community member can take to
+submit a changes or additions to the Mahout code base.	This can be new
+features, bug fixes optimizations of existing features, or tests of
+existing code to prove it works as advertised (and to make it more robust
+against possible future changes).
+
+Please note that these are the "optimal" steps, and community members that
+don't have the time or resources to do everything outlined on this below
+should not be discouraged from submitting their ideas "as is" per "Yonik
+Seeley's (Solr committer) Law of Patches" ...
+
+{quote}
+A half-baked patch in Jira, with no documentation, no tests
+and no backwards compatibility is better than no patch at all.
+{quote}
+
+Just because you may not have the time to write unit tests, or cleanup
+backwards compatibility issues, or add documentation, doesn't mean other
+people don't. Putting your patch out there allows other people to try it
+and possibly improve it.
+
+<a name="HowToContribute-Gettingthesourcecode"></a>
+### Getting the source code
+
+First of all, you need the Mahout source code.
+
+Get the source code on your local drive using [SVN](http://lucene.apache.org/mahout/developer-resources.html)
+.  Most development is done on the "trunk":
+
+{quote}
+> svn checkout [http://svn.apache.org/repos/asf/mahout/trunk](http://svn.apache.org/repos/asf/mahout/trunk)
+ mahout-trunk
+{quote}
+
+Note that committers have to use https instead of http here, but http is
+fine for read-only access to the trunk code.
+
+<a name="HowToContribute-MakingChanges"></a>
+### Making Changes
+
+Before you start, you should send a message to the [Mahout developer mailing list](http://lucene.apache.org/mahout/mailinglists.html)
+ (Note: you have to subscribe before you can post), or file a bug in [Jira|http://issues.apache.org/jira/browse/MAHOUT]
+.  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.
+
+Modify the source code and add some (very) nice features using your
+favorite IDE.
+
+But take care about the following points
+* All public classes and methods should have informative [Javadoc comments](http://java.sun.com/j2se/javadoc/writingdoccomments/)
+.
+* Code should be formatted according to [Sun's conventions](http://java.sun.com/docs/codeconv/)
+, with one exception:
+* indent two spaces per level, not four.
+* Contributions should pass existing unit tests.
+* New [unit tests](http://www.junit.org)
+ should be provided to demonstrate bugs and fixes.
+
+<a name="HowToContribute-Generatingapatch"></a>
+### Generating a patch
+
+A "patch file" is the format that all good contributions come in.  It
+bundles up everything that is being added, removed, or changed in your
+contribution.
+
+<a name="HowToContribute-UnitTests"></a>
+#### Unit Tests
+
+Please make sure that all unit tests succeed before constructing your
+patch.
+
+{quote}
+> cd mahout-trunk
+> mvn clean test
+{quote}
+After a while, if you see
+{quote}
+BUILD SUCCESSFUL
+{quote}
+all is ok, but if you see
+{quote}
+BUILD FAILED
+{quote}
+please, read carefully the errors messages and check your code.
+
+<a name="HowToContribute-Creatingthepatchfile"></a>
+#### Creating the patch file
+
+Check to see what files you have modified with:
+{quote}
+svn stat
+{quote}
+
+Add any new files with:
+{quote}
+svn add src/.../MyNewClass.java
+{quote}
+
+Subversions "add" command only modifies your local copy, so it doess not
+require commit permissions.  By using "svn add", your entire comtribution
+can be included in a single patch file, without needing to submit a
+seperate set of "new" files.
+
+Edit the ''CHANGES.txt'' file, adding a description of your change,
+including the bug number it fixes.
+
+In order to create a patch, just type:
+
+{quote}
+svn diff > MAHOUT-$issuenumber.patch
+{quote}
+
+$issuenumber here should be the number of the JIRA issue the patch is
+supposed to fix. This will report all modifications done on Mahout sources
+on your local disk and save them into the ''MAHOUT-$issuenumber.patch''
+file.  Read the patch file. Make sure it includes ONLY the modifications
+required to fix a single issue.
+
+Please do not:
+* reformat code unrelated to the bug being fixed: formatting changes should
+be separate patches/commits.
+* comment out code that is now obsolete: just remove it.
+* insert comments around each change, marking the change: folks can use
+subversion to figure out what's changed and by whom.
+* make things public which are not required by end users.
+
+Please do:
+* try to adhere to the coding style of files you edit;
+* comment code whose function or rationale is not obvious;
+* update documentation (e.g., ''package.html'' files, this wiki, etc.)
+
+<a name="HowToContribute-Contributingyourwork"></a>
+#### Contributing your work
+
+Finally, patches should be attached to a bug report in [Jira](http://issues.apache.org/jira/browse/MAHOUT)
+.  If you are revising an existing patch, please re-use the exact same name
+as the previous attachment, Jira will "grey out" the older versions so it's
+clear which version is the newest.
+
+Please be patient.  Committers are busy people too.  If no one responds to
+your patch after a few days, please make friendly reminders.  Please
+incorporate other's suggestions into into your patch if you think they're
+reasonable.  Finally, remember that even a patch that is not committed is
+useful to the community.
+
+
+<a name="HowToContribute-Review/ImproveExistingPatches"></a>
+# Review/Improve Existing Patches
+
+If there's a Jira issue that already has a patch you think is really good,
+and works well for you -- please add a comment saying so.   If there's room
+for improvement (more tests, better javadocs, etc...) then make the changes
+and attach it as well.	If a lot of people review a patch and give it a
+thumbs up, that's a good sign for committers when deciding if it's worth
+spending time on the patch -- and if other people have already put in
+effort to improve the docs/tests for a patch, that helps even more.
+
+<a name="HowToContribute-Applyingapatch"></a>
+## Applying a patch
+
+From the base directory (assuming that is where the patch is generated
+from), run:
+
+    patch -p 0 -i <PATH TO PATCH> [--dry-run]
+
+
+<a name="HowToContribute-HelpfulResources"></a>
+# Helpful Resources
+
+The following resources may prove helpful when developing Mahout
+contributions.	(These are not an endorsement of any specific development
+tools).  Note, these are the same code styles that Lucene and Solr use.
+
+* [Eclipse codestyle.xml file for Mahout's coding conventions, same as Lucene](http://svn.apache.org/viewvc/mahout/trunk/buildtools/Eclipse-Lucene-Codestyle.xml?view=co)
+
+* [IntelliJ IDEA codestyle.xml file for Mahout's coding conventions](http://wiki.apache.org/solr/HowToContribute?action=AttachFile&do=view&target=IntelliJ.codestyle.xml)
+ (deprecated - Please don't use this. You are welcome to change this file
+to match the checkstyle and remove this notice)

Added: mahout/site/mahout_cms/content/developers/how-to-release.mdtext
URL: http://svn.apache.org/viewvc/mahout/site/mahout_cms/content/developers/how-to-release.mdtext?rev=1538467&view=auto
==============================================================================
--- mahout/site/mahout_cms/content/developers/how-to-release.mdtext (added)
+++ mahout/site/mahout_cms/content/developers/how-to-release.mdtext Sun Nov  3 21:36:23 2013
@@ -0,0 +1,200 @@
+Title: How To Release
+*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 -Prelease package
+
+<a name="HowToRelease-Makingarelease"></a>
+## Making a release
+1. Check if documentation needs an update
+1. 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
+1. 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.
+1. If this is your first release, add your key to the KEYS file. The KEYS
+file is located in Subversion at
+https://svn.apache.org/repos/asf/mahout/trunk/distribution/KEYS and copy it
+to the release directory. Make sure you commit your change.  See
+http://www.apache.org/dev/release-signing.html.
+1. 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)
+.
+1. Add a profile to your ~/.m2/settings.xml in the <profiles> section with:
+ {code}
+  <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>
+
+     # 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):
+
+<server>
+  <id>apache.releases.https</id>
+  <username>USERNAME</username>
+  <password>PASSWORD</password>
+</server>
+
+     # 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 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, do not clean or release:clean
+without first trying to do: release:rollback.  This will likely save you
+time and do the right thing.  If it doesn't work, then do clean and
+release:clean and also delete the tag from svn, if it was created. 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.
+        {panel}
+        mvn -Pmahout_release versions:set -DnewVersion=PREVIOUS_SNAPSHOT
+        mvn -Pmahout_release versions:commit
+        svn commit 
+        svn rm https://svn.apache.org/repos/asf/mahout/tags/mahout-VERSION
+        {panel}  
+        # 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/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
+    
+    h2. Post Release
+    h3. Versioning
+     * Create the next version in JIRA (if it doesn't already exist)   
+     * Mark the version as "released" in JIRA (noting the release date)
+    
+    h3. Documentation
+     * Change wiki to match current best practices (remove/change deprecations,
+etc)
+    
+    h3. Publicity
+     * update freshmeat
+     * !TheServerSide blurb
+     * blog away
+     * Update MLOSS entry: http://mloss.org/revision/view/387/.  See Grant for
+details.
+    
+    h1. Related Resources
+    
+     * http://www.apache.org/dev/#releases
+     * http://www.apache.org/dev/#mirror
+    
+    h1. :TODO: Things To Cleanup in this document
+    
+    *TODO*
+     
+     * 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]

Added: mahout/site/mahout_cms/content/developers/how-to-update-the-website.mdtext
URL: http://svn.apache.org/viewvc/mahout/site/mahout_cms/content/developers/how-to-update-the-website.mdtext?rev=1538467&view=auto
==============================================================================
--- mahout/site/mahout_cms/content/developers/how-to-update-the-website.mdtext (added)
+++ mahout/site/mahout_cms/content/developers/how-to-update-the-website.mdtext Sun Nov  3 21:36:23 2013
@@ -0,0 +1,29 @@
+Title: How To Update The Website
+<a name="HowToUpdateTheWebsite-SomeDo'sandDont'sofupdatingthewiki"></a>
+## Some Do's and Dont's of updating the wiki
+1. Keep the wiki cleanly formatted. Assume the title is of size h1
+1. Try to keep a single page for a topic instead of starting multiple one.
+If the topics are related, put it under as a child under the similar page.
+1. Notify the developers of orphaned or broken links.
+1. Use the page title to link pages so that they get correctly updated by
+when someone changes the title
+  eg:
+
+    Correct format
+    [Name of the link|How To Update The Website]
+    
+    The following is incorrect. Please change then when you encounter them
+    [Name of the link|http://<path to>/how to update the website.html]
+
+
+To update the pages, update the wiki directly. Do not change the title of
+top level pages without updating the same on the landing page.
+
+<a name="HowToUpdateTheWebsite-Howtoupdatethemahouthomepage"></a>
+## How to update the mahout home page
+(*NOTE:* _You need committer rights to modify the home page._)
+To update the home page
+1. Commit changes to the website landing page at
+https://svn.apache.org/repos/asf/mahout/site/new_website/
+1. Ensure all outgoing links from the landing page to the wiki are working
+1. The site will automatically be exported from svn as soon as its committed

Added: mahout/site/mahout_cms/content/developers/issue-tracker.mdtext
URL: http://svn.apache.org/viewvc/mahout/site/mahout_cms/content/developers/issue-tracker.mdtext?rev=1538467&view=auto
==============================================================================
--- mahout/site/mahout_cms/content/developers/issue-tracker.mdtext (added)
+++ mahout/site/mahout_cms/content/developers/issue-tracker.mdtext Sun Nov  3 21:36:23 2013
@@ -0,0 +1,36 @@
+Title: Issue Tracker
+Anything that is to be added to [the source code repository](http://svn.apache.org/viewvc/mahout/ )
+ is first presented as a patch in the issue tracker. All conversations are
+echoed on the developer mailing list and people tend to respond or continue
+conversations there rather in the issue tracker, so in order to follow an
+issue you might also have to read to the mailing lists. 
+
+An issue does not literally have to be an issue. It could be a wish, task,
+bug report, etc. and it does not have to contain a patch.
+
+Mahout use [JIRA](http://issues.apache.org/jira/browse/MAHOUT)
+. It is made by the same company that made this Wiki and a handful of other
+collaborate software development tools that supposedly can communicate with
+each other and be trigged by actions such as commits to SVN with issue
+identity in the comments.
+
+<a name="IssueTracker-Bestpractise"></a>
+### Best practise
+
+Don't create duplicate issues. Make sure your problem is a problem and that
+nobody else already fixed it. If you are new to the project it is often
+prefered that the subject of an issue is discussed on one of our mailing
+list before an issue is created.
+
+Quote 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](patch-check-list.html)
+.)
+
+Use the issue identity when referring to an issue in any of our fora.
+"MAHOUT-n" and not "mahout-n" or "n". MAHOUT-1 would automatically be
+linked to [MAHOUT-1](http://issues.apache.org/jira/browse/MAHOUT-1)
+ in a better world.
+

Added: mahout/site/mahout_cms/content/developers/patch-check-list.mdtext
URL: http://svn.apache.org/viewvc/mahout/site/mahout_cms/content/developers/patch-check-list.mdtext?rev=1538467&view=auto
==============================================================================
--- mahout/site/mahout_cms/content/developers/patch-check-list.mdtext (added)
+++ mahout/site/mahout_cms/content/developers/patch-check-list.mdtext Sun Nov  3 21:36:23 2013
@@ -0,0 +1,33 @@
+Title: Patch Check List
+So, you want to apply a patch?	Here are tips, traps, etc. for dealing with
+patches (in no particular order):
+
+1. Get a fresh copy of trunk.  Or at least make sure you are up to date and
+clean your build area.	For complex patches, it is recommended you deal
+with a fresh checkout.
+1. Look at the patch and see where it is applied.  Ideally it is generated
+from the root, but not everyone does this, especially for contrib areas.
+1. patch \-p 0 \-i <path to patch>  Throw a \--dry-run on there if you want
+to see what happens w/o screwing up your checkout.
+1. Did the author write unit tests?  Are the unit tests worthwhile?
+1. How are the benchmark results?  contrib/benchmarker may be used to test
+performance in before/after scenarios.
+1. Are the licenses correct on newly added files? Has an ASF license been
+granted?
+1. Update CHANGES.txt.  Give proper credit to the authors.
+1. Make sure you update JIRA by assigning the issue to you so that others
+know you are working on it.
+1. If it is a complex change and you have added to the original author's
+patch, it is suggested that you create a new patch and attach that to JIRA
+so that it can be discussed.
+1. How's the documentation, esp. the javadocs?
+1. Before committing, make sure you add any new documents to SVN.  Just b/c
+the patch added them doesn't mean you have.
+1. Run all unit tests, verify all tests pass.
+1. Generate javadocs, verify no javadoc errors/warnings were introduced by
+the patch.
+1. Put in a meaningful commit message.  Reference the JIRA issue when
+appropriate.
+1. Remember to update the issue in JIRA when you have completed it.
+1. From the top directory "ant rat-sources" to make sure all the files have
+license headers.

Added: mahout/site/mahout_cms/content/developers/thirdparty-dependencies.mdtext
URL: http://svn.apache.org/viewvc/mahout/site/mahout_cms/content/developers/thirdparty-dependencies.mdtext?rev=1538467&view=auto
==============================================================================
--- mahout/site/mahout_cms/content/developers/thirdparty-dependencies.mdtext (added)
+++ mahout/site/mahout_cms/content/developers/thirdparty-dependencies.mdtext Sun Nov  3 21:36:23 2013
@@ -0,0 +1,23 @@
+Title: Thirdparty Dependencies
+If you have a dependency on a third party artifact that is not in Maven,
+you should:
+
+1. Ask the project to add it if at all possible.  Most open source projects
+want wider adoption, so this kind of request is often well received.
+1. If they won't add it, we may be able to add it to our Maven repo,
+assuming it can be published at the ASF at all (no GPL code, for instance).
+ Please ask on the mailing list first.
+1. Assuming it can be, then you need to sign and deploy the artifacts, as
+described below:
+  mvn gpg:sign-and-deploy-file	     
+-Durl=https://repository.apache.org/service/local/staging/deploy/maven2 
+-DrepositoryId=apache.releases.https -DgroupId=org.apache.mahout.foobar
+-DartifactId=foobar -Dversion=x.y -Dpackaging=jar -Dfile=foobar-x.y.jar
+1. Once it is deployed, go into http://repository.apache.org/ (use your SVN
+credentials to login in)
+1. Select Staging
+1. Find your repository artifacts
+1. Close them (this makes them publicly available, since you are closing the
+staging repo)
+1. Promote them. This adds them to the public Maven repo.
+

Added: mahout/site/mahout_cms/content/developers/version-control.mdtext
URL: http://svn.apache.org/viewvc/mahout/site/mahout_cms/content/developers/version-control.mdtext?rev=1538467&view=auto
==============================================================================
--- mahout/site/mahout_cms/content/developers/version-control.mdtext (added)
+++ mahout/site/mahout_cms/content/developers/version-control.mdtext Sun Nov  3 21:36:23 2013
@@ -0,0 +1,36 @@
+Title: Version Control
+The Mahout source code resides in the [Apache Subversion (SVN)](http://subversion.tigris.org/)
+ repository. The command-line SVN client can be obtained [here|http://subversion.tigris.org/project_packages.html]
+. The TortoiseSVN GUI client for Windows can be obtained [here|http://tortoisesvn.tigris.org/]
+. There are also SVN plugins available for both [Eclipse|http://subclipse.tigris.org/]
+ and [IntelliJ IDEA|http://svnup.tigris.org/]
+. 
+
+There is also a [git](http://git-scm.com/)
+ repository for Mahout available [at Apache|http://git.apache.org/]
+.
+
+<a name="VersionControl-WebAccess(read-only)"></a>
+## Web Access (read-only)
+
+The source code can be browsed via the Web at [http://svn.apache.org/viewvc/mahout/](http://svn.apache.org/viewvc/mahout/)
+. No SVN client software is required. 
+
+<a name="VersionControl-AnonymousAccess(read-only)"></a>
+## Anonymous Access (read-only)
+
+The SVN URL for anonymous users is [http://svn.apache.org/repos/asf/mahout/trunk](http://svn.apache.org/repos/asf/mahout/trunk)
+. Instructions for anonymous SVN access are here. 
+
+<a name="VersionControl-CommitterAccess(read-write)"></a>
+## Committer Access (read-write)
+
+The SVN URL for committers is [https://svn.apache.org/repos/asf/mahout/trunk](https://svn.apache.org/repos/asf/mahout/trunk)
+. Instructions for committer SVN access are [here|https://cwiki.apache.org/confluence/display/MAHOUT/IssueTracker]
+. 
+
+<a name="VersionControl-Issues"></a>
+## Issues
+
+All bugs, improvements, patches, etc. should be logged in [JIRA](http://issues.apache.org/jira/browse/MAHOUT)
+.

Added: mahout/site/mahout_cms/content/general/books-tutorials-and-talks.mdtext
URL: http://svn.apache.org/viewvc/mahout/site/mahout_cms/content/general/books-tutorials-and-talks.mdtext?rev=1538467&view=auto
==============================================================================
--- mahout/site/mahout_cms/content/general/books-tutorials-and-talks.mdtext (added)
+++ mahout/site/mahout_cms/content/general/books-tutorials-and-talks.mdtext Sun Nov  3 21:36:23 2013
@@ -0,0 +1,109 @@
+Title: Books Tutorials and Talks
+
+# Intro
+
+This page is a place to put links to info about talks (past and upcoming),
+tutorials, articles, books, slides, PDFs, discussions, etc. about Mahout,
+Machine Learning and related technologies.  No endorsements are implied or
+given.	Please keep all listings in alphabetical order within each section.
+
+# Background Material
+
+   * <a href="reference-reading.html">Reference Reading</a>
+
+   * <a href="http://www.inma.ucl.ac.be/~francois/blog/entries/entry_757.php">Collection of links to presentations on learning algorithms</a>
+
+# Books
+
+   * <a href="http://www.manning.com/owen/">Mahout in Action</a> - Book by Sean Owen, Robin Anil, Ted Dunning and Ellen Friedman published Oct 2011 by Manning Publications.
+   * <a href="http://www.manning.com/ingersoll/">Taming Text</a> - By Grant Ingersoll and Tom Morton, published by Manning Publications. Will have some Mahout coverage, but by no means as complete as Mahout in Action.
+   * <a href="http://www.cs.waikato.ac.nz/~ml/weka/book.html">Data Mining: Practical Machine Learning Tools and Techniques</a>
+   * <a href="http://www.amazon.com/Programming-Collective-Intelligence-Building-Applications/dp/0596529325/ref=pd_bbs_sr_1/104-1017533-9408723?ie=UTF8&s=books&qid=1214593516&sr=1-1">Programming Collective Intelligence</a>
+   * <a href="http://www.amazon.com/Collective-Intelligence-Action-Satnam-Alag/dp/1933988312/ref=pd_bbs_sr_3?ie=UTF8&s=books&qid=1214545249&sr=1-3">Collective Intelligence in Action</a>
+   * <a href="http://www.amazon.com/Machine-Learning-Mcgraw-Hill-International-Edit/dp/0071154671/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1214593709&sr=8-1">Machine Learning</a>
+   * <a href="http://www.amazon.com/Pattern-Recognition-Learning-Information-Statistics/dp/0387310738/ref=pd_bbs_sr_2?ie=UTF8&s=books&qid=1214593709&sr=8-2">Pattern Recognition and Machine Learning (Information Science and Statistics) </a>
+   * <a href="http://www-csli.stanford.edu/~hinrich/information-retrieval-book.html">Introduction to Information Retrieval</a>
+   * <a href="-http://www.inference.phy.cam.ac.uk/itprnn/book.html.html">Information Theory, Inference, and Learning Algorithms by David MacKay</a>
+   * <a href="-http://www.amazon.com/text-mining-application-programming/dp/1584504609.html">Text Mining Application Programming </a>
+   * <a href="http://www.amazon.com/Algorithms-Intelligent-Web-Haralambos-Marmanis/dp/1933988665/ref=sr_1_1?s=books&ie=UTF8&qid=1298005918&sr=1-1">Algorithms of the Intelligent Web</a>
+
+# News, Articles and Tutorials
+
+   * <a href="http://www.ibm.com/developerworks/java/library/j-mahout-scaling/">Apache Mahout: Scalable Machine Learning for Everyone</a>
+   * <a href="http://www.acunu.com/blogs/sean-owen/scaling-cassandra-and-mahout-hadoop/">Scaling up Cassandra and Mahout with Hadoop</a>
+   * <a href="http://www.acunu.com/blogs/sean-owen/recommending-cassandra/">Recommending (from) Cassandra</a>
+   * <a href="http://emmaespina.wordpress.com/2011/04/26/ham-spam-and-elephants-or-how-to-build-a-spam-filter-server-with-mahout/">How to build a spam filter server with Mahout</a> - Applying classification on a live server - April 2011
+   * <a href="http://ssc.io/deploying-a-massively-scalable-recommender-system-with-apache-mahout/">Deploying a massively scalable recommender system with Apache Mahout</a> - Blogpost of Sebastian Schelter in April 2011
+   * <a href="http://www.redmonk.com/cote/2010/11/04/makeall013/">Apache Mahout & the commoditization of machine learning </a> - Podcast interview with Grant Ingersoll at ApacheCon 2010
+   * <a href="http://isabel-drost.de/hadoop/slides/devoxx.pdf">Apache Mahout 0.4 mit neuen Algorithmen</a> - published after the 0.4 release by heise Open/ Developer, November 2010
+   * <a href="http://www.infoq.com/news/2009/04/mahout">Mahout on InfoQ</a> - Interview with Grant Ingersoll on InfoQ
+   * <a href="http://www.cloudera.com/blog/2009/04/21/hadoop-uk-user-group-meeting/">Mahout in the Cloudera weblog</a> - published after the Hadoop user group UK.
+   * <a href="http://blog.athico.com/2008/08/machine-learning-and-apache-mahout.html">Mahout in the Drools weblog</a> - Michael Neale published an article on Mahout in the drools weblog
+   * <a href="https://www.ibm.com/developerworks/java/library/j-mahout/index.html">Introducing Apache Mahout</a> - Grant Ingersoll - Intro to Apache Mahout focused on clustering, classification and collaborative filtering. Japanese translation available at: [http://www.ibm.com/developerworks/jp/java/library/j-mahout/](http://www.ibm.com/developerworks/jp/java/library/j-mahout/)
+   * <a href="http://philippeadjiman.com/blog/2009/11/11/flexible-collaborative-filtering-in-java-with-mahout-taste/">Flexible Collaborative Filtering In Java With Mahout Taste</a> - Philippe Adjiman - Quick starting guide on how to use the collaborative filtering package of Mahout (called Taste) to quickly and flexibly create, test and compare tailored recommendation engines.
+   * <a href="http://www.lucidimagination.com/blog/2010/03/16/integrating-apache-mahout-with-apache-lucene-and-solr-part-i-of-3/">Integrating Mahout with Lucene and Solr</a> Three part series on ways to integrate Mahout with Lucene and Solr
+
+# Coursework/Lectures
+
+   * <a href="http://videolectures.net/mlss05us_chicago/">http://videolectures.net/mlss05us_chicago/</a>
+   * <a href="http://videolectures.net/mlas06_pittsburgh/">http://videolectures.net/mlas06_pittsburgh/</a>
+   * <a href="http://wiki.ailab.wsu.edu/ml/index.php/Main_Page">http://wiki.ailab.wsu.edu/ml/index.php/Main_Page</a>
+   * <a href="http://see.stanford.edu/see/lecturelist.aspx?coll=348ca38a-3a6d-4052-937d-cb017338d7b1">Stanford Lectures on Machine Learning by Andrew Ng</a>
+   * <a href="https://docs.google.com/open?id=0ByhGL2_SCeitMDQ3OTczNjItM2ZjYi00ZDg5LWE0MzItZGQxODQ5NzkzYjNj">CMU@Qatar Introduction to Mahout lecture</a>
+
+
+# Talks
+
+   * Let's keep these in reverse chronological order, so that most recent talks
+are at the top
+
+   * <a href="http://www.slideshare.net/VaradMeru/introduction-to-mahout-and-machine-learning">Introduction to Mahout and Machine Learning</a> - Slides by Varad Meru, Software Development Engineer at Orzota. July 27th, 2013.
+   * <a href="https://github.com/ManuelB/facebook-recommender-demo/raw/master/docs/Talk-BedCon-Berlin-2012.pdf">How to build a recommender system based on Mahout and JavaEE</a> - Slides by Manuel Blechschmidt at Berlin Expert Days March, 2012.
+   * <a href="http://lanyrd.com/2011/apachecon-north-america/skdtb/">Apache Mahout for intelligent data analysis</a> - Slides from Isabel Drost at Apache Con NA November, 2011.
+   * <a href="http://lanyrd.com/2011/apachecon-north-america/skdrk/">Dr. Mahout: Analyzing clinical data using scalable and distributed computing</a> - Slides from Shannon Quinn at Apache Con NA November, 2011.
+   * <a href="http://berlinbuzzwords.de/sites/berlinbuzzwords.de/files/composing-mahout-clustering-jobs.pdf">Composing Mahout clustering jobs</a> - Slides from Frank Scholten at Berlin Buzzwords on June 7, 2011.
+   * Introduction to Collaborative Filtering using Mahout (updated) - Talk by Sean Owen at the London Hadoop User Group on April 14, 2011.
+   *  <a href="http://www.meetup.com/LA-HUG/pages/Video_from_March_16th_LA-HUG_Ted_Dunning_Mahout">Cool Tricks with Classifiers</a> - Talk by Ted Dunning at the Los Angeles HUG talking about Mahout classifiers on March 16, 2011.
+   * <a href="http://blog.isabel-drost.de/index.php/archives/325/apache-mahout-hackathon-berlin-2">Mahout Hackathon</a> - event write up of the first Mahout Hackathon, Berlin, March 2011.
+   * <a href="http://blog.jteam.nl/2011/01/13/announcement-lucene-nl-mahout-meetup-with-isabel-drost-feb-7/">Mahout meetup</a> - there were two talks at the Apache Mahout meetup at JTeam in Amsterdam, February 2011. ([Intro slides|http://isabel-drost.de/hadoop/slides/jteam.pdf]
+   * <a href="-http://www.fosdem.org/2011/schedule/event/mahoutclustering.html">Mahout clustering </a> - Talk on Mahout clustering at data dev room FOSDEM, February 2011.
+   * <a href="-http://strataconf.com/strata2011/public/schedule/detail/16827.html">Scaling Data Analysis with Apache Mahout </a> - talk on Mahout at O'Reilly Strata, February 2011. 
+   * <a href="http://www.slideshare.net/jaganadhg/mahout-tutorial-fossmeet-nitc">Practical Machine Learning</a> - Slides from Biju B and Jaganadh G, FOSSMEET-NITC, Calicut, India, February 2011.
+   * <a href="http://www.javaedge.com/jedge/pdf/Mahout.pdf">Mahout at AlphaCSPs The Edge 2010 (pdf)</a> - <a href="http://www.slideshare.net/arikogan/mahouts-presentation-at-alphacsps-the-edge-2010">slideshare</a> - Slides from <a href="http://il.linkedin.com/in/arielkogan">Ariel Kogan</a> AlphaCSP's The Edge, December 2010.
+   * <a href="http://isabel-drost.de/hadoop/slides/devoxx.pdf">Intelligent data analysis with Apache Mahout</a> - Slides from Isabel Drost, Devoxx Antwerp, November 2010.
+   * <a href="http://isabel-drost.de/hadoop/slides/codebits.pdf">Apache Mahout introduction</a> - Slides from Isabel Drost, codebits Lisbon, November 2010.
+   * <a href="http://isabel-drost.de/hadoop/slides/apachecon_2010.pdf">Apache Mahout - Making Data Analysis Easy</a> - Slides from Isabel Drost, Apache Con US Atlanta, November 2010.
+   * <a href="http://www.slideshare.net/jaganadhg/bck9">Practical Machine Learning</a> - Slides from Jaganadh G, BarCamp Kerala 9, November 2010.
+   * <a href="http://www.slideshare.net/tdunning/sdforum-11042010">Mahout and its new classification framework</a> - Slides from Ted Dunning, SDForum, November 2010.
+   * <a href="http://www.slideshare.net/sscdotopen/mahoutcf">Distributed Itembased Collaborative Filtering with Apache Mahout</a> - Slides from Sebastian Schelter, Hadoop Get Together Berlin, October 2010.
+   * <a href="http://isabel-drost.de/hadoop/slides/HMM.pdf">Hidden Markov Models for Mahout</a> - Slides from Max Heimel, Hadoop Get Together Berlin, October 2010.
+   * <a href="http://www.slideshare.net/robinanil/oscon-apache-mahout-mammoth-scale-machine-learning">Apache Mahout Mammoth Scale Machine Learning </a> - Slides from Robin Anil, OSCON 2010.
+   * <a href="http://slidesha.re/9LxOIu">Intro to Apache Mahout</a> - Slides from Grant Ingersoll,  RTP Semantic Web Group.
+   * <a href="http://www.slideshare.net/ydn/3-biometric-hadoopsummit2010">Case study: Biometric Databases and Hadoop </a> - Slides from Jason Trost, Hadoop Summit 2010.
+   * <a href="http://www.slideshare.net/hadoopusergroup/mail-antispam?from=ss_embed">Spam Fighting at Yahoo</a>
+   * <a href="http://www.slideshare.net/hadoopusergroup/bixo-hug-talk?from=ss_embed">Web Mining with Ken Krugler</a>
+   * <a href="http://berlinbuzzwords.wikidot.com/local--files/links-to-slides/ingersoll_bbuzz2010.pdf">Keynote on intelligent search</a> - Slides from Grant Ingersoll, Berlin Buzzwords, June 2010.
+   * <a href="http://berlinbuzzwords.wikidot.com/local--files/links-to-slides/owen_bbuzz2010.pdf">Simple co-occurrence-based recommendation on Hadoop</a> - Slides from Sean Owen, Berlin Buzzwords, June, 2010.
+   * <a href="http://berlinbuzzwords.wikidot.com/local--files/links-to-slides/scholten_bbuzz2010.odp">Introduction to Collaborative Filtering using Mahout</a> - Slides from Frank Scholten, Berlin Buzzwords, June, 2010.
+   * <a href="http://lucene.grantingersoll.com/2010/02/16/trijug-intro-to-mahout-slides-and-demo-examples/">Introduction to Scalable Machine Learning</a> - Slides and demos from Grant Ingersoll, March, 2010.
+   * <a href="http://www.scribd.com/doc/27637351/Mahout-India-Hadoop-Summit">Mahout @ India Hadoop Summit</a> - Slides from a 1 hour talk on Mahout at the India Hadoop Summit by Robin Anil, February 2010.
+   * <a href="http://www.isabel-drost.de/hadoop/slides/opensourceexpo09.pdf">Mahout in 10 minutes</a> - Slides from a 10 min intro to Mahout at the Map Reduce tutorial by David Z&uuml;lke at Open Source Expo in Karlsruhe, Isabel Drost, November 2009.
+   * <a href="http://www.isabel-drost.de/hadoop/slides/apacheconus2009.pdf">Mahout at Apache Con US </a> - Slides from a talk on "Going from raw data to information" (with Mahout) at Apache Con US in Oakland, Isabel Drost, November 2009.
+   * <a href="http://www.isabel-drost.de/hadoop/slides/froscon2009.pdf">Mahout at FrOSCon</a> - Slides from a talk on Mahout at FrOSCon in Sankt Augustin, Isabel Drost, August 2009.
+   * <a href="http://www.isabel-drost.de/hadoop/slides/dai.pdf">Mahout at DAI group TU Berlin</a> - Slides from a talk on Mahout at the DAI Laboratories TU Berlin, Isabel Drost, July 2009.
+   * <a href="http://www.hpi.uni-potsdam.de/naumann/lehre/ss_09/mapreduce_algorithms_on_hadoop.html">Machine Learning course at HPI Potsdam</a> that relies on Hadoop for efficient implementation. ([Some slides|http://www.isabel-drost.de/hadoop/slides/ewen.pdf] that try to explain, why students taking this course should come over and have a look at and participate in Mahout.)
+   * <a href="http://www.isabel-drost.de/hadoop/slides/ulf.pdf">Mahout at Machine Learning Group TU Berlin</a> - Slides from a talk on Hadoop with some detour to Mahout at the Machine
+   * Learning Group of Prof. Dr. Klaus-Robert M&uuml;ller at TU Berlin, Isabel Drost, June 2009.
+   * <a href="http://http://www.isabel-drost.de/hadoop/slides/dima.pdf">Mahout at DIMA TU Berlin</a> - Slides from the research colloquium at DIMA (Fachgebiet Datenbanksysteme und Informationsmanagement, Prof. Dr. rer. nat. Volker Markl) TU Berlin, Isabel Drost, May 2009.
+   * <a href="http://www.isabel-drost.de/hadoop/slides/google.pdf">Mahout at Google Z&uuml;rich</a> - Slides from a Google tech-talk on the past, present and future of Mahout, Isabel Drost, May 2009.
+   * <a href="http://static.last.fm/johan/huguk-20090414/isabel_drost-introducing_apache_mahout.pdf">Hadoop user group UK</a> - Slides from a talk on April 14, 2009 at the Hadoop User Group UK in London, Isabel Drost, April 2009.
+   * <a href="http://cwiki.apache.org/confluence/download/attachments/88410/SDForum.pdf">BI Over Petabytes: Meet Apache Mahout</a> - Slides from a talk by Jeff Eastman on April 21, 2009 at the Bay Area SD Forum Business Intelligence SIG meeting at SAP in Palo Alto, CA.
+   * Lucene Meetup and Apache Barcamp in Amsterdam, March 2009.
+   * <a href="http://barcamp.org/BarCampRDU">BarCampRDU</a> - No guarantee it will be scheduled, but Grant Ingersoll will be at BarCampRDU (Raleigh) on Aug. 2, 2008 and would like to talk with people interested in Mahout and Hadoop.
+   * <a href="http://www.us.apachecon.com/us2008">Introducing Mahout: Apache Machine Learning</a> - Committer Grant Ingersoll will be giving a gentle introduction to Mahout and Machine Learning at ApacheCon in November (3rd through 7th) in New Orleans, USA.  Schedule TBD.
+   * <a href="http://www.froscon.org/">Mahout: Scaling Machine Learning</a> - Introduction to Mahout and machine learning at FrOSCon in Sankt Augustin/Germany, Isabel Drost, August 2008.  (<a href="http://cwiki.apache.org/confluence/download/attachments/88410/froscon.pdf">slides</a>)
+   * <a href="http://upcoming.yahoo.com/event/807782/">Mahout: Scalable Machine Learning</a> - An introduction to Mahout and machine learning at the first German Hadoop gathering in newthinking store/ Berlin, Isabel Drost, July 2008.
+   * Apache Mahout: Industrial Strength Machine Learning - Committer Jeff Eastman gave an introduction to Mahout at Yahoo\!, May 2008
+   * <a href="http://people.apache.org/~berndf/openexpode08-lucene-talk.pdf">Apache Lucene - Mach's wie Google</a> - Bernd Fondermann presented an overview of the Apache Lucene project,
+   * including Mahout at Open Source Expo 2008 in Karlsruhe, May 2008.
+   * Apache Mahout: Bringing Machine Learning to Industrial Strength - Committer Isabel Drost gave a Fast Feather introduction the the new project Mahout at Apache Con EU April, 2008

Added: mahout/site/mahout_cms/content/general/downloads.mdtext
URL: http://svn.apache.org/viewvc/mahout/site/mahout_cms/content/general/downloads.mdtext?rev=1538467&view=auto
==============================================================================
--- mahout/site/mahout_cms/content/general/downloads.mdtext (added)
+++ mahout/site/mahout_cms/content/general/downloads.mdtext Sun Nov  3 21:36:23 2013
@@ -0,0 +1,75 @@
+Title: Downloads
+<a name="Downloads-OfficialRelease"></a>
+# Official Release
+
+Apache Mahout is an official Apache project and thus available from any of
+the Apache mirrors.
+
+The latest Mahout release is available for download at: *[http://www.apache.org/dyn/closer.cgi/mahout/](http://www.apache.org/dyn/closer.cgi/mahout/)
+*
+
+[MAHOUT:System Requirements](mahout:system-requirements.html)
+ are detailed online. 
+
+<a name="Downloads-SnapshotReleases"></a>
+# Snapshot Releases
+
+Recent builds are available on the Apache Jenkins [build server](https://builds.apache.org/job/Mahout-Quality/changes)
+To get the latest, navigate to "Build History", in the lower left-hand
+corner.
+Pick the latest build which has a yellow ball instead of a red ball.
+Go to "Build Artifacts" page.
+Download "all files in trunk" zip file
+
+Now, how you go from there to running examples: you don't. These build
+artifacts do not include the shell scripts and other materiel needed
+to run the Mahout examples: you are only able to use the jars in your
+own projects.
+
+[MAHOUT-935](https://issues.apache.org/jira/browse/MAHOUT-935)
+ is filed as a marker to make the builds more useable. You are welcome and
+encouraged to fix this problem!
+
+<a name="Downloads-FutureReleases"></a>
+# Future Releases
+
+Official releases are usually created when the developers feel there are
+sufficient changes, improvements and bug fixes to warrant a release. Watch
+the [Mailing lists](https://cwiki.apache.org/MAHOUT/mailinglistarchives.html)
+ for latest release discussions.
+
+<a name="Downloads-Backwardscompatibilityofreleases"></a>
+# Backwards compatibility of releases
+
+_Please note that below backwards compatibility contract is a draft. As
+soon as finished the line you are about to read will be deleted._
+
+As of version 1.0 Apache Mahout will provide the following backwards
+compatibility guarantees.
+
+<a name="Downloads-Datainputformats,Modelformats,Modeloutput"></a>
+## Data input formats, Model formats, Model output
+
+All minor versions within a major release can read prior versions data
+within the same major release.	That is, 3.4 can read a 3.3 data.  However,
+3.3 cannot read a 3.4 data file.  When a user reads 3.3 data w/ 3.4, it is
+silently upgraded to 3.4.
+
+A major TODO that you can help with if you are interested is to provide
+serialization methods based on [Apache Avro](http://avro.apache.org)
+ that would make support for input, output and model format upgrade easier.
+
+Another option is to use the [SequenceFile.Metadata](http://hadoop.apache.org/common/docs/current/api/org/apache/hadoop/io/SequenceFile.Metadata.html)
+ feature to store file format versions.
+
+<a name="Downloads-APIsandcommandlinescripts"></a>
+## APIs and command line scripts
+
+For APIs, we typically mark things as @mahout.experimental if we think they
+may change within minor releases.  We also mark things as deprecated that
+are going away.  Deprecated items are then removed on the next major
+release.  The upgrade path is usually to go to x.9, remove all deprecations
+and then go to x+1.0.
+
+We also communicate to users via release notes when we purposefully broke
+back compat.



Mime
View raw message