camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r935763 - in /websites/production/camel/content: cache/main.pageCache contributing.html
Date Sun, 11 Jan 2015 01:18:20 GMT
Author: buildbot
Date: Sun Jan 11 01:18:20 2015
New Revision: 935763

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/contributing.html

Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/camel/content/contributing.html
==============================================================================
--- websites/production/camel/content/contributing.html (original)
+++ websites/production/camel/content/contributing.html Sun Jan 11 01:18:20 2015
@@ -106,7 +106,7 @@ mvn eclipse:eclipse
 ]]></script>
 </div></div><h2 id="Contributing-Submittingpatches">Submitting patches</h2><p>The
easiest way to submit a patch is to</p><ul><li><a shape="rect" class="external-link"
href="https://issues.apache.org/jira/browse/CAMEL">create a new JIRA issue</a> (you
will need to register),</li><li>attach the patch or tarball as an attachment</li><li><strong>tick
the Patch Attached</strong> button on the issue</li></ul><p>We prefer
patches has unit tests as well and that these unit tests have proper assertions as well, so
remember to replace your system.out or logging with an assertion instead!</p><h2
id="Contributing-WorkingwithGit">Working with Git</h2><p>There are several
ways how Git users could improve Camel with their prefered tool:</p><ul><li>Apache
Git Mirror</li><li>Pull request at Github</li></ul><h3 id="Contributing-ApacheGitMirror">Apache
Git Mirror</h3><p>Cloning the Apache git repo.</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[git
clone https://git-wip-us.apache.org/repos/asf/camel.git]]></script>
-</div></div><p>Bringing your modifications back to Apache is the <a
shape="rect" class="external-link" href="https://git-wip-us.apache.org/docs/workflow.html">same
workflow as described before</a>.</p><h3 id="Contributing-PullrequestatGithub">Pull
request at Github</h3><p>There is also a Git <a shape="rect" class="external-link"
href="https://github.com/apache/camel" rel="nofollow">repository at Github</a> which
you could fork. Then you submit patches as any other github project - eg work on a new feature
branch and send a pull request. One of the committers then needs to accept your pull request
to bring the code &#160;to the ASF codebase. After the code has been included into the
ASF codebase, you need to close the pull request because we can't do that...</p><h3
id="Contributing-Moreresources">More resources</h3><p>Git is not a brand new
technology and therefore Camel is not the only ASF project thinking about using it. So here
are some more resources you mind find useful:</p><ul>
 <li><a shape="rect" class="external-link" href="http://wiki.apache.org/general/GitAtApache">http://wiki.apache.org/general/GitAtApache</a>:
Some basic notes about git@asf</li><li><a shape="rect" class="external-link"
href="http://git.apache.org/">http://git.apache.org/</a>: List of mgit-mirrors at
ASF</li><li><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/">https://git-wip-us.apache.org/</a>:
More Git infos from Apache</li></ul><h2 id="Contributing-Becomingacommitter">Becoming
a committer</h2><p>Once you've got involved as above, we may well invite you to
be a committer. See <a shape="rect" href="how-do-i-become-a-committer.html">How do I
become a committer</a> for more details.</p><h2 id="Contributing-Usingtheissuetracker">Using
the issue tracker</h2><p>Before you can raise an issue in the <a shape="rect"
class="external-link" href="http://issues.apache.org/activemq/browse/CAMEL">issue tracker</a>
you need to register with it. This is quick &amp; painless
 .</p><p>If you want to have a go at fixing an issue you need to be in the list
of activemq-developers on the issue tracker. To join the group, please mail the <code>dev@camel.apache.org</code>
mail list with the email address you used to register with the issue tracker and we'll add
you to the group.</p><h2 id="Contributing-Becommingacommitter">Becomming a committer</h2><p>The
first step is contributing to the project; if you want to take that a step forward and become
a fellow committer on the project then see the <a shape="rect" class="external-link" href="http://activemq.apache.org/becoming-a-committer.html">Committer
Guide</a></p></div>
+</div></div><p>Bringing your modifications back to Apache is the <a
shape="rect" class="external-link" href="https://git-wip-us.apache.org/docs/workflow.html">same
workflow as described before</a>.</p><h3 id="Contributing-PullrequestatGithub">Pull
request at Github</h3><p>There is also a Git <a shape="rect" class="external-link"
href="https://github.com/apache/camel" rel="nofollow">repository at Github</a> which
you could fork. Then you submit patches as any other github project - eg work on a new feature
branch and send a pull request. One of the committers then needs to accept your pull request
to bring the code &#160;to the ASF codebase. After the code has been included into the
ASF codebase, you need to close the pull request because we can't do that...</p><h3
id="Contributing-Moreresources">More resources</h3><p>Git is not a brand new
technology and therefore Camel is not the only ASF project thinking about using it. So here
are some more resources you mind find useful:</p><ul>
 <li><a shape="rect" class="external-link" href="http://wiki.apache.org/general/GitAtApache">http://wiki.apache.org/general/GitAtApache</a>:
Some basic notes about git@asf</li><li><a shape="rect" class="external-link"
href="http://git.apache.org/">http://git.apache.org/</a>: List of mgit-mirrors at
ASF</li><li><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/">https://git-wip-us.apache.org/</a>:
More Git infos from Apache</li></ul><h2 id="Contributing-Becomingacommitter">Becoming
a committer</h2><p>Once you've got involved as above, we may well invite you to
be a committer. See <a shape="rect" href="how-do-i-become-a-committer.html">How do I
become a committer</a> for more details.</p><h2 id="Contributing-Usingtheissuetracker">Using
the issue tracker</h2><p>Before you can raise an issue in the <a shape="rect"
class="external-link" href="http://issues.apache.org/activemq/browse/CAMEL">issue tracker</a>
you need to register with it. This is quick &amp; painless
 .</p><p>If you want to have a go at fixing an issue you need to be in the list
of camel-developers on the issue tracker. To join the group, please mail the <code>dev@camel.apache.org</code>
mail list with the email address you used to register with the issue tracker and we'll add
you to the group.</p><h2 id="Contributing-Becommingacommitter">Becomming a committer</h2><p>The
first step is contributing to the project; if you want to take that a step forward and become
a fellow committer on the project then see the <a shape="rect" class="external-link" href="http://activemq.apache.org/becoming-a-committer.html">Committer
Guide</a></p></div>
         </td>
         <td valign="top">
           <div class="navigation">



Mime
View raw message