From: compn <ff@hawaiiantel.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [RFC] Introducing policies regarding "AI" contributions
Date: Fri, 4 Jul 2025 06:43:29 -1000
Message-ID: <20250704064329.00000bda@hawaiiantel.net> (raw)
In-Reply-To: <mailman.5336.1751585487.1384.ffmpeg-devel@ffmpeg.org>
On Fri, 4 Jul 2025 01:31:19 +0200, Alexander Strasser via ffmpeg-devel
wrote:
> To find out if it is truly good code someone needs to review it very
> deeply, which is extra hard if it is "AI" generated code as it tends
> to look very plausible; which could waste a lot of time for the people
> looking at it and reviewing it. This also diminishes the actual value
> of the use of "AI" in the first place.
eh, if the code works, it works. if it can create a decoder for a
format that we do not have a decoder for, more power to it. its going
to have bugs (at least until code review models show up) the same as
human code.
i'm guessing it will be better than disassembled code (as we've seen in
the past win32 decoder code submitted and committed...)
for me:
morally:
not opposed.
copyright:
not opposed, if it was trained on gpl code.
code review/quality:
i agree with alex. if it doesnt conform to ffmpeg code standards, its
better if someone conforms it, or says its non conforming to avoid
lengthy code reviews.
-compn
_______________________________________________
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".
next prev parent reply other threads:[~2025-07-04 16:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 10:58 Alexander Strasser via ffmpeg-devel
2025-07-01 11:20 ` Gyan Doshi
2025-07-03 23:42 ` Alexander Strasser via ffmpeg-devel
2025-07-01 12:44 ` Kacper Michajlow
2025-07-03 23:31 ` Alexander Strasser via ffmpeg-devel
2025-07-04 16:43 ` compn [this message]
2025-07-04 18:11 ` softworkz .
2025-07-03 0:16 ` Gerion Entrup
2025-07-03 23:14 ` Alexander Strasser via ffmpeg-devel
2025-07-04 7:10 ` Nicolas George
2025-07-03 23:44 ` Leo Izen
2025-07-04 10:15 ` Michael Niedermayer
2025-07-05 11:20 ` Rémi Denis-Courmont
2025-07-05 12:22 ` Kacper Michajlow
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=20250704064329.00000bda@hawaiiantel.net \
--to=ff@hawaiiantel.net \
--cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git