The Apache Way Contribute ASF Sponsors

Formal board meeting minutes from 2010 through present. Please Note: The board typically approves minutes from one meeting during the next board meeting, so minutes will be published roughly one month later than the scheduled date. Other corporate records are published, as is an alternate categorized view of all board meeting minutes.

2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | Pre-organization meetings

OpenOffice

19 Apr 2017 [Marcus Lange / Mark]

Report was filed, but display is awaiting the approval of the Board minutes.

18 Jan 2017 [Marcus Lange / Bertrand]

DESCRIPTION
===========

Apache OpenOffice is an open-source office-document productivity suite.
There are six productivity applications based around the OpenDocument
Format (ODF) that are Writer, Calc, Impress, Draw, Math, Base. With
limited support for other file formats, OpenOffice ships for Windows,
macOS, Linux 64-bit, Linux 32-bit and in more than 40 languages.

STATUS
======

The typical year-end slow-down due to Christmas, holidays and family
visits in general has also reached OpenOffice. Due to this the activity
in the projects was more silent, too.

However, limitations of capacity of development is an ongoing concern.
But plans are still active to do more releases.

Compared to the previous reports this time it's shorter by intention.

ISSUES FOR BOARD AWARENESS
==========================

There are no current topics to be concerned with.

RELEASES
========

The current release is Apache OpenOffice 4.1.3 and was published on
2016-Oct-12.

Apache OpenOffice 4.1.4 is planned for release in 2017 Q1 for further
maintenance and available security fixes.

Apache OpenOffice 4.2.0 is planned for this year - but without to name a
specific time frame - to include new features and bigger enhancements
but of course more bugfixes and security fixes if needed.

Complete Release History
------------------------
2016-10-12 4.1.3
2016-08-30 4.1.2-patch1 (additional binaries)
2016-08-02 4.1.2-patch1 (source code only)
2015-10-28 4.1.2
2014-08-21 4.1.1
2014-04-29 4.1.0
2013-10-01 4.0.1
2013-07-17 4.0.0
2013-01-30 3.4.1 refresh (8 more languages)
2012-08-21 3.4.1 incubating
2012-05-08 3.4.0 incubating

PMC/COMMITTERS
==============

PMC
---
The recognition and invitation of potential PMC members remains on a
slow level. No new PMC members were added. A discussion is ongoing to
add a former PMC member.

There are currently 27 PMC members.

The last PMC addition was Malte Timmerman (malte) on 2016-07-14

The last PMC resignation was Kay Schenk (kschenk) on 2016-09-02

Committers
----------
There are 140 committers as of 2017-Jan-08. The recognition and
invitation of potential committers is continuing. The following people
were added:

2016-Nov-07	Peter Kovacs (petko)
2016-Nov-16	Matthias Seidel (mseidel)

Last previous committer addition was on 2016-Apr-26 Jan Høydahl (janhoy)

Last previous committer withdrawal was on 2016-Sep-02 Kay Schenk (kschenk)

ACTIVITY
========

Development and Release Engineering
-----------------------------------
The build system and its documentation is improving as the result of
work by experienced developers and committers.  The number of individuals
able to replicate release builds is increasing.

The release manager for the upcoming release 4.1.4 is found and working
on keeping the tasks together.

The hottest action at the moment is to transfer the build system from
the old dmake to the newer gbuild (Google Build). However, with more
than hundred sub-projects in SVN this remains a hugh task.

There are plans to work on a Apple signing service to be able to sign
install files for macOS.

Besides this bugfixing of issues is the next action item to name.

