Mailing-List: contact dev-help@corinthia.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@corinthia.incubator.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 dennis.hamilton@acm.org does not designate 216.234.124.52 as permitted
 sender)
Reply-To: <dennis.hamilton@acm.org>
From: "Dennis E. Hamilton" <dennis.hamilton@acm.org>
To: <dev@corinthia.incubator.apache.org>
References: <9E4866F0-135D-4339-AD32-7BCDF31A472C@apache.org>
In-Reply-To: <9E4866F0-135D-4339-AD32-7BCDF31A472C@apache.org>
Subject: RE: Copyright notices
Date: Fri, 13 Feb 2015 00:32:44 -0800
Organization: NuovoDoc
Message-ID: <00d201d04767$a47a0c90$ed6e25b0$@acm.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQIwVs2OpkhbwDZdsV/ocEEyicptppwt8Utw
Content-Language: en-us
Received-SPF: softfail (supercp.com: domain of transitioning
 dennis.hamilton@acm.org does not designate 75.165.123.152 as permitted
 sender)

Oops, let this sit in my draft folder for hours. I blame the wonders of =
oxycodone and pain management.

The TL;DR: You're doing great on the notices.

Some nuances and clarification of NOTICE below.

 - Dennis

Peter,

Thanks for asking about this.

I think the new notices on files are just fine (and COR-41 is totally =
elective but valuable as a casual undertaking).  The README.md probably =
needs an ASF notice too.

Some ASF purists expect that NOTICE and LICENSE will appear without a =
.txt extension.  I don't expect any/much push-back about that on a =
release, and if there were, it is probably something that could be fixed =
on a following release.

After a few years watching the lists about the proper use of these =
files, I think you are fine except for what might be needed for external =
dependencies, etc.  That can be dealt with as platform and =
external-dependencies (including for incorporated source code) are =
handled.

It would be useful to obtain an appraisal from the mentors on this.  I'm =
confident that we have enough information to avoid marching over to =
discuss-legal and general-incubator to hammer anything out.

We will need to run RAT on the repository as part of diligence with =
regard to third-party license notices and claims, and that should be =
done before declaring every release candidate.  I think this can be done =
on an unzip of the source archive for a given release, since there is =
more time to clean up IP on unreleased code/dependencies.

ABOUT NOTICE

It has been made very clear that NOTICE is not an attribution or =
acknowledgment file.  It must be limited to *legally-required* notice =
information.  Moving your copyright notice there is perfect under the =
third-party rules.  Any associated licenses that are required to be =
included are appended to LICENSE, and multiple uses of common licenses =
only needs to appear in LICENSE once.

(Aside: My inclination would be to include the git commit hash for the =
code as it was before you made the contribution cited in NOTICE, but I =
don't think that is a requirement.  Anyone willing to do some forensic =
work in the git can find that point on their own, a nice feature of Git =
having all history in each clone.)

MY COPYRIGHT AND NOTICE

I believe all of my contributions of any substance came after the move =
to the incubator, although I was made a member of the UX project before =
that.  In any case, I have not applied any copyright notices to files =
from me (except ASF notices) and I am in complete accord with the code =
being licensed to the ASF.  There is no requirement to do anything in =
NOTICE on my behalf.  Having a CONTRIBUTORS file would be valuable =
though.

It may be of interest to you that I have made a license declaration that =
goes beyond the iCLA.  I believe that declaration is on file with the =
ASF Secretary.  The purpose of my declaration is to establish that I =
provide the same license as the iCLA makes to *anyone* who obtains a =
contribution of mine from an ASF Project, even if the contribution is =
never (or not yet) reflected in a release. I did this to put no strings =
on my AOO contributions being used by LibreOffice and anyone else, =
regardless of ever being merged into an AOO release.  (I have made the =
identical declaration for any of my contributions to LibreOffice, =
providing all rights that an iCLA grants, with no limitation, not even =
mention, concerning MPL or any other license choice.)

Here is one public notification of the grant that I made concerning ASF =
contributions,
<http://mail-archives.apache.org/mod_mbox/openoffice-dev/201303.mbox/%3c0=
08801ce1c21$0deb3560$29c1a020$@apache.org%3e>
In the transmittal text (not part of the grant), the first appearance of =
"LibreOffice" (4th paragraph at the top of the list message body) should =
read "an ASF Project".

 - Dennis

-----Original Message-----
From: Peter Kelly [mailto:pmkelly@apache.org]=20
Sent: Thursday, February 12, 2015 19:29
To: dev@corinthia.incubator.apache.org
Subject: Copyright notices

I=E2=80=99ve finally gotten around to updating the copyright notices in =
all the source files to reflect the requirements described at =
http://www.apache.org/legal/src-headers.html. The copyright statement =
for UX Productivity now lives in NOTICES.txt; anyone else who has make =
contributions so far should add their name to this file.

I=E2=80=99ve left the files in platform unchanged to avoid merge =
conflicts with Jan=E2=80=99s changes; I=E2=80=99ll let him take care of =
those.

Could someone with more experience with Apache licensing than me please =
verify that the changes I=E2=80=99ve made are correct?

=E2=80=94
Dr Peter M. Kelly
pmkelly@apache.org

PGP key: http://www.kellypmk.net/pgp-key =
<http://www.kellypmk.net/pgp-key>
(fingerprint 5435 6718 59F0 DD1F BFA0 5E46 2523 BAA1 44AE 2966)