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: Sat, 17 Jul 2021 00:26:53 +0200 [thread overview]
Message-ID: <70ee390f652c34852aca9df7cbc2d0c3d4b20338.camel@student.tugraz.at> (raw)
In-Reply-To: <ee5382ef6bcceb867ae526e1afcd977c5d798eaa.camel@student.tugraz.at>
Am Donnerstag, den 15.07.2021, 13:06 +0200 schrieb Leo Prikler:
> 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.
To expand on this, the 160 characters thing is a compromise, as
according to §51a of the UrhG the use of copyrighted material for the
purposes of caricature or parody is legal in Germany [1]. Vader koalas
would probably fall under this paragraph.
Now one could hypothesize that this applies to other parts of the EU as
well, but I wouldn't be too sure about that. The Austrian UrhG at
least to my untrained eyes and substring search appears to be lacking
such a right to parody our great mouse overlord.
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.
Regards,
Leo
[1] https://www.gesetze-im-internet.de/urhg/__51a.html
next prev parent reply other threads:[~2021-07-16 22:28 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 [this message]
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=70ee390f652c34852aca9df7cbc2d0c3d4b20338.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).