public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: lkcl <luke.leighton@gmail.com>
Cc: Gabriel Ravier <gabravier@gmail.com>,
	Florian Weimer <fweimer@redhat.com>,
	 lkcl via Gcc <gcc@gcc.gnu.org>
Subject: Re: rust non-free-compatible trademark
Date: Tue, 19 Jul 2022 11:55:42 +0100	[thread overview]
Message-ID: <CAH6eHdTULSR+eSTs52ymSKHbQ9zf6qgvngMC7hC5Dv9U=WcpRA@mail.gmail.com> (raw)
In-Reply-To: <CAPweEDz3JOhbCeDDZLXAsC0iQZVFFEk-LxaVSJA9vnaZb9RmSA@mail.gmail.com>

On Tue, 19 Jul 2022 at 11:27, lkcl via Gcc <gcc@gcc.gnu.org> wrote:
>
> On Tue, Jul 19, 2022 at 12:41 AM David Edelsohn <dje.gcc@gmail.com> wrote:
> >
> > Luke,
> >
> > The GCC Community will give the issues that you raised due
> > consideration and resolve any problems through appropriate channels.
>
> David: although this was a private reply I am assuming that is in
> error, and i feel it is appropriate to make public, and wrap up this
> thread.
>
> thank you for being literally the first person to very kindly give an explicit
> indication that i've been heard.  that's all that any of you had to do, and
> now that i feel i've been heard i am no longer deeply frustrated and angry.

I already said you were not being ignored, but you chose to interpret
it as a dismissal of your feelings. Telling people to have more
empathy and then reacting negatively when people have responses you
don't like comes across as hypocritical. Your communication affects
others too.

>
>     https://www.crnhq.org/cr-kit/#empathy

This should apply to all parties, not just the ones that aren't you.

"Empathy is about building rapport, openness and trust between people.
When it is absent, people are less likely to consider your needs and
feelings."

You started this thread with strong words like "draconian", "Unlawful"
and immediately insisted on absolutes like "completely removed". No
attempt to build rapport, or consider the feelings of the gccrs
developers. It's no wonder it went downhill!

>
> Gabriel i very much appreciate your efforts to tell me that "i am
> the problem" (see #empathy above) and i acknowledge those efforts.
> let's not reduce the S/N ratio any further, eh?
>
> perhaps everyone can learn from this experience, and some point
> down the line appreciate that, as an outsider with no vested interest,
> i was the only member in this community that could safely raise that
> "The Rust Foundation Emperor has no Clothes" without damage to
> their tenure, client base, or career, in what is one of the highest-paying
> most strategically critical FOSS Projects in the world.

Nobody who has replied to you was trying to preserve their career or
tenure, they just didn't agree with you. That's allowed.

> in summary i look forward to seeing the public results of the consideration of
> conversion of the Rust Trademark to a Certification Mark and the clear benefits
> and natural fit with existing FOSS development practices that entails.
>
>     http://archive.adaic.com/pol-hist/policy/trademrk.txt
>
> l.
>
>
> l.

      reply	other threads:[~2022-07-19 10:55 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
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 [this message]

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='CAH6eHdTULSR+eSTs52ymSKHbQ9zf6qgvngMC7hC5Dv9U=WcpRA@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=gabravier@gmail.com \
    --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).