Re: [FFmpeg-devel] [RFC] Introducing policies regarding "AI" contributions

[Alexander Strasser via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>]

[-- Attachment #1: Type: message/rfc822, Size: 6961 bytes --]

From: Alexander Strasser <eclipse7@gmx.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Introducing policies regarding "AI" contributions
Date: Fri, 4 Jul 2025 01:42:10 +0200
Message-ID: <aGcVUqc_8_sbAhs4@metallschleim.local>

On 2025-07-01 16:50 +0530, Gyan Doshi wrote:
> 
> On 2025-07-01 04:28 pm, Alexander Strasser via ffmpeg-devel wrote:
> 
> > Thus I want this thread to start a discussion, that eventually leads
> > to a policy about submitting and integrating "AI" generated content.
>
> In practice. unless a patch(set) is explicitly marked or has telltale signs
> of being AI-generated,the project can't stop such AI code getting in.
> At best, we can require disclosure and for the human submitter to assume
> responsibility.

That's true. It's impossible to completely enforce adherence to a
policy that bans "AI" generated code.

I guess it would still be worthwhile to just do what you said.

From what I have looked at in the other projects so far (musl,
gentoo, llvm), they acknowledge too that they cannot enforce it.

In a way it's nothing new and actually since forever we would
not want to accept contributions of dubious or license-incompatible
origins.

Just the current times seem to warrant spelling this out, I fear.
So maybe just generically writing about it and explicitly mentioning
"AI" would be the better way to achieve the goal.

Thanks for commenting!


Best regards,
  Alexander

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".