[prev in list] [next in list] [prev in thread] [next in thread]
List: kwrite-devel
Subject: Re: Non-free file in pate js_utils plugin
From: "Philipp A." <flying-sheep () web ! de>
Date: 2013-12-03 14:41:54
Message-ID: CAN8d9gkCVktCe4yiM-=m3k8kk+FQRKuCXExn2-g+01iNQ95a9w () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
GOD DAMMIT i'm sorry. Afaik only JSLint, not JSHint is under doug's
modified MIT license (wikipedia is wrong that they allegedly use the same
license). and the phrase doug added which made JSLint's MIT license nonfree
is ridiculously "The Software shall be used for good, not evil"… If we
however identify as "minions of IBM", then we can freely use it, since he
explicitly allowed IBM (and their minions) to use his software for evil :)
i still want the user to be able to use JSLint, and there should be a
solution. while the old python lib that got used to provide JSLint
functionality "got around it" by downloading JSHint on demand, i doubt that
this is OK. the only difference is that it's not in our repo, but that
doesn't change the fact that js_utils used the code before just like it
uses the code now. so my change only directed attention to it, and didn't
add a new incompatible license.
i think we could require the user to click a one-time messagebox which says
"you're only allowed to lint your JavaScript for good, not for evil", and,
if he declines, fail to load the js_utils plugin with a
UserIsEvilException. sounds good?
2013/12/3 Alex Turbov <i.zaufi@gmail.com>
>
> On Tue, Dec 3, 2013 at 3:01 PM, Milian Wolff <mail@milianw.de> wrote:
>
>> On Monday 02 December 2013 17:40:36 T.C. Hollingsworth wrote:
>>
>> <snip>
>>
>> > I really hate being the licensing police, but this presents a big
>> > problem to downstream distributors. :-(
>>
>> Please don't feel bad for bringing such topics up. It's important and I
>> appreciate that you are taking care of it. Developers such as me often
>> simply
>> don't think about it at all, and/or are not aware of whats compatible with
>> what.
>>
>> So, @ the Pate guys - can you please take care of this asap? T.C. explains
>> what could be done. Generally, we might think about GHNS support for these
>> things, which would allow users to download the file at runtime,
>> completely
>> bypassing the distributors.
>>
>
> +1 for GHNS! (for Python plugins)
> also it will allow to ppl to share their plugins publicly (and probably
> can helps to increase amount of available plugins).
> but (also) we need a good tutorial about *how to write a python plugin in
> 15 minutes* to show that it is *really simple* (and fun) task...
>
>
>>
>> Cheers
>> --
>> Milian Wolff
>> mail@milianw.de
>> http://milianw.de
>> _______________________________________________
>> KWrite-Devel mailing list
>> KWrite-Devel@kde.org
>> https://mail.kde.org/mailman/listinfo/kwrite-devel
>>
>
>
> _______________________________________________
> KWrite-Devel mailing list
> KWrite-Devel@kde.org
> https://mail.kde.org/mailman/listinfo/kwrite-devel
>
>
[Attachment #5 (text/html)]
<div dir="ltr"><div><div><div>GOD DAMMIT i'm sorry. Afaik only JSLint, not JSHint is \
under doug's modified MIT license (wikipedia is wrong that they allegedly use the \
same license). and the phrase doug added which made JSLint's MIT license nonfree is \
ridiculously "The Software shall be used for good, not evil"… If we however \
identify as "minions of IBM", then we can freely use it, since he explicitly allowed \
IBM (and their minions) to use his software for evil :)<br> <br></div></div>i still \
want the user to be able to use JSLint, and there should be a solution. while the old \
python lib that got used to provide JSLint functionality "got around it" by \
downloading JSHint on demand, i doubt that this is OK. the only difference is that \
it's not in our repo, but that doesn't change the fact that js_utils used the code \
before just like it uses the code now. so my change only directed attention to it, \
and didn't add a new incompatible license.<br> <br>i think we could require the user \
to click a one-time messagebox which says "you're only allowed to lint your \
JavaScript for good, not for evil", and, if he declines, fail to load the js_utils \
plugin with a UserIsEvilException. sounds good?<br> </div></div><div \
class="gmail_extra"><br><br><div class="gmail_quote">2013/12/3 Alex Turbov <span \
dir="ltr"><<a href="mailto:i.zaufi@gmail.com" \
target="_blank">i.zaufi@gmail.com</a>></span><br><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div \
dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote"><div class="im">On \
Tue, Dec 3, 2013 at 3:01 PM, Milian Wolff <span dir="ltr"><<a \
href="mailto:mail@milianw.de" target="_blank">mail@milianw.de</a>></span> \
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">On Monday 02 December 2013 17:40:36 T.C. Hollingsworth \
wrote:<br> <br>
<snip><br>
<br>
> I really hate being the licensing police, but this presents a big<br>
> problem to downstream distributors. :-(<br>
<br>
Please don't feel bad for bringing such topics up. It's important and I<br>
appreciate that you are taking care of it. Developers such as me often simply<br>
don't think about it at all, and/or are not aware of whats compatible with<br>
what.<br>
<br>
So, @ the Pate guys - can you please take care of this asap? T.C. explains<br>
what could be done. Generally, we might think about GHNS support for these<br>
things, which would allow users to download the file at runtime, completely<br>
bypassing the distributors.<br></blockquote><div><br></div></div><div>+1 for GHNS! \
(for Python plugins)<br></div><div>also it will allow to ppl to share their plugins \
publicly (and probably can helps to increase amount of available plugins).<br>
but (also) we need a good tutorial about <i>how to write a python plugin in 15 \
minutes</i> to show that it is <b>really simple</b> (and fun) task...<br></div><div \
class="im"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Cheers<br>
<span><font color="#888888">--<br>
Milian Wolff<br>
<a href="mailto:mail@milianw.de" target="_blank">mail@milianw.de</a><br>
<a href="http://milianw.de" target="_blank">http://milianw.de</a><br>
_______________________________________________<br>
KWrite-Devel mailing list<br>
<a href="mailto:KWrite-Devel@kde.org" target="_blank">KWrite-Devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kwrite-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/kwrite-devel</a><br> \
</font></span></blockquote></div></div><br></div></div> \
<br>_______________________________________________<br> KWrite-Devel mailing list<br>
<a href="mailto:KWrite-Devel@kde.org">KWrite-Devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kwrite-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/kwrite-devel</a><br> \
<br></blockquote></div><br></div>
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic