Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Sam James via Gdb <gdb@sourceware.org>
To: Carlos O'Donell <carlos@redhat.com>
Cc: glibc developers <libc-alpha@sourceware.org>,
	 gdb developers <gdb@sourceware.org>
Subject: Re: Nominations for Anthropic’s Claude for Open Source program
Date: Sat, 13 Jun 2026 00:12:27 +0100	[thread overview]
Message-ID: <87h5n7cq04.fsf@gentoo.org> (raw)
In-Reply-To: <aac20a98-a70e-4268-a758-316ac0407a16@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2099 bytes --]

Carlos O'Donell <carlos@redhat.com> writes:

> Developers,
>
> Anthropic is generously offering 6 months of Claude Max 20x to Free and Open
> Source Software projects to support the FOSS ecosystem. These tools can be
> incredibly helpful with reviewing upstream code, evaluating the conformance of
> a particular interface to a standard, or just for your own learning and
> exploring the implementation of the project or subsystem.

Several developers often don't even refer to Coverity, but say "a static
analyzer service" or similar. I think maybe some discussion should be
had before naming a service (and giving some publicity) given this
precedent, though it's a bit late now.

>
> If you are an established, active contributor to the GNU Toolchain and are
> interested in having access to Claude Max 20x under Anthropic’s Claude for Open
> Source program, please respond to this email thread with a short description of
> how you would utilize the access and the potential impact on the GNU Toolchain.
> The program's slots are limited and David Edelsohn and I plan to review the
> proposals. Please keep in mind that these are individual grants from Anthropic
> to you personally. If you are approved you’ll get an email from Anthropic with
> further instructions.
>
> While the current GNU Project policy is not to accept LLM-generated content in
> the projects, that still leaves other uses like bug triage, patch review, and
> research as ways to use these tools.

.. but also, I think we probably need to have a policy discussion about
this. I hope we won't have anyone pasting LLM replies onto bugs or patch
review, or an automated process doing that. I would *not* want to see
something like Sashiko for example. It would seriously put me off
contributing to glibc and I don't think it is respectful of
contributors' time who have come to us with a bug report or patch.

We should discuss this I think before handing out access.

Now, if a maintainer wants to use it to aid their review (with great
care), that may be more acceptable.

sam

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 418 bytes --]

  parent reply	other threads:[~2026-06-12 23:13 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
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 [this message]
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=87h5n7cq04.fsf@gentoo.org \
    --to=gdb@sourceware.org \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=sam@gentoo.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