Author: buildbot
Date: Mon Nov 5 13:52:16 2012
New Revision: 837338
Log:
Staging update by buildbot for openofficeorg
Modified:
websites/staging/ooo-site/trunk/cgi-bin/ (props changed)
websites/staging/ooo-site/trunk/content/ (props changed)
websites/staging/ooo-site/trunk/content/stats/index.html
Propchange: websites/staging/ooo-site/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Nov 5 13:52:16 2012
@@ -1 +1 @@
-1405667
+1405789
Propchange: websites/staging/ooo-site/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Nov 5 13:52:16 2012
@@ -1 +1 @@
-1405667
+1405789
Modified: websites/staging/ooo-site/trunk/content/stats/index.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/stats/index.html (original)
+++ websites/staging/ooo-site/trunk/content/stats/index.html Mon Nov 5
13:52:16 2012
@@ -55,7 +55,10 @@ We use the <a href="mailto:ooo-marketing
<p>
These numbers should be taken with a grain of salt, and one should be
cautious when comparing numbers across projects. Contributor numbers are
especially sensitive to development methodology and tooling, e.g.,
- a project that uses distributed version control will see a different
count than one that processes patches through a smaller core group of
developers.
+ a project that uses distributed version control will see a different
count than one that processes patches through a smaller core group of
developers. Projects also differ in what project resources they include in
+ version control (Ohloh looks at files under version control), and which
version controlled files they associate with their Ohloh account. For Apache
OpenOffice our Ohloh account looks at files associated with our two main
+ project deliverables: the OpenOffice source code and the website. For
historical comparisons the Ohloh account also looks at the legacy
OpenOffice.org repository for commits prior to June 2011. The safest
comparison is
+ to look at the trend for a single project over a period of time when
version control and commit process is constant, e.g., since June 2011 for our
project.
</p>
