[CONF] Apache OpenOffice Community > 2013 Jul

[Kay Schenk (Confluence)]

2013 Jul Page edited by Kay Schenk Changes (19) ... Issues for Board Awareness --------------------------- None at this time. Discuss alternate location for ooo-extras? now on a Google service http://code.google.com/a/apache-extras.org/hosting/ (This will affect the ASF as a whole it seems.) Community Development/Outreach Progress --------------------------------------- (cloned from April; still to be updated) The project added 4 committers (pending one as of 07-08-2013), and one new PMC member since our last report in April. The project added a new committer, ... 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 the care taking of our LAMP services. 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 licence 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 ... ------------------------------------ The project released an update to version 3.4.1 in late January, to include 8 new language translations made available by volunteers. We will be releasing Apache OpenOffice 4.0 in July, likely the week of July 15. The next OpenOffice release will be labeled 4.0. Plans are to release in June, 2013. This release will provide elements from the IBM Symphony; a new, simplified product structure of to simplify development and installation; code changes (ongoing) for use with Java 7, rather than Java 6; and (likely) 23 languages. 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 In preparation for the upcoming 4.0 release, new rebranding was undertaken with a new logo and other graphic elements ready for the release. Many of our new volunteers were instrumental in this process. We are continuing build work for reinstating OpenOffice into Linux repositories, currently Fedora at this time. ... now kept in external files) allowing normal translation of these parts. ??? still relevant A new localization process, eventually leading to a more efficient translation workflow and a massive cleanup of tools and intermediate ... 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. Work had started on dropping the historical dmake used for building OpenOffice in favor of a pure GNU make approach. This work will continue after the 4.0 release. Additionally, a new branch has been started, rejuvenate01, to explore using native platform capabilities and libraries for building rather than downloading for building as has been done in the past. We feel taking these kind of development steps will result in both a better product for end users and simplify development and building for new developers. Full Content Reporting to the Apache Board is a periodic task of the Apache OpenOffice PMC Chair. See here and here for context. Apache OpenOffice 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 --------------------------- Discuss alternate location for ooo-extras? now on a Google service http://code.google.com/a/apache-extras.org/hosting/ (This will affect the ASF as a whole it seems.) Community Development/Outreach Progress --------------------------------------- The project added 4 committers (pending one as of 07-08-2013), and one new PMC member 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 the care taking of our LAMP services. A new documentation effort for an end-users manual under the ALv2 licence was started on the OpenOffice Wiki. 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 provide elements from the IBM Symphony; a new, simplified product structure of to simplify development and installation; code changes (ongoing) for use with Java 7, rather than Java 6; and (likely) 23 languages. In preparation for the upcoming 4.0 release, new rebranding was undertaken with a new logo and other graphic elements ready for the release. Many of our new volunteers were instrumental in this process. We are continuing build work 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. ??? still relevant 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. Work had started on dropping the historical dmake used for building OpenOffice in favor of a pure GNU make approach. This work will continue after the 4.0 release. Additionally, a new branch has been started, rejuvenate01, to explore using native platform capabilities and libraries for building rather than downloading for building as has been done in the past. We feel taking these kind of development steps will result in both a better product for end users and simplify development and building for new developers. Stop watching space | Change email notification preferences View Online | View Changes | Add Comment