From: Christopher Dimech <dimech@gmx.com>
To: Protesilaos Stavrou <info@protesilaos.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Dual license the colours of the Modus themes?
Date: Mon, 9 May 2022 15:32:50 +0200 [thread overview]
Message-ID: <trinity-1da0d9b9-074a-47da-ad1b-196835f191db-1652103170697@3c-app-mailcom-bs16> (raw)
In-Reply-To: <87ee13yzt5.fsf@protesilaos.com>
> Sent: Monday, May 09, 2022 at 6:39 PM
> From: "Protesilaos Stavrou" <info@protesilaos.com>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "emacs-devel" <emacs-devel@gnu.org>
> Subject: Re: Dual license the colours of the Modus themes?
>
> > From: Christopher Dimech <dimech@gmx.com>
> > Date: Sun, 08 May 2022 11:55:14 +0200
> >
> >> * Is it possible to keep the modus-themes under the GPL but also
> >> dedicate its colours to the public domain?
> >
> > Release modus-themes including its dedicate colours under GPLv3+, or
> > do something better by releasing under AGPLv3+. Then release the colours
> > separately under a free software license. If you want to use Creative
> > Commons, use only CC0.
>
> Thank you! The modus-themes are already GPLv3+ licensed and copyright
> is assigned to the FSF.
>
> 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.
There will be no complications.
> I will seek to confirm this conclusion and act accordingly. Again, my
> priority is Emacs: I will not jeopardise it.
You can release with any number of licences you want. If emacs want them
GPL Compatible, then release them for the emacs maintainers as GPL Compatible.
I discourage mixing licenses when releasing for Gnu. You can then release
the colours any other ways you want. As the author, no rules apply to you
with regards to how you can use them or release them, unless forced on you
by some license of somebody else.
> --
> Protesilaos Stavrou
> https://protesilaos.com
>
prev parent reply other threads:[~2022-05-09 13:32 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-1da0d9b9-074a-47da-ad1b-196835f191db-1652103170697@3c-app-mailcom-bs16 \
--to=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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.