public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@gnu.org>
To: Mark Wielaard <mark@klomp.org>
Cc: Siddhesh Poyarekar <siddhesh@gotplt.org>,
	Overseers mailing list <overseers@sourceware.org>,
	gdb@sourceware.org, libc-alpha@sourceware.org,
	binutils@sourceware.org, gcc@gcc.gnu.org
Subject: Re: The GNU Toolchain Infrastructure Project
Date: Tue, 11 Oct 2022 12:58:05 -0300	[thread overview]
Message-ID: <ora662nyia.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <517db8de93ece0eb81923fd05a731ca1da65e1dd.camel@klomp.org> (Mark Wielaard's message of "Fri, 07 Oct 2022 10:57:34 +0200")

On Oct  7, 2022, Mark Wielaard <mark@klomp.org> wrote:

> Hi Siddhesh,
> On Thu, 2022-10-06 at 17:07 -0400, Siddhesh Poyarekar wrote:
>> Could you clarify in what way you think the *scope* got changed
>> between 
>> the private communications and the proposal that actually got posted?

> Given that they were private I can only talk for myself:
> https://inbox.sourceware.org/overseers/Yz9dZWC9QIv+r4LH@elastic.org/T/#m22a52506bc116dbcb10c8cbfa8ed89510f4dc1b7
> But various people listed as "key stakeholders consulted" said they
> either didn't know anything about this, they were contacted but never
> got any details, or were only told about parts of it.

That makes me very concerned.

Negotiating a community agreement in secrecy is worrysome to boot, but
giving different stakeholders different views of what the agreement
supposedly amounts to is a political trick normally used to push an
agreement through that would have been rejected by a majority, even if
for different reasons.  By presenting different views to different
parties, and misrepresenting their support for those partial views as
support for the whole they didn't even know about, one might put enough
pressure to persuade other parties to drop their objections, if they
believe the claimed broad support.

Even I got presented two very different views of the proposal by two of
its lead proponents, with different motivations (which is reasonable)
but factually conflicting commitments (which is not).

This all taken together makes me conclude that the alleged support for
the proposal, claimed by its lead proponents, is not something that can
be counted on, or taken for granted.  It needs to be double-checked by
circulating publicly a proposal encompassing everything that the
proposal entails, and then seeing whether it's actually acceptable as a
whole.  Given the chosen strategy, I suspect it won't be.

-- 
Alexandre Oliva, happy hacker                https://FSFLA.org/blogs/lxo/
   Free Software Activist                       GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts.  Ask me about <https://stallmansupport.org>

  parent reply	other threads:[~2022-10-11 15:58 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d9cb6cf9-89f5-87bb-933b-a03240479e71@redhat.com>
     [not found] ` <a9396df3-5699-46ef-0b33-6c7589274654@redhat.com>
2022-10-02 20:47   ` Mark Wielaard
2022-10-04 13:46     ` Siddhesh Poyarekar
2022-10-04 14:01       ` Frank Ch. Eigler
2022-10-04 14:13         ` Siddhesh Poyarekar
2022-10-04 14:19           ` Frank Ch. Eigler
2022-10-04 14:33             ` Siddhesh Poyarekar
2022-10-04 14:41               ` Frank Ch. Eigler
2022-10-04 14:55                 ` Siddhesh Poyarekar
2022-10-04 15:07                   ` Frank Ch. Eigler
2022-10-06 21:42             ` Alexandre Oliva
2022-10-04 17:10       ` Christopher Faylor
2022-10-04 17:17         ` Siddhesh Poyarekar
2022-10-04 18:42           ` Christopher Faylor
2022-10-04 19:05           ` Mark Wielaard
2022-10-04 19:10             ` Siddhesh Poyarekar
2022-10-06 20:02               ` Mark Wielaard
2022-10-06 20:12                 ` Christopher Faylor
2022-10-06 21:37                   ` Siddhesh Poyarekar
2022-10-07 13:39                     ` Mark Wielaard
2022-10-06 21:07                 ` Siddhesh Poyarekar
2022-10-06 21:36                   ` Frank Ch. Eigler
2022-10-06 21:44                     ` Siddhesh Poyarekar
2022-10-06 22:57                       ` Frank Ch. Eigler
2022-10-11 13:02                         ` Siddhesh Poyarekar
2022-10-07  8:57                   ` Mark Wielaard
2022-10-11 13:24                     ` Siddhesh Poyarekar
2022-10-11 14:23                       ` Frank Ch. Eigler
2022-10-11 15:58                     ` Alexandre Oliva [this message]
2022-10-11 17:14                       ` David Edelsohn
2022-10-11 18:12                         ` Frank Ch. Eigler
2022-10-12  8:00                         ` Mark Wielaard
2022-10-12 13:18                           ` Florian Weimer
2022-10-12 21:23                             ` Mark Wielaard
2022-10-12 15:15                           ` Jonathan Corbet
2022-10-12 10:55                         ` Alexandre Oliva
     [not found] <b00dc0aa-31a6-a004-a430-099af3d0f6d1@redhat.com>
     [not found] ` <558996ac-e4a0-cf77-48b9-f7d0e13862e8@redhat.com>
2022-10-17 11:48   ` Luis Machado
2022-10-17 12:08     ` Siddhesh Poyarekar
2022-10-17 12:16       ` Luis Machado
2022-10-18 18:45         ` Siddhesh Poyarekar
2022-09-27 20:08 Carlos O'Donell
2022-09-28 22:38 ` Carlos O'Donell

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=ora662nyia.fsf@lxoliva.fsfla.org \
    --to=oliva@gnu.org \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=libc-alpha@sourceware.org \
    --cc=mark@klomp.org \
    --cc=overseers@sourceware.org \
    --cc=siddhesh@gotplt.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).