public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: lkcl <luke.leighton@gmail.com>
To: Mark Wielaard <mark@klomp.org>
Cc: GCC developers <gcc@gcc.gnu.org>
Subject: Re: rust non-free-compatible trademark
Date: Sun, 17 Jul 2022 19:29:22 +0100	[thread overview]
Message-ID: <CAPweEDy07TJJTg36zOMOg2yEqO6ekuBagrz1WffJo7yhs0TiMg@mail.gmail.com> (raw)
In-Reply-To: <CAPweEDwGU3S8N1nEPZbNFej1Mh7MjjrCZUteKheQFXku9UDx_g@mail.gmail.com>

ah. right. sorry Mark i missed something.

whilst you *as developers* have been in contact with the Rust Foundation
and presumably have private assurances that your use of the Trademarked
word "rust" is Authorised under License (through either implication or by
actual explicit approval) absolutely nobody else does.

all *new* gcc developers for example who have *not* been party to
those private conversations may not safely assume that they are part
of any such explicit or implicit consent.

and given that literally anyone in the world may pick up the gcc source
code and consider themselves to become a developer (as permitted
by the GPL) that's a serious concern.

in addition to that, even if you as developers have indeed been
explicitly or implicitly granted a Trademark License that does *not*
extend to *Distributors* of gcc and i again refer you to the wording that i
copied here, and to the debian bugreport.

i appreciate that this is a bloody nuisance.  i do however expect the
Rust Foundation to get their act together and act Reasonably and
Fairly to sort out the mess they've accidentally created.

after all, Trademarks do have value in FOSS Projects, to protect
them from harm in ways that Copyright Licenses cannot touch.
it's just rather unfortunate that they're really not well-understood,
not even by Lawyers!

l.

  reply	other threads:[~2022-07-17 18:29 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-17 15:28 lkcl
2022-07-17 16:25 ` Richard Biener
2022-07-17 16:47   ` lkcl
2022-07-17 18:24     ` Richard Kenner
2022-07-17 18:57   ` Alexandre Oliva
2022-07-17 16:31 ` Mark Wielaard
2022-07-17 17:06   ` lkcl
2022-07-17 17:41     ` Mark Wielaard
2022-07-17 18:11       ` lkcl
2022-07-17 18:29         ` lkcl [this message]
2022-07-17 22:59           ` Mark Wielaard
2022-07-17 23:07             ` lkcl
2022-07-17 23:55             ` Richard Kenner
2022-07-17 18:28       ` Richard Kenner
2022-07-17 18:54       ` Alexandre Oliva
2022-07-18  7:09   ` David Brown
2022-07-18  8:07     ` lkcl
2022-07-18  8:50       ` Jonathan Wakely
2022-07-18  9:06         ` lkcl
2022-07-18 14:30 ` lkcl
2022-07-18 17:11   ` Richard Kenner
2022-07-18 17:12   ` Richard Kenner
2022-07-18 18:32   ` Florian Weimer
2022-07-18 18:43     ` Arthur Cohen
2022-07-19  9:43       ` Florian Weimer
2022-07-18 19:35     ` lkcl
2022-07-18 21:01       ` David Malcolm
2022-07-18 23:09         ` lkcl
2022-07-19  9:27           ` Gabriel Ravier
2022-07-19 10:26             ` lkcl
2022-07-19 10:55               ` Jonathan Wakely

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPweEDy07TJJTg36zOMOg2yEqO6ekuBagrz1WffJo7yhs0TiMg@mail.gmail.com \
    --to=luke.leighton@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mark@klomp.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.
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).