From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Protesilaos Stavrou <info@protesilaos.com>
Cc: Christopher Dimech <dimech@gmx.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Dual license the colours of the Modus themes?
Date: Mon, 09 May 2022 08:21:01 -0400 [thread overview]
Message-ID: <jwvtu9yvr4s.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87ee13yzt5.fsf@protesilaos.com> (Protesilaos Stavrou's message of "Mon, 09 May 2022 09:39:50 +0300")
> My understanding is that I can distribute their colours---just the
> colours---under Creative Commons CC0 (I am their sole author). My
> concern was whether there could be complications for Emacs, since the
> modus-themes are a part of it. What I have gathered thus far is that
> such an arrangement should not be a problem.
AFAIK when you assigned the copyright to the FSF, the FSF returned to
you almost all those rights, including the right to redistribute this
same work under any license you like.
So if you want, *you* can distribute (on your side) the whole of
modus-themes under the CC0. There should be no problem with that.
And of course you can also distribute just "their colors" under any
license you like. [ Tho, I must admit I don't know what it means to
distribute "just their colors". ]
Stefan
next prev parent reply other threads:[~2022-05-09 12:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 4:31 Dual license the colours of the Modus themes? Protesilaos Stavrou
2022-05-05 5:06 ` Po Lu
2022-05-05 5:29 ` Protesilaos Stavrou
2022-05-05 18:31 ` Case Duckworth
2022-05-05 19:49 ` Protesilaos Stavrou
2022-05-08 9:55 ` Christopher Dimech
2022-05-08 10:30 ` Eli Zaretskii
2022-05-09 6:39 ` Protesilaos Stavrou
2022-05-09 12:21 ` Stefan Monnier [this message]
2022-05-09 13:21 ` Protesilaos Stavrou
2022-05-09 13:32 ` Stefan Monnier
2022-05-11 9:05 ` Richard Stallman
2022-05-09 13:33 ` Eli Zaretskii
2022-05-09 23:20 ` Richard Stallman
2022-05-09 13:32 ` Christopher Dimech
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvtu9yvr4s.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dimech@gmx.com \
--cc=emacs-devel@gnu.org \
--cc=info@protesilaos.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).