libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r865781 - in /websites/staging/libcloud/trunk/content: ./ contributing.html
Date Sat, 15 Jun 2013 23:25:06 GMT
Author: buildbot
Date: Sat Jun 15 23:25:05 2013
New Revision: 865781

Log:
Staging update by buildbot for libcloud

Modified:
    websites/staging/libcloud/trunk/content/   (props changed)
    websites/staging/libcloud/trunk/content/contributing.html

Propchange: websites/staging/libcloud/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Jun 15 23:25:05 2013
@@ -1 +1 @@
-1493306
+1493431

Modified: websites/staging/libcloud/trunk/content/contributing.html
==============================================================================
--- websites/staging/libcloud/trunk/content/contributing.html (original)
+++ websites/staging/libcloud/trunk/content/contributing.html Sat Jun 15 23:25:05 2013
@@ -107,7 +107,7 @@
 examples, ...).</p>
 <p>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.</p>
+on freenode) and we will do our best to assist you.</p>
 <h3 id="process"><a href="#process">General workflow</a></h3>
 
 <ol>
@@ -127,14 +127,28 @@ For more information about running the t
 https://github.com/apache/libcloud/pulls</li>
 <li>Wait for the code to be reviewed and address any outstanding comments.</li>
 <li>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:
  <code>git format-patch --stdout trunk &gt; patch_name.patch</code></li>
 </ol>
-<p>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.</p>
+<h4 id="contributing-bigger-changes">Contributing Bigger Changes</h4>
+<p>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.</p>
+<p>You can find more information on how to sign and file an ICLA on the
+<a href="https://www.apache.org/licenses/#clas">Apache website</a>.</p>
+<h4 id="note-about-github">Note about Github</h4>
+<p>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:</p>
+<p>::bash
+   git remote add upstream https://git-wip-us.apache.org/repos/asf/libcloud.git</p>
+<p>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.</p>
 <h3 id="things_to_keep_in_mind"><a href="#things_to_keep_in_mind">Things To Keep
In Mind</a></h3>
 
 <ul>



Mime
View raw message