corinthia-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject svn commit: r1652512 - /incubator/corinthia/www/contribute_howto.html
Date Fri, 16 Jan 2015 20:03:14 GMT
Author: jani
Date: Fri Jan 16 20:03:14 2015
New Revision: 1652512

URL: http://svn.apache.org/r1652512
Log:
updated howto text

Modified:
    incubator/corinthia/www/contribute_howto.html

Modified: incubator/corinthia/www/contribute_howto.html
URL: http://svn.apache.org/viewvc/incubator/corinthia/www/contribute_howto.html?rev=1652512&r1=1652511&r2=1652512&view=diff
==============================================================================
--- incubator/corinthia/www/contribute_howto.html (original)
+++ incubator/corinthia/www/contribute_howto.html Fri Jan 16 20:03:14 2015
@@ -13,47 +13,45 @@
 	  <!-- content section -->
 	  <div class="row">
       <div class="large-12 columns">
-	  <div class="float left"><img src="img/owl.jpg" width="250" height="250" alt=""
title="" /></div>	  	  
+	  <div class="hide-for-small float left"><img src="img/owl.jpg" width="250" height="250"
alt="" title="" /></div>	  	  
       <h3>How to contribute</h3>
 	  <p>Welcome and thank you for your interest in contributing to Apache Corinthia!
This guide will take you through the process of making contributions to the 
-	  Apache Corinthia code base. Contributor license agreement 
-      Apache Corinthia is licensed under the Apache License, Version 2.0. All contributions
will be under this license, so please read and understand this license 
-	  before contributing.      
-      For all but the most trivial patches, you are required to file a Contributor License
Agreement with the Apache Software Foundation. Please read the guide to 
-	  CLAs to find out how to file a CLA with the Foundation.</p>	  
+	     Apache Corinthia code base.</p>
+      <h4>Contributor license agreement</h4>
+          <p>Apache Corinthia is licensed under the Apache License, Version 2.0. All
contributions will be under this license,
+	     Please read and understand this license before contributing.<br>
+          <p>For all but the most trivial patches, you are required to file a Contributor
License Agreement with the Apache Software Foundation.<br>
+	     Please read the guide to CLAs to find out how to file a CLA with the Foundation.</p>
  
       <h3>Before you start - join the community</h3>
-      <p>If it’s your first contribution or it’s a particularly big or complex
contribution, things typically go much more smoothly when they start off with a 
-	  conversation. Join our development mailing list.
+          <p>If it is your first contribution or it is a particularly big or complex
contribution,things typically go much more smoothly
+	     when they start off with a conversation.<br>
+	     Join our development mailing list.
       <h3>Create an issue in Jira</h3>      
-      Your first step is to create or find an issue in Corinthia’s Jira for your feature
request or fix. For small changes this isn’t necessary, but it’s good 
-	  to see if your change fixes an existing issue anyway.</p>      
-	  <h3>Contributing using GitHub</h3>
-      <p>This is our preferred way for contributing code. Our GitHub repository is
located at https://github.com/apache/incubator-corinthia.      
-      Your commit messages must properly describes the changes that have been made and their
purpose (here are some guidelines). If your contributions fix a 
-	  Jira issue***, then ensure that you reference the issue (like CORINTHIA-9876***) in the
commit message.      
-      Create a pull request (PR) in GitHub for the change you’re interested in making.
The comment section of the PR must contain a link to the JirA*** issue 
-	  (if it has one).      
-      Some good references for working with GitHub are below. We ask that you keep your change
rebased to master as much as possible, and we will ask you to 
-	  rebase again if master has moved before accepting your patch.</p>
-      <ul><li>Setting Up Git with GitHub</li><li>Forking a Repository</li><li>Submitting
Pull Requests</li><li>Rebasing your Branch</li></ul>
-      <p>Finally, add a comment in the Jira issue with a link to the pull request so
we know the code is ready to be reviewed.</p>
+          <p>Your first step is to create or find an issue in Corinthi Jira for your
feature request or fix.
+	     For small changes this is not necessary, but it is good to see if your change fixes
an existing issue anyway.</p>      
+      <h3>Contributing using GitHub</h3>
+          <p>This is our preferred way for contributing code for non-committers. Our
GitHub repository is located at https://github.com/apache/incubator-corinthia.      
+	     Your commit messages must properly describes the changes that have been made and their
purpose (here are some guidelines).<br>
+	     - If your contributions fix a Jira issue***, then ensure that you reference the issue
(like CORINTHIA-9876***) in the commit message.<br>
+	     - Create a pull request (PR) in GitHub for the change. The comment must contain a link
to the JirA*** issue (if it has one).<br>
+             Some good references for working with GitHub can be found on our GIT FAQ page.
We ask that you keep your change rebased to master as much as possible,
+	     and we will ask you to rebase again if master has moved before accepting your patch.</p>
       <h3>Reviews</h3>
