From: "Rémi Denis-Courmont" <remi@remlab.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v2] avfilter: fix data type for {Tile, Untile}Context's image size Date: Wed, 24 Jul 2024 22:33:31 +0300 Message-ID: <17571621.YKE7GJzUs9@basile.remlab.net> (raw) In-Reply-To: <20240724130817.GJ4991@pb2> Le keskiviikkona 24. heinäkuuta 2024, 16.08.17 EEST Michael Niedermayer a écrit : > The question is not if its "warning-worthy", the question is what action > creates the best FFmpeg. And also an enviroment we are all happy to work in. That is complete nonsense. It is more obvious than patently obvious by now that that utopic environment does not exist, so that, with very contradictory wants from Paul or Nicolas on one hand, and, say Vittorio or Marvin on the other hand. Although you are correct for the wrong reasons that there is also no question about it being warning-worthy. It might have been debatable initially. But it is moot now that Paul has verified Godwin's law. That is simply wholly intolerable and there are no sane actions than for the CC to suspend him. The fact that the CC has done *nothing* in over 24 hours is already a bad enough look. > Some people do not at all like being warned publically, some people do not > at all like having the CC "Breathe into their neck". Nobody likes to be warned in public. Don't get me started on being on the receiving end of warnings in open-source projects. The whole point of a public warning are to make an example, and show consideration for the victims (if any), not to be friendly. > Some people dont like offensive language > > What we need is a middle way between all this that makes as many people > happy and contributing as possible Yes? And regrettably, Paul has repeatedly breached community rules if not common sense courtesy, and made a lot of people unhappy to contribute. He has also been warned many times and ignored or even rebuked those warnings. Yesterday was a new low (at least in the time frame that I have been subscribed to FFmpeg-devel). At this point, I unfortunately don't see a way forward other than excluding him for an extended period of time. This is extreme considering that he has been one of the most prolific contributor to FFmpeg, but then again, he de facto excluded himself by making a hostile fork. -- レミ・デニ-クールモン http://www.remlab.net/ _______________________________________________ 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:[~2024-07-24 19:33 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-07-08 19:00 [FFmpeg-devel] [PATCH] Mention that AV_OPT_TYPE_IMAGE_SIZE can be unsigned Andrew Sayers 2024-07-08 19:40 ` Marcus B Spencer 2024-07-08 19:59 ` [FFmpeg-devel] [PATCH v2] lavu/opt: " Andrew Sayers 2024-07-10 14:01 ` Paul B Mahol 2024-07-10 14:54 ` Andrew Sayers 2024-07-19 12:54 ` James Almer 2024-07-19 13:54 ` [FFmpeg-devel] [PATCH v2] avfilter: fix data type for {Tile, Untile}Context's image size Andrew Sayers 2024-07-19 15:31 ` Paul B Mahol 2024-07-19 15:45 ` Andrew Sayers 2024-07-23 14:42 ` [FFmpeg-devel] [PATCH v4] " Andrew Sayers 2024-07-23 15:17 ` [FFmpeg-devel] [PATCH v2] " James Almer 2024-07-23 16:17 ` Paul B Mahol 2024-07-23 16:24 ` Paul B Mahol 2024-07-23 16:36 ` James Almer 2024-07-23 20:00 ` Ronald S. Bultje 2024-07-23 22:10 ` Michael Niedermayer 2024-07-24 4:32 ` Michael Niedermayer 2024-07-24 4:49 ` Marvin Scholz (ePirat) 2024-07-24 13:08 ` Michael Niedermayer 2024-07-24 19:33 ` Rémi Denis-Courmont [this message] 2024-07-25 7:54 ` Ronald S. Bultje 2024-07-25 10:12 ` Rémi Denis-Courmont 2024-07-19 8:34 ` [FFmpeg-devel] [PATCH v2] lavu/opt: Mention that AV_OPT_TYPE_IMAGE_SIZE can be unsigned Andrew Sayers 2024-07-19 12:42 ` Paul B Mahol
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=17571621.YKE7GJzUs9@basile.remlab.net \ --to=remi@remlab.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