db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject Re: Derby code copyright question
Date Mon, 27 Sep 2004 01:20:08 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Geir Magnusson Jr. wrote:

> On Sep 26, 2004, at 11:37 AM, Daniel John Debrunner wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Geir Magnusson Jr. wrote:

>>>
>>> Traditionally, the only time we distribute code under someone else's
>>> copyright is when we are including other works as a convenience for  our
>>> users, such as packaging something in a distribution.  Otherwise, we
>>> tend not to host projects owned by other entities.  Sourceforge is  good
>>> for that.
>>
>>
>> Incorrect.
>>
>
> Not "Incorrect".  Show me software in the ASF that is not (c) ASF,
> besides standard APIs or such.  We may have attributed (c) ASF by
> mistake, or incorrectly, but it is all (c) ASF except for inclusions of
> outside works for packaging convenience.

Geir, I think we must be misunderstanding each other.

All code distributed by ASF may only have (C) ASF notices but that does
not change the fact that the code does have additional copyright
holders. I thought you were claiming that ASF only distributed code
where the only copyright holder was ASF.

Derby wants to follow existing ASF practices, I'm now no longer have any
idea what folks are objecting to. NOTICES file seems to be the new
issue, but again Derby wants to follow existing ASF practice, as seen in
the Xerces Java notice file and the Beehive notice file.

Dan.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBV2rIIv0S4qsbfuQRAtHiAKCt1sgIRNNg2Z6OwFpWFzMCTcq6AgCggKRc
tfrxS6JBypdtYLRRgcuo8Us=
=VEPZ
-----END PGP SIGNATURE-----


Mime
View raw message