unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Jesse Gibbons <jgibbons2357@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Kdenlive License follow-up.
Date: Sat, 21 Sep 2019 16:06:08 +0900	[thread overview]
Message-ID: <8736gq6sdb.fsf@gmail.com> (raw)
In-Reply-To: <d605399e8dad597ad13b54df1c3eddb082fe8871.camel@gmail.com> (Jesse Gibbons's message of "Wed, 18 Sep 2019 20:41:03 -0600")

Hi,

Jesse Gibbons <jgibbons2357@gmail.com> writes:

> On Wed, 2019-09-18 at 21:40 +0200, Ricardo Wurmus wrote:
>> Hi Fanis,
>> 
>> > I asked on the KDE matrix server regarding the Kdenlive licensing and
>> > turns out they use GPL-3 in OpenSUSE. Most files are either GPL-2 or
>> > GPL-3 or later + KDE Ev. clause so the package can't be licensed as
>> > GPL-2 like Gentoo or GPL-2+ as in Guix.
>> 
>> Thank you for the information.
>> 
>> If you could point us to a file that is licensed under GPL version 3 or
>> later we should change the license in the package definition to (list
>> license:gpl2+ license:gpl3+) with a comment to state that the package is
>> effectively under GPL version 3 or later.

Is it really useful to record gpl2+ in the license list?  I've always
seen the license field of records as 'the effective license(s)' that can
the package can be licensed under, as this seem more useful to me than
having an long exhaustive list of licenses that are overridden by
others.

So in this case, my personal preference would be to list the license of
the package as its actual license, that is, gpl3+.  Thoughts?

Maxim

      reply	other threads:[~2019-09-21  7:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-18 19:12 Kdenlive License follow-up marinus.savoritias
2019-09-18 19:40 ` Ricardo Wurmus
2019-09-19  2:41   ` Jesse Gibbons
2019-09-21  7:06     ` Maxim Cournoyer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8736gq6sdb.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=jgibbons2357@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).