From: "Rémi Denis-Courmont" <remi@remlab.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] VDD 2023, FFmpeg meeting notes, (23-11-2023, 4pm, Dublin) Date: Wed, 04 Oct 2023 18:11:27 +0300 Message-ID: <1863502.tdWV9SEqCh@basile.remlab.net> (raw) In-Reply-To: <20231004142312.GH3543730@pb2> Le keskiviikkona 4. lokakuuta 2023, 17.23.12 EEST Michael Niedermayer a écrit : > > Why are you part of a community project if you don't believe the > > community is capable of running a project? > > Questioning why some developer is part of FFmpeg is IMHO a violation of > the Code of Conduct. No matter how it is worded Kieran was asking a very valid *question*. NG has been vocally adamant (to put it mildly) about turning FFmpeg into (or back into) a place for fun experimentation and innovation, without the burden of reverse dependencies, down-stream packagers, users, and contributors with business interests. In the past year, I have not noticed anybody else support those directions. Your own (in)actions have been in direct contradiction with his stated views, for instance: - You keep making tons of "boring" fixes from OSS fuzz findings and other sources (I am thankful for your continued efforts on the first point, by the way; this is not meant as negative criticism). - You are listed as a prominent member of FFlabs (and you have not denounced that in any way). Admittedly, Kieran's question could be taken as loaded, but TBH the question seems valid, and calling it a violation of the CoC is too much of a stretch for me. > > Why not start your own project like TempleOS where you can do what you > > want? > are you suggesting that we all move to a system where every developer has > her/his own fork and they get merged ? He is suggesting that if one person *appears* to be alone in wanting to take (or take back) FFmpeg in the given directions that they advocate, they should consider starting their own project or fork. -- Rémi Denis-Courmont 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:[~2023-10-04 15:11 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-24 8:37 Kyle Swanson 2023-09-24 9:21 ` Matthias Dressel 2023-09-24 10:09 ` Michael Niedermayer 2023-09-24 10:13 ` Jean-Baptiste Kempf 2023-09-24 22:14 ` Derek Buitenhuis 2023-09-24 15:31 ` Ronald S. Bultje 2023-09-24 17:12 ` Nicolas George 2023-09-27 18:03 ` Michael Niedermayer 2023-10-04 14:51 ` Anton Khirnov 2023-09-24 12:36 ` Marton Balint 2023-09-24 13:46 ` Michael Niedermayer 2023-09-24 15:10 ` Ronald S. Bultje 2023-09-24 16:45 ` Michael Niedermayer [not found] ` <119D9DAB-2F0B-427B-A7D1-063C0AF7C3BD@cosmin.at> 2023-09-25 13:16 ` Cosmin Stejerean via ffmpeg-devel 2023-09-26 13:21 ` Ronald S. Bultje 2023-09-27 10:00 ` Michael Niedermayer 2023-09-27 13:29 ` Vittorio Giovara 2023-10-03 18:50 ` Nicolas George 2023-10-03 19:13 ` Vittorio Giovara 2023-10-03 19:29 ` Kieran Kunhya via ffmpeg-devel 2023-10-04 14:23 ` Michael Niedermayer 2023-10-04 15:06 ` Anton Khirnov 2023-10-05 12:55 ` Nicolas George 2023-10-05 17:32 ` Vittorio Giovara 2023-10-05 18:33 ` Michael Niedermayer 2023-10-05 19:45 ` Rémi Denis-Courmont 2023-10-05 19:54 ` Nicolas George 2023-10-05 19:00 ` Nicolas George 2023-10-04 15:11 ` Rémi Denis-Courmont [this message] 2023-10-03 19:29 ` Rémi Denis-Courmont 2023-10-03 19:36 ` Leo Izen 2023-09-26 19:26 ` Anton Khirnov 2023-09-26 18:44 ` Anton Khirnov 2023-09-27 13:15 ` Tomas Härdin 2023-10-02 9:55 ` Nicolas George 2023-10-03 18:41 ` Nicolas George
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=1863502.tdWV9SEqCh@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