incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache OpenOffice Community > Summary of Apache OpenOffice 3.4 IP Review Activities
Date Sat, 31 Mar 2012 18:54:00 GMT
Space: Apache OpenOffice Community (https://cwiki.apache.org/confluence/display/OOOUSERS)
Page: Summary of Apache OpenOffice 3.4 IP Review Activities (https://cwiki.apache.org/confluence/display/OOOUSERS/Summary+of+Apache+OpenOffice+3.4+IP+Review+Activities)

Change Comment:
---------------------------------------------------------------------
dictionaries

Edited by Andrea Pescetti:
---------------------------------------------------------------------
h2. 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 provc


h2. 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:   https://svn.apache.org/repos/asf/incubator/ooo/pmc/ip-review/

h2. 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".

h2. RAT scan results and walk-through of exceptions

(link to RAT scan results and a link to the exceptions file.  Ideally the exceptions
file can be annotated.  Here in the wiki we can explain at a high level what kinds
of things were excluded and why, e.g., binary resources that cannot take a license header,
files too small to contain creative content, etc.)


h2. Removal/replacement of category-x dependencies

(High level description and link to the wiki table for details)


h2. *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.)


h2. 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



h2. Structure of LICENSE and NOTICE files

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


h2.

Change your notification preferences: https://cwiki.apache.org/confluence/users/viewnotifications.action
   

Mime
View raw message