public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: lkcl <luke.leighton@gmail.com>
Cc: GCC developers <gcc@gcc.gnu.org>
Subject: Re: rust non-free-compatible trademark
Date: Mon, 18 Jul 2022 00:59:54 +0200	[thread overview]
Message-ID: <YtSUagpJh6cXcBq7@wildebeest.org> (raw)
In-Reply-To: <CAPweEDy07TJJTg36zOMOg2yEqO6ekuBagrz1WffJo7yhs0TiMg@mail.gmail.com>

Hi Luke,

On Sun, Jul 17, 2022 at 07:29:22PM +0100, lkcl wrote:
> 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.

As far as I know all discussions have been in public. The Rust
Foundation is aware of the gccrs frontend and other "unofficial"
implementations.

Using the word "rust" in the implementation of the gccrs frontend
doesn't need any "Authorization under License". Normal use of a word
isn't something that Trademarks prevent.

> 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.

I believe the Rust Foundation is reasonable. We aren't using the word
mark "Rust" in a way that needs any trademark license. And even if we
did the Rust Foundation allows all usage of the word mark as long as
you don't deliberately try to confuse about (commercially) shipping a
product called "Rust" that is officially endorsed by the Rust
Foundation.

If the Rust Foundation really believed that some of the marketing we
do around the gccrs frontend is confusing they would contact us and if
they are reasonable we can adjust the messaging (we can be reasonable
too).

The best advice I can give you is to listen to what the Rust
Foundation itself says about their trademark:

  Please do not approach users of the trademarks with a
  complaint. That should be left to the Rust Foundation and its
  representatives. Thanks!

  If you have a specific question or concern about promoting Rust or
  using its trademarks, please contact the Rust Foundation:
  contact@rustfoundation.org.

Cheers,

Mark

  reply	other threads:[~2022-07-17 22:59 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
2022-07-17 22:59           ` Mark Wielaard [this message]
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=YtSUagpJh6cXcBq7@wildebeest.org \
    --to=mark@klomp.org \
    --cc=gcc@gcc.gnu.org \
    --cc=luke.leighton@gmail.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.
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).