-      <p>The Apache Corinthia community will review your pull request before it is
merged. This process can take a while, so please be patient. If we are slow 
-	  to respond, please feel free to post a reminder to the mailing list - see the home page
to see how to contact us.
-      During the review process you may be asked to make some changes to your submission.
While working through feedback, it can be beneficial to create new 
-	  commits so the incremental change is obvious. This can also lead to a complex set of commits,
and having an atomic change per commit is preferred in the end. 
-	  Use your best judgement and work with your reviewer as to when you should revise a commit
or create a new one.
-      A pull request is considered ready to be merged once it gets at lease one +1 from a
committer. Once all the changes have been completed and the pull request 
-	  is accepted, you may be asked to rebase it against the latest code. You may also wish
to squash some commits together and make other history revisions, to 
-	  leave the commit history clean and easily understood.</p>
-	  <h3>Contributing without using GitHub</h3>
-      <p>If you prefer to not use GitHub, then that is fine - we are also happy to
accept patches attached to a Jira issue. Our canonical repository is located 
-	  at 
-	  <div class="panel">https://git-wip-us.apache.org/repos/asf/incubator-corinthia.git;
-	  <br>for example: $ git clone https://git-wip-us.apache.org/repos/asf/incubator-corinthia.git</div>
-      When producing patches, please use git format-patch or a similar mechanism - this will
ensure that you are properly attributed as the author of the patch 
-	  when a committer merges it.</p>
-	  
+          <p>The Apache Corinthia community will review your pull request before it
is merged. This process can take a while, so please be patient.
+	     If we are slow to respond, please feel free to post a reminder to the mailing list
- see the home page to see how to contact us.<br>
+             During the review process you may be asked to make some changes to your submission.
While working through feedback, it can be beneficial to create new 
+	     commits so the incremental change is obvious. This can also lead to a complex set of
commits, and having an atomic change per commit is preferred.<br>
+	     Use your best judgement and work with your reviewer as to when you should revise a
commit or create a new one.<br>
+             A pull request is considered ready to be merged once it gets at lease one +1
from a committer. Once all the changes have been completed
+	     and the pull request is accepted, you may be asked to rebase it against the latest
code. You may also wish to squash some commits together
+	     and make other history revisions, to leave the commit history clean and easily understood.</p>
+      <h3>Contributing without using GitHub</h3>
+          <p>If you prefer to not use GitHub, then that is fine - we are also happy
to accept patches attached to a Jira issue.<br>
+             Our canonical repository is located at 
+	     <div class="panel">https://git-wip-us.apache.org/repos/asf/incubator-corinthia.git;<br>
+		                for example: $ git clone https://git-wip-us.apache.org/repos/asf/incubator-corinthia.git</div>
+             When producing patches, please use git format-patch or a similar mechanism -
this will ensure that you are properly attributed
+	     as the author of the patch when a committer merges it.</p>
 	  </div></div></div> 
 <!--#include virtual="footer.html" -->
   </body>



Mime
View raw message