unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Protesilaos Stavrou <info@protesilaos.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
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 16:21:13 +0300	[thread overview]
Message-ID: <87ee12depi.fsf@protesilaos.com> (raw)
In-Reply-To: <jwvtu9yvr4s.fsf-monnier+emacs@gnu.org>

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Mon, 09 May 2022 08:21:01 -0400
>
>> 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.

Okay.  What I want is to preserve the GPL.

> 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".  ]

In this case, "just their colors" means to publish a page on my website
like protesilaos.com/modus-themes-colors that contains a table like the
following and which states it is distributed under CC0:

| name              | value   |
|-------------------+---------|
| bg-main           | #ffffff |
| fg-main           | #000000 |
| red               | #a60000 |
| magenta-alt-other | #5317ac |

[ All values will be taken from the variables
  modus-themes-operandi-colors, modus-themes-vivendi-colors. ]

-- 
Protesilaos Stavrou
https://protesilaos.com



  reply	other threads:[~2022-05-09 13: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
2022-05-09 13:21       ` Protesilaos Stavrou [this message]
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=87ee12depi.fsf@protesilaos.com \
    --to=info@protesilaos.com \
    --cc=dimech@gmx.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).