unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bone Baboon <bone.baboon@disroot.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: cowsay could attract copyright and trademark enforcement action
Date: Fri, 16 Jul 2021 08:39:06 -0400	[thread overview]
Message-ID: <87r1fyph5h.fsf@disroot.org> (raw)
In-Reply-To: <YPBli0HGj+wJyD8h@jasmine.lan>

Leo Famulari writes:

> On Sun, Jul 11, 2021 at 10:56:33PM -0400, Bone Baboon wrote:
>> cowsay has many questionable files that could attract copyright and
>> trademark enforcement action.
>
> I doubt it. Many of these files have been in the cowsay source code
> since 1999 (apparently), and at least since 2004, according to
> archive.org:
>
> https://web.archive.org/web/20040404080800/http://www.nog.net/~tony/warez/cowsay.shtml

Thanks for sharing that.

I would like to point out that the situation is not static as the
ownership of trademark and copyright can change over time and the new
owners may choose to behave differently.

A directly relevant example is the Star Wars cowsay
files. <https://en.wikipedia.org/wiki/Star_Wars> says that Lucasfilm
Ltd. the owners of the Star Wars franchise was acquired by Disney.


  reply	other threads:[~2021-07-16 12:43 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
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 [this message]
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=87r1fyph5h.fsf@disroot.org \
    --to=bone.baboon@disroot.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).