svn commit: r850500 - in /websites/staging/openoffice/trunk/content: ./ contributing-code.html

[bu...@apache.org]

Author: buildbot
Date: Wed Feb 13 14:51:13 2013
New Revision: 850500

Log:
Staging update by buildbot for openoffice

Modified:
    websites/staging/openoffice/trunk/content/   (props changed)
    websites/staging/openoffice/trunk/content/contributing-code.html

Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Feb 13 14:51:13 2013
@@ -1 +1 @@
-1445414
+1445639

Modified: websites/staging/openoffice/trunk/content/contributing-code.html
==============================================================================
--- websites/staging/openoffice/trunk/content/contributing-code.html (original)
+++ websites/staging/openoffice/trunk/content/contributing-code.html Wed Feb 13 14:51:13 2013
@@ -21,7 +21,7 @@
 <meta name="google-site-verification" content="wIHUbgA-JO5PaJHpR5jeI8N9E2y2iF94o4oUwpaAdk8" />
 <link href="/css/ooo.css" rel="stylesheet" type="text/css">
 
-<title>Contributing Code to Apache OpenOffice
</title>
+<title>Contributing Code to Apache OpenOffice</title>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 
 <script type="text/javascript">
@@ -98,7 +98,7 @@
   </div>
   <div id="contenta">
   
-    <h1 class="title">Contributing Code to Apache OpenOffice
</h1>
+    <h1 class="title">Contributing Code to Apache OpenOffice</h1>
     <p>If you have code that you want to contribute to the Apache OpenOffice project, then we would <a href="mailto:dev@openoffice.apache.org">love to talk to you</a> about this.</p>
 <p>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
@@ -107,8 +107,10 @@ if one of the first things we question y
 <ul>
 <li>The code must be under the Apache License 2.0.  Any dependencies must also be under that licence or a <a href="http://www.apache.org/legal/resolved.html#category-a">similar permissive license</a>.</li>
 <li>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.</li>
-<li>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.</li>
+<li>We're happy to accept a small patch to fix a bug here or there, without further commitment from the code author.  But the larger the contribution 
+the greater is the need for help integrating, testing and maintaining the code.  This doesn't necessarily
+require participation from the original author(s) of the code, though this is encouraged.  But we will want to see that there is support in the community
+sufficient for sustaining the development of significant contributions.</li>
 </ul>
 <p>Some specfic scenarios:</p>
 <ul>