From: Vittorio Giovara <vittorio.giovara@gmail.com> 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 23:41:14 +0100 Message-ID: <CABLWnS-h-dGrO+b1RrnoviPOLJiOt87+B3bRVdRk3192C9QAmQ@mail.gmail.com> (raw) In-Reply-To: <20250227181808.GG4991@pb2> On Thu, Feb 27, 2025 at 7:18 PM Michael Niedermayer <michael@niedermayer.cc> wrote: > 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) > To be completely honest, while I've been trying to be mostly professional in our interactions, I still have an inter-personal conflict with you, mostly related to my unfair and unilateral ban, or rather the fact that that act had no repercussions whatsoever. I'd really like the CC to resolve them and make sure we can keep working together without grudges. Also there are a lot of pending issues from that time (the most grave one IMO, how a mailing list admin unilaterally censors a thread) whose resolution we should at least hear about. > discussion about structured issue resolution in FFmpeg are a matter of the > whole community and not the CC. > The CC is the sole body that has and /should/ have the power of suspending or banning someone. An independent body elected by the most active users, what else could you want more? > "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 I don't think you should. You actively prevented the CC from operating blocking several suspensions, because they didn't affect "the other side" as well. But even then, why didn't you candidate for the CC and be part of the normal election process? The last such closed door discussion, was VDD2024 and after that we had > months of defamation and mobbing. > I thought the last closed discussion was about people going to NAB to have a ffmpeg booth. Or did that never happen entirely? Also just as a reminder... being called out for mistreating your fellow developers and your own project doesn't constitute mobbing, but rather it's just people trying to explain you why they believe your behavior is actively harming this community, especially coming from the most active developer And finally VDD2024 was not a closed discussion, everybody were able to join and the notes were published immediately after > > 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. This is a grave accusation and very revisionist view at what actually happened. Micheal, please seriously stop throwing a fit every time you get scared that things might not go your way. You say you want to work on releases and backporting cves? Then go do that instead of reopening the pandora's box every time. -- Vittorio _______________________________________________ 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 22:41 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 2025-02-27 22:41 ` Vittorio Giovara [this message] 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=CABLWnS-h-dGrO+b1RrnoviPOLJiOt87+B3bRVdRk3192C9QAmQ@mail.gmail.com \ --to=vittorio.giovara@gmail.com \ --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