Page History

...

For the benefit of IPMC reviewers of our 3.4 Release Candidate , and to provide a public record of what we have done, the following summarizes the activities that were undertaken to make OpenOffice 3.4 conform to Apache licensing and release policies. Links to details and supplemental information are provided in the AOO 3.4 Release FAQ.

SGA's from Oracle

The ASF received two Software Grant Agreements from Oracle, the first on June 1st, 2011 and a supplemental one on October 17th, 2011.  Presumably these agreements are available for inspection by Apache Members.

...

AOO is regularly scanned by the Release-Audit-Tool and the results are published here. The annotated exception input for the RAT tool is here to exclude e.g. , binary resources that cannot take a license header, files too small to contain creative content, etc.

...

Category-X dependencies have mostly been replaced with their permissively licensed counterparts and the remainder has been removed. The impact for end-users is that some components are considerably better than before like the SVG import, some are somewhat better like the Calc solver or the regular expression engine, some parts got more efficient and that some parts got lost were removed like e.g. the import of WordPerfect filesWordPerfect file import. Extensions that were not permissively licensed like the Report Builder will probably become available again as third-party extensions.

Treatment of category-b dependencies

...

Binary releases may be bundled with dictionaries licensed under different terms than AL2. This was approved in the Legal Discuss JIRA: https://issues. apache.org/jira/browse/LEGAL-117 . Dictionaries are packaged as independent extensions and are recognized to fall into the "mere aggregation" provision of the GPL license http://www.gnu.org/licenses/gpl-faq.html#MereAggregation

Structure of LICENSE and NOTICE files

.

Structure of LICENSE and NOTICE files

The LICENSE file lists the licenses applicable to the source release. Binary releases may contain category-b licensed components. The licenses of the in-tree category-b components that can only be explicitly requested are being collected in LICENSE_category_b. Licenses of other components that can be distributed under a "mere aggregation" clause are collected in LICENSE_aggregated.

The NOTICE file provides the notices required by the individual licenses of the source release. Like the LICENSE file for binary builds there are corresponding NOTICE_category_b and NOTICE_aggregated files that are being provided for the convenience of re-distributors.(especially if we are having separate versions for source versus binary packages, we should explain that)