unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Case Duckworth <acdw@acdw.net>
To: Protesilaos Stavrou <info@protesilaos.com>, Po Lu <luangruo@yahoo.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Dual license the colours of the Modus themes?
Date: Thu, 05 May 2022 13:31:07 -0500	[thread overview]
Message-ID: <87pmkrltlg.fsf@acdw.net> (raw)
In-Reply-To: <874k24sg2l.fsf@protesilaos.com>

Protesilaos Stavrou <info@protesilaos.com> writes:

>> From: Po Lu <luangruo@yahoo.com>
>> Date: Thu, 05 May 2022 13:06:47 +0800
>>
>> Disclaimer, IANAL.
>
> Thank you for the feedback!  Yes, I am the sole author.  I devised the
> colour palette from scratch and occasionally make minor tweaks to it.

Let me repeat Po Lu's warning of IANAL, but from a cursory search online
it appears that color schemes themselves can't be copyrighted, at least
under some legal environments (I'm in America, so I'm assuming my
searches are returning results at least semi-pertinent to American law).

You /can/ copyright images that use certain colors, but not the actual
pallette or distribution of colors themselves.  I would assume it's like
how recipes are non-copywriteable (hence the long digressions into the
author's personal life preceding all recipes found online).

I only checked [1] and [2] before sending this email, so you might want
to consult with a lawyer in your jurisdiction.

[1]: https://www.colormatters.com/color-and-marketing/color-branding-legal-rights
[2]: https://www.colourlovers.com/faq/18/How_can_you_copyright_a_color_palette

--
Hugs,
Case Duckworth
https://www.acdw.net
https://breadpunk.club/~breadw



  reply	other threads:[~2022-05-05 18:31 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 [this message]
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=87pmkrltlg.fsf@acdw.net \
    --to=acdw@acdw.net \
    --cc=emacs-devel@gnu.org \
    --cc=info@protesilaos.com \
    --cc=luangruo@yahoo.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).