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

[ro...@apache.org]

Author: robweir
Date: Tue Feb 12 22:11:58 2013
New Revision: 1445413

URL: http://svn.apache.org/r1445413
Log: (empty)

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

Added: openoffice/site/trunk/content/contributing-code.mdtext
URL: http://svn.apache.org/viewvc/openoffice/site/trunk/content/contributing-code.mdtext?rev=1445413&view=auto
==============================================================================
--- openoffice/site/trunk/content/contributing-code.mdtext (added)
+++ openoffice/site/trunk/content/contributing-code.mdtext Tue Feb 12 22:11:58 2013
@@ -0,0 +1,47 @@
+Title:     Contributing Code to Apache OpenOffice
+Notice:    Licensed to the Apache Software Foundation (ASF) under one
+           or more contributor license agreements.  See the NOTICE file
+           distributed with this work for additional information
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+If you have code that you want to contribute to the Apache OpenOffice project, then we would [love to talk to you](mailto:dev@openoffice.apache.org) about this.
+
+Apache projects put a strong emphasis on code pedigree and reviewing and documenting licences and notices, more so than many other open source projects.  This is done to make our
+projects more valuable to users, especially to other developers.  This is one of the ways we add value, one of the things that makes Apache special.  So please don't be offended
+if one of the first things we question you about is the license and the pedigree of the code. 
+
+The main requirements for contributing code to Apache OpenOffice are:
+
+  - The code must be under the Apache License 2.0.  Any dependencies must also be under that licence or a [similar permissive license](http://www.apache.org/legal/resolved.html#category-a).
+  - The code must be of sufficient quality and value  to the project that our programmer (Committers) approve it, or at least don't reject it.
+  - We're not interested in large code-dumps.  Although we're happy to accept a small patch to fix a bug here or there, a dump of 100,000 lines of code would not be appreciated.  However, if a community currently 
+  maintaining a sizable piece of code wants to join the project, then we might be more interested in adopting the community as well as the code.  "Community over code" as we say.
+
+
+Some specfic 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 contributons, 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 larges 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 Licence 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 
+[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 make it contribute it to
+us under the Apache License as well.
+