libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From to...@apache.org
Subject svn commit: r1493431 - /libcloud/site/trunk/content/contributing.mdtext
Date Sat, 15 Jun 2013 23:24:52 GMT
Author: tomaz
Date: Sat Jun 15 23:24:52 2013
New Revision: 1493431

URL: http://svn.apache.org/r1493431
Log:
Update contributing page.

Modified:
    libcloud/site/trunk/content/contributing.mdtext

Modified: libcloud/site/trunk/content/contributing.mdtext
URL: http://svn.apache.org/viewvc/libcloud/site/trunk/content/contributing.mdtext?rev=1493431&r1=1493430&r2=1493431&view=diff
==============================================================================
--- libcloud/site/trunk/content/contributing.mdtext (original)
+++ libcloud/site/trunk/content/contributing.mdtext Sat Jun 15 23:24:52 2013
@@ -7,7 +7,7 @@ examples, ...).
 
 This page explains how you can contribute to the Libcloud project. If you get
 stuck at any point during this process, stop by on our IRC channel (#libcloud
-on freenode) and we will do our best to help you.
+on freenode) and we will do our best to assist you.
 
 <h3 id="process"><a href="#process">General workflow</a></h3>
 
@@ -27,14 +27,34 @@ For more information about running the t
 https://github.com/apache/libcloud/pulls
 6. Wait for the code to be reviewed and address any outstanding comments.
 7. Once the code has been reviewed, all the outstanding issues have been
-addressed and the pull request has been ACK'ed, close the pull request,
+addressed and the pull request has been +1'ed, close the pull request,
 generate a patch and attach it to the JIRA issue you have created earlier:
  `git format-patch --stdout trunk > patch_name.patch`
 
-Note: We use Github only for pull requests and code review. Once a pull request
-has been reviewed, all the comments have been addresses and it's ready to be
-merged, user who submitted the pull request must close the pull request, create
-a patch and attach it to the original JIRA ticket.
+#### Contributing Bigger Changes
+
+If you are contributing a bigger change (e.g. large new feature or a new
+provider driver) you need to have have signed Apache Individual Contributor
+License Agreement (ICLA) in order to have your patch accepted.
+
+You can find more information on how to sign and file an ICLA on the
+[Apache website](https://www.apache.org/licenses/#clas).
+
+#### Note about Github
+
+Github repository is a read-only mirror of the official Apache git repository
+(https://git-wip-us.apache.org/repos/asf/libcloud.git). This mirror script runs
+only a couple of times per day which means this mirror can be slightly out of
+date. You are advised to add a separate remote for the official upstream
+repository:
+
+   ::bash
+   git remote add upstream https://git-wip-us.apache.org/repos/asf/libcloud.git
+
+Github read-only mirror is used only for pull requests and code review. Once a
+pull request has been reviewed, all the comments have been addresses and it's
+ready to be merged, user who submitted the pull request must close the pull
+request, create a patch and attach it to the original JIRA ticket.
 
 <h3 id="things_to_keep_in_mind"><a href="#things_to_keep_in_mind">Things To Keep
In Mind</a></h3>
 



Mime
View raw message