From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] FFmpeg Community Committee – Updates & Next Steps Date: Thu, 27 Feb 2025 19:18:08 +0100 Message-ID: <20250227181808.GG4991@pb2> (raw) In-Reply-To: <8c1d1b3f-8a76-42c2-9a18-9cc0cef5253d@betaapp.fastmail.com> [-- Attachment #1.1: Type: text/plain, Size: 2095 bytes --] Hi jb On Thu, Feb 27, 2025 at 12:11:39AM +0100, Jean-Baptiste Kempf wrote: > On Wed, 26 Feb 2025, at 02:51, Michael Niedermayer wrote: [...] > > 2. The CC is overstepping its authority. > > Literally, the email just says that the CC is now meeting regularly; what authority can it be overstepping? > People speaking together and meeting is now forbidden? "The Community Committee (CC) is here to arbitrage and make decisions when inter-personal conflicts occur in the project. It will decide quickly and take actions, for the sake of the project." There are NO inter-personal conflicts ATM (very luckily everyone was happy UNTIL the CC initiates conflicts) The mail said: "Starting this week, we will hold a weekly internal panel to discuss community matters and ensure more structured issue resolution. One of our key goals is to address some of the lingering discussions from 2024 while laying a strong foundation for the future." discussion about structured issue resolution in FFmpeg are a matter of the whole community and not the CC. "laying a strong foundation for the future. (of FFmpeg)" is not something a panel of 3 people who have never been elected for that can do behind closed doors I want to be part of these discussions for example. Iam one of the main authors. And iam sure others also want to be part of these discussions The last such closed door discussion, was VDD2024 and after that we had months of defamation and mobbing. > > > 3. About "internal panel", There should not be a "internal panel" dominated > > CC was elected by GA. GA is composed of most of the active developers. This is not a random internal panel. An election that was delayed by the vote superviser until a specific person joined. Then 2 resigned And now its not even publically known how many members this CC has. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Does the universe only have a finite lifespan? No, its going to go on forever, its just that you wont like living in it. -- Hiranya Peiri [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- 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".
next prev parent reply other threads:[~2025-02-27 18:18 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-02-25 23:04 Marth64 2025-02-26 1:51 ` Michael Niedermayer 2025-02-26 14:22 ` Vittorio Giovara 2025-02-26 22:33 ` Kieran Kunhya via ffmpeg-devel 2025-02-26 23:11 ` Jean-Baptiste Kempf 2025-02-27 18:18 ` Michael Niedermayer [this message] 2025-02-27 22:41 ` Vittorio Giovara 2025-02-28 7:13 ` compn 2025-02-28 13:48 ` Vittorio Giovara 2025-02-27 23:00 ` Marth64 2025-02-28 19:27 ` Michael Niedermayer 2025-02-28 20:35 ` Vittorio Giovara 2025-02-28 19:29 ` Michael Niedermayer 2025-03-02 10:16 ` Rémi Denis-Courmont 2025-02-26 23:51 ` James Almer
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=20250227181808.GG4991@pb2 \ --to=michael@niedermayer.cc \ --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