You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jclouds.apache.org by Apache Wiki <wi...@apache.org> on 2013/06/20 18:37:59 UTC

[Jclouds Wiki] Trivial Update of "Committers Guide" by IgnasiBarrera

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jclouds Wiki" for change notification.

The "Committers Guide" page has been changed by IgnasiBarrera:
https://wiki.apache.org/jclouds/Committers%20Guide?action=diff&rev1=1&rev2=2

Comment:
Just added the link to the CLAs

  || Github || https://github.com/jclouds/legacy-jclouds || The legacy repositories, as they were before the migration to the ASF, used to keep old code ||
  
  == Rules of thumb ==
-  1. Every contribution is a piece of intellectual property.  This is the precious sustenance that nourishes our project.  Please treat it with respect.  If it's sufficiently complex, or from a large corporate entity, ensure there is an ICLA or CCLA on file that covers the contribution.  Asking in #jclouds or #asf will probably be the easiest way to get an answer.
+  1. Every contribution is a piece of intellectual property.  This is the precious sustenance that nourishes our project.  Please treat it with respect.  If it's sufficiently complex, or from a large corporate entity, ensure there is an [[http://www.apache.org/licenses/#clas|ICLA]] or [[http://www.apache.org/licenses/#clas|CCLA]] on file that covers the contribution.  Asking in #jclouds or #asf will probably be the easiest way to get an answer.
   2. ALWAYS give credit where it is due, ensure EVERY merged commit reflects properly the individual who authored that commit.  Preserve both the name and email address.
   3. Ensure your name and email address are there as the committer prior to pushing it to the Apache repositories.
   4. Always strive for linear commit history, avoid merge commits while pulling in contributor's changes.