incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Jumper <mike.jum...@guac-dev.org>
Subject Re: [VOTE] Apache HAWQ (incubating) 2.0.0.0-incubating Release
Date Tue, 09 Aug 2016 23:43:20 GMT
On Tue, Aug 9, 2016 at 4:32 PM, Justin Mclean <justin@classsoftware.com> wrote:
> Hi,
>
>> Why? It would be perfectly fine for PG project to include, lets say an MIT
>> source code.
>
> That would be compatible with our license. But what if they included GPL or CDDL licensed
software?
>
>> That's why I don't feel comfortable putting the overall PG  licensed header there
on my own.
>
> Nor should you if the files are not licensed that way.
>
>> I think we're talking slightly past each other -- I told you I do KNOW that they
>> are licensed under the different ALv2 compatible license.
>
> The package as a whole is licensed that way. But you stated you didn’t not know how
that file is licensed it may be ALv2 or it may be something else. Just as it has different
copyright owner it also likely is under a different license, whose terms are very likely to
be APv2 compatible, but may not be.
>

I'd also like to point out, from the PostgreSQL license (emphasis added):

"... Permission to use, copy, modify, and distribute this software and
its documentation for any purpose, without fee, and without a written
agreement is hereby granted, **provided that the above copyright
notice and this paragraph and the following two paragraphs appear in
all copies**. ..."

Regardless of how uncomfortable it may be to modify that file and add
legal boilerplate, the project in question would be violating the
PostgreSQL license if it does not somehow include the copyright notice
and paragraphs along with the copied portions.

If it is absolutely known that the file is indeed under the PostgreSQL
license, I'd think the best thing would be to add it and thus comply.
If, on the other hand, the license of that file truly *isn't* known,
then its inclusion in any project is dangerous.

Perhaps the upstream project could be persuaded to add the appropriate
boilerplate themselves, and thus resolve this once and for all?

- Mike

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message