unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Protesilaos Stavrou <info@protesilaos.com>
To: "emacs-devel" <emacs-devel@gnu.org>
Subject: Dual license the colours of the Modus themes?
Date: Thu, 05 May 2022 07:31:09 +0300	[thread overview]
Message-ID: <87mtfwsir6.fsf@protesilaos.com> (raw)

Hello everyone,

The modus-themes (modus-operandi, modus-vivendi) are distributed under
the terms of the GNU GPLv3 and are part of Emacs.  I was wondering
whether their colours could be licensed under different terms, such as
by putting them in the public domain (with Creative Commons).

I am reading the GNU commentary on licenses[1] and understand that my
choice will have to be compatible with the GPL.  What I am not sure
about are the following:

* Is it possible to keep the modus-themes under the GPL but also
  dedicate its colours to the public domain?

* Does the inclusion of the modus-themes in Emacs impose any constraints
  on the possibility of such a dual license arrangement?

If there is any precedent or resources I could refer to, please let me
know.

I intend to do what is good for Emacs and, by extension, GNU: if a dual
license for the colours of the modus-themes can cause problems for
Emacs, then I will simply not do it.

As for why I am asking this: there are cases where someone wants to
reuse the colours of the modus-themes---just the colours---for stylistic
purposes and there is uncertainty whether they are allowed to do so
under the terms of the GPL.

All the best,
Protesilaos (or simply "Prot")

[1] <https://www.gnu.org/licenses/license-list.html>

-- 
Protesilaos Stavrou
https://protesilaos.com



             reply	other threads:[~2022-05-05  4:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05  4:31 Protesilaos Stavrou [this message]
2022-05-05  5:06 ` Dual license the colours of the Modus themes? 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
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=87mtfwsir6.fsf@protesilaos.com \
    --to=info@protesilaos.com \
    --cc=emacs-devel@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.
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).