unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Bone Baboon <bone.baboon@disroot.org>, guix-devel@gnu.org
Subject: Re: cowsay could attract copyright and trademark enforcement action
Date: Thu, 15 Jul 2021 13:06:56 +0200	[thread overview]
Message-ID: <ee5382ef6bcceb867ae526e1afcd977c5d798eaa.camel@student.tugraz.at> (raw)
In-Reply-To: <87a6mphubk.fsf@disroot.org>

Am Mittwoch, den 14.07.2021, 09:57 -0400 schrieb Bone Baboon:
> [...]
> 
> In this response to the pull request I submitted about the
> questionable files in the cowsay repository
> <
> https://github.com/tnalpgge/rank-amateur-cowsay/pull/4#issuecomment-878092487
> >
> apjanke is requesting feedback.
> 
> > If there are any actual IP lawyers, relevant IP owners, or
> > distributions who redistribute cowsay who would like to weigh in on
> > this, I'd definitely like to hear what you have to say.
> 
> For those who want to respond to apjanke but do not have or do not
> want to use a GitHub account I can link this email thread in the
> discussion about the pull request.
I am not an IP lawyer, nor do I own any of said characters, but I'd
like to point out that not all jurisdictions follow the US model.  In
Germany for example, you can (in the near future/already?) not use more
than 160 characters of copyrighted material -- granted, the cowfiles
are shorter than that, but copyright law is troubling over here in
Europe nonetheless.

Furthermore:
> Given that this is a noncommercial work [...] [a]nd they're [the
> characters] not being sold
I don't think applies to free as in the case of freedom distributions
like Trisquel or Guix.  A non-commercial clause would be a violation of
the GPL, the very license cowsay is distributed under.  As the author
of cowsay, apjanke could very well ship such characters with it (unless
they themselves also happen to use GPL'd software as dependency in
which they'd be violating that GPL), but unless they can pass on the
freedom to distribute those cows *under the terms of the GPL*, no one
else can either, which would make distributing cowsay with those
characters illegal
1. under trademark law
2. under the terms of the GPL

Clearly, copyright law in 2021 is not broken at all :^)

Regards,
Leo



  reply	other threads:[~2021-07-15 11:07 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 [this message]
2021-07-16 22:26     ` Leo Prikler
2021-07-17  1:42       ` Cees de Groot
2021-07-16 22:26     ` Leo Prikler
2021-07-17  5:46       ` Philip McGrath
2021-07-17  6:39         ` Leo Prikler
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=ee5382ef6bcceb867ae526e1afcd977c5d798eaa.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --cc=bone.baboon@disroot.org \
    --cc=guix-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/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).