[prev in list] [next in list] [prev in thread] [next in thread]
List: pykde
Subject: Re: [PyQt] My license mess
From: Jorge Tornero <jtorlistas () gmail ! com>
Date: 2015-06-23 9:08:42
Message-ID: CAEHjKAv-rPs-pj_uT8Ds7h1mV4WBZM4QJ0pRcb0MrXqOM3Ov3A () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hello All,
Thank you David and Phil for your kind answers. I think I'll try to begin
from scratch with the file later. There is a nice tutorial on how to do it
(the QQ article itself) and doesn't seem to be too difficult to achieve.
Anyway, this licensing stuff is sometimes so confusing. I guess everyone
has passed through this, so I guess I'll find the way sooner or later.
Again, Thanks.
Jorge
2015-06-22 12:28 GMT+02:00 David Boddie <david@boddie.org.uk>:
> On Mon Jun 22 09:21:26 BST 2015, Phil Thompson wrote:
>
> My personal opinion (I am not a lawyer) is that you can use whatever
>> license you want so long as it is compatible with the other bits of
>> software you are using. The files you mention are implementations of
>> boilerplate code and you can't really write them any other way - they
>> are almost like configuration files.
>>
>
> As far as I can see, the setup.py file and the files in the python
> directory are basically just implementing the required interfaces in the
> simplest way, which is really the only useful way to implement them.
>
> So, since there's very little room for creative expression, I'd expect it
> to be difficult to argue that the original implementations were even
> copyrightable, and there are probably plenty of differences between these
> implementations and the original ones. If someone started writing these
> interfaces from scratch, they would end up with something very much like
> the ones in the python directory.
>
> My advice to the author is: if you still feel uncomfortable about those
> files, start with an empty file for each of them and use the API
> documentation to write them from scratch. I personally don't see that this
> is necessary, but I understand if you want to go to the trouble of doing
> it.
>
> Really, those examples should have been permissively licensed in the first
> place. I don't remember why they weren't.
>
> Thanks to Jorge for finding the current location of the Qt Quarterly site:
>
> https://doc.qt.io/archives/qq/
>
> David
>
> _______________________________________________
> PyQt mailing list PyQt@riverbankcomputing.com
> http://www.riverbankcomputing.com/mailman/listinfo/pyqt
>
[Attachment #5 (text/html)]
<div dir="ltr">Hello All,<div><br></div><div>Thank you David and Phil for your kind \
answers. I think I'll try to begin from scratch with the file later. There is a \
nice tutorial on how to do it (the QQ article itself) and doesn't seem to be too \
difficult to achieve.</div><div><br></div><div>Anyway, this licensing stuff is \
sometimes so confusing. I guess everyone has passed through this, so I guess I'll \
find the way sooner or later.</div><div><br></div><div>Again, \
Thanks.</div><div><br></div><div>Jorge</div></div><div class="gmail_extra"><br><div \
class="gmail_quote">2015-06-22 12:28 GMT+02:00 David Boddie <span dir="ltr"><<a \
href="mailto:david@boddie.org.uk" \
target="_blank">david@boddie.org.uk</a>></span>:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span class="">On Mon Jun 22 09:21:26 BST 2015, Phil Thompson \
wrote:<br> <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> My personal opinion (I am not a lawyer) is that you can use \
whatever<br> license you want so long as it is compatible with the other bits of<br>
software you are using. The files you mention are implementations of<br>
boilerplate code and you can't really write them any other way - they<br>
are almost like configuration files.<br>
</blockquote>
<br></span>
As far as I can see, the setup.py file and the files in the python<br>
directory are basically just implementing the required interfaces in the<br>
simplest way, which is really the only useful way to implement them.<br>
<br>
So, since there's very little room for creative expression, I'd expect it<br>
to be difficult to argue that the original implementations were even<br>
copyrightable, and there are probably plenty of differences between these<br>
implementations and the original ones. If someone started writing these<br>
interfaces from scratch, they would end up with something very much like<br>
the ones in the python directory.<br>
<br>
My advice to the author is: if you still feel uncomfortable about those<br>
files, start with an empty file for each of them and use the API<br>
documentation to write them from scratch. I personally don't see that this<br>
is necessary, but I understand if you want to go to the trouble of doing it.<br>
<br>
Really, those examples should have been permissively licensed in the first<br>
place. I don't remember why they weren't.<br>
<br>
Thanks to Jorge for finding the current location of the Qt Quarterly site:<br>
<br>
<a href="https://doc.qt.io/archives/qq/" rel="noreferrer" \
target="_blank">https://doc.qt.io/archives/qq/</a><span class="HOEnZb"><font \
color="#888888"><br> <br>
David</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
PyQt mailing list <a href="mailto:PyQt@riverbankcomputing.com" \
target="_blank">PyQt@riverbankcomputing.com</a><br> <a \
href="http://www.riverbankcomputing.com/mailman/listinfo/pyqt" rel="noreferrer" \
target="_blank">http://www.riverbankcomputing.com/mailman/listinfo/pyqt</a></div></div></blockquote></div><br></div>
[Attachment #6 (text/plain)]
_______________________________________________
PyQt mailing list PyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic