Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Carlos O'Donell <carlos@redhat.com>
Cc: Andrew Pinski <pinskia@gmail.com>,
	Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
	glibc developers <libc-alpha@sourceware.org>,
	gdb developers <gdb@sourceware.org>
Subject: Re: Nominations for Anthropic’s Claude for Open Source program
Date: Tue, 16 Jun 2026 13:03:44 +0200	[thread overview]
Message-ID: <20260616110344.GI6729@gnu.wildebeest.org> (raw)
In-Reply-To: <5158b893-6bb4-4856-acc8-876157671f34@redhat.com>

Hi Carlos,

On Mon, Jun 15, 2026 at 05:11:18PM -0400, Carlos O'Donell wrote:
> On 6/15/26 7:39 AM, Mark Wielaard wrote:
> >On Fri, 2026-06-12 at 16:11 -0700, Andrew Pinski via Gdb wrote:
> >>All of this talk about llm and llm reviews is off-topic for this list.
> >>Including the original email is off-topic and should not have been sent.
> >
> >Agreed, promoting the use of a commercial, non-free, proprietary llm
> >through a saas model is not appropriate and off-topic for the GNU
> >development lists.
> 
> I disagree.
> 
> For all the reasons David lists here and more:
> https://inbox.sourceware.org/gcc/CAGWvnyk1x47jPWs3ML01J-TrgKt8ByALj3HzPpZodVS_73VSBg@mail.gmail.com/
> 
> We should always be able to *talk* about non-free alternatives, how to use
> them, what they do, how to create alternatives, and how to move away from them.

As explained to David nobody said you cannot talk about alternatives.
But that is something completely different from advertising the
specific use of a commercial, non-free, proprietary llm.

> >>Carlos,
> >>   Can you step down from the llm gcc working group for this email since it
> >>shows a conflict of interest of prompting one product.  Plus it shows poor
> >>taste of sending out an email about a non free product to a mailing list
> >>about glibc development.
> >>Can I also ask you to step down from CoC for violating the CoC here?
> >
> >Yeah. It is hard to not see a pattern here. But not sure it is enough
> >for banning someone. And we all make mistakes from time to time. But we
> >do want to avoid the appearance of a conflict of interest.
> Sorry, could you please expand on the pattern you see?

Just that the David and Carlos show seems to have this pattern of
maximal drama. Where you promote some corporate deal so "generous"
that people shouldn't question whether it is ethical, undermines the
community or the gnu project goals. Then when people obviously do
point out these issues you start attacking the community volunteers
that do the actual work and pick a needless fight with the FSF about
"purity" and "leadership".

Cheers,

Mark

  reply	other threads:[~2026-06-16 11:04 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-12 19:18 Carlos O'Donell via Gdb
2026-06-12 19:29 ` Andrew Pinski via Gdb
2026-06-12 21:18   ` Carlos O'Donell via Gdb
2026-06-12 21:21     ` Andrew Pinski via Gdb
2026-06-12 23:07   ` Adhemerval Zanella Netto via Gdb
2026-06-12 23:11     ` Andrew Pinski via Gdb
2026-06-15 11:39       ` Mark Wielaard
2026-06-15 21:11         ` Carlos O'Donell via Gdb
2026-06-16 11:03           ` Mark Wielaard [this message]
2026-06-16 13:53             ` Carlos O'Donell via Gdb
2026-06-17 16:28               ` Alexandre Oliva via Gdb
2026-06-18  5:27                 ` Eli Zaretskii via Gdb
2026-06-18  6:59                   ` Alexandre Oliva via Gdb
2026-06-18  7:41                     ` Eli Zaretskii via Gdb
2026-06-18 13:43                       ` Alexandre Oliva via Gdb
2026-06-18 14:11                         ` Eli Zaretskii via Gdb
2026-06-18 14:44                         ` Jeffrey Walton via Gdb
2026-06-18 17:11                   ` Thomas Dineen via Gdb
2026-06-19 22:21                     ` Andy Wang via Gdb
2026-06-16 16:03             ` Siddhesh Poyarekar
2026-06-20  0:09           ` Carlos O'Donell via Gdb
2026-06-15 17:25       ` Siddhesh Poyarekar
2026-06-12 23:46     ` Collin Funk via Gdb
2026-06-13  1:15       ` Sam James via Gdb
2026-06-15 21:17       ` Carlos O'Donell via Gdb
2026-06-15 21:35         ` Andrew Pinski via Gdb
2026-06-15 23:10           ` Adhemerval Zanella Netto via Gdb
2026-06-16 14:50             ` Xi Ruoyao via Gdb
2026-06-16 14:59               ` Adhemerval Zanella Netto via Gdb
2026-06-16 17:49                 ` Carlos O'Donell via Gdb
2026-06-22 18:35                   ` Gokhan via Gdb
2026-06-16 16:22             ` Joseph Myers via Gdb
2026-06-16 16:44               ` Collin Funk via Gdb
2026-06-12 23:12 ` Sam James via Gdb
2026-06-15 21:19   ` Carlos O'Donell via Gdb
2026-06-16 16:08     ` Siddhesh Poyarekar
2026-06-16 16:36       ` Joseph Myers via Gdb
2026-06-16 18:01         ` Carlos O'Donell via Gdb
2026-06-13  0:19 ` Alexandre Oliva via Gdb

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=20260616110344.GI6729@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=carlos@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=libc-alpha@sourceware.org \
    --cc=pinskia@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