Author: buildbot
Date: Wed Sep 30 05:33:31 2015
New Revision: 967270
Log:
Staging update by buildbot for oodt
Modified:
websites/staging/oodt/trunk/content/ (props changed)
websites/staging/oodt/trunk/content/community.html
websites/staging/oodt/trunk/content/development.html
Propchange: websites/staging/oodt/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Sep 30 05:33:31 2015
@@ -1 +1 @@
-1705921
+1705964
Modified: websites/staging/oodt/trunk/content/community.html
==============================================================================
--- websites/staging/oodt/trunk/content/community.html (original)
+++ websites/staging/oodt/trunk/content/community.html Wed Sep 30 05:33:31 2015
@@ -189,18 +189,13 @@ h2:hover > .headerlink, h3:hover > .head
<h3>Community</h3>
<p>Apache OODT has a dedicated community based globally. To keep in contact
they make use of a variety of tools.</p>
-<h4>Mailing Lists</h4>
+<h3>Mailing Lists</h3>
<p>Apache OODT runs a mailing list for general communication and development
chat.
To ask questions about Apache OODT join the [email protected] mailing list
and say hello!</p>
<h4>IRC</h4>
<p>We also have an OODT IRC channel for real time OODT discussion, you can
find this on <a href="http://freenode.net/";>Freenode</a> at <a
href="irc://irc.freenode.net/#oodt">#oodt</a>.</p>
<p>If you don't haven an IRC client installed, you can still join the channel
using the <a href="webchat.freenode.net/?channels=oodt">webchat</a> to stop by
and introduce yourself!
-<h3>Development Tools</h3>
-<h4>Bug tracker</h4>
-<p>To submit bugs, feature requests and other issues to the Apache OODT
project you can use the <a
href="https://issues.apache.org/jira/browse/OODT";>Apache Jira</a>. Sign up and
fill out an issue form,
-from there you can follow the progress from inception to build.</p>
-
<h3>Social Media</h3>
<h4>Twitter</h4>
You can follow us on twitter using the <a
href="http://twitter.com/apache_oodt";>apache_oodt</a> account.
Modified: websites/staging/oodt/trunk/content/development.html
==============================================================================
--- websites/staging/oodt/trunk/content/development.html (original)
+++ websites/staging/oodt/trunk/content/development.html Wed Sep 30 05:33:31
2015
@@ -57,101 +57,141 @@ under the License.
}
h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
<!-- HEADER
-================================================== -->
+ ================================================== -->
<div class="row">
- <div class="four columns">
- <div class="logo">
- <a href="index.html">
- <img src="./oodt-images/oodt_asf_logo.png"
style="height:60px">
- </a>
- </div>
- </div>
- <div class="eight columns noleftmarg">
- <nav id="nav-wrap">
- <ul class="nav-bar sf-menu">
- <li>
- <a href="about.html">About</a>
- </li>
- <li>
- <a href="components.html">Components</a>
- </li>
- <li class="current">
- <a href="download.html">Download</a>
- </li>
- <li>
- <a href="development.html">Development</a>
- </li>
- <li>
- <a href="contact.html">Contact</a>
- </li>
- </ul>
- </nav>
- </div>
+ <div class="four columns">
+ <div class="logo">
+ <a href="index.html">
+ <img src="./oodt-images/oodt_asf_logo.png" style="height:60px">
+ </a>
+ </div>
+ </div>
+ <div class="eight columns noleftmarg">
+ <nav id="nav-wrap">
+ <ul class="nav-bar sf-menu">
+ <li>
+ <a href="about.html">About</a>
+ </li>
+ <li>
+ <a href="components.html">Components</a>
+ </li>
+ <li class="current">
+ <a href="download.html">Download</a>
+ </li>
+ <li>
+ <a href="development.html">Development</a>
+ </li>
+ <li>
+ <a href="contact.html">Contact</a>
+ </li>
+ </ul>
+ </nav>
+ </div>
</div>
-<div class="clear">
-</div>
+<div class="clear"></div>
<!-- SUBHEADER
-================================================== -->
+ ================================================== -->
<div id="subheader">
- <div class="row">
- <div class="twelve columns">
- <h4>Development</h4>
- </div>
- </div>
+ <div class="row">
+ <div class="twelve columns">
+ <h4>Development</h4>
+ </div>
+ </div>
</div>
-<div class="hr">
-</div>
+<div class="hr"></div>
<!-- CONTENT
-================================================== -->
+ ================================================== -->
<div class="row">
- <!-- MAIN CONTENT-->
- <div class="eight columns">
-
-
-
-<div class="subProductWrapper"><div class="subProductHeader"><h3
id="productSubheadSlot">How we keep OODT alive and kicking</h3></div></div><div
class="visualContentWrapper"><div class="contentGradient"></div><div
id="content"><div class="diptych triptychSpace"><div class="visualPadding"
id="leftPlate"><p class="callout">
- Like many open source projects, Apache OODT is continually being
developed and improved upon
- by its devoted team members.
- </p>
- <h4>Build Details</h4><p>
- The majority of the <a href="../components">components</a> of OODT
is written in
- <a href="http://java.sun.com/";>Java</a>, while the <a
href="../components/agility">Agility</a>
- component is written in <a href="http://python.org/";>Python</a>.
Knowledge of both is nice, though.
- </p><p>Each component of the Java build is controlled by <a
href="http://maven.apache.org/";>Maven</a>.
- However, there is also a top-level <a
href="http://maven.apache.org/pom.html";>project object model</a>
- that orchestrates building <em>all</em> of the OODT components.
Maven is not used for the
- Agility component; being Python, it takes advantage of the
traditional Python Distutils
- enhanced by <a href="http://python-distribute.org/";>Distribute</a>.
- </p><h4>Testing</h4><p>
- While we may not fully subscribe to the idea that "untested code
is broken code", we do strive
- to include a lot of automated unit and functional testing. Apache
OODT has its own
- <a href="https://builds.apache.org/job/oodt-trunk/";>Jenkins
continuous integration</a>
- server that runs nightly, and automatically after each commit.
- </p></div><div class="visualClear"></div></div><div
class="triptychRight"><div class="columnBorder"><div class="visualPadding"
id="rightPlate"><div id="sidebar">
- <h4>Developer Details</h4>
- <ul><li><a href="#">Roadmap</a> to future releases</li>
- <li><a
href="http://issues.apache.org/jira/browse/OODT";>Bug</a> and other issue
reports</li>
- <li>
- <a href="source">Source code</a>
- <ul><li><a
href="https://svn.apache.org/repos/asf/oodt";>Subversion Repository</a></li>
- <li><a
href="http://svn.apache.org/viewvc/oodt/";>ViewVC</a> repository viewer</li>
- </ul></li>
- <li><a href="../contact">Mailing lists</a></li>
- <li><a
href="https://cwiki.apache.org/confluence/display/OODT/Home";>Wiki</a></li>
- </ul><h4>Additional Resources</h4>
- <ul><li><a href="../components">Component</a> structure</li>
- <li><a href="https://cwiki.apache.org/OODT/home.html";>OODT
Wiki</a></li>
- </ul></div></div></div></div></div></div><div style="clear:
both;"> </div>
-
-</div>
-
+ <!-- MAIN CONTENT-->
+ <div class="eight columns">
+ <div class="subProductWrapper">
+ <div class="subProductHeader">
+ <h3 id="productSubheadSlot">How we keep OODT alive and kicking</h3>
+ </div>
+ </div>
+ <div class="visualContentWrapper">
+ <div class="contentGradient"></div>
+ <div id="content">
+ <div class="diptych triptychSpace">
+ <div class="visualPadding" id="leftPlate">
+ <p class="callout">
+ Like many open source projects, Apache OODT is continually being
developed and improved upon
+ by its devoted team members.
+ </p>
+ <h4 id="tracker">Issue tracker</h4>
+ <p>To submit bugs, feature requests and other issues to the Apache
OODT project you can use the <a
href="https://issues.apache.org/jira/browse/OODT";>Apache Jira</a>. Sign up and
fill out an issue form,
+ from there you can follow the progress from inception to build.
+ </p>
+ <h4 id="build">Build Details</h4>
+ <p>
+ The majority of the <a href="../components">components</a> of
OODT are written in
+ <a href="http://java.sun.com/";>Java</a>, while the <a
href="../components/agility">Agility</a>
+ component is written in <a href="http://python.org/";>Python</a>.
Knowledge of both is nice, though.
+ </p>
+ <p>
+ Each component of the Java build is controlled by <a
href="http://maven.apache.org/";>Apache Maven</a>.
+ There is however also a top-level <a
href="http://maven.apache.org/pom.html";>project object model</a>
+ that orchestrates building <em>all</em> of the OODT components.
Maven is not used for the
+ Agility component; being Python, it takes advantage of the
traditional Python Distutils
+ enhanced by <a
href="http://python-distribute.org/";>Distribute</a>.
+ </p>
+ <h4 id="testing">Testing</h4>
+ <p>
+ While we may not fully subscribe to the idea that "untested code
is broken code", we do strive
+ to include a lot of automated unit and functional testing.
Apache OODT has its own
+ <a href="https://builds.apache.org/job/oodt-trunk/";>Jenkins
continuous integration</a>
+ server that runs nightly, and automatically after each commit.
+ </p>
+ <h4 id="roadmap">OODT Roadmap</h4>
+ <p>
+ Using the issue tracker we try our best to plan our releases
setting issues for releases
+ based upon community requests and requirements. You can check
out the
+ <a href="http://s.apache.org/Aw9";>Release Roadmap</a> for future
releases.
+ </p>
+ <h4 id="scm">Source Code Management</h4>
+ <p>
+ OODT uses one of Apache Infrastructure's
+ <a href="http://www.apache.org/dev/writable-git";>Writable Git
Repositories</a> for source code management
+ with the OODT repsoitory being located at
<code>https://git-wip-us.apache.org/repos/asf?p=oodt.git</code>
+ </p>
+ <p>
+ As a <b>User</b>, you will most likely want to work with the
+ <a href="https://github.com/apache/oodt";>Github mirror</a> as it
is typically easier
+ to submit patches whilst keeping up with development. It should
be noted that the Github mirror is NOT
+ the canonical source code for Apache OODT. The canonical code
resides at the Writable Git Repository as
+ mentioned above. If you are working with the Github Mirror you
will most likely want to follow the Workflow
+ as described within the <a
href="https://github.com/apache/oodt/blob/master/README.md";>README</a>.
+ </p>
+ <p>
+ On the other hand, if you are an <b>OODT Developer</b> actively
developing the codebase then you will
+ be most frequently interacting with the Writable Git Repository.
The following explains how you can migrate from the old SVN repository to the
Git repository.
+ </p>
+ <p>
+ Say for example you are currently in <code>$OODT_HOME</code>,
you can migrate as follows:
+ </p>
+ <ol>
+ <li><code>git init</code></li>
+ <li><code>git remote add origin
https://git-wip-us.apache.org/repos/asf/oodt.git</code></li>
+ <li><code>git fetch</code></li>
+ </ol>
+ <p>
+ The above will prepare your repository and enable you to sync
with the live development code maintained
+ within the Writable Git Repository. If you have any questions
and/or queries then please reach out to us on the <a
href="http://oodt.apache.org/contact.html";>mailing lists</a>
+ </p>
+ </div>
+ <div class="visualClear"></div>
+ </div>
+ </div>
+ </div>
+ <div style="clear: both;"> </div>
+ </div>
</div>
