From: Christian Couder <christian.couder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Git PLC <git@sfconservancy.org>
Subject: Re: [RFC/PATCH] SubmittingPatches: forbid use of genAI to generate changes
Date: Tue, 8 Jul 2025 16:23:26 +0200 [thread overview]
Message-ID: <CAP8UFD1StfAY3kLNmCtBJrCVM9ADuDVjQ-WC=9yMdSSouLLCbw@mail.gmail.com> (raw)
In-Reply-To: <xmqqms9nkhms.fsf@gitster.g>
On Tue, Jul 1, 2025 at 6:20 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> Christian Couder <christian.couder@gmail.com> writes:
> > Here we would forbid licensing any "AI content generator" output, not
> > just AI code generator output. So what we would forbid might be more
> > general than what QEMU folks forbid. For example they might still
> > accept a new logo, or even commit messages, made using an AI while we
> > wouldn't.
>
> I didn't think about the distinction you are trying to draw when I
> wrote the patch, but after thinking about it, I think it is a good
> thing to prevent us from adopting a new logo graphics somebody may
> have ownership rights without us knowing. I would consider the
> commit log message as an integral part of any "contribution", and
> read the word "contribution" used in the [[dco]] section as such, if
> the rule covers the commit log message, that is very much
> appreciated.
I am not sure about logos, but for the commit message, it seems to me
that it could have drawbacks related to translation or wordings.
For example if someone is not a good English writer, they could write
a commit message in their native language and then ask an AI to
translate it. Or they could write it in their bad English and then ask
an AI to improve the wordings. I am not sure we want to forbid all
that.
> >> +Hence, the project asks that contributors refrain from using AI content
> >> +generators on changes that are submitted to the project.
> >
> > Here it looks like using an AI capable of generating content to just
> > check code that would be submitted could also be forbidden. I don't
> > think this is what we want, so I think we might want to reword this.
>
> Good point. Asking agents to proofread and suggest improvements is
> like asking your friends to do so. Care to suggest replacement to
> these two sentences (above and below)?
I could try but I would feel better if we tried to find and ask people
around who have thought about this subject already.
Especially I think it's difficult to draw the line between a tool that
suggests improvements and a tool that generates content. For example
if I were a very bad English writer and asked an AI to suggest
improvements to a commit message I wrote, then the AI might actually
rewrite nearly everything and the result could be very similar to what
the AI would have generated in the first place based only on the diff
part of the patch.
next prev parent reply other threads:[~2025-07-08 14:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 20:32 [RFC/PATCH] SubmittingPatches: forbid use of genAI to generate changes Junio C Hamano
2025-06-30 21:07 ` brian m. carlson
2025-06-30 21:23 ` Collin Funk
2025-07-01 10:36 ` Christian Couder
2025-07-01 11:07 ` Christian Couder
2025-07-01 17:33 ` Junio C Hamano
2025-07-01 16:20 ` Junio C Hamano
2025-07-08 14:23 ` Christian Couder [this message]
2025-10-01 14:02 ` [PATCH v2] SubmittingPatches: add section about AI Christian Couder
2025-10-01 18:59 ` Chuck Wolber
2025-10-01 23:32 ` brian m. carlson
2025-10-02 2:30 ` Ben Knoble
2025-10-03 13:33 ` Christian Couder
2025-10-01 20:59 ` Junio C Hamano
2025-10-03 8:51 ` Christian Couder
2025-10-03 16:20 ` Junio C Hamano
2025-10-03 16:45 ` rsbecker
2025-10-08 7:22 ` Christian Couder
2025-10-01 21:37 ` brian m. carlson
2025-10-03 14:25 ` Christian Couder
2025-10-03 20:48 ` Elijah Newren
2025-10-03 22:20 ` brian m. carlson
2025-10-06 17:45 ` Junio C Hamano
2025-10-08 4:18 ` Elijah Newren
2025-10-12 15:07 ` Junio C Hamano
2025-10-08 9:28 ` Christian Couder
2025-10-13 18:14 ` Junio C Hamano
2025-10-23 17:32 ` Junio C Hamano
2025-10-08 4:18 ` Elijah Newren
2025-10-08 8:37 ` Christian Couder
2025-10-08 9:28 ` Michal Suchánek
2025-10-08 9:35 ` Christian Couder
2025-10-09 1:13 ` Collin Funk
2025-10-08 7:30 ` Christian Couder
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP8UFD1StfAY3kLNmCtBJrCVM9ADuDVjQ-WC=9yMdSSouLLCbw@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=git@sfconservancy.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).