From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: gfp <gfp@posteo.at>
Cc: help-guix@gnu.org, Felix Lechner <felix.lechner@lease-up.com>,
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>,
Luis Felipe <sirgazil@zoho.com>
Subject: Re: copyright licence
Date: Thu, 23 May 2024 18:37:11 +0200 [thread overview]
Message-ID: <87r0dso56w.fsf@web.de> (raw)
In-Reply-To: <7cb01979-b66c-eae7-7e97-96b44808cc1e@posteo.at> (gfp@posteo.at's message of "Thu, 23 May 2024 14:51:31 +0000")
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]
gfp <gfp@posteo.at> writes:
> 1.
> what copyright licence would be appropriate
> that only the GUIX community can use my song,
> but nobody else?
This kind of exclusion of the world is inherently incompatible with the
values at the heart of Free Culture and of Guix.
I know that this is unusual compared to much of the world being about
conflict between different groups, and I know that it can take some time
to get used to. It took me some time to do it back when I built fantasy
worlds. But it is worth it.
It is what makes Free Software special — building creations for all of
humanity instead of only to those who are part of an in-group.
If you however want to prevent people from using the song to corrupt the
core values of Guix, a sharealike license is the way to go: only allow
those to use the song who support similar values of Free Culture.
It doesn’t matter how their community calls itself as long as they
adhere to the Freedoms the Sharelike license protects.
Best wishes,
Arne
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
next prev parent reply other threads:[~2024-05-23 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 14:51 copyright licence gfp
2024-05-23 16:37 ` Dr. Arne Babenhauserheide [this message]
2024-05-23 17:14 ` pelzflorian (Florian Pelz)
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=87r0dso56w.fsf@web.de \
--to=arne_bab@web.de \
--cc=felix.lechner@lease-up.com \
--cc=gfp@posteo.at \
--cc=help-guix@gnu.org \
--cc=pelzflorian@pelzflorian.de \
--cc=sirgazil@zoho.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).