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:11:40 +0100	[thread overview]
Message-ID: <CAPweEDwGU3S8N1nEPZbNFej1Mh7MjjrCZUteKheQFXku9UDx_g@mail.gmail.com> (raw)
In-Reply-To: <20220717174101.GA4487@gnu.wildebeest.org>

On Sun, Jul 17, 2022 at 6:41 PM Mark Wielaard <mark@klomp.org> wrote:

> I think you are misinterpreting when you need a trademark license for
> usage a word mark in an implementation of a compiler for a programming
> language.

i'm aware of the difference.  i mentioned this in my first reply to Richard
(and covered it briefly in my reply to you as well)

> Note that gcc used to come with a full implementation of the
> Java programming language, compiler, runtime and core library
> implementation (for which I was the GNU maintainer). None of that
> required a trademark license because the usage of the word java was
> just for compatibility with the java programming language.

yes. i mentioned that example in my reply to you and in my separate
reply to Richard: you may have missed it.

that would likely be down to the difference in the Java Trademark License
and the Rust Trademark License.

with the wording the Rust Trademark License has attempted to create a poor-man's
Certification Mark.

Certification Mark Law is an advanced variant of Trademark Law covering
Standards Compliance.

> And since
> there was no claim of being or distributing Java(tm). The same is true
> for Rust(tm) and the gccrs frontend.

this would be perfectly fine if the Rust Foundation had not explicitly
worded the Trademark License in terms of a poor-man's Certification
Mark.

i gave the relevant section that you can pass over to appropriate Legal
Counsel.

i leave it with you as i am just a "reasonably well-informed
non-lawyer messenger"
here.

> Also note that the Rust Foundation is aware of the work and has
> already integraeted parts of gcc through another alternative
> implementation (based on libgccjit). As far as we know thy have no
> problem with either alternative implementation of the Rust programming
> language.

then that needs to be put into writing and made public.  only the Trademark
Holder may do that - not you. otherwise if you claim something and it turns
out not to be true, you can be sued for misrepresentation.

did i say Trademarks are a pig already?

l.

  reply	other threads:[~2022-07-17 18:11 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 [this message]
2022-07-17 18:29         ` lkcl
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=CAPweEDwGU3S8N1nEPZbNFej1Mh7MjjrCZUteKheQFXku9UDx_g@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).