From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: Christopher Allan Webber <cwebber@dustycloud.org>,
"guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: [ANN] An impudent introduction to Guile
Date: Fri, 5 Feb 2016 22:46:40 +0100 [thread overview]
Message-ID: <CAMFYt2buNkJOt6_pPZdS45tDwijO2nHay5ida1F3xDE+i4eqqg@mail.gmail.com> (raw)
In-Reply-To: <87zivfxg1w.fsf@dustycloud.org>
[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]
2016-02-05 17:44 GMT+01:00 Christopher Allan Webber <cwebber@dustycloud.org>
:
> Panicz Maciej Godek writes:
>
> >> CC BY-SA 4.0 is actually what I've been thinking about.
> > I will add the legal notice by the end of the day (I only realized the
> lack
> > of it while I was writing the announcement)
> >
> >
> >> I see there's a copy of the GPL included with it; is it thus also
> >> licensed under GPL v3 or later?
> >>
> >>
> > I see you're an expert, so perhaps you could explain to me what would the
> > implications be.
> > My original intent was to publish the software that comes along with the
> > book under GPL v3, because AFAIK GPL regards software, but if there's
> more
> > to it, then it would be nice to know
>
>
> You can dual license it under CC BY-SA 4.0 and GPLv3 or later, which is
> what I'd recommend. CC BY-SA 4.0 is GPLv3 compatible, but not "or
> later", and I think having an "or later" in anything GPL'ed is a good
> idea.
>
> For now I've updated legal notice so that now the book contains
information about the CC BY-SA 4.0 license. Although I have nothing against
applying the dual license, I used the "doclicense" LaTeX package to
generate the information, and I don't know how to handle such use case.
Maybe I will fight with that later, but I guess that the code snippets will
sooner or later become a part of the repository that is already GPLv3+
> I've loaded the book on my e-reader, look forward to reading it!
>
I hope you have a pleasant read! :)
[-- Attachment #2: Type: text/html, Size: 2332 bytes --]
next prev parent reply other threads:[~2016-02-05 21:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 23:09 [ANN] An impudent introduction to Guile Panicz Maciej Godek
2016-02-05 0:30 ` Christopher Allan Webber
[not found] ` <CAMFYt2YkMi2X0G_7eTtwkc66w1UhXndy+z91ui+PF6d0ie2Rug@mail.gmail.com>
2016-02-05 7:22 ` Fwd: " Panicz Maciej Godek
2016-02-05 16:48 ` Christopher Allan Webber
[not found] ` <87zivfxg1w.fsf@dustycloud.org>
2016-02-05 21:46 ` Panicz Maciej Godek [this message]
2016-02-05 6:48 ` Shakthi Kannan
2016-02-05 18:55 ` Amirouche Boubekki
2016-02-05 22:09 ` Panicz Maciej Godek
2016-02-05 19:46 ` Lawrence Bottorff
2016-02-05 20:29 ` Panicz Maciej Godek
-- strict thread matches above, loose matches on Subject: below --
2016-02-06 0:47 Cao Jin
2016-02-06 6:08 ` Panicz Maciej Godek
2016-02-06 8:52 ` Arne Babenhauserheide
2016-02-06 9:16 ` Cao Jin
2016-02-06 10:18 ` Jan Wedekind
2016-02-07 9:54 ` A0
2016-02-07 21:51 ` Lawrence Bottorff
2016-02-08 19:58 ` Panicz Maciej Godek
2016-02-09 8:26 ` tomas
2016-02-09 18:41 ` Lawrence Bottorff
2016-02-10 19:47 ` Panicz Maciej Godek
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMFYt2buNkJOt6_pPZdS45tDwijO2nHay5ida1F3xDE+i4eqqg@mail.gmail.com \
--to=godek.maciek@gmail.com \
--cc=cwebber@dustycloud.org \
--cc=guile-user@gnu.org \
/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).