Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Introducing policies regarding "AI" contributions
Date: Mon, 7 Jul 2025 09:38:31 +0200
Message-ID: <aGt5d6ljgFkaaLjo@phare.normalesup.org> (raw)
In-Reply-To: <71ADCF87-98DE-4F0B-B596-55B598C97506@gmail.com>

Marvin Scholz (HE12025-07-07):
> IMHO if something is a huge "go away" it is the lack of a modern development
> workflow, like what a modern Git forge offers…

Indeed, that weeds out a lot of lazy programmers. We should absolutely
keep it.

-- 
  Nicolas George
_______________________________________________
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".

  parent reply	other threads:[~2025-07-07  7:38 UTC|newest]

Thread overview: 21+ 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
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-06 22:29   ` Alexander Strasser via ffmpeg-devel
2025-07-07  0:10     ` Michael Niedermayer
2025-07-07  0:35       ` Marvin Scholz
2025-07-07  2:52         ` Michael Niedermayer
2025-07-07  7:38         ` Nicolas George [this message]
2025-07-07  2:01     ` Michael Niedermayer
2025-07-05 11:20 ` Rémi Denis-Courmont
2025-07-05 12:22   ` Kacper Michajlow
2025-07-06 22:18   ` Alexander Strasser via ffmpeg-devel

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=aGt5d6ljgFkaaLjo@phare.normalesup.org \
    --to=george@nsup.org \
    --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