mahout-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vans...@apache.org
Subject [14/52] [partial] mahout git commit: removed website directory- this folder should be empty except for the output directory
Date Tue, 27 Jun 2017 16:29:53 GMT
http://git-wip-us.apache.org/repos/asf/mahout/blob/978d4467/website/oldsite/css/global.css
----------------------------------------------------------------------
diff --git a/website/oldsite/css/global.css b/website/oldsite/css/global.css
deleted file mode 100644
index 318b577..0000000
--- a/website/oldsite/css/global.css
+++ /dev/null
@@ -1,938 +0,0 @@
-/********************************** 
- 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;
-}
-
-em {
-  font-style: italic;
-}
-
-strong {
-  font-weight: bold;
-}
-
-a img {
-  border: 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 {
-  color: #555;
-  margin: 0;
-  padding: 0;
-  background-color: #cde9fc;
-  text-align: center;
-  font-family: Arial;
-}
-
-.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-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;
-}
-
-h4 {
-    padding: 20px 10px 5px;
-}
-
-p,dl {
-  padding-left: 10px;
-  padding-top: 5px;
-  padding-bottom: 5px;
-  margin: 0;
-}
-
-ul{
-  /*margin: 10px 10px;*/
-  /*padding: 0 0 0 10px;*/
-  margin-left: 40px;
-  margin-right: 20px;
-}
-
-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 {
-  text-align: left;
-  overflow: auto;
-  font: 1em/ 1.5em 'Lucida Console', 'courier new', monospace;
-  margin: 0px;
-  border: 1px solid #DDD;
-  background-color: #F8F8F8;
-  border-radius: 3px;
-  padding: 0px;
-}
-
-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 {
-  font-weight: bold;  
-  height: 16px;
-  padding-left: 12px;
-  padding-right: 12px;
-  color: black;
-  text-align: left;
-}
-
-tr {
-  height: 34px;
-}
-
-td {
-  padding-left: 11px;
-  padding-right: 11px;
-}
-
-input,select {
-  padding: 4px;
-  font-size: 1em;
-  font-weight: 300;
-  color: #555;
-}
-
-input[type="search"] {
-  width: 220px;
-}
-
-#sidebar-wrap {
-  padding: 0 0 0 0px;
-}
-
-#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;
-  color: #555;
-  background: #fff;
-}
-
-textarea {
-  width: 400px;
-  padding: 4px;
-  font-size: 1em;
-  font-weight: 300;
-  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;
-  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 {
-  width: 1200px;
-  margin: 0 auto;
-  text-align:left;
-}
-
-#content-wrap  {
-  width: 860px;
-  margin: 0;
-  padding-bottom: 42px;
-  background-color: white;
-}
-
-#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:860px;
-  border-top: 1px solid #eee;
-  background-color: #E2E2E2;
-  padding: 20px 0;
-}
-
-#footer #container {
-  width: 860px;
-  margin: 0;
-  float: left;
-}
-
-#foot {
-  text-align:left;
-  position:relative;
-  top:5px;
-  left:30px;
-}
-
-
-
-#header {
-  position: relative;
-  width: 945px;
-  height: 166px;
-  padding: 0;
-  margin: 0;
-  background: transparent;
-}
-
-#header #logo {
-  position: absolute;
-  top: 20px;
-  left: 10px;
-  height: 104px;
-  width: 498px;
-}
-
-#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:40px;
-  padding:5px;
-  padding-top:4px;
-  padding-left:33px;
-  background-color:#444;
-  width: 260px;
-  height: 133px;
-}
-
-.hintText {
-  display: none;
-}
-
-.fieldWithHint {
-  color: #001f2f;
-}
-
-#nav {
-  position: absolute;
-  clear: both;
-  margin: 0;
-  padding: 0;
-  padding-right:5px;
-  padding-left:5px;
-  right:0;
-  height: 33px;
-  top: 133px;
-  z-index: 99999;
-  background-color:#444;
-}
-
-div.navbar-inner {
-  min-height: 33px;
-  padding-right: 0px;
-  padding-left: 0px;
-  background-color: #FAFAFA;
-  background-image: none;
-  background-repeat: repeat-x;
-  border: none;
-  border-radius: 4px;
-  box-shadow: 0px 1px 4px rgba(0, 0, 0, 0.067);
-}
-
-#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);
-}
-
-.navbar .nav {
-  float: right;
-  margin-right: 30px;
-}
-
-.navbar .nav > li > a {
-  text-align: left;
-  color: #fff;
-}
-
-.navbar .container {
-  width: 860px;
-  text-align: left;
-}
-
-#main {
-  float: left;
-  width: 826px;
-  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;
-}
-
-#main h1 a {
-  color: #333;
-  text-decoration: none;
-  background: none;
-  border: none;
-}
-
-#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;
-  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: 300px;
-  margin-left: 20px;
- /*  margin: 0 20px 0 10px;*/
-  display:inline;
-  padding: 15px;
-  color: #a8569c;
-}
-
-#main .highlights h4 {
-  padding-top: 10px;
-}
-
-#sidebar {
-  float: right;
-  width: 280px;
-  padding: 0;
-  
-  display: inline;
-}
-
-#sidebar h2 {
-  margin-top: 10px;
-  padding: 15px 5px 0px 10px;
-  font-size: 1.5em;
-  font-weight: 300;
-  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;
-}
-
-pre {
-  padding: 9.5px;
-  margin: 0px 0px 10px;
-  background-color: #F5F5F5; 
-  border: 1px solid rgba(0, 0, 0, 0.15);
-  border-radius: 4px;        
-  margin-left: 10px;
-  margin-right: 10px;  
-}
-
-#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;
-  width: 1150px;
-  margin: 0 auto;
-  text-align: left;
-}
-
-body#home #header {
-  position: relative;
-  width: 860px;
-  padding: 0;
-  margin: 0;
-  background-color: white;
-}
-
-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: 1200px;
-  margin: 0 auto;
-  text-align: left;
-}
-
-#search-form {
-  margin-top: 20px;
-}
-
-#search-form input {
-  float: left;
-}
-
-#search-form .search-query {
-  font-family: Arial;
-  width: 180px;
-  margin-right: 10px;
-}
-
-#search-form #submission {
-  border: none;
-  background: transparent;
-  margin-right: 10px;
-}
-
-code.has-jax {font: inherit; font-size: 100%; color: #555; background: inherit; border: inherit;}

http://git-wip-us.apache.org/repos/asf/mahout/blob/978d4467/website/oldsite/css/global__.css
----------------------------------------------------------------------
diff --git a/website/oldsite/css/global__.css b/website/oldsite/css/global__.css
deleted file mode 100644
index b3001dd..0000000
--- a/website/oldsite/css/global__.css
+++ /dev/null
@@ -1,886 +0,0 @@
-/********************************** 
- 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: 1200px;
-  margin: 0 auto;
-  text-align:left;
-}
-
-#content-wrap  {
-  width:1200px;
-  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:1200px;
-  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: 826px;
-  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: 323px;
-  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-v3.png) top center no-repeat;
-  width: 1200px;
-  margin: 0 auto;
-  text-align: left;
-}
-
-body#home #header {
-  position: relative;
-  width: 1200px;
-  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: 1200px;
-  margin: 0 auto;
-  text-align: left;
-}

http://git-wip-us.apache.org/repos/asf/mahout/blob/978d4467/website/oldsite/css/main.css
----------------------------------------------------------------------
diff --git a/website/oldsite/css/main.css b/website/oldsite/css/main.css
deleted file mode 100644
index a6cb362..0000000
--- a/website/oldsite/css/main.css
+++ /dev/null
@@ -1,4 +0,0 @@
-.feather {
-	background-image:url('http://www.apache.org/images/feather-small.gif');
-	background-repeat:no-repeat;
-}
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/mahout/blob/978d4467/website/oldsite/developers/buildingmahout.md
----------------------------------------------------------------------
diff --git a/website/oldsite/developers/buildingmahout.md b/website/oldsite/developers/buildingmahout.md
deleted file mode 100644
index 8e1e7f0..0000000
--- a/website/oldsite/developers/buildingmahout.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-layout: default
-title: BuildingMahout
-theme:
-    name: retro-mahout
----
-
-# Building Mahout from source
-
-## Prerequisites
-
-* Java JDK 1.7
-* Apache Maven 3.3.3
-
-
-## Getting the source code
-
-Checkout the sources from the [Mahout GitHub repository](https://github.com/apache/mahout)
-either via
- 
-    git clone git@github.com:apache/mahout.git
-or
- 
-    git clone https://github.com/apache/mahout.git
-
-##Hadoop version
-Mahout code depends on hadoop-client artifact, with the default version 2.4.1. To build Mahout against to a
-different hadoop version, hadoop.version property should be set accordingly and passed to the build command.
-Hadoop1 clients would additionally require hadoop1 profile to be activated.
-
-The build lifecycle is illustrated below. 
-
-## Compiling
-
-Compile Mahout using standard maven commands
-
-    # With hadoop-2.4.1 dependency
-    mvn clean compile
-
-    # With hadoop-1.2.1 dependency
-    mvn -Phadoop1 -Dhadoop.version=1.2.1 clean compile
-
-##Packaging
-
-Mahout has an extensive test suite which takes some time to run. If you just want to build Mahout, skip the tests like this
-
-    # With hadoop-2.4.1 dependency
-    mvn -DskipTests=true clean package
-
-    # With hadoop-1.2.1 dependency
-    mvn -Phadoop1 -Dhadoop.version=1.2.1 -DskipTests=true clean package
-
-
-In order to add mahout artifact to your local repository, run
-
-    # With hadoop-2.4.1 dependency
-    mvn clean install
-
-    # With hadoop-1.2.1 dependency
-    mvn -Phadoop1 -Dhadoop.version=1.2.1 clean install
-
- 
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/mahout/blob/978d4467/website/oldsite/developers/developer-resources.md
----------------------------------------------------------------------
diff --git a/website/oldsite/developers/developer-resources.md b/website/oldsite/developers/developer-resources.md
deleted file mode 100644
index 01de4e5..0000000
--- a/website/oldsite/developers/developer-resources.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-layout: default
-title: Developer Resources
-theme:
-    name: retro-mahout
----
-
-<a name="DeveloperResources-MakingaContribution"></a>
-## Making a Contribution
-
-Mahout is always looking for contributions, especially in the areas of
-documentation. See our [How to contribute](/developers/how-to-contribute.html) page for details.
-
-
-<a name="DeveloperResources-SourceCode"></a>
-## Source Code
-
-The source files are stored using Git, our page on [version control](/developers/version-control.html) has details on how to access the sourcecode.
-
-
-<a name="DeveloperResources-Documentation"></a>
-## Documentation
-
-Javadoc and Scaladoc documentation is available online by module:
-
- * [Mahout Math](http://apache.github.io/mahout/0.10.1/docs/mahout-math/index.html)
- * [Mahout Math Scala bindings](http://apache.github.io/mahout/0.10.1/docs/mahout-math-scala/index.html)
- * [Mahout Spark bindings](http://apache.github.io/mahout/0.10.1/docs/mahout-spark/index.html)
- * [Mahout Spark bindings shell](http://apache.github.io/mahout/0.10.1/docs/mahout-spark-shell/index.html)
- * [Mahout H2O backend Scaladoc](http://apache.github.io/mahout/0.10.1/docs/mahout-h2o/scaladocs/index.html)
- * [Mahout H2O backend Javadoc](http://apache.github.io/mahout/0.10.1/docs/mahout-h2o/javadoc/index.html)
- * [Mahout HDFS](http://apache.github.io/mahout/0.10.1/docs/mahout-hdfs/index.html)
- * [Mahout Map-Reduce](http://apache.github.io/mahout/0.10.1/docs/mahout-mr/index.html)
- * [Mahout Examples](http://apache.github.io/mahout/0.10.1/docs/mahout-examples/index.html)
- * [Mahout Integration](http://apache.github.io/mahout/0.10.1/docs/mahout-integration/index.html)
-
-
-<a name="DeveloperResources-Issues"></a>
-## Issues
-
-All bugs, improvements, [pull requests](http://mahout.apache.org/developers/github.html), etc. should be logged in our [issue tracker](/developers/issue-tracker.html).
-
-<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.
-
-## Board reports
-
-Every three months Mahout submits a report to the Apache board. All of the drafts that get sent are checked into svn. See here:
-
-<a href="https://svn.apache.org/repos/asf/mahout/pmc/board-reports/">https://svn.apache.org/repos/asf/mahout/pmc/board-reports/</a>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/mahout/blob/978d4467/website/oldsite/developers/github.md
----------------------------------------------------------------------
diff --git a/website/oldsite/developers/github.md b/website/oldsite/developers/github.md
deleted file mode 100644
index 61a373d..0000000
--- a/website/oldsite/developers/github.md
+++ /dev/null
@@ -1,157 +0,0 @@
----
-layout: default
-title:
-theme:
-    name: retro-mahout
----
-
-# 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 be 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

http://git-wip-us.apache.org/repos/asf/mahout/blob/978d4467/website/oldsite/developers/githubPRs.md
----------------------------------------------------------------------
diff --git a/website/oldsite/developers/githubPRs.md b/website/oldsite/developers/githubPRs.md
deleted file mode 100644
index 3186c59..0000000
--- a/website/oldsite/developers/githubPRs.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-layout: default
-title:
-theme:
-    name: retro-mahout
----
-# Handling Github PRs #
-
-----------
-
-
-## how to create a PR (for contributers)
-
-Read [[1]]. 
-
-Pull requests are made to apache/mahout repository on Github. 
-
-## merging a PR and closing it (for committers). 
-
-Remember that pull requests are equivalent to a remote 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 contributer's commits. In order to do that, as well as close the PR at the 
-same time, it is recommended to use **squash commits**.
-
-Read [[2]] (merging locally). Merging pull requests are equivalent to merging 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 
-
-
-In this example we assume that contributor Github handle is "cuser" and the PR branch name is "cbranch" there. We also 
-assume that *apache* remote is configured as 
-
-    apache  https://git-wip-us.apache.org/repos/asf/mahout.git (fetch)
-    apache  https://git-wip-us.apache.org/repos/asf/mahout.git (push)
-
-
-Squash pull ensures all PR history is squashed into single commit. Also, it is not yet committed, even if 
-fast forward is possible, so you get chance to change things before committing.
-
-At this point resolve conflicts, if any, or ask contributor to rebase on top of master, if PR went out of sync.
-
-Also run regular patch checks and change CHANGELOG.
-
-Suppose everything is fine, you now can commit the squashed request 
-
-    git commit -a
-
-edit message to contain "MAHOUT-YYYY description **closes #ZZ**", where ZZ is the pull request number. 
-Including "closes #ZZ" will close PR automatically. More information [[3]].
-
-   push apache master
-
-(this will require credentials).
-
-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 
-
-When we want to reject a PR (close without committing), just do the following commit on master's HEAD 
-*without merging the PR*: 
-
-    git commit --allow-empty -m "closes #ZZ *Won't fix*"
-    git push apache master
-
-that should close PR without merging and any code modifications in the master repository.
-
-## Apache/github integration features 
-
-Read [[4]]. Issue handles mentioned in comments and PR name should post to mailing lists and Jira.
-
-
-[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

http://git-wip-us.apache.org/repos/asf/mahout/blob/978d4467/website/oldsite/developers/gsoc.md
----------------------------------------------------------------------
diff --git a/website/oldsite/developers/gsoc.md b/website/oldsite/developers/gsoc.md
deleted file mode 100644
index 1005724..0000000
--- a/website/oldsite/developers/gsoc.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-layout: default
-title: GSOC
-theme:
-    name: retro-mahout
----
-
-# Google Summer of Code
-
-Mahout has been mentoring students in Google Summer of Code (GSoC) 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 fun, a great career builder and can open up many
-opportunities for you.
-
-## 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.
-
-
-## 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
-
- * [GSoC Home](http://code.google.com/soc/) - official GSoC page
- * [GSoC FAQ](http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs) - official FAQ
- * [Apache GSoC coordination](http://community.apache.org/gsoc.html) - official Apache GSoC documentation, especially important  if you want to become a mentor
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/mahout/blob/978d4467/website/oldsite/developers/how-to-become-a-committer.md
----------------------------------------------------------------------
diff --git a/website/oldsite/developers/how-to-become-a-committer.md b/website/oldsite/developers/how-to-become-a-committer.md
deleted file mode 100644
index 37e683f..0000000
--- a/website/oldsite/developers/how-to-become-a-committer.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-layout: default
-title: How To Become A Committer
-theme:
-    name: retro-mahout
----
-
-# 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/978d4467/website/oldsite/developers/how-to-contribute.md
----------------------------------------------------------------------
diff --git a/website/oldsite/developers/how-to-contribute.md b/website/oldsite/developers/how-to-contribute.md
deleted file mode 100644
index 9b70124..0000000
--- a/website/oldsite/developers/how-to-contribute.md
+++ /dev/null
@@ -1,154 +0,0 @@
----
-layout: default
-title: How To Contribute
-theme:
-    name: retro-mahout
----
-
-# 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!
-
-<a name="HowToContribute-BeInvolved"></a>
-## Get Involved
-
-Discussions at Apache happen on the mailing list. To get involved, you should join the [Mahout mailing lists](/general/mailing-lists,-irc-and-archives.html).  In particular:
-
-* The **user list** (to help others)
-* The **development list** (to join discussions of changes)  -- This is the best place
-to understand where the project is headed.
-* The **commit list** (to see changes as they are made)
-
-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)
-.  Apache  has a number of [email tips for contributors][1] as well.
-
-<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: documentation, performance improvements, better tests, etc.
-The best place to start is by looking into our [issue tracker](https://issues.apache.org/jira/browse/MAHOUT) 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 this website. Feel free 
-to contribute texts and tutorials! Committers will make sure they are added 
-to this website, and we have a [guide for making website updates][2].
-We also have a [wide variety of books and slides][3] for learning more about 
-machine learning algorithms. 
-
-If you are interested in working towards being a committer, [general guidelines are available online](/developers/how-to-become-a-committer.html).
-
-<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": 
-
-*A half-baked patch in Jira, with no documentation, no tests and no backwards compatibility is better than no patch at all.*
-
-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 to get the [Mahout source code](/developers/version-control.html). Most development is done on the "trunk".  Mahout mirrors its codebase on [GitHub](https://github.com/apache/mahout). The first step to making a contribution is to fork Mahout's master branch to your GitHub repository.  
-
-
-<a name="HowToContribute-MakingChanges"></a>
-## Making Changes
-
-Before you start, you should send a message to the [Mahout developer mailing list](/general/mailing-lists,-irc-and-archives.html)
-(note: you have to subscribe before you can post), or file a ticket in  our [issue tracker](/developers/issue-tracker.html).
-Describe your proposed changes and check that they fit in with what others are doing and have planned for the project.  Be patient, it may take folks a while to understand your requirements.
-
- 1. Create a JIRA Issue (if one does not already exist or you haven't already) 
- 2. Pull the code from your GitHub repository 
- 3. Ensure that you are working with the latest code from the [apache/mahout](https://github.com/apache/mahout) master branch.
- 3. Modify the source code and add some (very) nice features. 
-     - Be sure to adhere to the following points:
-         - All public classes and methods should have informative Javadoc
-    comments.  
-         - Code should be formatted according to standard
-    [Java coding conventions](http://www.oracle.com/technetwork/java/codeconventions-150003.pdf),
-    with two exceptions:
-             - indent two spaces per level, not four.  
-             - lines can be 120 characters, not 80.  
-         - Contributions should pass existing unit tests. 
-         - New unit tests should be provided to demonstrate bugs and fixes.
- 4. Commit the changes to your local repository. 
- 4. Push the code back up to your GitHub repository.
- 5. Create a [Pull Request](https://help.github.com/articles/creating-a-pull-request) to the to apache/mahout repository on Github.
-     - Include the corresponding JIRA Issue number and description in the title of the pull request: 
-        - ie. MAHOUT-xxxx: < JIRA-Issue-Description >
- 6. Committers and other members of the Mahout community can then comment on the Pull Request.  Be sure to watch for comments, respond and make any necessary changes.
-
-Please be patient. Committers are busy people too. If no one responds to your Pull Request after a few days, please make friendly reminders on the mailing list.  Please
-incorporate other's suggestions into into your changes if you think they're reasonable.  Finally, remember that even changes that are not committed are useful to the community.
-
-<a name="HowToContribute-UnitTests"></a>
-#### Unit Tests
-
-Please make sure that all unit tests succeed before creating your Pull Request.
-
-Run *mvn clean test*, if you see *BUILD SUCCESSFUL* after the tests have finished, all is ok, but if you see *BUILD FAILED*, 
-please carefully read the errors messages and check your code.
-
-#### Do's and Don'ts
-
-Please do not:
-
-* reformat code unrelated to the bug being fixed: formatting changes should
-be done in separate issues.
-* 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, the website, etc.)
-
-
-<a name="HowToContribute-Review/ImproveExistingPatches"></a>
-## Review/Improve Existing Pull Requests
-
-If there's a JIRA issue that already has a Pull Request with changes that you think are 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 on your GitHub branch and add a comment about them.	If a lot of people review a Pull Request and give it a
-thumbs up, that's a good sign for committers when deciding if it's worth spending time to review it -- and if other people have already put in
-effort to improve the docs/tests for an issue, that helps even more.
-
-For more information see [Handling GitHub PRs](http://mahout.apache.org/developers/github.html).
-
-
-  [1]: http://www.apache.org/dev/contrib-email-tips
-  [2]: http://mahout.apache.org/developers/how-to-update-the-website.html
-  [3]: http://mahout.apache.org/general/books-tutorials-and-talks.html
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/mahout/blob/978d4467/website/oldsite/developers/how-to-release.md
----------------------------------------------------------------------
diff --git a/website/oldsite/developers/how-to-release.md b/website/oldsite/developers/how-to-release.md
deleted file mode 100644
index 30cc13d..0000000
--- a/website/oldsite/developers/how-to-release.md
+++ /dev/null
@@ -1,235 +0,0 @@
----
-layout: default
-title: How To Release
-theme:
-    name: retro-mahout
----
-
-# 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 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/978d4467/website/oldsite/developers/how-to-update-the-website.md
----------------------------------------------------------------------
diff --git a/website/oldsite/developers/how-to-update-the-website.md b/website/oldsite/developers/how-to-update-the-website.md
deleted file mode 100644
index 2aea3ec..0000000
--- a/website/oldsite/developers/how-to-update-the-website.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-layout: default
-title: How To Update The Website
-theme:
-    name: retro-mahout
----
-
-# How to update the Mahout Website
-
-<a name="HowToUpdateTheWebsite-Howtoupdatethemahouthomepage"></a>
-## How to update the mahout home page
-1. If you are not a committer of Apache Mahout, please open a ticket in our [issue tracker](/developers/issue-tracker.html) and attach a text describing the changes/additions you want to  contribute
-1. If you are a committer:
-    1. Make sure you have the [Apache CMS bookmarklet](https://cms.apache.org/#bookmark) installed.
-    1. For all else refer to the [Apache CMS reference docs](http://www.apache.org/dev/cmsref.html).
-
-<a name="HowToUpdateTheWebsite-SomeDo'sandDont'sofupdatingthewiki"></a>
-## Some Do's and Dont's of updating the web site
-1. Keep all pages cleanly formatted - this includes using standard formatting for headers etc.
-1. Try to keep a single page for a topic instead of starting multiple ones.
-If the topics are related, put it under as a child under the similar page.
-1. Notify the developers of orphaned or broken links.

http://git-wip-us.apache.org/repos/asf/mahout/blob/978d4467/website/oldsite/developers/issue-tracker.md
----------------------------------------------------------------------
diff --git a/website/oldsite/developers/issue-tracker.md b/website/oldsite/developers/issue-tracker.md
deleted file mode 100644
index c16f7c8..0000000
--- a/website/oldsite/developers/issue-tracker.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-layout: default
-title: Issue Tracker
-theme:
-    name: retro-mahout
----
-
-# Issue tracker
-
-
-Mahout's issue tracker is located [here](http://issues.apache.org/jira/browse/MAHOUT).
-For most changes (apart from trivial stuff) Mahout works according to a review-then-commit model.
-This means anything that is to be added is first presented as a patch in the issue tracker. All conversations in the issue tracker are automatically
-echoed on the developer mailing list and people tend to respond or continue
-conversations there rather in the issue tracker, so in order to follow an
-issue you also have to read to the <a href="http://mahout.apache.org/general/mailing-lists,-irc-and-archives.html">mailing lists</a>. 
-
-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 uses [JIRA](https://confluence.atlassian.com/display/JIRA/JIRA+Documentation) by Atlassian.
-
-<a name="IssueTracker-Bestpractise"></a>
-#### Best practices
-
-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
-preferred that the subject of an issue is discussed on one of our mailing
-lists before an issue is created - in particular when it comes to adding new functionality.
-
-Quote only what it is you are responding to in comments.
-
-Patches should be created at trunk or trunk parent level and if possible be
-a single uncompressed text file so it is easy to inspect the patch in a web
-browser. (See [Patch Check List](/developers/patch-check-list.html)
-.)
-
-Use the issue identity when referring to an issue in any discussion.
-"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.
-
-A note to committers: Make sure to mention the issue id in each commit. Not only has
-JIRA the capability of auto-linking commits to the issue they are related to
-that way, it also makes it easier to get further information for a specific commit
-when browsing through the commit log and within the commit mailing list.

http://git-wip-us.apache.org/repos/asf/mahout/blob/978d4467/website/oldsite/developers/patch-check-list.md
----------------------------------------------------------------------
diff --git a/website/oldsite/developers/patch-check-list.md b/website/oldsite/developers/patch-check-list.md
deleted file mode 100644
index 0e77064..0000000
--- a/website/oldsite/developers/patch-check-list.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: default
-title: Patch Check List
-theme:
-    name: retro-mahout
----
-
-# Patch Check List
-
-So, you want to merge a contribution- or you want to know in more detail what committers look for in your contribution?
-Here are tips, traps, etc. for dealing with
-PRs:
-
-  - Did the author write unit tests?  Are the unit tests worthwhile?
-  - Are the licenses correct on newly added files? Has an ASF license been
-granted?
-  - Make sure you update JIRA by assigning the issue to you so that others
-know you are working on it.
-  - How is the documentation, especially the javadocs?
-  - Before committing, make sure you add any new documents to your local Git repo.  
-  - Run all unit tests, verify that all tests pass.
-  - Lastly, update the [CHANGELOG](https://github.com/apache/mahout/blob/master/CHANGELOG) file. Give proper credit to the authors.
- 
-After the above steps are verified and completed, and the contribution is ready to merge, follow the steps in the "Merging a PR" section in: [Handling Github PRs](http://mahout.apache.org/developers/github.html).
-
- - Remember to update the issue status in JIRA when you have completed it.
-
-
-  
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/mahout/blob/978d4467/website/oldsite/developers/thirdparty-dependencies.md
----------------------------------------------------------------------
diff --git a/website/oldsite/developers/thirdparty-dependencies.md b/website/oldsite/developers/thirdparty-dependencies.md
deleted file mode 100644
index 04511d4..0000000
--- a/website/oldsite/developers/thirdparty-dependencies.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-layout: default
-title: Thirdparty Dependencies
-theme:
-    name: retro-mahout
----
-
-# Adding Thirdparty Dependencies in Maven
-
-If you have a dependency on a third party artifact that is not in Maven,
-you should:
-
-
-* 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.
-* 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.
-* 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*
-
-* Once it is deployed, go into [http://repository.apache.org/](http://repository.apache.org/) by using your SVN
-credentials to login in
-* Select Staging
-* Find your repository artifacts
-* Close them (this makes them publicly available, since you are closing the
-staging repo)
-* Promote them. This adds them to the public Maven repo.

http://git-wip-us.apache.org/repos/asf/mahout/blob/978d4467/website/oldsite/developers/version-control.md
----------------------------------------------------------------------
diff --git a/website/oldsite/developers/version-control.md b/website/oldsite/developers/version-control.md
deleted file mode 100644
index 809ca6b..0000000
--- a/website/oldsite/developers/version-control.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-layout: default
-title: Version Control
-theme:
-    name: retro-mahout
----
-
-# Version control access
-
-The Mahout source is mirrored in the **[Apache Mahout GitHub](https://github.com/apache/mahout)** repository.
-  
-<a name="VersionControl-WebAccess(read-only)"></a>
-## Web Access (read-only)
-
-The source code can be browsed via the Web at [https://github.com/apache/mahout](https://github.com/apache/mahout). 
-
-<a name="VersionControl-AnonymousAccess(read-only)"></a>
-## Anonymous Access (read-only)
-
-The Git URL for anonymous users is [https://github.com/apache/mahout.git](https://github.com/apache/mahout.git).
-
-<a name="VersionControl-CommitterAccess(read-write)"></a>
-## Committer Access (read-write)
-
-The Git URL for committers is [https://git-wip-us.apache.org/repos/asf/mahout.git](https://git-wip-us.apache.org/repos/asf/mahout.git).
-
-## Mahout Website 
-The Mahout website resides in the [Apache SVN repository](https://svn.apache.org/viewvc/mahout/site).
-
-The SVN URL for the Mahout site is: [https://svn.apache.org/repos/asf/mahout/site](https://svn.apache.org/repos/asf/mahout/site).
-
-The Mahout website can be edited via the [ASF CMS Editor](http://www.apache.org/dev/cms.html) or by checking out the source locally from SVN.  A handy tool for publising the website locally while editing is available [here](https://gist.github.com/tuxdna/11223434). 
-
-
-<a name="VersionControl-Issues"></a>
-## Issues
-
-All bugs, improvements, [pull requests](http://mahout.apache.org/developers/github.html), etc. should be logged in our [issue tracker](https://mahout.apache.org/developers/issue-tracker.html).
\ No newline at end of file


Mime
View raw message