Author: buildbot
Date: Tue Dec 8 13:17:43 2015
New Revision: 974962
Log:
Staging update by buildbot for olingo
Added:
websites/staging/olingo/trunk/content/contribute.html
Modified:
websites/staging/olingo/trunk/content/ (props changed)
websites/staging/olingo/trunk/content/sitemap.html
Propchange: websites/staging/olingo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Dec 8 13:17:43 2015
@@ -1 +1 @@
-1714918
+1718587
Added: websites/staging/olingo/trunk/content/contribute.html
==============================================================================
--- websites/staging/olingo/trunk/content/contribute.html (added)
+++ websites/staging/olingo/trunk/content/contribute.html Tue Dec 8 13:17:43
2015
@@ -0,0 +1,191 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html lang="en">
+ <head>
+ <meta http-equiv="content-type" content="text/html; charset=utf-8">
+ <meta http-equiv="X-UA-Compatible" content="IE=edge">
+ <meta name="viewport" content="width=device-width, initial-scale=1">
+ <meta name="description" content="Apache Olingo provides libraries which
enable developers to implement OData producers and OData consumers. The
available OData Java library implements OData version 2.0. In future on goal is
to provide an OData 4.0 compliant library once the OData standard is published
at OASIS. The focus within the community is currently on the Java technology
but it is up to the community to discuss if other environments find interest.">
+ <meta name="author" content="">
+ <link rel="icon" href="/favicon.ico">
+ <title>
+ Apache Olingo Library
+ </title><!-- Bootstrap core CSS -->
+ <link href="/css/bootstrap.css" rel="stylesheet" type="text/css"><!--
Custom styles for this template -->
+ <link href="/css/navbar.css" rel="stylesheet" type="text/css"><!-- Just
for debugging purposes. Don't actually copy these 2 lines! -->
+ <link href="/css/offcanvas.css" rel="stylesheet" type="text/css"><!--
Custom styles for this template -->
+ <link rel="stylesheet" href="/css/main.css">
+ <!--[if lt IE 9]><script
src="/js/ie8-responsive-file-warning.js"></script><![endif]-->
+
+ <script src="/js/ie-emulation-modes-warning.js" type="text/javascript">
+</script><!-- IE10 viewport hack for Surface/desktop Windows 8 bug -->
+
+ <script src="/js/ie10-viewport-bug-workaround.js" type="text/javascript">
+</script><!-- HTML5 shim and Respond.js IE8 support of HTML5 elements and
media queries -->
+ <!--[if lt IE 9]>
+ <script src="/js/html5shiv.min.js"></script>
+ <script src="/js/respond.min.js"></script>
+ <![endif]-->
+ </head>
+
+ <body>
+ <div class="container">
+ <!-- Static navbar -->
+ <div class="navbar navbar-default" role="navigation">
+ <div class="container-fluid">
+ <div class="navbar-header">
+ <button type="button" class="navbar-toggle" data-toggle="collapse"
data-target=".navbar-collapse">
+ <span class="sr-only">Toggle navigation</span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ </button>
+ <img class="navbar-brand" src="/img/OlingoOrangeTM.png"
style="width:62px;" >
+ <a class="navbar-brand" href="#">Apache Olingoâ¢</a>
+ </div>
+ <div class="navbar-collapse collapse">
+ <ul class="nav navbar-nav">
+
+ <li><a href="/">Home</a></li>
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle"
data-toggle="dropdown">ASF <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+ <li><a href="http://www.apache.org/foundation/";>ASF
Home</a></li>
+ <li><a
href="http://projects.apache.org/";>Projects</a></li>
+ <li><a href="http://people.apache.org/";>People</a></li>
+ <li><a
href="http://www.apache.org/foundation/getinvolved.html";>Get Involved</a></li>
+ <li><a
href="http://www.apache.org/dyn/closer.cgi";>Download</a></li>
+ <li><a
href="http://www.apache.org/security/";>Security</a></li>
+ <li><a
href="http://www.apache.org/foundation/sponsorship.html";>Support Apache</a></li>
+ </ul>
+ </li>
+
+ <li><a href="http://www.apache.org/licenses/";>License</a></li>
+
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle"
data-toggle="dropdown">Download <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+ <li><a href="/doc/odata2/download.html">Download OData
2.0 Java</a></li>
+ <li><a href="/doc/odata4/download.html">Download OData
4.0 Java</a></li>
+ <li><a href="/doc/javascript/download.html">Download
OData 4.0 JavaScript</a></li>
+ </ul>
+ </li>
+
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle"
data-toggle="dropdown">Documentation <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+ <li><a href="/doc/odata2/index.html">Documentation OData
2.0 Java</a></li>
+ <li><a href="/doc/odata4/index.html">Documentation OData
4.0 Java</a></li>
+ <li><a href="/doc/javascript/index.html">Documentation
OData 4.0 JavaScript</a></li>
+ </ul>
+ </li>
+ <li><a href="/support.html">Support</a></li>
+
+ </ul>
+
+ <img class="navbar-right" height="50px"
src="/img/asf-logo.gif">
+
+ </div><!--/.nav-collapse -->
+ </div><!--/.container-fluid -->
+ </div><!-- Main component for a primary marketing message or call to
action --><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
+<h1 id="apache-olingo-how-to-contribute">Apache Olingo - How To Contribute<a
class="headerlink" href="#apache-olingo-how-to-contribute" title="Permanent
link">¶</a></h1>
+<h3 id="overview">Overview<a class="headerlink" href="#overview"
title="Permanent link">¶</a></h3>
+<p>If you want to contribute to the Olingo Project, you can submit patches,
report bugs or provide documentation and tutorials. Contributions are managed
in the project <a href="https://issues.apache.org/jira/browse/OLINGO";>JIRA</a>.
So if you found a bug or want to provide a contribution please open a new <a
href="https://issues.apache.org/jira/browse/OLINGO";>JIRA</a> ticket. Detailed
information how to contribute can be found in the following capter.</p>
+<h3 id="contribute-via-git-patchpull-request-and-olingo-jira">Contribute via
Git-Patch/Pull-Request and Olingo-JIRA<a class="headerlink"
href="#contribute-via-git-patchpull-request-and-olingo-jira" title="Permanent
link">¶</a></h3>
+<p>The Olingo uses the following process for contributins:
+1. Reporting a bug or feature
+2. Develop the according bugfix / feature
+3. Prepare your code for contribtion
+4. Submit your JIRA ticket to receive feedback</p>
+<h4 id="clone-the-olingo-project">Clone the Olingo Project<a
class="headerlink" href="#clone-the-olingo-project" title="Permanent
link">¶</a></h4>
+<p>The current development version can be found in the Apache git repository.
Please note that there are two different repositories, one for Version 2 and
one for Version 4 of the OData protocol.</p>
+<p>To clone the current master branch of the Olingo project please use one of
the folling commands:</p>
+<p><strong>OData V2 Code</strong></p>
+<div class="codehilite"><pre><span class="n">git</span> <span
class="n">clone</span> <span class="n">https</span><span
class="p">:</span><span class="o">//</span><span class="n">git</span><span
class="o">-</span><span class="n">wip</span><span class="o">-</span><span
class="n">us</span><span class="p">.</span><span class="n">apache</span><span
class="p">.</span><span class="n">org</span><span class="o">/</span><span
class="n">repos</span><span class="o">/</span><span class="n">asf</span><span
class="o">/</span><span class="n">olingo</span><span class="o">-</span><span
class="n">odata2</span>
+</pre></div>
+
+
+<p><strong>OData V4 code</strong></p>
+<div class="codehilite"><pre><span class="n">git</span> <span
class="n">clone</span> <span class="n">https</span><span
class="p">:</span><span class="o">//</span><span class="n">git</span><span
class="o">-</span><span class="n">wip</span><span class="o">-</span><span
class="n">us</span><span class="p">.</span><span class="n">apache</span><span
class="p">.</span><span class="n">org</span><span class="o">/</span><span
class="n">repos</span><span class="o">/</span><span class="n">asf</span><span
class="o">/</span><span class="n">olingo</span><span class="o">-</span><span
class="n">odata4</span>
+</pre></div>
+
+
+<h4 id="create-an-jira-issue-with-your-bugfeature-request">Create an JIRA
issue with your bug/feature request<a class="headerlink"
href="#create-an-jira-issue-with-your-bugfeature-request" title="Permanent
link">¶</a></h4>
+<p><strong>Reporting a bug</strong>
+If you found a bug, please provide a detailed explaination how the bug can be
reproduced.</p>
+<p>You should meation the following properties:
+ * Version of the libray e.g. Olingo V4 (4.0.0-beta-03)
+ * If a part of the implementation is not compliant to the OData protocol,
please link the the related part of the spefication or provide a link to the
related JIRA issue of OData protcoll. The offical OASIS-OData JIRA can be found
<a href="https://issues.oasis-open.org/browse/ODATA/";>here</a>
+ * Often bugs are related to the underlaying metadata document. Please
append the related part of the metadata document to reproduce the bug.
+ * Provide a code snipped to reproducte the bug.
+ * If you receive an exception, provide the stack trace of the exception.
+ * Append further information in which part of the libray the bug occurs.
(only if available)
+ * If you have fixed a bug, you can append the solution to the request.
Further information how to sent your solution are provided in the following
chapters.</p>
+<p><strong>Bug Priorities</strong>
+The Olingo project uses the following definition of priorities:
+ * Blocker - The bug must be fixed before the next release
+ * Critical - The bug should be resolved immediately and must be fixed
before the next major release.
+ * Major - This bug should be resolved as soon as possible in the normal
course of development activity, before the software is released.
+ * Minor (default) - This bug should be repaired after serious bugs have
been fixed.
+ * Trivial -It can be resolved in a future major system revision or not be
resolved at all.</p>
+<p>The default priority is Minor.</p>
+<h4 id="develop-the-according-bugfix-feature">Develop the according bugfix /
feature<a class="headerlink" href="#develop-the-according-bugfix-feature"
title="Permanent link">¶</a></h4>
+<p><strong>Providing code</strong>
+To provide a bug fix, checkout the current master branch of the project and
develop your solution. In Olingo we truly belive in tests, so your contribution
should at least contain tests that show that your contribution works as
expected and also tests that reproductes the previous reported bug. If you
provide a new feature your tests should reach at least 80 percent
test-coverage.</p>
+<p>To append your contribution to a JIRA ticket, please create a patch file as
explained in the chapter.</p>
+<p><strong>Providing documentation for the Apache website</strong>
+To provide documentaion or tutorials you should write your contribution using
Markdown syntax.</p>
+<h4 id="prepare-your-code-for-contribution">Prepare your code for
contribution<a class="headerlink" href="#prepare-your-code-for-contribution"
title="Permanent link">¶</a></h4>
+<p>To append you contribution to a JIRA issue, please create a <a
href="https://git-scm.com/docs/git-format-patch";>patch file</a>. The commit
message should contain the JIRA request number (e.g. OLINGO-42) and a short
commit message.</p>
+<p><strong>Example - Create a patch file</strong>
+You have done serval commits and want to provide a single commit which
contains all your changes.</p>
+<div class="codehilite"><pre><span class="p">...</span>
+<span class="n">git</span> <span class="n">commit</span> <span
class="o">-</span><span class="n">m</span> "<span class="p">[</span><span
class="n">OLINGO</span><span class="o">-</span>42<span class="p">]</span> <span
class="n">Start</span> <span class="n">development</span> <span
class="n">new</span> <span class="n">feature</span>"
+<span class="n">git</span> <span class="n">commit</span> <span
class="o">-</span><span class="n">m</span> "<span class="p">[</span><span
class="n">OLINGO</span><span class="o">-</span>42<span class="p">]</span> <span
class="n">Added</span> <span class="n">new</span> <span
class="n">tests</span>"
+<span class="n">git</span> <span class="n">commit</span> <span
class="o">-</span><span class="n">m</span> "<span class="p">[</span><span
class="n">OLINGO</span><span class="o">-</span>42<span class="p">]</span> <span
class="n">Typo</span> <span class="n">fixed</span>"
+<span class="p">...</span>
+<span class="n">git</span> <span class="n">rebase</span> <span
class="o">-</span><span class="nb">i</span> <span class="n">HEAD</span><span
class="o">~</span>3
+<span class="n">git</span> <span class="n">format</span><span
class="o">-</span><span class="n">patch</span> <span class="o">-</span>1
+</pre></div>
+
+
+<p>First rebase your local history to create a single commit. Afer that create
a patch file using git format-patch. Now you can upload and append your created
patch file to the JIRA issue.</p>
+<p><strong>Example - Appling a patch file</strong>
+You like to apply a patch file named "OLINGO_42.patch". Use the following
commands:</p>
+<div class="codehilite"><pre><span class="n">git</span> <span
class="n">am</span> <span class="o">--</span><span class="n">signoff</span>
0001<span class="o">-</span><span class="n">Test</span><span
class="p">.</span><span class="n">patch</span>
+</pre></div><div align="center">
+<p>Copyright © 2013-2015, The Apache Software Foundation<br>
+ Apache Olingo, Olingo, Apache,
the Apache feather, and
+ the Apache Olingo project logo are trademarks
of the Apache Software
+ Foundation.</p>
+ <small><a href="/doc/odata2/privacy.html">Privacy</a></small>
+ </div>
+ </div><!-- /container -->
+ <!-- Bootstrap core JavaScript
+ ================================================== -->
+ <!-- Placed at the end of the document so the pages load faster -->
+ <script src="/js/jquery.js" type="text/javascript">
+</script>
+ <script src="/js/bootstrap.js" type="text/javascript">
+ <script src="/js/offcanvas.js" type="text/javascript">
+</script>
+ <!-- Google Analytics: change UA-XXXXX-X to be your site's ID. -->
+ <script>
+ (function(b,o,i,l,e,r){b.GoogleAnalyticsObject=l;b[l]||(b[l]=
+ function(){(b[l].q=b[l].q||[]).push(arguments)});b[l].l=+new Date;
+ e=o.createElement(i);r=o.getElementsByTagName(i)[0];
+ e.src='//www.google-analytics.com/analytics.js';
+ r.parentNode.insertBefore(e,r)}(window,document,'script','ga'));
+ ga('create','UA-44963757-1');ga('send','pageview');
+ </script>
+ </body>
+</html>
Modified: websites/staging/olingo/trunk/content/sitemap.html
==============================================================================
--- websites/staging/olingo/trunk/content/sitemap.html (original)
+++ websites/staging/olingo/trunk/content/sitemap.html Tue Dec 8 13:17:43 2015
@@ -99,6 +99,7 @@
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>
<ul>
<li><a href="/">Apache Olingo</a></li>
+<li><a href="/contribute.html"></a></li>
<li><a href="/documentation.html">Documentation</a></li>
<li><a href="/documentation2.html"></a></li>
<li><a href="/download.html"></a></li>
