On Thu, 19 Dec 2024 13:16:23 -0300, James Almer wrote: > On 12/19/2024 1:12 PM, compn wrote: > > On Thu, 19 Dec 2024 10:04:53 -0300, James Almer wrote: > >> I have no idea who added the rule for "upcoming vote", but i just > >> removed it. > >> > > > > i added upcoming vote to mod as devs were getting personal about booths > > and whatnot. as you've removed it, now we see the flames on the list. > > You can't silently and unilaterally add a filter to stop a thread in its > tracks. That is something that needs to go through the CC, and publicly > announced.
could you link me to the actual rules that state any of this? none of what you said is in the ffmpeg code of conduct. https://ffmpeg.org/community.html if you cannot link me to rules that show any of what you said i broke the rules of, i would like an apology. > It speaks poorly of how you would perform as part of the CC if you think > acting alone and making bad use of your ml admin privileges is ok. keeping out flames is part of the ml admin duties. see for ex: emergency moderation, moderate all users, mod individual, spam filtering options. these stop flames duties were told to me by previous roots (gabu, diego) and current roots (michael, alex). reading the mails stuck in the moderation queue and clearing the moderation queue is also part of the duties of the ml admin. -compn _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
