unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0@n0.is
To: Jelle Licht <jlicht@fsfe.org>
Cc: guix-devel@gnu.org
Subject: Re: Guix trademarked by Express Logic
Date: Mon, 11 Mar 2019 21:33:35 +0000	[thread overview]
Message-ID: <20190311213335.ybjika3lacbe6eyd@uptimegirl> (raw)
In-Reply-To: <86d0mxgrw5.fsf@jlicht.xyz>

Jelle Licht transcribed 1.9K bytes:
> mikadoZero <mikadozero@yandex.com> writes:
> 
> > I have search guix-devel for this and did not find it.  I would like to
> > [ snip ] 
> Thanks for looking into this.
> 
> > # Proactive name change
> >
> > Looking at the pug thread above shows that it would have been nice if
> > Jade had not been forced to change their name so quickly and could have
> > engaged it's community further on ideas for a new name.
> >
> > This raises the idea that proactively changing Guix's name might be
> > better than reacting to a forced name change.  A benefit to a proactive
> > name change is being able to chose the timing.  So for example the name
> > change could be planned to coincide with the 1.0 release which I have
> > heard is approaching.  Similar to a butterfly emerging from a
> > chrysalis.  Maybe there is a opportunity here and this could be turned
> > into a nice announcement.
> 
> I humbly disagree with proactively doing anything of the sorts; first of
> all, there are two separate issues (as you mentioned):
> - Are we allowed to call Guix Guix?
> - Do we want to call Guix Guix?
> 
> As such, I think it is premature to proactively change something which
> *might* not even be a (legal) problem at all, let alone something
> desired by the community. I *do* agree that these questions should
> probably be answered before 1.0 comes around.
> 
> > [ snip ]
> > # Contacting Express Logic
> >
> > Also it might be good to reach out to Express Logic as they may not
> > actually have any problem with the Guix free software project using the
> > name they have trademarked.
> 
> I really think that "software" is much too broad a category to consider
> for a trademark clash in this case. From what I can see, there is barely
> any overlap between our Guix and the GUIX product that Express Logic is
> working on. This might just be my vocational bias in action as a
> software engineer though, and of course; I Am Not A Lawyer.

The other Guix keeps coming up over the years.
I don't think we have to do anyting because it's 2 separate fields
of software.
No problem unless one of the Guix starts making it one.
 
> >
> > # Summary
> >
> > I am not recommending any specific course of action.  I just want to
> > start a discussion.
> 
> Point taken :-).
> 
> 

  reply	other threads:[~2019-03-11 21:34 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 [this message]
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 ` Express Logic claims GUIX trademark Tobias Geerinckx-Rice
2019-03-12  4:06   ` 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=20190311213335.ybjika3lacbe6eyd@uptimegirl \
    --to=ng0@n0.is \
    --cc=guix-devel@gnu.org \
    --cc=jlicht@fsfe.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).