Downloads
---------
The downloads are at a consistent rate. On 2016-Nov-18 A new record has
been reached. OpenOffice hit the mark of 200 million downloads (source:
http://www.openoffice.org/stats/downloads.html).

The downloads regarding to plattform and country over the last 3 months
are spread like the following (source:
https://sourceforge.net/projects/openofficeorg.mirror/files/stats/map?dates=2016-10-15%20to%202017-01-08):

76 % for Windows
 8 % for macOS
 1 % for Linux
15 % for other platforms

17 % United States
13 % France
13 % Germany
 7 % Italy
 7 % Spain
 4 % Poland
 4 % United Kingdom
 3 % Russia
 3 % Japan
 2 % Canada
27 % all other countries

Websites
--------
There is action to improve the translation and structure of webpages for
Danish, Norwegian, German, Portuguese and Korean. The social media
representation (Youtube, Facebook, Twitter) was improved, too.

Community Lists/Archives and Actions
------------------------------------
The list below is in decreasing order by 2016 activity.

           LIST    AVERAGE MONTHLY ACTIVITY
                 2012  2013  2014  2015 2016

           dev@  1266  1124   552   340  323
         users@   235   198   328   219  208
          l10n@   211   225   119    34   18
            qa@   150   127    71    16   16
     marketing@    63    87    18     3    4
           api@    30    35    20    15    1
           doc@     7    41    25    12   13
   recruitment@     -     -     -    -     3 (start in Sep 2016, 38 in
total up to now)

        dev-de@     0     0    42     6   13
      users-de@    38   167   147    94   89
    general-es@    34    24     9     4    4
      users-fr@     1     4     6     0    1
     utenti-it@    29    40    30    37   27
   progetto-it@    12    17     8     2    1
    general-ja@     3     2     0     0    0
    geral-ptbr@    21     5     1     0    0

A new list, recruitment@, was launched on September, 5th. The list is
intended to act as a single-point-of-contact to provide a gentler on-ramp
for newcomers without contending with the active dev@ list for guidance.
The traffic is low but recognized. There have been 31 messages since the
report in October.

The geral-ptbr@ list was closed with the retirement of a moderator and
sustained inactivity.

Apache OpenOffice is represented at a few fairs and events. This is
managed by a small but fine team. Next event is FOSDEM Feb, 4th-5th in
Brussels, Belgium. Here we will share the booth with Apache in general.

Issue Tracking (Bugzilla)
-------------------------
The rate of new Bugzilla issues is decreasing since a few years. The
rate at which issues remain unresolved over all that time is more than
40%. But volunteers are managing the new issue reports that come in.

Development Capacity
--------------------
The arrival of new developers is still slow. But there are indeed people
willing to dig into the code. But with our low number of developers
assignments and mentoring is slow by itself.

A number of previously-active committers have returned to activity
as part of the response to the previous-quarter public discussion
of what AOO retirement would look like.

Next Steps: Improving the mentoring of newcomers and expanding the
capacity to address major issues as part of new releases.

Handling of Security
--------------------
There will be at least one security fix in the under-development
release 4.1.4.


Branding
--------
In average there is nearly 1 request per month for use of the marks.

The same for reports about suspected trademark misuse (or confusion
about selling of Apache OpenOffice binaries, e.g., on eBay).

The fight against these kind of windmills is still active but seems
endless; especially on a project like OpenOffice with a very well-known
brand name.

Governance
----------
The discussions on the retirement of OpenOffice start in September 2016
were very heated. Since many weeks they became silent now on our mailing
lists.

ISSUES
======

No topics

19 Oct 2016 [Marcus Lange / Brett]

DESCRIPTION
===========

Apache OpenOffice is an open-source office-document productivity suite.
There are six productivity applications based around the OpenDocument
Format (ODF) that are Writer, Calc, Impress, Draw, Math, Base. With
limited support for other formats, OpenOffice ships for Windows, Max OS
X, Linux 64-bit, Linux 32-bit and in dozens of languages.

STATUS
======

The first release after a longer time has been done and released and
announced successfully. This makes sure that the community can build a
release. So, we are back in the playground of active projects. However,
limitations of capacity and coordination of the project's moving parts
are ongoing concerns.

ISSUES FOR BOARD AWARENESS
==========================

Concerns for Board attention are in the Issues section, below.

RELEASES
========

Apache OpenOffice 4.1.3 was developed at the end of the 3rd quarter,
with release on 2016-10-12.

Apache OpenOffice 4.1.4 is contemplated for release around year end for
further maintenance and available security fixes.

Apache OpenOffice 4.2.0 is planned for next year (maybe Q1) to include
new features and bigger enhancements but of course also further bugfixes
and security fixes if needed.

Complete Release History
------------------------
 2016-10-12 4.1.3
 2016-08-30 4.1.2-patch1 (additional binaries)
 2016-08-02 4.1.2-patch1 (source code only)
 2015-10-28 4.1.2
 2014-08-21 4.1.1
 2014-04-29 4.1.0
 2013-10-01 4.0.1
 2013-07-17 4.0.0
 2013-01-30 3.4.1 refresh (8 more languages)
 2012-08-21 3.4.1 incubating
 2012-05-08 3.4.0 incubating

PMC/COMMITTERS
==============

The recognition and invitation of potential PMC members has slowed.
There are 27 current PMC members. Complete history is available in PDF
at http://s.apache.org/vji.

 2016-07-14 Malte Timmermann (malte) joined the PMC
 The last preceding PMC addition was on 2016-03-05

 2016-09-02 Kay Schenk (kschenk) retired from the PMC
 The last preceding retirement was on 2016-06-08

Committers
----------

There are 138 committers as of 2016-10-12. 23 have registered PGP keys.
The recognition and invitation of potential committers is continuing.

 2016-04-22 Jan Høydahl (janhoy) joined the project
 Last previous committer addition was on 2016-02-26

 2016-09-02 Kay Schenk (kschenk) withdrew as committer
 Last previous committer withdrawal was on 2016-06-08

ACTIVITY
========

Development and Release Engineering
-----------------------------------

The build documentation is further updated as the result of experience
producing release 4.1.3. The number of individuals able to replicate
release builds is increasing.

As part of a help-wanted effort along with public and mailing-list
attention to the possibility of project retirement, 21 newcomers offered
to contribute in various areas of the project. One is quite active with
others not showing steady activity so far.

In addition, 5 previous contributors offered to return to active
participation with varying presence so far. One returnee is highly
experienced and is heavily active on security, bug fixes, and release
management.

The arrival and continuing involvement of newcomers has been tracked in
the PMC Private OpenOffice Calc spreadsheet at <https://s.apache.org/4Xij>.

Deployment and Take-Up
----------------------

The take-up of Apache OpenOffice in terms of downloads is at a
consistent rate, showing a decrease for 4.1.2 of less than 10% compared
to 4.1.1.

For the 12 months spanning release of AOO 4.1.2 through 2016-09-30,
there are 37 million downloads, averaging about 3.1 million per month.

 86.1% for Windows,
  7.9% for Macintosh, and
  6.0% for all other distributions

For comparison, release of AOO 4.1.1 averaged 3.2 million per month
(correcting a calculation error reflected in previous reports). Details
are at https://s.apache.org/dxaX

US destinations have the greatest number of downloads by nationality,
representing 16% of the total. About 40% of the worldwide downloads are
for English localizations. The estimation of language proportions is at
https://s.apache.org/2fwg

Branding
--------

There is no priority to update to the new feather logo and to adapt a
new "Power-By" logo.

There is typically one request per month for use of the marks.

There is typically a report per month of a suspected trademark misuse
(or confusion about selling of Apache OpenOffice binaries, e.g., on
Ebay). One requested correction due to an incorrect use of OpenOffice in
a product name was confirmed in September.

Community Lists and Archives
----------------------------

An Apache OpenOffice booth was manned at FrosCon 2016 near Bonn,
Germany, in August. In November, there will be booths at events in The
Netherlands and in Oberhausen, Germany.

The year-over-year decline in mailing list activity continues. A few
bumps reflect the Q3 4.1.3 activity, developer recruitment, and
discussions about retirement and avoiding retirement.

A new list, recruitment@, was launched on September 5. There have only
been 8 messages so far. The list is intended to act as a
single-point-of-contact to make it easier to support a gentler on-ramp
for newcomers rather than contending with the active dev@ list for guidance.

Detailed data is in PDF at <https://s.apache.org/OHfh>. The list below
is in decreasing order by 2015 activity.

         LIST    AVERAGE MONTHLY ACTIVITY
               2012  2013  2014  2015 2016Q1-Q3

         dev@  1266  1124   552   340  313
       users@   235   198   328   219  209
    users-de@    38   167   147    94   90
   utenti-it@    29    40    30    37   25
        i10n@   211   225   119    34   19
          qa@   150   127    71    16   18
         api@    30    35    20    15    1
         doc@     7    41    25    12   17
      dev-de@     0     0    42     6   12
  general-es@    34    24     9     4    4
   marketing@    63    87    18     3    2
 progetto-it@    12    17     8     2    0
    users-fr@     1     4     6     0    0
  geral-ptbr@    21     5     1     0    0
  general-ja@     3     2     0     0    0

Bugzilla and Issue Tracking
---------------------------

The rate of new Bugzilla issues is steadily decreasing since 2013, the
first full year of the Apache OpenOffice Top-Level Project. The rate at
which issues remain unresolved over all that time is stubbornly more
than 40%. The Q3 activity related to issues treated for maintenance
release 4.1.3 has not altered that condition. Full comparative analysis
is in the PDF at <http://s.apache.org/YFT>. Qualitative analysis at
<http://s.apache.org/SNg> applies.

Wiki and Documentation
----------------------

The documentation effort initiated in 2013 is stalled. A committer and
PMC member wanted to make progress here was be convinced to still keep
active in the project, now probably in other areas.

Along with significant outdated material on the MediaWiki, changes in
the product are not accompanied by corresponding user documentation.

The few documentation volunteers that arrived as part of the Q3
help-wanted effort have not shown any impact on documentation so far.

ISSUES
======

Continued identification of risks and issues of capacity and capability
is brought to public lists for discussion on the state of the project in
the community. The general reaction

The limited supply of expert contributors with the capacity, capability,
and availability for sustaining the project is reported.

As part of monthly reporting requested by the Apache Board, the
following concerns are featured here:

 Development Capacity
 Handling of Security
 Trademarks
 Governance

Development Capacity
--------------------

The arrival of newcomers is at a slow trickle. Arrivals on the
developer, QA, and docs lists seek assignments and mentoring. The
newcomers appear eager though lacking project and product knowledge. The
project has a low capacity to support them at that level. However, there
are volunteers to take over the role as mentor.

A couple of developers, including returnees to the project, have arrived
ready to work, making a noteworthy difference.

Effort to provide rapid maintenance releases has succeeded. There is now
greater capacity for producing maintenance builds and having multiple
release-manager candidates.

Next Steps: Improving the mentoring of newcomers and expanding the
capacity to address major issues as part of a feature release.

Handling of Security
--------------------

Release 4.1.3 provides a full-update for the vulnerability CVE-2016-1513
that was disclosed before there were updated binaries available. Release
4.1.3 also provides fixes for two additional vulnerabilities. There is
concurrent disclosure of those as CVE-2016-6803 and -6804.

For the three eliminated vulnerabilities in 4.1.3, the average number of
days before an update was 248, the longest delay being 367 days, the
shortest being 88 days.

In comparison, for the five eliminated vulnerabilities in 4.1.2, the
average number of days before update was 146, the longest delay being
247 days and the shortest being 86 days.

So, the average time has maybe increased. However, effort to turn these
times down is serious.

The security team was streamlined somewhat, including the addition of
more PMC members so that coordination of security with overall project
governance is improved. An energetic security investigator has added to
the team, and another returned as part of the community concerns over
the future of the project.

Branding
--------

There continue to be significant abuses of the Apache OpenOffice brands
by providers of downloads that introduce possible adware along with
misrepresenting association with the project. One peculiar case
(Softpedia.com) started to offer "Apache OpenOffice.org 4.1.3" [sic] two
days before the release was officially announed by the project itself.
Perpetrators have also discovered the easy use of "openoffice" as a
subdomain (i.e., like openoffice.foo.com).

Materials for gathering and managing these cases have been set up on the
PMC private repository.

The fight against these kind of windmills is still active but seems
endless; especially on a project like OpenOffice with a very well-known
brand name.

Governance
----------

Transition to the new Chair has occurred smoothly. Updating and turnover
of documentation will be concluded in October.

The September discussions on "What Would OpenOffice Retirement Involve?"
and "What Would OpenOffice NON-retirement involve?" were very heated,
attract attention and have gone in a direction that was not wanted by
the project. Luckily, these have died down, as has the arrival of
newcomers and past contributors as part of the "Help-wanted" effort. We
hope that this is entierly cooling down with showning more activity
again. And new releases are a great help here.

The improvement to do new releases is a critical first step in building
sustainability. We as project have shown that we can do it.

21 Sep 2016

Change the Apache OpenOffice Project Chair

 WHEREAS, the Board of Directors heretofore appointed Dennis E.
 Hamilton (orcmid) to the office of Vice President, Apache OpenOffice,
 and

 WHEREAS, the Board of Directors is in receipt of the resignation of
 Dennis E. Hamilton from the office of Vice President, Apache
 OpenOffice, and

 WHEREAS, the Community of the Apache OpenOffice project has chosen to
 recommend Marcus Lange (marcus) as the successor to the post;

 NOW, THEREFORE, BE IT RESOLVED, that Dennis E. Hamilton is relieved
 and discharged from the duties and responsibilities of the office of
 Vice President, Apache OpenOffice, and

 BE IT FURTHER RESOLVED, that Marcus Lange be and hereby is appointed
 to the office of Vice President, Apache OpenOffice, to serve in
 accordance with and subject to the direction of the Board of Directors
 and the Bylaws of the Foundation until death, resignation, retirement,
 removal or disqualification, or until a successor is appointed.

 Special Order 7C, Change the Apache OpenOffice Project Chair,
 was approved by Unanimous Vote of the directors present.

21 Sep 2016 [Dennis E. Hamilton / Bertrand]

 This is an abbreviated interim report to focus on concerns for
 which monthly updates have been requested by the Board.
 The next complete report will be for the October Board Meeting.

STATUS
======

Limitations of capacity and coordination of the project's moving parts
are ongoing concerns.

ISSUES FOR BOARD AWARENESS
==========================

Concerns for Board Attentions are on the following topics:

 Development Capacity
 Handling of Security
 Trademarks
 Governance

Development Capacity
--------------------

 2016-08-30 4.1.2-patch1 hotfix released
 2016-08-02 4.1.2-patch1 source released
 2015-10-28 4.1.2 released
 2014-08-21 4.1.1 released

A drive to produce Maintenance Release 4.1.3 is now underway.  The release
will provide full binary distributions for all platforms.  It will not
introduce features that involve GUI changes, documentation requirements,
or significant new localization.  It is a constrained release to demonstrate
rapid production of maintenance releases.

Upon release of 4.1.3, maintenance release 4.1.4 will follow, tentatively
targeted for release this year.

To expand development capacity and capability of the project, a recruit-
ment effort has been initiated, with notification on the Downloads page.
New mailing list recruitment@openoffice.apache.org, established on
2016-09-06, is for new volunteers to have a quieter on-ramp than the dev@
list.

Since the beginning of August, there have been a dozen requests from new
contributors.  These are for QA, documentation, localization, and
development.  The new developers do not know the AOO code base.  All require
some degree of mentoring.

In addition, there are five returning contributors, including one with
significant OpenOffice development, security, and release-deployment
experience.


Handling of Security
--------------------

The public distribution of Apache OpenOffice 4.1.2 on 2015-10-28 included
mitigations for five vulnerabilities.  One of these had been disclosed on
2015-04-25 with a workaround but no update.  For the five 4.1.2 mitigations,
the average number of days from report to update was 146.  The longest was
247 days and the shortest was 86 days.

On 2016-07-21, there was disclosure and an OpenOffice advisory for
CVE-2016-1513, a vulnerability reported on 2015-10-20, 275 days earlier.
A source patch and hotfix binary were made available subsequently.  As of
Wednesday, 2016-09-14, 330 days after the initial report, the mitigation
has not appeared in a full binary distribution.

The release of 4.1.3 with full binaries will include the mitigation of
CVE-2016-1513.  Release 4.1.3 and subsequent work toward a 4.1.4 maintenance
release begins a drive to have timely resolution of security defects become
a sustainable activity for the still-strained developer resources.

Recent progress in handling security reports is owed to two developers
who have stepped into working on these reports in the last few weeks.  There
is also cooperation with the [OfficeSecurity] team around identifying and
treating vulnerabilities in common.  This should keep pace with the
establishment of expedited maintenance releases.

Trademarks
----------

The previously-asked question of how trademarks should be handled in the event
of OpenOffice retirement or pivoting remains open.

Meanwhile, the PMC is able to respond to simple request for permissions to
use the marks on print and video materials.  There is no pro-active handling
of identified infringements in misleading product offerings and in web sites
and domain names.

The PMC lacks the capacity and capability to be diligent against the
onslaught of Apache OpenOffice marks abuse.


Governance
----------

The current Chair is resigning after serving more than the promised one year.
Request for nominations for the next proposed Chair ended on September 14,
with PMC Member Marcus Lange the only nominee.  The [VOTE] to recommend
Marcus to the Board is underway.

One highly-active, long-term PMC member has resigned.  The project is
still being held together by around a half-dozen active individuals.  The
incorporation of new and returning enthusiasts will depend on how the current
help-wanted recruiting drive plays out.

On September 1, this Chair introduced the dev@ list topic,
"[DISCUSS] What Would OpenOffice Retirement Involve? (long)", expressing
concerns about the limited capacity and capability being unsurmountable as
a practical matter.

In the midst of the external attention, and the extensive discussion on that
thread, a returnee offered a new topic the next day,
"What would OpenOffice NON-retirement involve?"

The NON-retirement discussion has been energetic and ended up focusing on the
current help-wanted/recruitment effort and the drive to achieve rapid
building, release candidacy, and deployment of full releases with binaries.

At the same time, the [DISCUSS] on prospects of retirement and its
orchestration is deemed illegitimate and denied, with only non-retirement
actions underway.  That is the extent of consideration for retirement and/or
pivoting the project.

17 Aug 2016 [Dennis Hamilton]

Although the Board relates its comments to the PMC and asks about the PMC,
I pointed out that recently, most conversations have been on the AOO security
list and now the developer (and QA) lists.  In particular, conversations about
how the project proceeds, what resources it needs/has, and the handling of
now-disclosed security vulnerabilities are on dev@.  With regard to senior ASF
members watching the PMC list and being silent, I requested that there be more
visibility, if only to have the PMC reminded that we are being observed for
how we are dealing with matters of importance that have been conveyed from the
Board.  It is important for the PMC and the project to understand that the
Board is not forgetful.

1. Monthly Reporting.

Apache OpenOffice will report monthly from now on, although the non-quarterly
reports will not be comprehensive.  I propose that focus be on the key issues
where on-going visibility is called for.  I have committed to that as the
Chair, and my successor would be expected to follow suit.

Key observations.  Today, there was no opportunity to consult with the PMC,
so these are clearly my personal observations.  My verbal report was not so
comprehensive.

2. Handling of Security

In the past 60 days there have been imminent disclosure of an unexploited
vulnerability (with proof-of-concept), working out of a hotfix approach that
avoids full-up binary releases, response to disclosure with an advisory and a
source patch, and, now, readiness of tested hotfixes with end-user procedure
for general availability.  The project has now taught itself, after much
to-and-fro, how to accomplish this.  Were there another vulnerability that
could be remedied in this way, it could be done in much less time.

It remains problematic how to provide emergency releases that put new installs
into the hands of users.  There is no consensus on the need for doing so
separate from crunching toward feature releases instead. There is push-back
against even going through what might be essentially fire drills (with real
patches) to confirm controlled ways of doing this.  This despite there being
some pent-up issues that would qualify and could grow to emergencies.  There is
also significant effort to upgrade the OpenOffice dependencies on external
resources to use the latest versions for their vulnerability repairs, lest the
vulnerabilities be exposures to OpenOffice.  No source release nor binary
distributions reflect these updates.

There are insufficient resources to attend to security analysis and preparation
of emergency patch/maintenance releases concurrent with focused progress toward
a feature release.  There is ongoing investigation and discussion on this topic.

3. Trademarks

At the July Board meeting, there was concern about what to do about branding
and trademarks if it is concluded that the Apache OpenOffice project must
retire or pivot away from providing end-user distributions. My recommendation,
today, is that this question cannot be addressed up front.  It is necessary to
first determine what the stages of any retirement would be and how soft-landing
of user-facing resources would be accomplished.  Given a practicable scenario,
it would be appropriate to determine how branding and trademarks can best be
handled.

4. Existential Questions and the OpenOffice Contingent Future

In partial response to the July Board feedback, there has been a renewed effort
to seek additional volunteers for work on Apache OpenOffice development.  This
is done in the face of an aging and disappearing population of developers with
ready-to-hand subject-matter knowledge of OpenOffice, its code base, and the
development/deployment methodologies on which it rests.  The learning curve for
additions to that population is challenging.  There are not resources and
skills for mentoring and cultivating interested beginners who have the
necessary persistence.

While worthwhile, and the project is pouring its heart into this, this is not a
short-term remedy to immediate concerns.

The fundamental reality is that, from a development perspective, the project is
being held together by about a half-dozen part-time volunteers.

A special report was presented verbally by Dennis Hamilton during the board concall. Below are notes on that report:

Dennis: lots of activity on security and developer lists issued an advisory on a security issue will release a hot fix early next week general ability to respond: taking too long and no solution for quick releases for all platforms binaries there is pushback on releasing patch releases for stable platforms don’t know if there can be consensus on releasing security patches steep learning curve for new volunteers down to about 6 people who are experts in the code base

Jim: Board feedback was given to PMC Discussion morphed into a build platform issue Will continue to monitor and stimulate discussion over the long term plan for the project

Dennis: Some discussion has spilled over to the dev list.

Mark: Currently lurking on private list Response to security issues is not adequate

Dennis: It is useful to be reminded of security obligations Wants to step down as chair, hopefully for October board meeting

@Dennis change to monthly board reporting @Dennis send email with verbal summary

After the meeting, Dennis provided a written summary of the verbal discussion (above) and expanded some particular points into a larger report, which is in Attachment BV.

20 Jul 2016 [Dennis E. Hamilton / Chris]

DESCRIPTION
===========

Apache OpenOffice is an open-source office-document productivity
suite.  There are six productivity applications based around the
OpenDocument Format (ODF). With limited support for other formats,
OpenOffice ships for several platforms and in dozens of
languages.

STATUS
======

Limitations of capacity and coordination of the project's moving parts are
ongoing concerns.


ISSUES FOR BOARD AWARENESS
==========================

Concerns for Board attention are in the Issues section, below.


RELEASES
========

There is no Apache OpenOffice release in this quarter.  It has been 8 months
since the last release and a backlog of maintenance and feature updates
is accumulating.

Complete Release History
  2015-10-28 4.1.2
  2014-08-21 4.1.1
  2014-04-29 4.1
  2013-10-01 4.0.1
  2013-07-17 4
  2013-01-30 3.4.1 refresh (8 more languages)
  2012-08-21 3.4.1 incubating
  2012-05-08 3.4   incubating

PMC/COMMITTERS
==============

The recognition and invitation of potential PMC members has slowed.
There are 27 current PMC members.  Complete history is available in
PDF at http://s.apache.org/vji .

   The last preceding PMC addition was on 2016-03-05

   2016-06-08 Oliver-Rainer Wittmann (orw) retired
       The last preceding retirement was on 2016-01-28

In this quarter, 87% of the 199 (down from Q1 540) private@ posts
were by PMC members.  Of those posts, 89% were by 7 members (relatively
unchanged) and 11 did not post at all (a decline).

Committers
----------

There are 139 committers as of 2016-06-30.  22 have registered PGP keys.
The recognition and invitation of potential committers has flattened out.

       Last previous committer addition was on 2016-04-22

   2016-06-08 Oliver-Rainer Wittmann withdrew
       Last previous committer withdrawal was on 2016-01-28

ACTIVITY
========

Moving parts of the Apache OpenOffice project span three inter-connected
layers.

 * Development, Release Engineering, and Deployment
   - Development and release engineering
   - Deployment and take-up
   - Branding
     and internationalization, QA, and documentation

 * Project Community Lists and Archives
   development topics, user-facing information, user reports,
   trouble-shooting, and feedback

 * Public Project-Community Interfaces
   tying together development, users, and support areas:
   - Bugzilla and issue tracking
   - Wiki and Documentation
   web site (two flavors), and Community Forums

Development and Release Engineering
-----------------------------------

Separate source-only release of UNO Tools for independent usage has stalled
with inability to obtain enough binding votes for a release candidate.

Addition of feature updates along with maintenance for a release 4.2.0 has
stalled without preparation of any release candidates as of 2016-06-30.

Activity to upgrade the build system stalled on difficulties with obtaining
efficient Windows builds.

A documented walkthrough of the Windows build process still needs review
since the previous report.

Deployment and Take-Up
----------------------

For the eight months since release of AOO 4.1.2 through 2016-06-30,
there are 29 million downloads, averaging about 850,000 per week and now
down to about 600,000 as we enter North American Summer in the last week.
Platform take-up is relatively constant:

   87.5% for Windows,
    7.8% for Macintosh, and
    4.7% for all other distributions

In the same time span, release 4.1.1 had 26.2 million downloads.

US destinations have the greatest number of downloads by nationality,
representing but 15% of the total.  English language localization
is chosen for 41% of recent downloads, with 11 languages in the top
92%: English, French, German, Italian, Spanish, Japanese, Russian, Polish,
Portuguese, Chinese and Dutch in decreasing order.  The remaining 8%
includes 27 additional languages and the SDK.  Details are in the PDF at
https://s.apache.org/2fwg

SourceForge serving of downloads has continued with its much-improved
usability and up-time.


Branding
--------

The project is still not making any changes involving the new feather logo
and powered-by graphics.  This is not a priority.

There is typically one request for use of the marks each month.

The counterfeit OpenOffice of an anonymous imposter has finally been removed
from the application store where it was offered.

There is typically one monthly report of a suspected trademark misuse (or
confusion about selling of Apache OpenOffice).

Community Lists and Archives
----------------------------

Every mailing list has decreased in average monthly activity from 2016 Q1
to 2016 Q2.  Some mailing lists have insignificant traffic.  Because of
Northern Hemisphere Summer, it is too soon to know how much the year-over-
year decline in activity has continued.

The complete compilation of the data is in PDF at
<https://s.apache.org/OHfh>.  The list is in decreasing order by 2015
activity.

         LIST    AVERAGE MONTHLY ACTIVITY
               2012  2013  2014  2015 2016Q1-Q2

         dev@  1266  1124   552   340  226
       users@   235   198   328   219  208
    users-de@    38   167   147    94  102
   utenti-it@    29    40    30    37   22
        i10n@   211   225   119    34   18
          qa@   150   127    71    16   15
         api@    30    35    20    15    1
         doc@     7    41    25    12   19
      dev-de@     0     0    42     6    7
  general-es@    34    24     9     4    4
   marketing@    63    87    18     3    2
 progetto-it@    12    17     8     2    0
    users-fr@     1     4     6     0    0
  geral-ptbr@    21     5     1     0    0
  general-ja@     3     2     0     0    0

Bugzilla and Issue Tracking
---------------------------

The rate of new bugzilla issues is steadily decreasing since 2013, the first
full year of the Apache OpenOffice Top-Level Project.  The rate at which
issues remain unresolved over all that time is stubbornly in excess of 40%.
The complete tabulation is in the PDF at http://s.apache.org/YFT
Qualitative analysis at <http://s.apache.org/SNg> applies.

Wiki and Documentation
----------------------

The documentation effort initiated in 2013 is stalled.

New volunteers arrive periodically although concerted, sustained effort is
absent.

Along with significant outdated material on the MediaWiki, changes in the
product are not accompanied by corresponding user documentation.


ISSUES
======

Continued identification of risks and issues of capacity and capability is
brought to public lists for discussion on the state of the project in the
community.

The limited supply of expert contributors with the capacity, capability, and
availability for sustaining the project is reported.

Overall
-------

The arrival of newcomers is at a slow trickle.  Arrivals on the developer, QA,
and docs lists seek assignments and mentoring.  The newcomers appear eager
though lacking project and product knowledge. The project has negligible
capacity to support them at that level.

Release Engineering
-------------------

Providing a faster maintenance-release cadence to push out important
fixes still has no support.

The buildbot for Windows binaries has failed continually for almost a
full year (since 2015-07-28).  There is no buildbot for OS X.  The project
fears risk of regressions from changes that are developed and successfully
applied for Linux and FreeBSD, the primary tools of the few active developers.

The project also risks inability to prepare release candidates and then
provide adequate binding votes for candidates that might be achieved.

Branding
--------

Investigation of inappropriate use of Apache brands for OpenOffice occurs
when brought to the attention of the PMC.  It is also easy to conduct
internet searches and discover a frightening number of likely trademark
misuse cases.  Try an Internet search for "Open Office."  Or just search for
the same on ebay.com or ebay.co.uk.  E.g.,
http://www.ebay.com/sch/i.html?_from=R40&_nkw=Open+Office

The PMC is overwhelmed by this onslaught.  There is insufficient capacity
and comfort at working through this situation.

We need to develop better templates for engaging producers of products that
invite confusion with Apache OpenOffice.  We need to find ways to pursue such
cases that do not overwhelm the capacity of the Project Management Committee
to manage.  We also need to simplify the engagement of trademarks@, especially
where distributors of third-party software impose friction in the acceptance
of trademark violation complaints.

That looks like a full-time job and the volunteer cycles are not available.

Server Support
--------------

The Apache OpenOffice PMC is obligated to provide software installation,
maintenance, and administration of unique services spun up on behalf
of the project.  This includes the Community Forums, the MediaWiki, and
build slaves for Windows and flavors of Linux.  It would apply
to a build slave for OS X if one were added to the list.

That's a rare skill among those to whom work and support of Apache OpenOffice
appeals.  We appear to lack enough expertise and capacity to handle the
obligations for tending to these infrastructure-hosted services.

We require assistance in finding a way to arrive at a satisfactory
arrangement that the PMC has the ability to support.

@Jim: Work with PMC to plan next steps for the project

20 Apr 2016 [Dennis E. Hamilton / Jim]

DESCRIPTION
===========

Apache OpenOffice is an open-source office-document productivity
suite.  There are six productivity applications based around the
OpenDocument Format (ODF). With limited support for other formats,
OpenOffice ships for several platforms and in dozens of
languages.


STATUS
======

The project is warming up for its next release, Apache OpenOffice 4.2.0.

There is growing attention to security of dependencies and also ways to
improve release engineering.

Limitations of capacity and coordinating the project's moving parts are
concerns.


ISSUES FOR BOARD AWARENESS
==========================

Concerns and warning signs for Board attention are in the Issues section,
below.

RELEASES
========

There is no Apache OpenOffice release in this quarter.

Complete Release History
  2015-10-28 4.1.2
  2014-08-21 4.1.1
  2014-04-29 4.1
  2013-10-01 4.0.1
  2013-07-17 4
  2013-01-30 3.4.1 refresh (8 more languages)
  2012-08-21 3.4.1 incubating
  2012-05-08 3.4   incubating

PMC/COMMITTERS
==============

PMC
---

The recognition and invitation of potential PMC members is improving and
expected to continue.  Complete PMC membership history is available in PDF at
<http://s.apache.org/vji>.

The AOO PMC consists of 28 individuals as of 2016-03-31.  Eleven have
registered PGP keys.

   17 have remained continuously out of the
      23 from TLP formation in October, 2012.
   11 are new or returned PMC members

    9 of the current PMC are Apache Software Foundation
      Members, including the original and current Chairs

  2016-03-05 Keith N. McNamara (knmc) joined the PMC
  2016-02-29 Patricia Shanahan (pats) joined the PMC
  2016-02-14 Carl Marcum (cmarcum) joined the PMC
        The last preceding addition was on 2015-10-18

   2016-01-28 Louis Suarez-Potts (louis) retired
   2016-01-20 Rob Weir (robweir) retired
       The last preceding retirement was on 2015-10-18

In this quarter, 87% of the 540 private@ posts were by PMC members.  Of those
posts, 97% were by 10 members and 9 did not post at all.

Committers
----------

There are 139 committers as of 2016-03-31.  Twenty-one have registered PGP
keys.  The recognition and invitation of potential committers is improving
and expected to continue.

   2016-02-25 Jon Peli Oleaga added
   2016-02-23 Patricia Shanahan added
       Last previous committer addition was on 2015-12-04

   2016-01-28 Louis Suarez-Potts withdrew
   2016-01-22 Jean Hollis Weber withdrew
   2016-01-20 Rob Weir withdrew
       Last previous committer withdrawal was on 2015-09-23


ACTIVITY
========

Moving parts of the Apache OpenOffice project span three inter-connected
layers.

 * Development, Release Engineering, and Deployment:
   development, testing, internationalization, QA, documentation, deployment,
   and branding

 * Project Community Lists and Archives:
   development topics, user-facing information, user reports,
   trouble-shooting, and feedback

 * Public Project-Community Interfaces
   tying together development, users, and support areas:
   Bugzilla, wiki (two flavors), web site (two flavors), and Community
   Forums

Development and Release Engineering
-----------------------------------

Separate source-only release of UNO Tools for independent usage is
progressing.

Maintainors of some writing aids (e.g., spelling checkers) provide regular
updates for eventual release inclusion.

Fixes for issues deferred from the 4.1.2 release are now retargeted for
4.2.0.  Issues and fixes are flagged as part of warming-up for 4.2.0.  There
is no projected release date.  SVN preparations for release-candidate
staging of 4.2.0 have not begun.

Significant change to the build system are staged.  Updates to third-party
components incorporate their latest security fixes.

A documented walkthrough of the Windows build process needs review.  Changing
the build system requires updated documentation.

Occasional newcomers want to work on the project.  The learning curve is
still steep, especially for Windows.  It is not unusual for new volunteers
to disappear after a short time.

Deployment and Take-Up
----------------------

For the five months since release of AOO 4.1.2 through 2016-03-31,
there are 19.9 million downloads, roughly 4.0 million per month
at a rate of 800,000 per week.

   87.9% for Windows,
    7.8% for Macintosh, and
    4.3% for all other distributions

Although US destinations have the greatest number of downloads by
nationality, that represents only 15% of the total for this
highly-international project.

For comparison, release 4.1.1 binaries had been downloaded 48.1 million times
over the 16 months of that release, roughly 4.3 million monthly at a rate of
1 million per week.

There is new management at SourceForge, the provider of Apache OpenOffice
download mirrors, Extras archives, and third-party extensions and templates
downloads.  There appears to be no impact.  There is serious improvement
how advertising is separated on the download-starting page, reducing
confusion about whether the download has been requested and will start
without any more clicking.

Branding
--------

Trademark registration/renewal activity, coordinated with trademarks@,
is underway.

The project is not making any changes involving the new feather logo and
powered-by graphics.

There is typically one request for use of the marks each month, including a
request this quarter for display of Apache OpenOffice as a prop in a
French action-adventure television series.

One misuse of Apache OpenOffice marks has been addressed with a publisher
and acceptable remedies are in place.

Major abuse of "OpenOffice" by an anonymous imposter is difficult to thwart.
Effort is continuing with assistance of trademarks@.

Community Lists and Archives
----------------------------

The tabulation below summarizes the average rate of mailing list usage for all
of the public lists since Apache OpenOffice became a top-level project in
November 2012.  The complete compilation of the data is in PDF at
<https://s.apache.org/OHfh>.  The list is in decreasing order by 2015
activity.

         LIST    AVERAGE MONTHLY ACTIVITY
               2012  2013  2014  2015 2016Q1

         dev@  1266  1124   552   340  305
       users@   235   198   328   219  231
    users-de@    38   167   147    94  111
   utenti-it@    29    40    30    37   27
        i10n@   211   225   119    34   22
          qa@   150   127    71    16   25
         api@    30    35    20    15    2
         doc@     7    41    25    12   36
      dev-de@     0     0    42     6   12
  general-es@    34    24     9     4    5
   marketing@    63    87    18     3    5
 progetto-it@    12    17     8     2    0
    users-fr@     1     4     6     0    0
  geral-ptbr@    21     5     1     0    0
  general-ja@     3     2     0     0    0

Bugzilla and Issue Tracking
---------------------------

Tabulation of Bugzilla issue growth extends to the end of 2016Q1.  The rate
of unresolved issues continues to be in excess of 40%.  The complete
tabulation is at <http://s.apache.org/YFT>.  Qualitative analysis at
<http://s.apache.org/SNg> applies.

Wiki and Documentation
----------------------

In 2013Q1, a new documentation effort for an end-users manual was started on
the OpenOffice MediaWiki.  That is the only user-documentation effort.
Material from an "OpenOffice for Students" was being incorporated.  As
reported in 2015Q1, documentation efffort stalled.

New volunteers arrive regularly although concerted, sustained effort is
absent.

There is much outdated material on the MediaWiki and changes in the product
are not accompanied by coordinated documentation.


ISSUES
======

Continued identification of risks and issues of capacity and
capability is brought to public lists for discussion
on the state of the project in the community.

Overall
-------

Newcomers to the developer, QA, and docs lists seek assignments the project
lacks capacity to provide and mentor.  Newcomers appear eager though lacking
project and product knowledge.

Release Engineering
-------------------

Providing a faster maintenance-release cadence to pick up important
fixes has no support.

The buildbot for Windows binaries has not been successful since 2015-07-28.
This impairs QA testing and patch testing.  There is risk of regressions from
changes that are developed and successfully applied to Linux and FreeBSD, the
primary tools of the few active developers.

The 4.1.2 release manager is going to work with one or more "interns" to
cultivate additional committers with experience at producing Apache
OpenOffice builds for the extensive set of binaries that are produced.  The
4.2.0 release candidates will be the laboratory.

The project is vulnerable to inability to prepare candidates if release-
engineering capacity deteriorates.

Having enough PMC members to confirm builds from source to cover the different
platform distributions is a concern.  Current CTR commits receive little if
any visible indications of "R".  Requests for review can go unanswered.  One
committer has refused to create Bugzilla issues to account for SVN changes.

Deployment
----------

Proof of concept for digital signing of Windows builds was achieved in 2014.
Signing is not in production.

Digital signing is crucial.  It allows the platform to verify that the binary
installer is an unmodified authentic build from the project.  It assists
detection of counterfeits that drop adware and malware.

NEXT STEPS: Explore prospects for changing to signed .msi Windows installers
for 4.2.0 despite the compounding of changes and possible delays for
a feature release.  Seek ways to accomplish this in controlled steps.

Branding
--------

Investigation of inappropriate use of Apache brands for OpenOffice occurs
when brought to the attention of the PMC.  There are two cases this quarter.
There are difficulties in going farther.

  1. The distributors of misleading products make it difficult to
     remove offenders that are casually allowed to make misleading offers.

  2. The project is not pro-active in finding offenders and requesting
     compliance with Apache brand usage.  In particular, "Open Office" is
     heavily used and search services treat it as a synonym for "OpenOffice."
     There appear to be over 100 AOO download/disc offers that claim the
     need for advertising to support the "product" effort.

  3. Where paid advertisements accompany search results, these can have more
     prominence than "Apache OpenOffice" results which otherwise rank highest.

  4. When contact is achieved, it can take considerable effort and
     communication to have the producer honor Apache brands.

NEXT STEPS: Find better templates for engaging producers of products that
invite confusion with Apache OpenOffice.  Find ways to pursue such cases that
do not overwhelm the capacity of the Project Management Committee to manage.
Simplify the engagement of trademarks@, especially where distributors of
third-party software impose friction in the acceptance of trademark
violation complaints.

20 Jan 2016 [Dennis E. Hamilton / Shane]

DESCRIPTION
===========

Apache OpenOffice is an open-source, office-document productivity
suite providing six productivity applications based around the
OpenDocument Format (ODF). OpenOffice is released on multiple
platforms and in dozens of languages.

STATUS
======

The Project succeeded with maintenance release 4.1.2 on October 28.
This is a significant milestone and the first release in 14 months.

Warning signs around sustainability and disconnects across the
community are being brought gradually and gingerly to community
attention.

ISSUES FOR BOARD AWARENESS
==========================

The Board needs to be aware of Activity concerns and Sustainability
warning signs reported/reviewed in the Issues sections, below.


RELEASES
========

Release 4.1.2 was approved on October 26 and announced as available on
2015-10-28.  In addition, Java UNO tools for Maven, jar files of AOO 4.1.2
components for independent usage, were distributed on 2015-12-21.

Complete Release History
 2015-10-28 4.1.2
 2014-08-21 4.1.1
 2014-04-29 4.1
 2013-10-01 4.0.1
 2013-07-17 4
 2013-01-30 3.4.1 refresh (8 more languages)
 2012-08-21 3.4.1 incubating
 2012-05-08 3.4   incubating


ACTIVITY
========

Release Effort and Plans
------------------------

Non-4.1.2-release-blocker issues and some anticipated features were
retargeted to a subsequent Apache OpenOffice release in order to
accelerate release of 4.1.2.

Improvements for performing unit testing have been introduced by
introducing Google Test in place of cppunit.  Some finalization
is needed to have the changes work for Windows builds.

There is not yet any action plan or staging for releases beyond
October's 4.1.2.  There are no projected release dates.

Community Operations
--------------------

The Apache OpenOffice community has three main pillars: development,
support, and end-user services.  The pillars are permeable, with
interdependencies from end to end.

For AOO, the provision of authenticated binaries as part of Apache
releases is not a mere convenience.  It is overwhelmingly the purpose
of the project in its origin and as brought to Apache, however much
the limited downstream use of the code base is also desired and
supported.

As evidence of that importance, by 2015-12-31, binary installers
of previous release 4.1.1 had been downloaded 48.1 million times.
Of these,

  87.7% were for Windows
   8.9% were for Macintosh
   3.4% were for all other distributions, including Linux

For 4.1.2 binaries, since release at the end of October until
2015-12-31, there are 7.7 million downloads, now continuing at
about 1 million per week, with

  87.5% for Windows,
   8.1% for Macintosh, and
   4.4% for all other distributions

Although US destinations have the greatest number of downloads
by nationality, that represents only 15% of the total for this
highly-international project.

That overwhelmingly defines the community of next-in-line adopters
of Apache OpenOffice software.


PMC/COMMITTERS
==============

The practice of welcoming new PMC/committer members on the dev list
dropped out and has been restored.

PMC
---

The AOO PMC consists of 27 individuals as of 2015-12-31.  Gavin
McDonald joined the PMC and Peter Junge retired in the October-
December quarter.

  18 have remained continuously out of the
     23 from TLP formation in October, 2012.
   9 are new or returned PMC members

   7 of the current PMC are Apache Software Foundation
     Members, including the original Chair

 2015-10-18 Gavin McDonald (gmcdonald) joined the PMC
 2015-10-08 Damjan Jovanovic (damjan) joined the PMC
 2015-02-13 Dennis E. Hamilton joined the PMC
 2015-02-11 Jan Iversen returned to PMC as Chair
 2015-01-03 Mechtilde and Dr. Michael Stehmann joined the PMC
      The last preceding addition was on 2014-01-16

  2015-10-18 Peter Junge (pj) retired
  2015-09-09 Ian Lynch (ingotian) deceased May, 2015
  2015-08-23 Jan Iversen retired
      The last preceding retirement was on 2014-08-30

PMC membership history is available in PDF at <http://s.apache.org/vji>.

Committers
----------

There are 140 committers as of 2015-12-31.  Twenty-four have registered PGP
keys. Don Lewis became a committer in the October-December quarter.

  2015-12-04 Don Lewis added
  2015-08-06 Manik Malhotra added
  2015-07-27 Gavin McDonald added
      Last previous committer addition was Tal Daniel on 2014-04-29

  2015-09-23 Ingrid von der Mehden (ingrid), deceased 2013-06-12
  2015-09-09 Ian Lynch (ingotian), deceased May, 2015
  2015-08-23 Jan Iversen resigned

The recognition and invitation of potential committers is improving and
expected to continue.


ISSUES
======

With the positive movement seen in this quarter, some issues linger.
It is slow going identifying obstacles and bringing them before the entire
community for its wisdom in identification of consensus-based direction.

Recent progress is owed to heroic efforts on the part of a small group.
We must find a way to not have that as the only way of operating,
burning out devoted contributors.  The inevitability of turnover is
worrisome.

Governance
----------

ACTION ITEM: Following the October 2015 Board Meeting, considering the
general lack of energy and resources reported, the AOO PMC was
requested to report plans for informing the public on current
difficulties and risks to the project.

STATUS: The PMC has not addressed the action item.  The Chair has made
an initial few [RISK? ...] posts on the dev@ list to bring individual
cases to general-community attention.  There are mixed results.

NEXT STEPS: Continue identifying risks and issues of capacity and
capability on the public lists to provide a grounded discussion on the
state of the project in the community.

Development
-----------

PREVIOUSLY: Chair was to follow through with PMC to develop a slip-stream
release setup that is always in hand regardless of what feature release
development is underway.  Have in place as soon as possible after release
4.1.2.
STATUS: Preparation for short-cycle releases and controlled changes,
such as code-signing and straightforward maintenance, has no alignment
on the PMC.  There is concern that this will distract from achieving a
feature release.
NEXT STEPS: Take the concerns to the dev@ community for discussion there.

RESOURCE ISSUES: The buildbot for Windows binaries has not
made a successful build since since 2015-07-28.  This has limited QA
testing and patch testing.  There is risk of regressions from changes that
are developed and successfully applied to Linux builds, the primary tool
active developers.

CAPACITY CONCERNS. Based on the crunch to release AOO 4.1.2, it is clear
that 5-6 developers, all on the PMC, completely held together the release
and deployment of AOO 4.1.2.  While there are important contributions from
many others on and off the PMC, without those five the release would not have
happened when it did.
  The involvement of QA volunteers was limited.
  There are also limitations around having enough PMC members provide
builds from source corresponding to the different configurations that are
supported.

Community
---------

PREVIOUSLY: Misalignment in the connection and support from developers
all the way to end-users via lists, forums, and bugzilla was raised as a
concern.  The incoherence in where fixes are focused versus where usability
is an issue are part of that concern.
STATUS: This has been raised among the different subgroups with modest
success.  Some do not see a problem.
NEXT STEPS: Continue to cultivate this issue.  Downgrade from an issue for
board attention.

ISSUE CLEARANCE AND TECHNICAL DEBT.  The handling of issues is how the cycle
of improvement from developers to users to developers is demonstrated.
  The tabulation of bugzilla issue growth has been completed to the end
of 2015.  The rate at which issues remain unresolved continues to be in
excess of 40%.  The overall tabulation is at <http://s.apache.org/YFT>.
A qualitative analysis is at <http://s.apache.org/SNg>.
  NOTE: There is a strenuous objection to the use of "technical debt" in
the analysis of unresolved-issue accrual.
  KEY CONCERN: No matter how the tracking and understanding of these issues
improves, there does not appear to be developer capacity for addressing
very many of them.  This may discourage further defect reporting and
diminish user confidence in their reliance on the software.

Previous Sustainability Concerns
--------------------------------

CUSTOM IT SUPPORT.  A project member has taken over the maintenance
of the MediaWiki software.  The Forum services are running successfully.
This is no longer an issue.

RELEASE MANAGEMENT.  A new Release Manager provided AOO 4.1.2.  The ability
to train others in managing releases is not fully established and resources
for the different builds are strained.  Improvement is expected to continue.
  NEXT STEPS: Continued attention.

SKILL DEVELOPMENT. Exploring engagement with companies that might
have a strategic reason for contributing skills to the project has
not been fruitful.
  Although there are occassional newcomers wanting to work on the project,
the learning curve is very steep, especially for Windows development.  It is
not unusual for new volunteers to disappear after a short time.
  On the bright side, three students are now being mentored by a senior
developer.
  NEXT STEPS: Continued attention, improve the Windows situation.

COMMITTER/PMC AVAILABILITY.  As of 2015-10-20, all 140 committers have updated
their passwords since the previously-required reset.  It remains to determine
what committers/PMC are still subscribed to the dev/private lists.  In any
case, most of the 140 are not regulary involved.
  NEXT STEPS: Promote more active contributors as committers, assess
capacity for development more closely.

INFRASTRUCTURE ISSUES.
  PREVIOUSLY From 2015-09 Report. Clarify the situation and achieve a
sustainable arrangement in consultation with Infra.  Identify at least
temporary relief, with solid arrangement by January.
  STATUS: The Forum and Wiki systems are maintained by a project member
and the procedures are documented for use by others.
  NEXT STEPS: None.

21 Oct 2015 [Dennis E. Hamilton / David]

For quarter-to-quarter comparison consistency, this October 2015 report
rolls-up, updates, and expands material from the September 2015 Interim
report.

                -  -  -  -  -  -  -  -  -  -  -  -

Apache OpenOffice is an open-source, office-document productivity
suite providing six productivity applications based around the
OpenDocument Format (ODF). OpenOffice is released on multiple
platforms and in dozens of languages.

STATUS
======

The Project is working urgently toward maintenance release 4.1.2.
There is continuing adjustment to the change of Chair for the second
time in 2015. Warning signs around sustainability and disconnects across
the community are being brought gingerly to community-wide attention.

ISSUES FOR BOARD AWARENESS
==========================

The Board needs to be aware of Community concerns, Sustainability
warning signs, and other matters reported in the Issues sections, below.


RELEASES
========

There is no release in the July - September quarter.

Release 4.1.2 is now anticipated in October 2015, using an accelerated
approach.

Complete Release History
  2014-08-21 4.1.1
  2014-04-29 4.1
  2013-10-01 4.0.1
  2013-07-17 4
  2013-01-30 3.4.1 refresh (8 more languages)
  2012-08-21 3.4.1 incubating
  2012-05-08 3.4   incubating


ACTIVITY
========

Release Effort and Plans
------------------------

Developer focus is on provision of the Apache OpenOffice 4.1.2
maintenance release.  This will extend to localization, web site
updates, and provision of any associated security advisories.

Non-4.1.2-release-blocker issues and some anticipated features are
targeted for the future Apache OpenOffice 4.2 release.  There
is no anticipated date at this time.  To accelerate 4.1.2, some but
not all 4.1.2 blockers and additional feature developments have been
triaged to 4.2.

Community Operations
--------------------

The Apache OpenOffice community has three main pillars: development, support,
and end-user services.  The pillars are permeable, with interdependencies
from end to end.

For AOO, the provision of authenticated binaries as part of Apache releases
is not a mere convenience.  It is overwhelmingly the purpose of the project
in its openoffice.org origin and as brought to Apache, however much
downstream use of the code base is also desired and supported.

For context, by the end of August 2015 there were 41 million downloads
of AOO 4.1.1 since its release one year earlier.

   87.7% were for Windows
    9.1% were for Macintosh
    3.2% were for everything else, including Linux

A virtuous cycle of learning and improvement best extends out to those users,
circling back via end-user services, support functions, and the developer
community.

Currently, the pillars operate semi-independently in what has been typical of
operations since the beginning of the project at Apache.


PMC/COMMITTERS
==============

PMC
---
The AOO PMC consists of 26 individuals as of 2015-09-30

   19 have remained continuously out of the
      23 from TLP formation in October, 2012.
    7 are new or returned PMC members

    6 of the current PMC are Apache Software Foundation
      members, including the original Chair

  2015-02-13 Dennis E. Hamilton joined the PMC
  2015-02-11 Jan Iversen returned to PMC as Chair
  2015-01-03 Mechtilde and Dr. Michael Stehmann joined the PMC
       The last preceding addition was on 2014-01-16

   2015-09-09 Ian Lynch (ingotian) deceased May, 2015
   2015-08-23 Jan Iversen retired
       The last preceding retirement was on 2014-08-30

PMC membership history is available in PDF at <http://s.apache.org/Tw8>.

Committers
----------

There are 139 committers as of 2015-09-30.  Twenty-four have registered PGP
keys.

   2015-08-06 Manik Malhotra added
   2015-07-27 Gavin McDonald added
       Last previous committer addition was Tal Daniel on 2014-04-29

   2015-09-23 Ingrid von der Mehden (ingrid), deceased 2013-06-12
   2015-09-09 Ian Lynch (ingotian), deceased May, 2015
   2015-08-23 Jan Iversen resigned
       Reduction in committers is generally not tracked.
       That's introduced now.


ISSUES
======

The lack of progress on all fronts in the project has been a
continuing issue.  Obstacles are being identified and brought before
the entire community for its wisdom in identification of consensus-
based direction.

Development
-----------

The ability to make "hot" maintenance releases on a compressed schedule for
critical defects and mitigation of security vulnerabilities remains to be
introduced post-4.1.2.  More compression and an abbreviated release process
are required to be able to make a hot update in around 30 days or less by
avoiding all feature enhancements and non-urgent fixes and using an existing
release as base.

    ACTIONS: Follow through with PMC to develop a slip-stream release setup
        that is always in hand regardless of what feature release development
        is underway.  Have in place as soon as possible after release 4.1.2.

There is an issue with respect to release dependencies based on optional
presence of a Java JRE of the same bit-ness (x86 or x64) as the installed
AOO binaries.  Absence of the corresponding JRE denies full functionality
(i.e., operation of the embedded help system and ability to use the default
database created by the OpenOffice Base application).  Although no JRE is
distributed with AOO, the dependency remains and is inadequately "optional"
according to Apache principles.

     ACTIONS: Verify the optionality consideration. Determine ways to
        avoid surprising and confusing the users.

Community
---------

At the moment, the various pillars (development, support, and end-user
service) are served by different individuals although a few notable
contributors work across the full span.

There is no consolidated organization of expertise (i.e., on the PMC) where
the diverse interests of contributors of all kinds, including end-users, are
aligned to address end-to-end project issues and direction.

Considering that the end-user population is dominated by Windows (87.7%)
and Macintosh (9.1%), it is a concern that the key developers have their
greatest affinity and direct experience with the least-popular platforms
(3.7%) in contrast.  It is also a concern that development does not keep
pace with the evolution of the dominant platforms and arrival of their new
variants.  Failure to do so blocks achieving ubiquitous presence in store
systems and other provisions that inspire end-user confidence and take-up.

Issues brought to the developer and user lists about usage are addressed by
volunteer users, sometimes unevenly.  Discussion is yet to begin on improved
coordination of issues across the Bugzilla, lists, wiki and forums.  There
is much room for more-reliable capture of issues and consistent provision of
resolutions and work-arounds.

There are clear misalignments that must be identified more closely and then
addressed.  A noteworthy example is the presence of long-standing (over
years) usability issues involving crashers for which no repairs have been
provided.  In the face of that, supporters of lists and forums have developed
manual power-user-class workarounds that are provided when the issues are
regulary reported anew.

   ASSESSMENT. The current arrangement is incoherent.  Separate actions
     among the pillars are sometimes at cross purposes, especially around
     usability issues that confront non-expert (i.e. most) users.
   ACTIONS
     Broaden participation and coordination among the PMC so that those
   with expertise on particular areas provide consultation and have their
   concerns heard.  Have all apprised of the overall picture so that impacts
   on areas of individual focus are better understood.
     Continue obtaining and presenting measures that expose recuring
   problems in the context of overall activity so that pain points can be
   appraised in a realistic manner aligned with the purpose of the project.


Sustainability
--------------
The following warning signs are noticed with regard to
sustainability.

CUSTOM IT SUPPORT.  The Project has not maintained consistent
support of the servers that is has agreed to operate as part of its
agreement with Infra. The services are at risk. (See Infrastructure
in the next section.)

RELEASE MANAGEMENT.  A single Release Manager has undertaken all
releases up until now.  On the stepping down of that RM, Andrea
Pescetti has stepped in for 4.1.2 and others are needed to rotate
into Release Management duties thereafter.

SKILL DEVELOPMENT. The learning curve required to contribute
effectively to the current code base has proven to make it difficult
to develop or attract experienced developers to the project. While the
ASF is traditionally about the people and not companies, the AOO
project is evaluating engagement with companies that might
have a strategic reason for contributing skills to the project.

EXISTING CAPACITY. The depth and breadth of developer coverage of
the code base will be assessed after the sprint toward release 4.1.2
can be reviewed and development and QA capacity assessed.

ISSUE CLEARANCE AND TECHNICAL DEBT.  Analysis of bugzilla status
since the inception of that database provides the following portrait
of issue legacy as of 2015-08-05

 * the oldest unresolved issue is #497 created on 2001-03-02
 * 24115/121298 (20%) issues are unresolved from before November,
              2012 commencement as a TLP
 * 2232/5139 (43%) issues unresolved of new issues from November,
              2012 through July, 2015
 * 192/452 (42%) issues unresolved of those created in the first
              seven months of 2015

There are a number of factors that impact the quality of these
statistics (PDF details at <http://s.apache.org/OEy>).  There is
every reason to fear that, after suitable filtering, the rate
of technical debt accrual is even greater than 42-43%.

The disposition of bugzilla issues will continue to be monitored
along with discussion of improved coordination across the user-facing
activities of the project.

   ASSESSMENT [2015-09-30]
     LACKING QU50: The project strives to respond to documented bug reports
        in a timely manner.

PMC OPERATION.  There is reduction of PMC-inessential discussions. There is
honoring of the principal that PMC-inessential topics one is unwilling to
discuss in public are not worth discussing in private.  Now the inhibition
to discuss community issues in public needs to be addressed.

COMMITTER/PMC AVAILABILITY. The list of OpenOffice commmitters does not
appear to reflect available, active committers.  A census of available
PMC/committers and their areas of commitment is called for.

  ACTION: Determine which committers/PMC failed to update their accounts
       during the past reset.  Determine which PMC/committers are no longer
       subscribed to the AOO dev list.  Confirm absence of participation
       and adjust accordingly.  Engage the remainder with regard to
       available capabilities and their capacity.  Complete in the
       October-December 2015 quarter.

Infrastructure Issues/Needs
---------------------------
Apache OpenOffice, by long-standing agreement with Apache Infra,
takes responsibility for the custom MediaWiki and Forum servers
operating on Infra-provided VMs.  Limited support is achieved;
more is required.  Although operational, the software is out-of-
date.

   There is also need to support buildbots from within the project.
   ACTION From 2015-09 Report. Clarify the situation and achieve a
sustainable arrangement in consultation with Infra.  Identify at least
temporary relief, with solid arrangement by January.
   PROGRESS: No progress in September.
   NEXT STEPS: To be carried out in the October-December 2015 Quarter.

@Bertrand: Convey to the PMC concerns regarding the different perspectives of the public web site and the actual state of the community

16 Sep 2015

Change the Apache OpenOffice Project Chair

 WHEREAS, the Board of Directors heretofore appointed Jan Iversen (jani)
 to the office of Vice President, Apache OpenOffice, and

 WHEREAS, the Board of Directors is in receipt of the resignation of Jan
 Iversen from the office of Vice President, Apache OpenOffice, and

 WHEREAS, the Community of the Apache OpenOffice project has chosen to
 recommend Dennis E. Hamilton (orcmid) as the successor to the post;

 NOW, THEREFORE, BE IT RESOLVED, that Jan Iversen is relieved and
 discharged from the duties and responsibilities of the office of Vice
 President, Apache OpenOffice, and

 BE IT FURTHER RESOLVED, that Dennis E. Hamilton be and hereby is
 appointed to the office of Vice President, Apache OpenOffice, to serve
 in accordance with and subject to the direction of the Board of
 Directors.  and the Bylaws of the Foundation until death, resignation,
 retirement, removal or disqualification, or until a successor is
 appointed.

 Special Order 7A, Change the Apache OpenOffice Project Chair,
 was approved by Unanimous Vote of the directors present.

16 Sep 2015 [Dennis E. Hamilton/ Rich]

This interim status provides early visibility on issues
that will be rolled-up/revised as part of the regular quarterly
report in October 2015.

                -  -  -  -  -  -  -  -  -  -  -  -

Apache OpenOffice is an open-source, office-document productivity
suite providing six productivity applications based around the
OpenDocument Format (ODF). OpenOffice is released on multiple
platforms and in dozens of languages.

STATUS
======

The Project is working diligently toward maintenance release 4.1.2.
There is adjustment to the change of Chair for the second time in
2015.  The PMC is moving all inessential private@ discussions to
dev@ for engagement of the AOO community.  Warning signs around
sustainability are being brought to community attention.

ISSUES FOR BOARD AWARENESS
==========================

The Board needs to be aware of warning signs concerning Sustainability
reported in the Issues section, below.

RELEASES
========

There is no release expected in the current August-October quarter.

Release 4.1.2 is anticipated before year-end 2015.

Complete Release History
  2014-08-21 4.1.1
  2014-04-29 4.1
  2013-10-01 4.0.1
  2013-07-17 4
  2013-01-30 3.4.1 refresh (8 more languages)
  2012-08-21 3.4.1 incubating
  2012-05-08 3.4   incubating


ACTIVITY
========

Release Effort and Plans
------------------------

Developer focus is on provision of the Apache OpenOffice 4.1.2
maintenance release.  This will extend to localization, web site
updates, and provision of any associated security advisories.

Non-4.1.2-release-blocker issues and some anticipated features are
targeted for th future Apache OpenOffice 4.2 release.  There
is no anticipated date at this time.

Community Operations
--------------------

The developer and support channels (users mailing list and official
forums) remain typical.   There has been some finger-pointing in
conjunction with the world-wide upgrading to Microsoft Windows 10,
although complaints seem to be minimal considering the pace of
upgrading.

Issues brought to the developer and user lists about usage are
addressed by volunteer users, sometimes unevenly.  Discussion is
just beginning on improved coordination of issues across the
Bugzilla, lists, wiki and forums.  The goal is more-reliable capture
of issues and consistent provision of resolutions and work-arounds.

PMC/COMMITTERS
==============

PMC
---
The AOO PMC consists of 26 individuals as of 2015-08-31

   19 have remained continuously out of the
      23 from TLP formation in October, 2012.
    7 are new or returned PMC members

    6 of the current PMC are Apache Software Foundation
      Members, including the original Chair

  2015-08-23 Jan Iversen retired
  2015-02-13 Dennis E. Hamilton joined the PMC
  2015-02-11 Jan Iversen returned to PMC as Chair
  2015-01-03 Mechtilde and Dr. Michael Stehmann were added

  The last preceding addition was on 2014-01-16
  The last preceding retirement was on 2014-08-30

PMC membership history is available in PDF at <http://s.apache.org/Tw8>.

Committers
----------
 - Currently 141 committers

   2015-08-23 Jan Iversen resigned
   2015-08-06 Manik Malhotra
   2015-07-27 Gavin McDonald

 - Last previous committer addition was Tal Daniel on 2014-04-29

ISSUES
======

The lack of progress on all fronts in the project has been a
continuing issue.  Obstacles are being identified and brought before
the entire community for its wisdom in identification of consensus-
based direction.

Initial achievements on this approach will be reported in October.

Sustainability
--------------
The following warning signs are noticed with regard to
sustainability.

CUSTOM IT SUPPORT.  The Project has not maintained consistent
support of the servers that is has agreed to operate as part of its
agreement with Infra. The services are at risk. (See Infrastructure
in the next section.)

RELEASE MANAGEMENT.  A single Release Manager has undertaken all
releases up until now.  On the stepping down of that RM, Andrea
Pescetti has stepped in for 4.1.2 and others are needed to rotate
into Release Management duties thereafter.
SKILL DEVELOPMENT. The learning curve required to contribute
effectively to the current code base has proven to make it difficult
to develop or attract experienced developers to the project. While the
ASF is traditionally about the people and not companies, the AOO
project is evaluating engagement with companies that might
have a strategic reason for contributing skills to the project.

EXISTING CAPACITY. The depth and breadth of developer coverage of
the code base will be assessed by October when the sprint toward
4.1.2 can also be appraised and development capacity assessed.

ISSUE CLEARANCE AND TECHNICAL DEBT.  Analysis of bugzilla status
since the inception of that database provides the following portrait
of issue legacy as of 2015-08-05

 * the oldest unresolved issue is #497 created on 2001-03-02
 * 24115/121298 (20%) issues are unresolved from before November,
              2012 commencement as a TLP
 * 2232/5139 (43%) issues unresolved of new issues from November,
              2012 through July, 2015
 * 192/452 (42%) issues unresolved of those created in the first
              seven months of 2015

There are a number of factors that impact the quality of these
statistics (PDF details at <http://s.apache.org/OEy>), including

 * Unresolved issues are not here differentiated by type.  Feature
   and enhancement requests are counted among confirmed defects.
 * The resolved proportion includes issues rejected as duplicates,
   as lacking supporting information, and as usability/support
   matters rejected as not being bugs, even when obviously about
   defects.

There is every reason to fear that, after such adjustments, the rate
of technical debt accrual is even greater than 42-43%.

   The disposition of bugzilla issues will continue to be monitored
along with improved coordination of issues across the user-facing
activities of the project now beginning discussion.

PMC OPERATION.  The AOO PMC was unable or unwilling to find a
replacement in its own ranks for retiring Chair, Andrea Pescetti.
The election of a new Chair was held between two non-PMC nominees
after there was no consensus on the only PMC member who stood as a
nominee.

   On the subsequent retirement of that new Chair, the only nominee
to step forward had been on the PMC six months and had no PMC
involvement since graduation of the AOO podling in October 2012.
Whatever the level of confidence that reflects, it remains that
there does not appear to be a strong, ready bench and easy
succession.  The Chair-elect intends to retire in September, 2016.

Infrastructure Issues/Needs
---------------------------
Apache OpenOffice, by long-standing agreement with Apache Infra,
takes responsibility for the custom MediaWiki and Forum servers
operating on Infra-provided VMs.  Limited support is achieved;
more is required.  Although operational, the software is out-of-
date.

   There is also need to support buildbots from within the
project.

   ACTION: Clarify the situation and achieve a sustainable arrange-
ment in consultation with Infra.  Identify at least temporary
relief by October, with solid arrangement by January.

15 Jul 2015 [Jan Iversen / Sam]

## Description:
Apache OpenOffice is an open-source, office-document productivity
suite providing six productivity applications based around the
OpenDocument Format (ODF). OpenOffice is released on multiple
platforms and in dozens of languages.

## Activity:
The support channels (users mailing list and official forums) remain
active, the mailing lists have a low but steady flow.

The level of commits on trunk remain low, only a few simple commits.

Due to a contributor, the buildbots were maintained to a operational
again. They are still some configuration work outstanding.

The same contributor provided a patch to solve a rat-scan issue. We
still have a minor rat-scan issue (6 non-critical files are being
reported)

A PMC member volunteered to be release manager (limited to the
upcoming release), discussion is ongoing.

There will not be a AOO track at apacheCON CORE, since only a few
talks have been submitted.

## Issues:
The lack of progress on all fronts in the project is a major concern,
and the PMC have been trying for some time to find consensus about
the road ahead.

## PMC/Committership changes:
 - Currently 140 committers and 29 PMC members in the project.
 - New PMC members:
    - Dennis E. Hamilton was added to the PMC on Fri Feb 13 2015
 - Last committer addition was Tal Daniel at Tue Apr 29 2014


## Releases:
 - Last release was 4.1.1 on Thu Aug 21 2014

AOO remains committed to bring out version 4.1.2, but no real
work has been done since last report. The issues destined for 4.1.2
have been given a BZ status that allows a faster integration (less
test demand). Digital signing is still a wish for the new release.

22 Apr 2015 [Jan Iversen / Jim]

## Description:
Apache OpenOffice is an open-source, office-document productivity
suite providing six productivity applications based around the
OpenDocument Format (ODF). OpenOffice is released on multiple
platforms and in dozens of languages.


## Activity:
Andrea Pescetti resigned as Chair after 2 years in order to enable
a "rotating" Chair role (i.e., a change every 1-2 years). Andrea
remains an active PMC member. Jan Iversen was elected as new Chair
and the transition was smooth.

The mailing lists for users and the development list are fairly
active, while specialized lists see a lower, but steady, activity
(which is natural considering their specialized nature).

The support channels (users mailing list and official forums) are
very active as usual, thanks to the work of many of volunteers.

New volunteers for development show up regularly, but our lack of
mentors have made it very difficult to keep them active. The level
of commits on trunk remain low, only a few simple fixes have been
committed.

The challenging position as release manager remains open since
Jürgen Schmidt announced he wanted to resign as release manager.
Jürgen is still an active PMC member.

The 2 Mac (buildbot) delivered Q3 2014 from Infra are not
operational, but a little group of volunteers work on installing
the AOO development platform.

Proof of concept for Digital Signing was made mid. 2014, no further
work have been done. Once version 4.1.2 is ready for internal
testing, work will continue.

OpenOffice was present at FOSDEM (January 2015 in Brussels,Belgium),
with talks and had a table that was well visited. We look forward to
the idea of having an Apache Stand in 2016, where AOO want to be an
integrated part.

A BoF was held in CSDN OSTC (March 2015, China).

2 Volunteers worked on preparing a AOO track for Austin, in the end
it was decided not to make a track. Traditionally Europe is stronger
for AOO so we look forward to Budapest.

A major issue for AOO is the current activity level (practically no
development). The community only has a few active developers, which
makes a bootstrapping a challenge.

As always AOO wants to cooperate with derived project, and believe
derived projects benefit from a AOO with a high development level.
Talks are (as usual) ongoing and are currently focused on how
development in derived projects can be integrated in AOO and thereby
help the whole eco-system. Talks in particular with one project, has
been more intensive, but has currently not lead to any agreements,
except it is clear that a cooperation must be a win-win situation,
where AOO make changes adapting to the needs to the derived project.


## Issues:
The current CMS discussion based on a proposal to decommission the
tool and ask projects to find other solutions would cause a
significant problem for AOO. The AOO Web pages depend on the
features of CMS  that cannot be easily ported to other tools. If
Infra is to stop the service, AOO will need to either only maintain
only a few pages or run CMS on a project VM. The Board should
remember to look at the total cost of this change, not only the
Infra costs.


## PMC/Committership changes:
 - Currently 140 committers and 29 PMC members in the project.
 - New PMC members:
    - Jan Iversen was added to the PMC on Wed Feb 11 2015
    - Mechtilde Stehmann was added to the PMC on Sat Jan 03 2015
    - Dr. Michael Stehmann was added to the PMC on Sat Jan 03 2015
    - Dennis E. Hamilton was added to the PMC on Fri Feb 13 2015
 - Last committer addition was Tal Daniel at Tue Apr 29 2014


## Releases:
 - Last release was 4.1.1 on Thu Aug 21 2014

Even though AOO remains committed to bring out version 4.1.2, it is
only progressing slowly. It is decided this will be the first
digitally signed release. The slowness is due to focus on other
challenges (like electing a new chair) and to lack of  developers /
release manager.


## Mailing list activity:
  - users@openoffice.apache.org:
    - 569 subscribers (down -16 in the last 3 months):
    - 917 emails sent to list (866 in previous quarter)
  - dev@openoffice.apache.org:
    - 500 subscribers (up 0 in the last 3 months):
    - 1377 emails sent to list (1195 in previous quarter)
 - private@openoffice.apache.org:
    - 507 emails sent to list (624 in previous quarter)
We are working on reducing the amount of unnecessary mails as
it is too high for the private mailing list.

 - progetto-it@openoffice.apache.org:
    - 203 subscribers (up 4 in the last 3 months):
    - 6 emails sent to list (27 in previous quarter)
 - marketing@openoffice.apache.org:
    - 171 subscribers (down -3 in the last 3 months):
    - 22 emails sent to list (25 in previous quarter)
 - geral-ptbr@openoffice.apache.org:
    - 18 subscribers (up 0 in the last 3 months):
    - 0 emails sent to list (4 in previous quarter)
 - doc@openoffice.apache.org:
    - 149 subscribers (up 2 in the last 3 months):
    - 20 emails sent to list (36 in previous quarter)
 - forum-admin@openoffice.apache.org:
    - 3 subscribers (up 0 in the last 3 months)
 - utenti-it@openoffice.apache.org:
    - 356 subscribers (up 0 in the last 3 months):
    - 109 emails sent to list (51 in previous quarter)
 - announce@openoffice.apache.org:
    - 11334 subscribers (down -37 in the last 3 months):
    - 1 emails sent to list (0 in previous quarter)
 - general-ja@openoffice.apache.org:
    - 24 subscribers (up 0 in the last 3 months):
    - 1 emails sent to list (0 in previous quarter)
 - issues@openoffice.apache.org:
    - 97 subscribers (up 9 in the last 3 months):
    - 1698 emails sent to list (1919 in previous quarter)
 - general-es@openoffice.apache.org:
    - 87 subscribers (up 4 in the last 3 months):
    - 4 emails sent to list (21 in previous quarter)
 - l10n@openoffice.apache.org:
    - 251 subscribers (up 5 in the last 3 months):
    - 257 emails sent to list (118 in previous quarter)
 - qa@openoffice.apache.org:
    - 280 subscribers (down -5 in the last 3 months):
    - 57 emails sent to list (57 in previous quarter)
 - api@openoffice.apache.org:
    - 155 subscribers (up 10 in the last 3 months):
    - 65 emails sent to list (38 in previous quarter)

18 Feb 2015

Change the Apache OpenOffice Chair

 WHEREAS, the Board of Directors heretofore appointed Andrea
 Pescetti to the office of Vice President, Apache OpenOffice, and

 WHEREAS, the Board of Directors is in receipt of the resignation
 of Andrea Pescetti from the office of Vice President, Apache
 OpenOffice, and

 WHEREAS, the Project Management Committee of the Apache
 OpenOffice project has chosen by vote to recommend Jan Iversen
 as the successor to the post;

 NOW, THEREFORE, BE IT RESOLVED, that Andrea Pescetti is relieved
 and discharged from the duties and responsibilities of the office
 of Vice President, Apache OpenOffice, and

 BE IT FURTHER RESOLVED, that Jan Iversen be and hereby is
 appointed to the office of Vice President, Apache OpenOffice, to
 serve in accordance with and subject to the direction of the
 Board of Directors and the Bylaws of the Foundation until
 death, resignation, retirement, removal or disqualification, or
 until a successor is appointed.

 Special Order 7E, Resolution to Change the Apache OpenOffice
 Chair, was approved by Unanimous Vote of the directors
 present.

21 Jan 2015 [Andrea Pescetti / Ross]

Apache OpenOffice is an open-source, office-document productivity
suite providing six productivity applications based around the
OpenDocument Format (ODF). OpenOffice is released on multiple
platforms and in dozens of languages.

### Issues for Board Awareness
1) Andrea Pescetti, the current PMC Chair, gave his availability
to resign as soon as a successor can be elected: after 2 years it's
time for a rotation. Discussions are still ongoing, so the
resolution won't arrive in time for the January Board meeting.

2) The Apache OpenOffice community is still struggling in
involving new volunteers who can independently work on big
developments. Lack of appropriate mentors is still the main issue.

3) Following the many discussions we had in 2014, OpenOffice now
needs a replacement for Apache Extras. SourceForge provided a
proof of concept that could work for us, but we prefer that the new
location for Apache Extras is decided at an ASF-wide level (i.e.,
that, as it used to be the case, all Apache projects put their
"Extras" in a common space).

### Community Development/Outreach Progress
Since the last report, the project added two PMC members:
Michael and Mechtilde Stehmann (mikeadvo, mechtilde) in
December 2014. The latest committer addition is from May 2014 (tal).

We continue to see new volunteers who would like to be involved,
but we are able to use them for relatively easy tasks only, since we
are still witnessing a reduced level of activity (in terms of both
contributed lines of code and e-mails to the dev list) from more
experienced developers.

The OpenOffice custom infrastructure (wiki, forum) is now out of the
"minimal maintenance" mode and is assigned to Jan Iversen.

A new documentation effort for an end-users manual under the ALv2
licence is stalled, even though new volunteers show up regularly.
The problem is still the lack of appropriate coordinators/mentors.

The localization community is growing, with new volunteers and new
languages.

A survey run just before ApacheCon EU showed that we have a lot
on unexpressed potential in our volunteers, especially for
non-development tasks. The challenge is now to implement the "better
tools" and "better guidance" that these volunteers asked for, in
several fields, from documentation to marketing to QA.

OpenOffice had a dedicated track at ApacheCon Budapest, with
talks spanning all the main project areas except core development.
OpenOffice will have a dedicated booth and a devroom (shared
with other OpenDocument Editors) at FOSDEM 2015, 31 January in
Brussels.

The mailing lists for user support, localization, development are
quite active, the marketing, documentation, QA lists are moderately
active. Activity in social media is still good. Community support
forums remain popular with users, with an average of over 100 posts
per day.

### Product/Project Development Progress
Apache OpenOffice 4.1.2 is currently in the plans. It will be a
bugfix release, but it will contain a major new feature in terms of
packaging, with digitally signed installers and executables that
will be accepted by modern Windows systems without warnings.
Considering the many counterfeited sites offering variants of
OpenOffice and the number of our users, this will be a significant
milestone for the project.

Activities that are still foreseen, but mostly stalled at the
moment, include: actions for an easier installation and availability
on mainstream Linux distributions; a new localization process, now
progressing in the l10n40 branch; a rewritten OOXML filter,
allowing import and (later) export.

The download trend remains very strong: Apache OpenOffice passed the
130 million downloads at the end of 2014.

15 Oct 2014 [Andrea Pescetti / Jim]

Apache OpenOffice is an open-source, office-document productivity
suite providing six productivity applications based around the
OpenDocument Format (ODF). OpenOffice is released on multiple
platforms and in dozens of languages.

### Issues for Board Awareness

The Apache OpenOffice community is currently focusing on attracting
new volunteers in code development. This is working well for the
initial involvement and simple code contributions, but we need to
have more resources available for the second step, i.e., mentoring
more significant code contributions. This may require a shift of
internal responsibilities in the project, which in turn may result
in slower activity in some areas.

### Community Development/Outreach Progress

The project did not invite new committers or PMC members since the
last report. The latest committer addition is from May 2014 (tal)
and the latest PMC addition is from November 2013 (fanyuzhen).

Thanks to a recent effort focused on new code volunteers, we are now
seeing many more patches and contributions coming from new
volunteers, but at the same time we are witnessing a reduced level
of activity (in terms of both contributed lines of code and e-mails
to the dev list) from more experienced developers. This will need to
be monitored closely, as the project needs both new and experienced
developers for a smooth progress.

The OpenOffice custom infrastructure (wiki, forum) is still in a
"minimal maintenance" mode. The infrastructure team internal to the
OpenOffice project is insufficient and mostly inactive. Apache Infra
has been providing support and (when possible) timely notifications,
thus easing the task of the internal team.

Several volunteers are getting involved by updating our many native
language websites with the more recent approach (editing the HTML
files rather than working through the CMS).

A new documentation effort for an end-users manual under the ALv2
licence is progressing more slowly than expected on the OpenOffice
Wiki, even though new volunteers show up regularly.

The localization community is growing: OpenOffice 4.1.1, released
21 August 2014, is fully released in 41 languages, 3 of which
(Catalan, Valencian AVL, Valencian RACV) are new with respect to
version 4.1.0.

A survey to know about existing volunteers and their unexpressed
potential (i.e., reasons that may limit their contributions to fewer
fields than the ones they could actually be active in) was launched,
with the aim of analyzing and presenting results by ApacheCon EU.

OpenOffice will have a dedicated track at ApacheCon Budapest, with
talks spanning all the main project areas. But most of the project
committers will not attend the event despite the good location
and promotion, probably a symptom that we need to investigate
other event formats in addition to ApacheCon.

The mailing lists for user support, localization, QA are quite
active, the marketing and documentation lists are moderately active.
Activity in social media is still good. The developer (dev) list
remains very active in terms of messages posted. Community support
forums remain popular with users, with an average of over 100 posts
per day.

### Product/Project Development Progress

Apache OpenOffice 4.1.1, a bugfix release introducing stability and
security fixes, as well as new languages, was published on 21 August
2014.

Activities that are still ongoing, but at a slower pace than
expected, include: actions for an easier installation and
availability on mainstream Linux distributions; a new localization
process, now progressing in the l10n40 branch; a rewritten OOXML
filter, allowing import and (later) export.

The download trend remains very strong: Apache OpenOffice reached
120 million downloads at the end of September 2014.

16 Jul 2014 [Andrea Pescetti / Ross]

Apache OpenOffice is an open-source, office-document productivity
suite providing six productivity applications based around the
OpenDocument Format (ODF). OpenOffice is released on multiple
platforms and in dozens of languages.

### Issues for Board Awareness

The mail outage experienced by Apache last May is unacceptable
both for a reputable foundation like the ASF and for a
well-established project like OpenOffice.  We appreciate that the
Foundation is now aware that a well-working infrastructure is a
priority and that steps are being taken to guarantee a higher
quality of service.

### Community Development/Outreach Progress

The project added 1 new committer (May: tal) since our last report
in April. The new committer is involved in localization and website
improvements. No new PMC members since November 2013 (fanyuzhen).

The OpenOffice custom infrastructure (wiki, forum) is still in a
"minimal maintenance" mode. We are now starting to address the queue
of improvements requested by the community, but faster reaction
times are needed. The infrastructure team internal to the OpenOffice
project is insufficient and lacks coordination. We are
progressively standardizing on the Infra processes to minimize the
amount of "non-standard" sysadmin work needed.

Several volunteers engaged in translating the website to their
language by simply editing the HTML files; this proved to work
better in our case than sending people to the Apache CMS and asking
them to send patches.

We have new volunteers and new developments in the main website
too, with a completely reworked download section and more visibility
for localized websites thanks to a new language drop-down.

A new documentation effort for an end-users manual under the ALv2
licence is progressing more slowly than expected on the OpenOffice
Wiki, even though new volunteers show up regularly.

The localization community is growing: OpenOffice 4.1, released
29 April 2014, is fully released in 38 languages, 6 of which
(Bulgarian, Danish, Hebrew, Hindi, Norwegian Bokmal and Thai)
were new with respect to version 4.0.

OpenOffice had a dedicated track during ApacheCon Denver and
is set to have one during ApacheCon Budapest too, judging by the
number of submitted talk proposals.

The mailing lists for user support, localization, QA are quite
active, the marketing and documentation lists are moderately active.
Activity in social media is progressing well. The developer (dev)
list remains very active.

Community support forums remain popular with users, with an average
of over 100 posts per day. The online users counter reached two peaks
in May (359) and July (404). As for graphics, the forum header is
now consistent with the Extensions and Templates sites.

### Product/Project Development Progress

Apache OpenOffice 4.1.0, a release with some major improvements
including IA2 accessibility, OOXML compatibility, Mac OS X specific
features (64-bit application), replacement of outdated Mozilla code
with the NSS libraries, was published on 29 April 2014.

A bugfix release, Apache OpenOffice 4.1.1, is expected in August.
It will contain bugfixes and a few new translations.

Activities that are still ongoing include: actions for an easier
installation and availability on mainstream Linux distributions; a
new localization process, now progressing in the l10n40 branch; a
redesign of the build approach, dropping the historical dmake;
a rewritten OOXML filter, allowing import and (later) export.

The download trend remains very strong: Apache OpenOffice celebrated
100 million downloads on 17 April 2014.

16 Apr 2014 [Andrea Pescetti / Chris]

Apache OpenOffice is an open-source, office-document productivity
suite providing six productivity applications based around the
OpenDocument Format (ODF). OpenOffice is released on multiple
platforms and in dozens of languages.

Issues for Board Awareness
---------------------------

https://issues.apache.org/jira/browse/LEGAL-190 was opened to
check whether we need to have uniform ADA (Americans with
Disabilities Act) statements for all the public websites of the
Apache projects.

Community Development/Outreach Progress
---------------------------------------

The project added 3 committers (January: rbd; February: clarence_guo;
March: astepukonis) since our last report in January. The new
committers are involved in QA, development, localization. No new
PMC members since November 2013 (fanyuzhen).

The OpenOffice custom infrastructure (wiki, forum) is still in a
"minimal maintenance" mode. Important fixes get applied timely, but
many improvements requested by the community have been in queue for
months. The infrastructure team internal to the OpenOffice project
is insufficient and cannot work effectively due to disagreements on
the system administration policy. The best option seems to
progressively standardize on the Infra processes and minimize the
amount of "non-standard" sysadmin work needed.

Experimental solutions to make website translation easier have
been tested. The first ones are already online and we are engaging
new volunteers.

A new documentation effort for an end-users manual under the ALv2
license is progressing on the OpenOffice Wiki.

The localization community is growing: OpenOffice 4.1, expected
mid-April, will be fully released in 38 languages, 6 of which
(Bulgarian, Danish, Hebrew, Hindi, Norwegian Bokmal and Thai)
are new with respect to version 4.0.

OpenOffice co-organized a track (devroom) at FOSDEM, a major
European free and open source software conference, in February 2014
and will have a dedicated track during ApacheCon Denver.

The mailing lists for user support, localization, QA are quite
active, the marketing list is moderately active. Activity in social
media is progressing well. The developer (dev) list remains very
active.

Community support forums remain popular with users, with an average
of over 100 posts per day.

In the previous report OpenOffice mentioned that the new policy
announced for Apache Extras http://s.apache.org/hzJ would have been
a major problem. But three months later no complaints were seen on
the dev list. It must be considered, though, that in the past months
the focus was mainly on consolidating the 4.1 release, so no
external libraries like the ones hosted in Apache Extras were
updated.


Product/Project Development Progress
------------------------------------

Apache OpenOffice 4.1.0, a release with some major improvements
including IA2 accessibility, OOXML compatibility, Mac OS X specific
features (64-bit application), replacement of outdated Mozilla code
with the NSS libraries, is currently in Release Candidate phase and
is expected to be approved mid-April. Apache OpenOffice 4.1.0-beta
was officially voted and released for public testing on 10 March
2014.

Activities that are still ongoing include: actions for an easier
installation and availability on mainstream Linux distributions; a
new localization process, now progressing in the l10n40 branch; a
redesign of the build approach, dropping the historical dmake;
implementation of export to OOXML formats.

The download trend remains very strong, with about 95 million
downloads of Apache OpenOffice as of 31 March 2014.

19 Feb 2014 [Andrea Pescetti / Doug]

An issue about ADA (Americans with Disabilities Act) statements has
been opened at https://issues.apache.org/jira/browse/LEGAL-190
to investigate complaints about ADA compliance of the Apache/OpenOffice
web sites.

15 Jan 2014 [Andrea Pescetti / Doug]

Apache OpenOffice is an open-source, office-document productivity
suite providing six productivity applications based around the
OpenDocument Format (ODF). OpenOffice is released on multiple
platforms and in dozens of languages.

Issues for Board Awareness
---------------------------

OpenOffice depends on code stored at Apache Extras for its binary
releases. It is unclear whether Apache Extras will adopt the same
policy as Google Code http://s.apache.org/hzJ but, if it does, this
will be a major problem for OpenOffice starting 15 January. In
earlier conversations on the Infra list this was determined to be
a ComDev issue and there were no public updates so far about it.

Community Development/Outreach Progress
---------------------------------------

The project added 6 committers (October: fanyuzhen, bourock, wlada;
November: knmc, joesch; December: hanya) and one PMC member
(November: fanyuzhen) since our last report in October.

The new committers span different areas of expertise: development,
QA, localization, documentation, extensions, user support in native
languages.

A new documentation effort for an end-users manual under the ALv2
license is progressing well on the OpenOffice Wiki, and materials
from an "OpenOffice for students" guide have been made available
and are being integrated.

The OpenOffice custom infrastructure (wiki, forum) is still in a
"minimal maintenance" mode, with many improvements waiting to be
implemented. A proposal to move forward in a way that is also
acceptable by Infra has recently received consensus; a team is
forming and we are looking forward to offer professional and
responsive infrastructure support to the project community members.

Experimental solutions to make website translation easier have
been tested. The first pilot languages are already online.

The localization community is growing, with 5 localizations
(Bulgarian, Danish, Hindi, Norwegian Bokmal, Thai) reaching 100%
since the last report.

There is a growing interest on the mailing list from new volunteers
who would like to help with simple core development tasks.

OpenOffice will co-organize a track (devroom) at FOSDEM, a
major European free and open source software conference, to be held
1-2 February 2014 in Brussels, Belgium. Several project developers
will be presenting their latest work and the upcoming features.

Community support forums remain popular with users, with an average
of over 100 posts per day. The community also reached consensus on
a new graphical identity, to be implemented as part of the pending
tasks.

The mailing lists for user support, localization, QA and marketing
are quite active. Activity in social media is progressing well. As
Apache OpenOffice is a client product, we continue to investigate
ways to direct users to appropriate support venues. The developer
(dev) list remains very active.

Product/Project Development Progress
------------------------------------

Apache OpenOffice 4.0.1, a maintenance release, was released on
1 October 2013.

A possible "language update" release of Apache OpenOffice 4.0.1 to
include the 5 additional languages now ready for release (Bulgarian,
Danish, Hindi, Norwegian Bokmal, Thai) is being discussed, with a
tentative release date in late January.

Version 4.1.0, with a tentative release date in early April, will
feature several improvements, including the IA2 accessibility work
and the replacement of outdated Mozilla code with the NSS libraries:
both are already merged to trunk and now being tested.

Activities that are still ongoing for the next release include:
the rejuvenate01 branch, to explore using native platform
capabilities and libraries for building; actions for an easier
installation and availability on mainstream Linux distributions; a
new localization process, now progressing in the l10n40 branch; a
redesign of the build approach, dropping the historical dmake.

The download trend remains very strong, with 85 million downloads of
Apache OpenOffice as of 31 December 2013.

16 Oct 2013 [Andrea Pescetti / Roy]

Apache OpenOffice is an open-source, office-document productivity
suite providing six productivity applications based around the
OpenDocument Format (ODF). OpenOffice is released on multiple
platforms and in dozens of languages.

Issues for Board Awareness
---------------------------

OpenOffice, like the ASF as a whole, is hit by the announced policy
change of Apache Extras. The project hopes that a solution will be
found at the ASF level.

Community Development/Outreach Progress
---------------------------------------

The project added 3 committers (July: elish, christef; August: sebb)
since our last report in July. The last PMC addition is jani (April
2013).

The new committers span different areas of expertise, ranging from
QA to localization, recruitment of new volunteers, website updates
and procedural advice.

A new documentation effort for an end-users manual under the ALv2
licence is progressing well on the OpenOffice Wiki.

The OpenOffice forum infrastructure was successfully updated last
Summer. The OpenOffice custom infrastructure is now in a "minimal
maintenance" mode, and the project could benefit from more
volunteers helping with infrastructure work and more well-defined
processes for system administration. A proposal is currently under
preliminary discussion, with contributions from Infra.

Experimental solutions to make website translation easier are
being developed, with a couple of translated versions of the
website close to completion.

New versions of the Extensions and Templates sites, externally
hosted, were put online in the last months.

OpenOffice participated in the Google Summer of Code program for
the first time after several years.

OpenOffice was accepted for a track (devroom) at FOSDEM, a
major European free and open source software conference, to be held
1-2 February 2014 in Brussels, Belgium.

Community support forums remain popular with users: on the
English forum, registered users reached 60,000 on 17 September and
the forum hit 300 users online, a new traffic record.

The mailing lists for user support, localization, QA and marketing
are quite active. Activity in social media is progressing well. As
Apache OpenOffice is a client product, we continue to investigate
ways to direct users to appropriate support venues. The developer
(dev) list remains very active.

Product/Project Development Progress
------------------------------------

Apache OpenOffice 4.0 was released on 23 July 2013, followed by
another release, Apache OpenOffice 4.0.1, on October 1st.

Version 4.0 featured a new, more modern, user interface, a
reworked directory layout to simplify development and installation,
code updates to allow building on newer platforms and 23 languages.

Version 4.0.1 added 9 languages (some of which hadn't been updated
in years) and important bugfixes. The additional translations were
made possible by the community growth and the availability of new
volunteers.

Activities that are already ongoing for the next release include:
the rejuvenate01 branch, to explore using native platform
capabilities and libraries for building; the IA2 accessibility work;
actions for an easier installation and availability on mainstream
Linux distributions; a new localization process, now progressing in
the l10n40 branch; a build approach that is progressively dropping
the historical dmake in favor of GNU make.

The download trend remains very strong, with over 70 million
downloads of Apache OpenOffice so far.

17 Jul 2013 [Andrea Pescetti / Greg]

Apache OpenOffice is an open-source, office-document productivity
suite providing six productivity applications based around the
OpenDocument Format (ODF). OpenOffice is released on multiple
platforms and in dozens of languages.

Issues for Board Awareness
---------------------------

OpenOffice, like the ASF as a whole, is hit by the announced policy
change of Apache Extras. The project currently stores several libraries
there, in an area known as ooo-extras, and the build process downloads
them when options like --enable-category-b are used. A solution should
be found at the ASF level.

Community Development/Outreach Progress
---------------------------------------

The project added 4 committers (May: dwhytock, akerbeltz, vkadal;
July: pmralbuquerque) and one new PMC member (April: jani) since our
last report in April.

These new committers are primarily involved in the translation efforts
to incorporate additional native language capability into Apache
OpenOffice. Our new PMC member has many years of experience in open
source, and is assisting in administration of our LAMP servers.

A new documentation effort for an end-users manual under the ALv2
licence was started on the OpenOffice Wiki and is progressing well.

OpenOffice is participating in the Google Summer of Code program for
the first time after several years.

Community support forums remain popular with users. The mailing lists
for user support, localization, QA and marketing are quite active. As
Apache OpenOffice is a client product, we continue to investigate ways
to direct users to appropriate support venues. The developer list,
ooo-dev, remains very active.

Product/Project Development Progress
------------------------------------

We will be releasing Apache OpenOffice 4.0 in July, likely the week
of July 15.

This release will feature a new, more modern, user interface, a
reworked directory layout to simplify development and installation,
code updates to allow building on newer platforms and (at least) 23
languages.

AI: Greg: discuss "extras" issue with PMC and see if there is anything to be done at the "ASF level"

17 Apr 2013 [Andrea Pescetti / Sam]

Apache OpenOffice is an open-source, office-document productivity
suite providing six productivity applications based around the
OpenDocument Format (ODF). OpenOffice is released on multiple
platforms and in dozens of languages.

Issues for Board Awareness

The project had a long policy discussion on veto powers and code
reverts: the discussion was difficult also due to uncertainties about
the Apache policy, now clarified after an articulated discussion on the
members list; this will reduce the risk of similar discussions to
happen again in future. This remained an isolated incident.

Community Development/Outreach Progress
---------------------------------------

The project added a new committer, Samer Mansour.

Blog posts calling for new development, documentation, QA, design
volunteers have proved successful, with many new people contacting the
mailing lists and some providing sustained contributions to the
discussions and activities. Orientation modules for new volunteers were
made available, to simplify introduction of new volunteers.

Apache OpenOffice participated in FOSDEM 2013 in Brussels, with a
booth for two days and a dedicated track (devroom) for a full day of
technical talks, and in ApacheCon NA in Portland, with presentations
and meetings.

The OpenOffice Wiki, running on MediaWiki, was very unstable. It has
been fresh installed on a new vm and updated to the latest release
under the guidance of Infra, and is now stable, documented and
maintained.

A new documentation effort for an end-users manual under the ALv2
license was started on the OpenOffice Wiki.

A new project logo is currently being selected for version 4.0.

A small team of volunteers was created to take care of the LAMP virtual
machines used for the OpenOffice Wiki, the OpenOffice Forum and an
ASF-wide new Pootle server for software translations. The Apache
Infrastructure team is providing guidance and support. The OpenOffice
infrastructure needs have been discussed with Infra to allow proper
planning and budgeting.

Community support forums remain popular with users. The mailing lists
for user support, localization, QA and marketing are quite active. As
Apache OpenOffice is a client product, we continue to investigate ways
to direct users to appropriate support venues. The developer list,
ooo-dev, remains very active.

Product/Project Development Progress
------------------------------------

The project released an update to version 3.4.1 in late January,
to include 8 new language translations made available by volunteers.

The next OpenOffice release will be labeled 4.0. Plans are to release
in June, 2013.

New ports, languages and other distribution channels are expected. The
new release in June will be provided in many more native languages. New
volunteers have come forth to assist with this effort. Build work has
started for reinstating OpenOffice into Linux repositories, currently
Fedora at this time.

The source tree has been cleaned of non en-US messages (these are
now kept in external files) allowing normal translation of these parts.

A new localization process, eventually leading to a more efficient
translation workflow and a massive cleanup of tools and intermediate
formats, is being implemented. The toolset is independent of OpenOffice
and can be easily adopted by other projects especially in combination
with the new translate/Pootle server.

Most of the work towards version 4.0 is being done in branches, with
integration to trunk expected to begin soon. Buildbots and QA tests
cover both trunk and branches, to guarantee optimal coverage.

Work is beginning on a Strategic Plan for the project. The plan will
likely be sub-divided into various components: Web/Wiki, User Support,
Documentation, Project: General, Project: Writer, Project: Calc,
Project:Base, etc. We anticipate this will be a rather lengthy process
involving both volunteers and our end users.

16 Jan 2013 [Andrea Pescetti / Brett]

Apache OpenOffice is an open-source, office-document productivity
suite providing six productivity applications based around the
OpenDocument Format (ODF). OpenOffice is released on multiple
platforms and in dozens of languages.

Issues for Board Awareness

None at this time.

Community Development/Outreach Progress

Recruiting new volunteers for the project through announcements on
the website is proving very effective. The current effort, after a
successful call for translation volunteers, is aimed at finding Quality
Assurance volunteers willing to help with early testing of OpenOffice
4.0, due later in 2013. The volunteers mailing lists keep growing in
traffic and diversity of posters.

We continue to use social networking accounts – Google +, Facebook – to
collect feedback and ideas from our user base. A Google+ community was
recently started. An initiative called "Ask OpenOffice" was run to
collect the top 10 non-support questions from our users, which were then
discussed on the dev mailing list and answered in a blog post.

We have several volunteers ready to attend FOSDEM (February 2013,
Brussels, Belgium) where the Apache OpenOffice project will have a
dedicated track for developers ("devroom") and a stand for the whole
conference. We also submitted talks for the ApacheCon NA in Portland
and we'll have several volunteers attending it too.

Project Development Progress

The graduation process can be considered complete. All relevant
resources have been fully migrated.

The next OpenOffice release will be labelled 4.0. Plans are to release
around April 2013. Volunteers have taken responsibility for the major
new features, which are being documented for developers and for users
on the project wiki.

The project prepared test snapshots for new languages of OpenOffice
3.4.1 (the current stable version), with the aim of releasing at least
8 new languages in late January. The project will release an update to
the 3.4.1 sources (including the new translation resources) and binary
packages for the added languages only.

Community support forums remain popular with users.
The mailing lists for user support and localization are quite active,
and those for QA and marketing are fast growing. As Apache OpenOffice
is a client product, we continue to investigate ways to direct users to
appropriate support venues. The developer list, ooo-dev, remains very
active.

19 Dec 2012 [Andrea Pescetti / Sam]

Apache OpenOffice is an open-source, office-document productivity
suite providing six productivity applications based around the
OpenDocument Format (ODF). OpenOffice is released on multiple
platforms and in dozens of languages.

* Issues for Board Awareness

The graduation process, as expected, was non-trivial and involved
migration of multiple resources. Infra was very helpful, but it
took about 7 weeks before the main resources could be considered
to be fully migrated.

* Community Development/Outreach Progress

A major effort is ongoing to recruit new volunteers for the project,
through announcements on the website, blog posts and calls on the
ooo-announce list. We managed to recruit volunteers for translation
(about 20 new languages), Quality Assurance and Marketing. The dedicated
mailing lists are now seeing a strong increase in traffic and diversity
of posters.

We continue to use social networking accounts - Google +, Facebook - to
collect feedback and ideas from our user base. A Google+ community was
recently started. An initiative called "Ask OpenOffice" was launched too,
to collect the top 10 non-support questions from our users: they will be
answered in a blog post, to help users reach a better understanding of
OpenOffice at Apache.

Dozens of project volunteers attended the 3-day OpenOffice track at
ApacheCon EU, often meeting in person for the first time; the ApacheCon
experience allowed volunteers to discuss about the project, to get media
exposure and to learn more about the Apache Foundation and the Apache Way.

We have several volunteers ready to attend FOSDEM (February 2013, Brussels,
Belgium) where the Apache OpenOffice project will have a dedicated track
for developers ("devroom") and, pending final approval by FOSDEM, a stand
for the whole conference. We also submitted talks for the ApacheCon NA in
Portland and we'll have several volunteers attending it too.

* Project Development Progress

The next OpenOffice release will be labelled 4.0. Plans are to release
it in Q1 2013 or shortly after. Volunteers are stepping up to take
responsibility for the major new features, opening wiki pages to document
their progress and inviting other potential developers to join.

The project will also release new languages for OpenOffice 3.4.1 (the
current stable version), with a translation deadline set to end of 2012 and
a release expected in January 2013. The project will release an update to
the 3.4.1 sources (including the new translation resources) and binary
packages for the added languages only.

The project added 3 new committers since the graduation date.

Community support forums remain popular with users.
The mailing lists for user support and localization are quite active, and
those for QA and marketing are fast growing. As Apache OpenOffice is a
client product, we continue to investigate ways to direct users to
appropriate support venues. The developer list, ooo-dev, remains very
active.

21 Nov 2012 [Andrea Pescetti / Brett]

Apache OpenOffice entered incubation 2011-06-13 and graduated from the
Incubator on 2012-10-17.
OpenOffice is an open-source, office-document productivity suite providing
six productivity applications based around the OpenDocument Format (ODF).
OpenOffice is released on multiple platforms. Its localizations support 110
languages worldwide.

As the project graduated very recently, this report still focuses on the
pre-graduation phase and uses the pre-graduation template.

MOST IMPORTANT ITEMS TO ADDRESS TOWARD GRADUATION

OpenOffice graduated in October. To that aim, the project since the last
report had:
1. chosen a PMC with public nominations on the ooo-dev list
2. elected a PMC chair
3. carefully checked the compliance of code in its repository with the Apache
rules.

ISSUES FOR IPMC OR ASF BOARD AWARENESS

No new issues at this time.

COMMUNITY DEVELOPMENT/OUTREACH PROGRESS

We are increasing our global reach by recruiting volunteers to help update
and maintain the large set of native language home pages and to update the
OpenOffice translations into several languages. We managed to recruit new
translation volunteers and get them involved in the project.

Because our product is client-centric, we have put additional focus on our
social networking accounts - Google +, Facebook - in collecting feedback and
ideas from our user base. For example, 1260 users proposed ideas for
OpenOffice 4.0 in a survey we conducted using Google Moderator.

In anticipation of additional growth post-graduation, we are developing
web pages to support new volunteers, especially in the localization
and QA areas.

We are also looking at conferences and events to increase our outreach: after
ApacheCon, we will have a strong presence at FOSDEM (February 2013, Brussels,
Belgium) where the Apache OpenOffice project will have a dedicated track for
developers ("devroom").

PROJECT DEVELOPMENT PROGRESS

We started discussing plans for the next OpenOffice release. It will contain
several new features and it will probably be labelled 4.0. Plans are to
release it in Q1 2013 or shortly after.

Community support forums remain popular with users. The English forum reached
50,000 members in June (or, if we remove the spam accounts which manage to go
through, in September 2012, almost 5 years after its creation). The ooo-users
list also is quite active and the localization list ooo-L10N is fast growing.
As Apache OpenOffice is a client product, we continue to investigate ways to
direct users to appropriate support venues.

The developer list, ooo-dev, remains very active.

17 Oct 2012

Establish the Apache OpenOffice Project

 WHEREAS, the Board of Directors deems it to be in the best
 interests of the Foundation and consistent with the Foundation's
 purpose to establish a Project Management Committee charged with
 the creation and maintenance of open-source software, for
 distribution at no charge to the public, related to the OpenOffice
 personal productivity applications.

 NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
 (PMC), to be known as the "Apache OpenOffice Project", be and hereby
 is established pursuant to Bylaws of the Foundation; and be it
 further

 RESOLVED, that the Apache OpenOffice Project be and hereby is
 responsible for the creation and maintenance of software related to
 the OpenOffice personal productivity applications; and be it further

 RESOLVED, that the office of "Vice President, OpenOffice" be and
 hereby is created, the person holding such office to serve at the
 direction of the Board of Directors as the chair of the Apache
 OpenOffice Project, and to have primary responsibility for
 management of the projects within the scope of responsibility of
 the Apache OpenOffice Project; and be it further

 RESOLVED, that the persons listed immediately below be and hereby
 are appointed to serve as the initial members of the Apache
 OpenOffice Project:

     * Andre Fischer (af)
     * Andrea Pescetti (pescetti)
     * Andrew Rist (arist)
     * Ariel Constenla-Haile (arielch)
     * Armin Le Grand (alg)
     * Dave Fisher (wave)
     * Donald Harbison (dpharbison)
     * Drew Jensen (atjensen)
     * Ian Lynch (ingotian)
     * Jürgen Schmidt (jsc)
     * Kay Schenk (kschenk)
     * Kazunari Hirano (khirano)
     * Louis Suarez-Potts (louis)
     * Marcus Lange (marcus)
     * Oliver-Rainer Wittmann (orw)
     * Pedro Giffuni (pfg)
     * Peter Junge (pj)
     * Raphael Bircher (rbircher)
     * Regina Henschel (regina)
     * RGB.ES (rgb-es)
     * Roberto Galoppini (galoppini)
     * Yang Shih-Ching (imacat)
     * Yong Lin Ma (mayongl)

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Andrea Pescetti be
 appointed to the office of Vice President, OpenOffice, to serve in
 accordance with and subject to the direction of the Board of
 Directors and the Bylaws of the Foundation until death,
 resignation, retirement, removal or disqualification, or until a
 successor is appointed; and be it further

 RESOLVED, that the initial Apache OpenOffice Project be and hereby
 is tasked with the creation of a set of bylaws intended to
 encourage open development and increased participation in the
 OpenOffice Project; and be it further

 RESOLVED, that the Apache OpenOffice Project be and hereby is tasked
 with the migration and rationalization of the Apache OpenOffice.org
 podling; and be it further

 RESOLVED, that all responsibilities pertaining to the Apache
 Incubator OpenOffice.org podling encumbered upon the Apache
 Incubator Project are hereafter discharged.

 Special Order 7F, Establish the Apache OpenOffice Project, was
 approved by Unanimous Vote of the directors present.

19 Sep 2012

OpenOffice entered incubation 2011-06-13
OpenOffice is an open-source, office-document productivity suite providing
six productivity applications based around the OpenDocument Format (ODF).
OpenOffice is released on multiple platforms. Its localizations support
have supported 110 languages worldwide.

Most Important Items To Address Toward Graduation

 1. We are discussing the makeup of the future PMC. This will be a slow
    process as we digest input from our Mentors. We are separating our
    discussion about who should be a PMC member from what makes an ideal
    PMC member. The first will remain private for now and the second will
    be renewed on ooo-dev.

 2. We have begun discussing the Chair.

 3. Continue our review of distributed articles to ensure compliance
    with ASF policy.

 We are working to fulfill graduation requirements in the next quarter.

Issues for IPMC or ASF Board Awareness

 No new issues at this time.

 In regards to the ooo-private leak reported on our last report. The PPMC
 is satisfied with the result. The Board is aware of the result as well.
 If this issue needs further discussion please ask on ooo-private.

Community Development/Outreach Progress

 There are now 110 committers with 72 of those on the PPMC. Relative to the
 last report, that is an increase of 15 committers and a decrease of
 3 committers on the PPMC (following an audit to reconcile subscribers to
 the ooo-private mailing list).

 We have improved to act more as a self organized project to address and
 solve project related topics (e.g. forum moderation)

 We are putting more effort into addressing trademark and third-party
 distribution requests. Ongoing emphasis as to how to accommodate and
 track these requests is becoming an important concern.

 We are increasing our global reach by recruiting volunteers to help
 update and maintain the large set of native language home pages

 Because our product is client-centric, we have put additional focus on our
 social networking accounts - Google +, Facebook - in collecting feedback
 and ideas from our user base.

Project Development Progress

 We released Apache OpenOffice 3.4.1 on August 23, 2012. This was primarily
 a maintenance release and included:

 - Official Source tarballs in English
 - Six different client platform convenience install versions in 19 languages
 - Software development kit packaging for 5 platforms
 - Language packs for 19 languages
 - Fixes for 69 bugs and an important security fix
 - Over 1.4M downloads the first week.

 A summary of downloads for the installs can be found at:
 http://sourceforge.net/projects/openofficeorg.mirror/files/stats/timeline

 The build artifacts in this last source release do not strictly follow
 guidelines as some fallback downloads of dependencies do access svn.a.o.
 This has been fixed in trunk by eliminating the use of svn in all cases.

 Testing and implementation of old update service for OpenOffice has been
 accomplished. This service is for older OpenOffice clients to identify
 updates and, optionally, install an update if available. Older versions
 of OpenOffice (3.1 and less) are problematic when we turned these on it
 created a DDOS attack on www.apache.org which we regret.

 The IBM Symphony code (mentioned in the June report) was brought into svn
 in mid-May. There was discussion on the ooo-dev list about how best to
 use/integrate this contribution. After some discussion, the community was
 most in favor of integrating Symphony aspects into the current AOO base
 over a period of time, rather than the reverse.

 Community support forums remain popular with users but registration seems
 to have stabilized. The ooo-users list also is quite active. As Apache
 OpenOffice is a client product, we continue to investigate ways to direct
 users to appropriate support venues.

 The developer list, ooo-dev, now has more than 440 subscribers and remains
 very active.

Signed-off-by: rgardler, jukka

20 Jun 2012

* OpenOffice entered incubation 2011-06-13

OpenOffice is an open-source, office-document productivity suite providing
six productivity applications based around the OpenDocument Format (ODF).
OpenOffice is released on multiple platforms.  Its localizations support
have supported 110 languages worldwide.

Most Important Items To Address Toward Graduation

 1. Review of distributed articles to ensure compliance with ASF policy
 2. Given the size and scope of OpenOffice, continue work on "community
    readiness" especially with regard to organization and communication style.

We have started preliminary discussion concerning graduation as we would
like to propose graduation within the next month.

Issues for IPMC or ASF Board Awareness

 - Leaks from ooo-private to outside agencies

 Possible leaks of information from the ooo-private email list are
 being investigated. Our first objective is to first establish if and
 how leaks occurred. Once full details are available we will be working
 to address the issue directly. No action is currently required from
 the board and an update will be provided, at the latest, in our next
 report.

Community Development/Outreach Progress

 Since our last report we have voted in 13 new Committers/PPMC members.

 Since our last report, 2 committer/PPMC members have resigned

 We have improved to act more as a self organized project to address
 and solve project related topics (e.g. forum moderation)

 We were able to initiate transfer of SPI funds formerly earmarked for
 OpenOffice.org to the ASF. However, due to changes in the ASF Fundraising
 chair, this transfer has been postponed. Followup with ASF Fundraising is
 needed to complete this transaction. These funds, as previously discussed,
 will primarily be used for developer travel when needed.

 We accepted an offer from SourceForge to host our older 3.3 version and
 provide client installs of latest release 3.4. This event was accomplished
 after much discussion among members and consultation with mentors.

 Due to heightened interest, we are putting more resources (services,
 volunteers) into translation efforts

 We are more putting effort into addressing trademark and third-party
 distribution requests. Ongoing emphasis as to how to accommodate and track
 these requests is becoming an important concern.

 We are increasing our global reach by recruiting volunteers to help update
 and maintain the large set of native language home pages

 Established various social programming accounts for additional outreach:
 Twitter, Google+, Facebook

 Setup two additional native language mailing lists

Project Development Progress

 Pootle services for the project were established and used. Translation
 services will be ongoing as new contributors for this service join.

 We released Apache OpenOffice 3.4 on May 8, 2012. This release included:
 - Six different client platform install versions in 15 languages
 - Source tarballs in English
 - Software development kit packaging for 5 platforms
 - Language packs for 15 languages
 Over 3 million downloads the first month.
 A summary of downloads for the installs can be found at:
 http://sourceforge.net/projects/openofficeorg.mirror/files/stats/timeline

 We are currently working on an alternate repository for category-B code
 to comply with graduation requirements

 An SGA was received from IBM for IBM Lotus Symphony. We are now preparing
 to import IBM Symphony changes into the OpenOffice repository. This should
 be complete by the time of the June board meeting.

 We are putting renewed effort into the "user experience". Apache OpenOffice
 is an end-user product, the best quality product and best experience for
 end users is one of our primary goals.

 Testing and implementation of old update service for OpenOffice has been
 accomplished. This service is for older OpenOffice clients to identify
 updates and, optionally, install an update if available.

 Community support forums remain popular with users but registration seems
 to have stabilized. The ooo-users list also is quite active. As Apache
 OpenOffice is a client product, we continue to investigate ways to direct
 users to appropriate support venues.

 Spam issues with the support Forums (reported in March) has been completely
 eradicated from community English forum with new counter measures (new
 users moderation and new moderators).

 A new root admin (imacat) has been promoted and is now taking the job to
 insure smooth running and consistency with infra requirements.

 The developer list, ooo-dev, now has 409 subscribers and is very active
 with post averaging about 100 per day

Signed off by mentor: joes, rgardler

18 Apr 2012

Out-of-Band Report

On March 22nd we issued a security bulletin and patch for a vulnerability
reported in OpenOffice.org 3.3, the last released pre-Apache version of
OpenOffice.

Technical details of the issue and patch can be found in this announcement:

http://mail-archives.apache.org/mod_mbox/incubator-ooo-announce/201203.mbox/%3CCAP-ksoj7o5%2B2YH-E4XzR044V0e3YZfZvuef7eJuNGhdy%2Bk9kyA%40mail.gmail.com%3E

The IPMC and Board should note that this extraordinary patch was made
available, as a courtesy to the ecosystem, based on the severity of the
reported vulnerability and the ease of exploiting it.  The patch was made
available under ALv2, and distribution was done via the Apache mirrors,
although this did not constitute an official release.

Because of the required secrecy around the preparation of such security
patches, a minimum number of Apache members were involved in vetting this
release, though we did try to touch all bases by involving mentors, Infra
and Legal Affairs.

Signed off by mentor: joes, rgardler

21 Mar 2012

* OpenOffice entered incubation 2011-06-13

OpenOffice is an open-source, office-document productivity suite providing
six productivity applications based around the OpenDocument Format (ODF).
OpenOffice is released on multiple platforms.  Its localizations support
110 languages worldwide.

Most Important To Address:

 1. Completion of the IP-review portions of the incubation checklist
 2. A Successful Podling Release
 3. Increase size and diversity of the active development community

Issues for IPMC or ASF Board Awareness

 - None

Community Development Progress

 - Since our last report we have voted in 3 new Committers.
 - We have improved to act more as a self organized project to address
   and solve project related topics (e.g., budget transfer from SPI, forum
   moderation).
 - We accepted an offer from SourceForge to host our extension repository
   (host, upgrade, improve) as interim solution.
 - With the start of QA and translation effort, additional volunteers have
   now started becoming active in the project.
 - We continue to get trademark usage permission requests, including an
   interesting one to use Apache OpenOffice as "stage dressing" in a
   Hollywood motion picture.

Project Development Progress

 - We believe that all category-x copyleft code has been removed.
   Development focus has shifted to preparing our initial Podling Release
   (release 3.4)
 - Buildbot now doing nightly Linux 64bit and Windows builds.
   Linux 32bit and MacOS is in-progress.
 - Work on a working translation process has started. We restore and backup
   the old Pootle data, analyzed the data and the translation process.
   Work ongoing (very complex to understand the roundtrip)
 - Started organized QA work (manual testing + automated testing)
 - Provide weekly developer snapshots for Linux (32, 64 bit), Windows,
   MacOS and partly Solaris (x86)
 - Added script to build source packages for releases
 - Working on final pieces of infrastructure migration, including shut
   down of legacy openoffice.org email forwarder.
 - Community support forums remain popular with users, hitting a new
   concurrency record (296), but also seeing more spammers:
   http://user.services.openoffice.org/en/forum/viewtopic.php?p=222874#p222874

Signed off by mentor: rgardler, joes

21 Dec 2011

# OpenOffice (was OpenOffice.org)

* OpenOffice entered incubation 2011-06-13.

OpenOffice is an open-source, office-document productivity suite providing
six productivity applications based around the OpenDocument Format (ODF).
OpenOffice is released on multiple platforms.  Its localizations support 110
languages worldwide.

* Most Important To Address:

1) Completion of the IP-review portions of the incubation checklist

