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: Fri, 28 Feb 2025 14:48:34 +0100 Message-ID: <CABLWnS9oVRKCYqPMCtkcMMiK_+Gqrsf+7jWzKOgdwQWGFTamxA@mail.gmail.com> (raw) In-Reply-To: <20250227211357.00002824@hawaiiantel.net> On Fri, Feb 28, 2025 at 8:14 AM compn <ff@hawaiiantel.net> wrote: > On Thu, 27 Feb 2025 23:41:14 +0100, Vittorio Giovara wrote: > > > 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. > > holding mails for moderation is not censorship. it would be nice if you > as a CC member would decrease the intensity of your accusations towards > me. > I'm not a CC member Sorry to ruffle your feathers, but I haven't brought up this issue in month. The fact that people don't talk about it any more doesn't mean you get to get away scott free of your actions, or that people should forget. Once you face proper repercussions for your actions, or the CC decides it was well within your power, then I'll stop bringing it up. Maybe ask Micheal to stop filibustering the CC so that the proper course of action can take place. > the CC's job is not to determine, declare, nor issue edicts of the ml > admins job duties. > > as said moderation was thread wide and not on any individual developer, > there is no inter-personal conflict between me or anyone else. everyone > is equal in the eyes of the moderation. > > its possible that some developers are upset about being equals? i think > the CC could help those developers to understand mailing list > administration and moderation if they have an inter-personal conflict > with me. > > i think i've sent my thoughts to the previous CC on this issue. but if > the new CC would like to talk, i'm available. You should step down, that's the only honorable route left for any abuse of power. -- 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-28 13:48 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 2025-02-28 7:13 ` compn 2025-02-28 13:48 ` Vittorio Giovara [this message] 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=CABLWnS9oVRKCYqPMCtkcMMiK_+Gqrsf+7jWzKOgdwQWGFTamxA@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