Author: mseidel
Date: Wed Mar 8 18:18:07 2017
New Revision: 1786052
URL: http://svn.apache.org/viewvc?rev=1786052&view=rev
Log:
Fixed typos
Modified:
openoffice/ooo-site/trunk/content/stats/index.html
Modified: openoffice/ooo-site/trunk/content/stats/index.html
URL:
http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/stats/index.html?rev=1786052&r1=1786051&r2=1786052&view=diff
==============================================================================
--- openoffice/ooo-site/trunk/content/stats/index.html (original)
+++ openoffice/ooo-site/trunk/content/stats/index.html Wed Mar 8 18:18:07 2017
@@ -40,8 +40,8 @@ We use the <a href="mailto:marketing@ope
<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. Projects also differ in what project resources they include in
- version control (Open Hub looks at files under version control), and
which version controlled files they associate with their Open Hub. For Apache
OpenOffice our Open Hub looks at files associated with our two main
- project deliverables: the OpenOffice source code and the website. For
historical comparisons the Open Hub also looks at the legacy OpenOffice.org
repository for commits prior to June 2011. The safest comparison is
+ version control (Open Hub looks at files under version control), and
which version controlled files they associate with their Open Hub account. For
Apache OpenOffice our Open Hub account looks at files associated with our two
main
+ project deliverables: the OpenOffice source code and the website. For
historical comparisons the Open Hub 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>