2) A Successful Podling Release

3) Increase size and diversity of the active development community


* Issues for IPMC or ASF Board Awareness

None


* Community Development Progress

Since our last report we have voted in 11 new Committers.

We have created a new ooo-marketing list.

We voted to change the name of the product from OpenOffice.org to Apache
OpenOffice.

The volunteers of the legacy OpenOffice.org user support forums have joined
the project and their forums are now hosted by Apache.


With assist from legal-discuss (special thanks to rdonkin and rubys) we now
have a much better idea of the license and notice requirements of source and
binary releases.

* Project Development Progress

Dev focus has been on IP review and replacement of copyleft dependencies.

Buildbot now doing nightly Linux builds.  Windows is in-progress.

Working on final pieces of infrastructure migration.

Working on notification of users for shutdown of openoffice.org email
forwarder.

26 Oct 2011

* OpenOffice.org entered incubation 2011-06-13.

OpenOffice.org is an open-source, office-document productivity suite
providing six productivity applications based around the OpenDocument Format
(ODF).  OpenOffice.org is released on multiple platforms.  Its localizations
support 110 languages worldwide.

* Most Important To Address

1) Migration of the legacy OpenOffice.org website's content and services to
Apache infrastructure, including defect tracking, wiki, forums, mailing
lists, and cross-service registration using customized software not already
supported by Apache projects and infrastructure.  Successful negotiation of
governance migration of user-supported services brought under incubation.
Resolution of copyright, license and notice for content migrated from
legacy OpenOffice.org website.

