You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Purpose

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.

The list of files covered by each of these grants, were extracted from the SGA and can be found in these files

Trademark

The ASF has been assigned the US trademark registration for "OpenOffice.org".  To conform to Apache branding guidelines, and after a vote in the community, the PMC agreed to change the name to "Apache OpenOffice".  There is more work to be done to complete the rebranding effort, both in the product and on the website.  We intend to do this during our next release.  So the current 3.4 release will exhibit some residual references to "OpenOffice.org".

RAT scan results and walk-through of exceptions

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.

Removal/replacement of category-x dependencies

Category-X dependencies have mostly been replaced with 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 and that some parts got lost like e.g. the import of WordPerfect files.

Treatment of category-b dependencies

(Description of why we carry category-b source in SVN how we segregate that source code, how it is not in the source packages, etc.)

Spell-checking dictionaries and the "mere aggregation" exception in GPL

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

(especially if we are having separate versions for source versus binary packages, we should explain that)

  • No labels