From: "Gábor Boskovits" <boskovits@gmail.com>
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: guix-devel <guix-devel@gnu.org>,
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>,
Paul Garlick <pgarlick@tourbillion-technology.com>
Subject: Re: Video license
Date: Sat, 15 Jun 2019 07:33:46 +0000 [thread overview]
Message-ID: <CAE4v=phEgVivrA=_TVJ9Hf5Sp3KX62EfYfHEGG9yARw7zoL06w@mail.gmail.com> (raw)
In-Reply-To: <20190614114422.522628aa@alma-ubu>
[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]
Hello,
Björn Höfling <bjoern.hoefling@bjoernhoefling.de> ezt írta (időpont: 2019.
jún. 14., P, 9:44):
> Hi Gábor,
>
> On Wed, 12 Jun 2019 09:12:14 +0200
> Gábor Boskovits <boskovits@gmail.com> wrote:
>
> > Hello,
> >
> > iirc this license discussion came about earlier, please have a look
> > at that also.
> > There were some problems regarding license compatibility. Otherwise I
> > ageree.
>
> I can't find the older discussions. Which are the problems regarding
> license compatibility you see here?
>
>
Unfortunately I can't find it either, but I remember that this discussed.
Sorry
about not being able to come up with more details.
The two things that came up was:
1. the manual is under GNU FDL, but as long as the videos are not considered
deriving from the manual, this should not be a problem.
2. can the videos have a separate license from the code that they are
critically
dependent on? - believe yes.
So all in all, I believe that the license choices you made make sense, and
iirc
I proposed exactly the same set of licenses on that older thread, which I
will
try to find. It is well possible that it was discussed on irc.
I would like to see this fixed soon, the idea of having source code in
> Guix' repositories that is only open-sourced but not free software
> annoys me.
>
> Björn
>
Yes, I agree, it would be great to fix this soon.
Best regards,
g_bor
--
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21
[-- Attachment #2: Type: text/html, Size: 2368 bytes --]
next prev parent reply other threads:[~2019-06-15 7:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 22:36 Video license Björn Höfling
2019-06-06 10:29 ` Paul Garlick
2019-06-11 22:25 ` Björn Höfling
2019-06-11 22:56 ` Laura Lazzati
2019-06-12 7:12 ` Gábor Boskovits
2019-06-14 9:44 ` Björn Höfling
2019-06-15 7:33 ` Gábor Boskovits [this message]
2019-06-22 13:41 ` Laura Lazzati
2019-06-23 21:53 ` Björn Höfling
2019-06-24 14:58 ` Laura Lazzati
2019-06-25 22:40 ` Laura Lazzati
2019-06-26 21:21 ` Björn Höfling
2019-06-27 5:33 ` Gábor Boskovits
2019-06-26 21:20 ` Björn Höfling
2019-06-12 9:48 ` Ricardo Wurmus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE4v=phEgVivrA=_TVJ9Hf5Sp3KX62EfYfHEGG9yARw7zoL06w@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=bjoern.hoefling@bjoernhoefling.de \
--cc=guix-devel@gnu.org \
--cc=pgarlick@tourbillion-technology.com \
--cc=ricardo.wurmus@mdc-berlin.de \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.