2) Completion of the IP-review portions of the incubation checklist, which
will require getting an amended SGA from Oracle to cover additional source
files; scrubbing of incompatible notices from SGA-licensed code and
resolving provenance of other existing materials being migrated.

3) A Successful Podling Release

* Issues for IPMC or ASF Board Awareness

Notices concerning encryption methods employed in code now in the podling
SVN have not been produced; legal-discuss is being consulted in regard to
product class for OpenOffice.org.

* Community Development Progress

As of 2011-09-12 there are 72 committers, with 55 on the PPMC, up from 71
and 52 at last report.  Eleven initial committers have failed to submit
iCLAs and are out of communication.

Discussion is underway with the operators of the existing OpenOffice.org
user-support forums for migration of the forums into the project, with
adjustment of governance to provide appropriate PPMC oversight.

We have created a ooo-users.i.a.o mailing list.  A Japanese-language
ooo-general-ja.i.a.o is also starting.

We have reviewed a request for permission to use the OpenOffice.org
trademark by a German book publisher, and sent our approval recommendation
to Apache Branding.

A "Building OpenOffice.org for Linux" buildfest was announced on the project
blog and carried out over the Internet in the first full week of September.


* Project Development Progress

The OpenOffice.org trademarks have been transferred to Apache.  The
OpenOffice.org domain-name registrations are being transferred to Apache.

The legacy OpenOffice.org Issue Tracking Bugzilla has been moth-balled as
read-only and an Apache Bugzilla established for continuation of Issue
Tracking under the podling.

The main source code base has been transferred to Apache SVN and is being
actively tested and modified.  Merging of additional work spaces from
OpenOffice.org, and preservation of versioning history is being pursued.
The current effort is focused on successful build of a counterpart of the
last complete build at OpenOffice.org.

Test configurations of the OpenOffice.org forum system and the
OpenOffice.org Wiki have been brought up on Apache infrastructure fixtures.
Cutover of the forum system is anticipated as part of the OpenOffice.org
migration.

Detailed planning continues on public wiki:
https://cwiki.apache.org/confluence/display/OOOUSERS/

21 Sep 2011

* OpenOffice.org entered incubation 2011-06-13.

OpenOffice.org is an open-source, office-document productivity suite
providing six productivity applications based around the OpenDocument Format
(ODF).  OpenOffice.org is released on multiple platforms.  Its localizations
support 110 languages worldwide.

* Most Important To Address

1) Migration of the legacy OpenOffice.org website's content and services to
Apache infrastructure, including defect tracking, wiki, forums, mailing
lists, and cross-service registration using customized software not already
supported by Apache projects and infrastructure.  Successful negotiation of
governance migration of user-supported services brought under incubation.
Resolution of copyright, license and notice for content migrated from
legacy OpenOffice.org website.

