[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-community
Subject: Re: Licensing policy change proposal
From: Mirko Boehm <mirko () kde ! org>
Date: 2019-01-28 13:11:04
Message-ID: 09900405-E492-4B56-B6D8-0BC71FBFB499 () kde ! org
[Download RAW message or body]
Hi,
> On 28. Jan 2019, at 13:23, Krešimir Čohar <kcohar@gmail.com> wrote:
>
> I don't think there are any problems with using public domain images, and even if \
> there were I'd rather view them as challenges to overcome than obstacles to avoid.
There is. We cannot prove that we have explicit permission from the author to use or \
distribute the work. We also have no way of tracking that who submits the work to our \
channels has the right to do so. The idea of "public domain" only really works for \
works where copyright has expired.
> > These are both non-free licences and we can not ship files which can
> only be copied with their restrictions.
>
> Why not? As far as Unsplash goes, their only restriction is not to start a \
> competing service, which is not even remotely what we are trying to do. Surely that \
> is a reasonable and acceptable restriction. It's not unlike the copyleft \
> restrictions ("freedoms") of the GPL.
It violates the Open Source definition, especially the rule against discrimination \
against use or user. This has been a long-time yardstick for the KDE community.
Best,
Mirko.
--
Mirko Boehm | mirko@kde.org | KDE e.V.
FSFE Team Germany
Qt Certified Specialist and Trainer
Request a meeting: https://doodle.com/mirkoboehm
[Attachment #3 (unknown)]
<html><head><meta http-equiv="Content-Type" content="text/html; \
charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; \
line-break: after-white-space;" class="">Hi,<br class=""><div><br \
class=""><blockquote type="cite" class=""><div class="">On 28. Jan 2019, at 13:23, \
Krešimir Čohar <<a href="mailto:kcohar@gmail.com" \
class="">kcohar@gmail.com</a>> wrote:</div><br \
class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, \
0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: \
normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: \
0px; text-transform: none; white-space: normal; word-spacing: 0px; \
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline \
!important;" class="">I don't think there are any problems with using public domain \
images, and even if there were I'd rather view them as challenges to overcome than \
obstacles to avoid.</span></div></blockquote><div><br class=""></div>There is. We \
cannot prove that we have explicit permission from the author to use or distribute \
the work. We also have no way of tracking that who submits the work to our channels \
has the right to do so. The idea of "public domain" only really works for works where \
copyright has expired.</div><div><br class=""><blockquote type="cite" class=""><div \
class=""><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: \
12px; font-style: normal; font-variant-caps: normal; font-weight: normal; \
letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; \
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; \
text-decoration: none;" class="">> These are both non-free licences and we can not \
ship files which can<br class="">only be copied with their restrictions.<br \
style="color: rgb(80, 0, 80);" class=""></div><div style="caret-color: rgb(0, 0, 0); \
font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: \
normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: \
0px; text-transform: none; white-space: normal; word-spacing: 0px; \
-webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br \
class=""></div><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; \
font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; \
letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; \
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; \
text-decoration: none;" class="">Why not? As far as Unsplash goes, their only \
restriction is not to start a competing service, which is not even remotely what we \
are trying to do. Surely that is a reasonable and acceptable restriction. It's not \
unlike the copyleft restrictions ("freedoms") of the GPL.</div></div></blockquote><br \
class=""></div><div>It violates the Open Source definition, especially the rule \
against discrimination against use or user. This has been a long-time yardstick for \
the KDE community.</div><div><br class=""></div><div>Best,</div><div><br \
class=""></div><div>Mirko.</div><div class=""> <div style="color: rgb(0, 0, 0); \
letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; \
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: \
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div \
style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: \
space; line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); \
letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; \
-webkit-text-stroke-width: 0px; text-align: start; text-indent: 0px; word-wrap: \
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" \
class="">-- <br class=""></div><div style="text-align: start; text-indent: 0px; \
word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" \
class="">Mirko Boehm | <a href="mailto:mirko@kde.org" class="">mirko@kde.org</a> | \
KDE e.V.<br class="">FSFE Team Germany<br class="">Qt Certified Specialist and \
Trainer<br class="">Request a meeting: <a href="https://doodle.com/mirkoboehm" \
class="">https://doodle.com/mirkoboehm</a><br class=""></div></div></div> </div>
<br class=""></body></html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic