svn commit: r1415266 - /servicemix/site/production/community/contributing.html

[ge...@apache.org]

Author: gertv
Date: Thu Nov 29 16:49:20 2012
New Revision: 1415266

URL: http://svn.apache.org/viewvc?rev=1415266&view=rev
Log:
Updating main website contents

Modified:
    servicemix/site/production/community/contributing.html

Modified: servicemix/site/production/community/contributing.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/community/contributing.html?rev=1415266&r1=1415265&r2=1415266&view=diff
==============================================================================
--- servicemix/site/production/community/contributing.html (original)
+++ servicemix/site/production/community/contributing.html Thu Nov 29 16:49:20 2012
@@ -98,7 +98,7 @@
               </td>
               <td height="100%" width="100%">
                 <div class="wiki-content">
-<h1 id="AnyoneCanContribute">Anyone Can Contribute! </h1><p>There are many ways you can help make ServiceMix a better piece of software - please dive in and help!</p><p>Surf the documentation - if somethings confusing or not clear, let us know or even edit it yourself. All you need to do is <a href="http://cwiki.apache.org/confluence/signup.action">register for a wiki account</a> and you can begin contributing your own docs, fixing docs, updating docs, etc. </p><p>Download the code, try it out, and see what you think. Browse the source code. Got an itch to scratch, want to tune some operation or add some feature? Anyone can dive right in. </p><p>Want to do some hacking on ServiceMix? Try surfing the our <a href="http://issues.apache.org/activemq/browse/SM">issue tracker</a> for open issues or features that need to be implemented, take ownership of an issue and try to fix it.</p><p>If you'd rather have a more gentle introduction to working on the ServiceMix project, look at t
 he <a href="http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-core/src/test/java/org/apache/servicemix/">unit tests cases</a> and help us to improve our test coverage.</p><h2 id="ApacheCommitters">Apache Committers</h2><p>Apache committers are allowed write access to the <a href="https://svn.apache.org/repos/asf/servicemix/sandbox">ServiceMix sandbox</a>.  This makes it easy to collaborate with us on components or integration efforts with other Apache projects.  Simply create a directory with your Apache userid and branch the code you want to work on.  Create a Jira issue with a description of the work and use this Jira ID in the comments for your commits.  The work history will now appear in the Fisheye and Subversion Commits tabs of the Jira issue.</p><h2 id="GettingInTouch">Getting In Touch</h2><p>There are various ways of communicating with the ServiceMix community.</p><ul style="list-style: square"><li>visit the <a href="http://www.nabble.com/Service
 Mix---User-f12050.html">Discussion Forum</a></li><li>subscribe to the <a href="mailing-lists.html">Mailing Lists</a> and take part in any conversations</li><li>pop by on <a href="irc://irc.codehaus.org/servicemix">IRC</a> and say hi</li><li>add some comments to the <a href="../site/navigation.html">wiki</a>(requires a log in)</li><li>if you use ServiceMix please tell us about it on our <a href="users.html">Users page</a></li></ul><h2 id="IfYouFindaBugorProblem">If You Find a Bug or Problem</h2><p>Please create a new issue in the <a href="http://issues.apache.org/activemq/browse/SM">JIRA issue tracker</a></p><h3 id="CreatingaJIRAIssue">Creating a JIRA Issue </h3><ol><li><a href="Register for a JIRA account|https://issues.apache.org/activemq/secure/Signup!default.jspa">Register for a JIRA account|https://issues.apache.org/activemq/secure/Signup!default.jspa</a> </li><li>Log in to the JIRA issue tracking system </li><li>Visit the <a href="http://issues.apache.org/activemq/brows
 e/SM">ServiceMix JIRA page</a> and click the link named <a href="Create a new issue in project ServiceMix|https://issues.apache.org/activemq/secure/CreateIssue!default.jspa">Create a new issue in project ServiceMix|https://issues.apache.org/activemq/secure/CreateIssue!default.jspa</a> </li><li>Fill in as much detail as possible </li><li>Add a JUnit test if possible</li></ol><p>If you can create a JUnit test case then your issue is more likely to be resolved quicker. The best way to start is to take a look at some of the <a href="http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-core/src/test/java/org/apache/servicemix/">existing unit tests</a> as examples. Then we can commit your test case along with your patch to Subversion so that we'll know that the issue its really fixed and we can ensure that it stays fixed in future releases.</p><h2 id="SubmittingPatches">Submitting Patches</h2><p>We gladly accept patches if you can find ways to improve, tune or fix
  ServiceMix in some way. To submit a patch, please use the following steps: </p><ol><li>Build against the trunk to ensure that your code compiles correctly and that your test runs </li><li>Create a new <a href="http://issues.apache.org/activemq/browse/SM">JIRA issue</a> that fully explains the situation, including the environments you've tested, the JVM version and vendor you're using and anything else that might be useful to know about the situation </li><li>Attach the patch to the issue that you are creating and make sure to tick the 'Patch Attached' checkbox on the issue </li><li>Send an email to the <a href="mailing-lists.html">Mailing Lists</a> or <a href="discussion-forums.html">Discussion Forums</a> to let people know you've filed an issue and contributed a patch for the issue </li><li>Please try to also submit tests in the patch. Including tests makes applying the patch much easier and faster. Tests allow a patch to be applied and tested much quicker which results in
  your issue being fixed faster. </li></ol><h3 id="CreatingthePatch">Creating the Patch </h3><p>Most IDEs can create nice patches now very easily. If you're a command line person try the following to create the patch:</p><pre class="none code-none">
+<h1 id="AnyoneCanContribute">Anyone Can Contribute! </h1><p>There are many ways you can help make ServiceMix a better piece of software - please dive in and help!</p><p>Surf the documentation - if somethings confusing or not clear, let us know or even edit it yourself. All you need to do is <a href="http://cwiki.apache.org/confluence/signup.action">register for a wiki account</a> and you can begin contributing your own docs, fixing docs, updating docs, etc. </p><p>Download the code, try it out, and see what you think. Browse the source code. Got an itch to scratch, want to tune some operation or add some feature? Anyone can dive right in. </p><p>Want to do some hacking on ServiceMix? Try surfing the our <a href="http://issues.apache.org/activemq/browse/SM">issue tracker</a> for open issues or features that need to be implemented, take ownership of an issue and try to fix it.</p><p>If you'd rather have a more gentle introduction to working on the ServiceMix project, look at t
 he <a href="http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-core/src/test/java/org/apache/servicemix/">unit tests cases</a> and help us to improve our test coverage.</p><h2 id="ApacheCommitters">Apache Committers</h2><p>Apache committers are allowed write access to the <a href="https://svn.apache.org/repos/asf/servicemix/sandbox">ServiceMix sandbox</a>.  This makes it easy to collaborate with us on components or integration efforts with other Apache projects.  Simply create a directory with your Apache userid and branch the code you want to work on.  Create a Jira issue with a description of the work and use this Jira ID in the comments for your commits.  The work history will now appear in the Fisheye and Subversion Commits tabs of the Jira issue.</p><h2 id="GettingInTouch">Getting In Touch</h2><p>There are various ways of communicating with the ServiceMix community.</p><ul style="list-style: square"><li>visit the <a href="discussion-forums.html">Discu
 ssion Forums</a></li><li>subscribe to the <a href="mailing-lists.html">Mailing Lists</a> and take part in any conversations</li><li>pop by on <a href="irc://irc.codehaus.org/servicemix">IRC</a> and say hi</li><li>add some comments to the <a href="../site/navigation.html">wiki</a>(requires a log in)</li><li>if you use ServiceMix please tell us about it on our <a href="users.html">Users page</a></li></ul><h2 id="IfYouFindaBugorProblem">If You Find a Bug or Problem</h2><p>Please create a new issue in the <a href="http://issues.apache.org/activemq/browse/SM">JIRA issue tracker</a></p><h3 id="CreatingaJIRAIssue">Creating a JIRA Issue </h3><ol><li>Register for a JIRA account at <a href="https://issues.apache.org/jira/secure/Signup!default.jspa">https://issues.apache.org/jira/secure/Signup!default.jspa</a></li><li>Log in to the JIRA issue tracking system </li><li>Visit the <a href="http://issues.apache.org/jira/browse/SMX4">ServiceMix JIRA page</a> - at the top right of the page, y
 ou can create a new JIRA issue.</li><li>Fill in as much detail as possible </li><li>Add a JUnit test if possible</li></ol><p>If you can create a JUnit test case then your issue is more likely to be resolved quicker. The best way to start is to take a look at some of the <a href="http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-core/src/test/java/org/apache/servicemix/">existing unit tests</a> as examples. Then we can commit your test case along with your patch to Subversion so that we'll know that the issue its really fixed and we can ensure that it stays fixed in future releases.</p><h2 id="SubmittingPatches">Submitting Patches</h2><p>We gladly accept patches if you can find ways to improve, tune or fix ServiceMix in some way. To submit a patch, please use the following steps: </p><ol><li>Build against the trunk to ensure that your code compiles correctly and that your test runs </li><li>Create a new <a href="http://issues.apache.org/activemq/browse/SM"
 >JIRA issue</a> that fully explains the situation, including the environments you've tested, the JVM version and vendor you're using and anything else that might be useful to know about the situation </li><li>Attach the patch to the issue that you are creating and make sure to tick the 'Patch Attached' checkbox on the issue </li><li>Send an email to the <a href="mailing-lists.html">Mailing Lists</a> or <a href="discussion-forums.html">Discussion Forums</a> to let people know you've filed an issue and contributed a patch for the issue </li><li>Please try to also submit tests in the patch. Including tests makes applying the patch much easier and faster. Tests allow a patch to be applied and tested much quicker which results in your issue being fixed faster. </li></ol><h3 id="CreatingthePatch">Creating the Patch </h3><p>Most IDEs can create nice patches now very easily. If you're a command line person try the following to create the patch:</p><pre class="none code-none">
 diff -u Main.java.orig Main.java >> patchfile.txt
 </pre><p>or, if you're working against the code base checked out from the Subversion repository (this is the best way to work), then just use the <tt>svn diff</tt> command in the Subversion client. </p><pre class="none code-none">
 svn diff Main.java >> patchfile.txt