2) Completion of the IP-review portions of the incubation checklist, which
will require getting an amended SGA from Oracle to cover additional source
files; scrubbing of incompatible notices from SGA-licensed code and
resolving provenance of other existing materials being migrated.

3) A Successful Podling Release

* Issues for IPMC or ASF Board Awareness

Notices concerning encryption methods employed in code now in the podling
SVN have not been produced; legal-discuss is being consulted in regard to
product class for OpenOffice.org.

* Community Development Progress

As of 2011-09-12 there are 72 committers, with 55 on the PPMC, up from 71
and 52 at last report.  Eleven initial committers have failed to submit
iCLAs and are out of communication.

Discussion is underway with the operators of the existing OpenOffice.org
user-support forums for migration of the forums into the project, with
adjustment of governance to provide appropriate PPMC oversight.

We have created a ooo-users.i.a.o mailing list.  A Japanese-language
ooo-general-ja.i.a.o is also starting.

We have reviewed a request for permission to use the OpenOffice.org
trademark by a German book publisher, and sent our approval recommendation
to Apache Branding.

A "Building OpenOffice.org for Linux" buildfest was announced on the project
blog and carried out over the Internet in the first full week of September.


* Project Development Progress

The OpenOffice.org trademarks have been transferred to Apache.  The
OpenOffice.org domain-name registrations are being transferred to Apache.

The legacy OpenOffice.org Issue Tracking Bugzilla has been moth-balled as
read-only and an Apache Bugzilla established for continuation of Issue
Tracking under the podling.

The main source code base has been transferred to Apache SVN and is being
actively tested and modified.  Merging of additional work spaces from
OpenOffice.org, and preservation of versioning history is being pursued.
The current effort is focused on successful build of a counterpart of the
last complete build at OpenOffice.org.

Test configurations of the OpenOffice.org forum system and the
OpenOffice.org Wiki have been brought up on Apache infrastructure fixtures.
Cutover of the forum system is anticipated as part of the OpenOffice.org
migration.

Detailed planning continues on public wiki:
https://cwiki.apache.org/confluence/display/OOOUSERS/

17 Aug 2011

* OpenOffice.org entered incubation 2011-06-13.

OpenOffice.org is an open-source, office-document productivity suite
providing six productivity applications based around the OpenDocument Format
(ODF). OpenOffice.org is released on multiple platforms. Its localizations
support 110 languages worldwide.

* Issues

Some challenges exist: Under SUN/Oracle, semi-autonomous single focus
"projects" were the basis of structure of OOo, many would like a similar
system to be used under Apache. By contrast a single overarching authority
is proposed with oversight of the entire project by the (P)PMC. Discussions
are ongoing.

Discussions with regard to licensing, especially with regards to
documentation, are continuing.

* Community development progress

As of 2011-08-06, 71 committers, 52 on the PPMC up from 56 and 49 at last
report. Steps are continuing to bring onboard the last of the initial
Committers who have not yet provided an ICLA.

208 people are subscribed to the ooo-dev list. 124 people have posted to
the list of those 59 have more than 10 posts. 9 posters have more than 50
posts each.
User related queries or posts were virtually nil.
The shape and methodology of the Community Outreach is still in discussion.
An OOo blog has been initiated and is getting a high number of hits daily

* Project development progress

The grant from Oracle America, Inc for OpenOffice trademarks, logos, domain
names has been received.

Work with Infra: OOo Mediawiki has been successfully moved onto Apache
infrastructure. Some concerns relating to IP of materials on the wiki are
still in the proces of resolution.

www.openoffice.org is now in an Apache sandbox and work is being done to
recreate it in the Apache CMS

20 Jul 2011

* OpenOffice.org entered incubation 2011-06-13.

OpenOffice.org is an open-source, office-document productivity suite
providing six productivity applications based around the OpenDocument Format
(ODF).  OpenOffice.org is released on multiple platforms.  Its localizations
support 110 languages worldwide.


* Most important to address

1) Migration of the legacy OpenOffice.org website's content and services to
Apache infrastructure, including defect tracking and wiki instances which
have undergone significant customizations.

2) Completion of the IP-review portions of the incubation checklist, which
will require getting an amended SGA from Oracle to cover additional source
files.

3) A successful Podling Release

* Issues

None at this time.

* Community development progress

Initial work toward establishing committers and a PPMC has, as of
2011-07-08, 56 committers including 2 mentors and 38 PPMC members.

There are tentative steps toward engaging the existing OpenOffice.org
community and users.  There is limited discussion with related Apache
Projects such as POI and the possible incubation of the ODF Toolkit project.

* Project development progress

Addressing issues on migration of code repositories and other pieces of
project infrastructure.  Discussing migration of existing OpenOffice.org
as-is versus "house cleaning" for a streamlined initial website at Apache.

Created a podling project web site:
http://incubator.apache.org/openofficeorg/

Started more detailed planning discussion on public wiki:
https://cwiki.apache.org/confluence/display/OOOUSERS/Project+Planning