svn commit: r1446975 - /openoffice/site/trunk/content/contributing-code.mdtext

[pe...@apache.org]

Author: pescetti
Date: Sat Feb 16 23:05:16 2013
New Revision: 1446975

URL: http://svn.apache.org/r1446975
Log:
Minor fixes and enhancements

Modified:
    openoffice/site/trunk/content/contributing-code.mdtext

Modified: openoffice/site/trunk/content/contributing-code.mdtext
URL: http://svn.apache.org/viewvc/openoffice/site/trunk/content/contributing-code.mdtext?rev=1446975&r1=1446974&r2=1446975&view=diff
==============================================================================
--- openoffice/site/trunk/content/contributing-code.mdtext (original)
+++ openoffice/site/trunk/content/contributing-code.mdtext Sat Feb 16 23:05:16 2013
@@ -34,15 +34,17 @@ sufficient for sustaining the developmen
 Some specific scenarios:
 
   - For small bug fixes and enhancements, contributed by the original author of the code, these are best submitted as patches attached to a [Bugzilla issue](https://issues.apache.org/ooo/)
-  - For larger contributions, contributed by a single original author, we might ask you to submit an [Individual Contributor License Agreement (ICLA)](http://www.apache.org/licenses/icla.txt) form.  This helps
-  project the users of Apache OpenOffice.  All project Committers have also signed this form.
-  - For contributions of multi-author code, it is best to start a discussion on our [dev mailing list](dev@openoffice.apache.org) so we can discuss the most appropriate way of processing it.
+  - For larger contributions, contributed by a single original author, we might ask you to
+  submit an [Individual Contributor License Agreement (ICLA)](http://www.apache.org/licenses/icla.txt) form.
+  The copyright on your code will still belong to you, but the ICLA helps
+  protect the users of Apache OpenOffice.  All project Committers have also signed this form.
+  - For contributions of multi-author code, it is best to start a discussion on our [dev mailing list](mailto:dev@openoffice.apache.org) so we can discuss the most appropriate way of processing it.
   - For large codebases developed outside of Apache, especially ones created behind a corporate firewall, we typically require a [Software Grant Agreement](http://www.apache.org/licenses/cla-corporate.txt) 
   before we can accept the contribution.  Again, an early discussion on our [dev mailing list](mailto:dev@openoffice.apache.org) is recommended.
 
 Note: It is perfectly fine for a programmer to contribute the same bug fix or feature patch to multiple open source projects.  As the author you have the right to make your code available
 to us under the Apache License as well as to make the same code available to another project under LGPL.  Similarly, if you have code that you've contributed to another project under
-MPL or LPGL you can also make it available to us under the Apache License, maximizing the number of people who will benefit from your work.  For small patches it would be sufficient to 
+MPL or LGPL you can also make it available to us under the Apache License, maximizing the number of people who will benefit from your work.  For small patches it would be sufficient to 
 [send us a note](mailto:dev@openoffice.apache.org) pointing to an existing patch or VCS revision containing your contribution and stating that you wish to contribute it to
 us under the Apache License as well.