db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jalud Abdulmenan <te...@rogers.com>
Subject Re: [VOTE] Change Copyright notice to ASF
Date Wed, 15 Sep 2004 03:09:01 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John McNally wrote:

> Jalud Abdulmenan wrote:
>
>>
>> However, we
>> are including the IBM copyright statement line, to achieve consensus
>> while abiding by ASF copyright guidelines.
>>
>>
>>
>
> In all previous instances that I am aware of code that has been donated
> to the ASF, previous copyright declarations have been dropped.  IBM
> still does have a version of the files in which they have copyright, but
> the copyright holder for the files in a ASF repository is the ASF.
>
> I'm pretty sure there is legal reasoning behind the way I've seen it
> done in the past, but I don't really know what those reasons are.  I
> think it probably makes sense to clarify if either option 1 or option 2
> are really acceptable before continuing the vote.  But if not, please do
> so before actually performing the work.
>
> John McNally
>

Personally, I prefer to only have the ASF copyright notice in the source
code files and to have the IBM copyright notice in the NOTICE file.
However, based on the previous discussions on this topic, there seem to
be a strong support among the Derby dev community to keep the IBM
copyright notice.

To build a community around Derby and to have an official release, the
copyright notice in the source code files need to change until those
with the expertise and experience make their pronouncements on the final
copyright notice.

In the interim, I am proposing a solution that will allow us to have an
official release as well as foster a community around Derby.

The fact that Derby is in incubation and the lack of clear disapproval
in both the ASF license http://www.apache.org/licenses/LICENSE-2.0 and
the how-to of the ASF license
http://www.apache.org/dev/apply-license.html gives us some flexibility
in using the proposed interim solution.

Jalud,


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

iD8DBQFBR7JN2MOhC3LM/1oRAqBxAJ4zFUTHzJL9h2qKnxDdyuNoKeBArACgvvnY
I2EqMVbavz2ndhJzBZPBh7E=
=uTlH
-----END PGP SIGNATURE-----


Mime
View raw message