unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <somebody@not-sent-or-endorsed-by.tobias.gr>
To: mikadoZero <mikadozero@yandex.com>
Cc: guix-devel@gnu.org
Subject: Re: Express Logic claims GUIX trademark
Date: Mon, 11 Mar 2019 20:00:16 +0100	[thread overview]
Message-ID: <87a7i1jkxr.fsf@nckx> (raw)
In-Reply-To: <pnqxtgyz.fsf@yandex.com>

Guix, mikadoZero,

I know you're not a fan of [the common pronunciation of] the name 
Guix, but going straight from my ironic quote of a shitty PDF to a 
public and ‘proactive name change’ proposal is at best premature.

> If it is the case that Guix the free software project does not 
> have a
> trademark for Guix, then I would like to share what looks like a 
> clear
> parallel.  It involves another free software project that used 
> to be
> called Jade.  Jade did not have a trademark for Jade.  A 
> software
> company had the trademark for Jade.  The company forced Jade to 
> change
> it's name.

Wow.  That's super disingenuous (by ‘that’ I mean the original 
posts[0], which you accurately paraphrase).  It certainly didn't 
leave me with the favourable impression of the Free software 
project that was probably intended.

Yes, if you start a software repo in 2010 using the name that a 
software(!) company had registered in 2003 for their (you guessed 
it) software, you might be ‘forced’ to be just a bit more 
original.  The heart truly weeps.  At least they restyled 
themselves Pug and not UnderDog.

So no, and luckily for everyone, there are few parallels to Guix 
to be found here.

It took me all of 20 seconds to find the actual GUIX trademark 
registration[1], so we can stop basing this discussion on 
regrettable typographical choices in press releases.

It's 4 months old.

Meanwhile, we have:

  commit 207cba8114d354737b231e510d6110ea2a42e07b
  Author: Ludovic Courtès <ludo@gnu.org>
  Date:   Wed Apr 18 23:21:11 2012 +0200

    Initial commit.

Do 6+ years of prior public use trump registration?  Not 
necessarily, but it's a far cry from what the Jade-lang folks did.

I think we should talk to a lawyer.

Kind regards,

T G-R

[0]: https://github.com/pugjs/pug/issues/2184
[1]: 
http://tsdr.uspto.gov/#caseNumber=87948650&caseType=SERIAL_NO&searchType=statusSearch

  parent reply	other threads:[~2019-03-12  0:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11 18:15 Guix trademarked by Express Logic mikadoZero
2019-03-11 18:58 ` Jelle Licht
2019-03-11 21:33   ` ng0
2019-03-12  0:31     ` mikadoZero
2019-03-12  4:37       ` Leo Famulari
2019-03-12 10:52         ` ng0
2019-03-11 21:54   ` mikadoZero
2019-03-11 22:37     ` Jelle Licht
2019-03-11 19:00 ` Tobias Geerinckx-Rice [this message]
2019-03-12  4:06   ` Express Logic claims GUIX trademark Pjotr Prins
2019-03-12  9:10   ` Hartmut Goebel
2019-03-12 10:05     ` Tobias Geerinckx-Rice
2019-03-12 14:33   ` Ludovic Courtès

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=87a7i1jkxr.fsf@nckx \
    --to=somebody@not-sent-or-endorsed-by.tobias.gr \
    --cc=guix-devel@gnu.org \
    --cc=mikadozero@yandex.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).