From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Philip McGrath <philip@philipmcgrath.com>,
Bone Baboon <bone.baboon@disroot.org>,
guix-devel@gnu.org
Subject: Re: cowsay could attract copyright and trademark enforcement action
Date: Sat, 17 Jul 2021 08:39:51 +0200 [thread overview]
Message-ID: <dd1563dc7df6f5eb1012c16fa531fba9dd1b60b5.camel@student.tugraz.at> (raw)
In-Reply-To: <6f1db8a2-b3b3-5a54-53e8-f54751f8299d@philipmcgrath.com>
Fair points and well argued.
Am Samstag, den 17.07.2021, 01:46 -0400 schrieb Philip McGrath:
> On 7/16/21 6:26 PM, Leo Prikler wrote:> As others point out, it is
> debatable whether or not such a trademark
> > can be enforced, but what we should be discussing -- and I'd be
> > more
> > than happy to be wrong on this -- is whether or not the cowfiles
> > can be
> > distributed under GPL-compatible terms/in accordance with the FSDG.
> These files seem to me to be non-functional data, analogous to game
> graphics, which the FSDG do not require to have free/libre licenses.
> Just as firmware is still code, even if it is represented as an array
> of
> numbers, I think ASCII art templates are data, even if they are
> embedded
> in Perl fragments.
>
> (In the Lisp tradition, I think the distinction between code and data
> is
> a fuzzy one, but this case seems fairly clear to me.)
>
> On the broader issues, I also am not a lawyer, but I would expect all
> of
> these files to be protected by the rights of fair use, fair dealing,
> and
> other limitations or exceptions to copyright. Limitations and
> exceptions
> seem to trademark law also seem to apply.
>
> Fair use and analogous rights are vitally important protections of
> freedom, including software freedom. For example, in the recent case
> of
> Google v. Oracle, fair use was the legal right which protected the
> freedom of the Java APIs. (The decision also left open the
> possibility
> that APIs may not be copyrightable at all.)
>
> Apparently these files are over 20 years old and have been widely
> distributed without objections. If Guix were to remove these files,
> we
> would implicitly be disagreeing with the apparent community
> consensus
> and saying that users do not have the freedom to create, use, or
> share
> such cowfiles. That's not a position I think Guix ought to take,
> especially not against the apparent consensus of the broader free
> software community.
>
> -Philip
next prev parent reply other threads:[~2021-07-17 6:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 2:56 cowsay could attract copyright and trademark enforcement action Bone Baboon
2021-07-14 13:57 ` Bone Baboon
2021-07-15 11:06 ` Leo Prikler
2021-07-16 22:26 ` Leo Prikler
2021-07-17 5:46 ` Philip McGrath
2021-07-17 6:39 ` Leo Prikler [this message]
2021-07-16 22:26 ` Leo Prikler
2021-07-17 1:42 ` Cees de Groot
2021-07-15 16:42 ` Leo Famulari
2021-07-16 12:39 ` Bone Baboon
2021-07-16 14:24 ` fuzzyTew
2021-07-16 20:23 ` Bone Baboon
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dd1563dc7df6f5eb1012c16fa531fba9dd1b60b5.camel@student.tugraz.at \
--to=leo.prikler@student.tugraz.at \
--cc=bone.baboon@disroot.org \
--cc=guix-devel@gnu.org \
--cc=philip@philipmcgrath.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/guix.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).