[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-licensing
Subject: Re: EPL 1.0 files as input data for Unit Tests
From: Mirko Boehm <mirko () kde ! org>
Date: 2012-08-27 9:54:06
Message-ID: 7C384F50-0DFB-46F1-9C48-FC6A5E8F0D37 () kde ! org
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
> From: Andreas Cord-Landwehr <phoenixx@uni-paderborn.de>
> ...
> Dear all,
>
> I want to use Graphvis example files as input data for automatic unit tests
> for a KDE program. Due to different licenses and the KDE license policy I am
> not sure if this is possible in the way I am currently planning and I want to
> ask for some expert knowledge on that matter :)
>
> My Plan: I want to import example graph files [3] from the Graphvis project
> (licensed under EPL 1.0) into the Rocs source directory. Rocs is in the KDE
> Edu module and hence follows the KDE license policy [2].
>
> The test files shall only be used as input data for the automatic unit tests.
> They are not going to be installed. Explicitely, they are not part of the
> compiled binaries nor the binaries are linked to them.
>
> My question is, if it is possible to include them in the source tree?
> And if yes, is it enough to put a specific EPL 1.0 license file in the
> directory with them? Or is more needed?
Distributing the files as input files for unit tests under the EPL is fine. I suggest \
adding the EPL license text to the directory where the files are located. Make sure \
to leave the license statements in the files intact.
Note: The files should not be linked into the unit test binaries (for example, as Qt \
resources), to avoid the license compatibility quirks between EPL and *GPL.
Cheers,
Mirko.
--
Mirko Boehm | mirko@kde.org | KDE e.V.
FSFE Fellow
Qt Certified Specialist
[Attachment #5 (unknown)]
<html><head><meta http-equiv="Content-Type" content="text/html \
charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: \
space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div \
style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: \
0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(127, 127, \
127, 1.0);"><b>From: </b></span><span style="font-family:'Helvetica'; \
font-size:medium;">Andreas Cord-Landwehr <<a \
href="mailto:phoenixx@uni-paderborn.de">phoenixx@uni-paderborn.de</a>><br></span></div><div \
style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: \
0px;"><font color="#7f7f7f"><b>... </b></font></div></blockquote><br><blockquote \
type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; \
margin-left: 0px;">Dear all, </div><br>I want to use Graphvis example files as \
input data for automatic unit tests <br>for a KDE program. Due to different licenses \
and the KDE license policy I am <br>not sure if this is possible in the way I am \
currently planning and I want to <br>ask for some expert knowledge on that matter \
:)<br><br>My Plan: I want to import example graph files [3] from the Graphvis project \
<br>(licensed under EPL 1.0) into the Rocs source directory. Rocs is in the KDE \
<br>Edu module and hence follows the KDE license policy [2].<br><br>The test files \
shall only be used as input data for the automatic unit tests. <br>They are not going \
to be installed. Explicitely, they are not part of the <br>compiled binaries nor the \
binaries are linked to them.<br><br>My question is, if it is possible to include them \
in the source tree?<br>And if yes, is it enough to put a specific EPL 1.0 license \
file in the <br>directory with them? Or is more \
needed?<br></blockquote><div><br></div><div>Distributing the files as input files for \
unit tests under the EPL is fine. I suggest adding the EPL license text to the \
directory where the files are located. Make sure to leave the license statements in \
the files intact. </div><div><br></div><div>Note: The files should not be linked \
into the unit test binaries (for example, as Qt resources), to avoid the license \
compatibility quirks between EPL and \
*GPL. </div><div><br></div><div>Cheers, </div><div><br></div><div>Mirko.</div><div>-- </div></div><div><span \
class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; \
"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, \
0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: \
normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; \
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; \
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; \
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; \
-webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: \
break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Mirko \
Boehm | <a href="mailto:mirko@kde.org">mirko@kde.org</a> | KDE e.V.<br>FSFE \
Fellow<br>Qt Certified Specialist<br><br><br><br></div></span></span> </div>
<br></body></html>
_______________________________________________
Kde-licensing mailing list
Kde-licensing@kde.org
https://mail.kde.org/mailman/listinfo/kde-licensing
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic