unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: guile-user@gnu.org
Subject: Re: Starting a GNU Guile awesome list
Date: Thu, 16 Jul 2020 00:40:22 +0200	[thread overview]
Message-ID: <878sfkxuzt.fsf@web.de> (raw)
In-Reply-To: <c3cb1b89-0491-dc95-d2e7-d5d9ae590e8c@posteo.de>

[-- Attachment #1: Type: text/plain, Size: 834 bytes --]

Hi Zelphir,

Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> writes:
> I just read multiple articles about GFDL and CC0 and still don't know
> what the better choice is for the list.
>
> In particular I do not find information about whether CC0 is copyleft or
> not (1), which perhaps means, that it is not and I do not understand the
> impact of invariant sections on the list (2).

CC0 is definitely not copyleft. It says "this is up for grabs".

Invariant sections mean that someone can limit re-use by requiring you
to keep parts that do not match the format of what you want to build.

If someone were to subsample the awesome-lists into a comparison post,
all the invariant sections of all sources would have to be retained.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein
ohne es zu merken

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1076 bytes --]

  reply	other threads:[~2020-07-15 22:40 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13 21:19 Starting a GNU Guile awesome list Zelphir Kaltstahl
2020-07-13 21:56 ` Jack Hill
2020-07-13 22:56 ` Aleix Conchillo Flaqué
2020-07-14 23:26   ` Zelphir Kaltstahl
2020-07-14  9:00 ` Dmitry Alexandrov
2020-07-14 21:23   ` Zelphir Kaltstahl
2020-07-15  6:32     ` Dr. Arne Babenhauserheide
2020-07-16  8:47       ` Dmitry Alexandrov
2020-07-16 19:01         ` Dr. Arne Babenhauserheide
2020-10-10 12:31         ` Zelphir Kaltstahl
2020-10-10 13:14           ` Matt Wette
2020-10-11  0:57             ` Zelphir Kaltstahl
2020-10-11 19:51               ` Ricardo Wurmus
2020-10-11 23:39                 ` Zelphir Kaltstahl
2020-10-12 10:33                   ` Ricardo Wurmus
2020-11-08 17:09                     ` Zelphir Kaltstahl
2020-11-08 18:55                       ` Paul Smith
2020-12-05 18:15                         ` Zelphir Kaltstahl
2020-07-15  6:36     ` Dr. Arne Babenhauserheide
2020-07-15 21:14       ` Zelphir Kaltstahl
2020-07-15 22:40         ` Dr. Arne Babenhauserheide [this message]
2020-07-16  9:18         ` A licence for an ‘awesome list’ (was: Starting a GNU Guile awesome list) Dmitry Alexandrov
2020-07-16 18:56           ` Dr. Arne Babenhauserheide
2020-07-16 18:58             ` Dr. Arne Babenhauserheide
2020-07-16 20:47           ` Zelphir Kaltstahl
2020-07-16 22:55             ` Vladimir Zhbanov
2020-07-16 23:05               ` Vladimir Zhbanov
2020-07-17  0:20             ` John Cowan
2020-07-17  6:43               ` Dr. Arne Babenhauserheide
2020-07-14 14:14 ` Starting a GNU Guile awesome list Dr. Arne Babenhauserheide
2020-07-15 21:24   ` Zelphir Kaltstahl
2020-07-15 22:29     ` Dr. Arne Babenhauserheide
2020-07-14 16:37 ` Taylan Kammer

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=878sfkxuzt.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=guile-user@gnu.org \
    --cc=zelphirkaltstahl@posteo.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.
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).