From: Michael Niedermayer <michael@niedermayer.cc> To: Marth64 <marth64@proxyid.net> Cc: cc@ffmpeg.org, FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] Democratization Date: Sun, 26 Jan 2025 16:06:28 +0100 Message-ID: <20250126150628.GW1904408@pb2> (raw) In-Reply-To: <CA+28BfAm2Dsxzn-measXfNWk5Cfu4y4wRvD1uik2MS7wROmM-Q@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 6549 bytes --] Hi Marth64 On Sat, Jan 25, 2025 at 04:40:00PM -0600, Marth64 wrote: > Hello Michael, > > Complaint acknowledged. In the spirit of moving forward and de-escalating: > > Would you be open to a scheduled IRC meeting where we can talk through > some of the project issues in real time? > Ideally it is moderated by a neutral party to keep it civil and to the > point of project problems without interpersonal arguments. as you say "project issues" I believe discusion about ffmpeg should be public and on the mailing list where everyone can participate Also as you say "without interpersonal arguments" I see no reason for it not to be on the public mailing list The CC also had no problems banning nicolas and paul for basically doing nothing (compared to this) and not asking the people complaining to join a IRC meeting to talk about some project issues. And complaints about members and friends of the CC are ignored since several years. Now they have become so bold to make outright false claims And still no action, no really, the CC should do its job or the CC should be disolved. People asked for the new CC to be given a chance, this is the CCs chance. So far i see more offensive mail being posted after the CC is notified not less. The CC can stop this, or the CC can allow people to create a pretext for a fork. (the whole "michael is evil" is such a pretext if its not obvious to anyone) If the CC takes a clear action, this whole drama simply stops. Otherwise i suspect it will lead to a fork eventually. In the fork case they will leave with several others. I think thats a much bigger loss In fact the longer this continues the more people will leave And the final outcome will still not differ, people doing these attacks still will likely be lost to the project. thx > > On Sat, Jan 25, 2025 at 2:26 PM Michael Niedermayer > <michael@niedermayer.cc> wrote: > > > > Hi CC > > > > please see my complaints inline below > > > > On Fri, Jan 24, 2025 at 09:36:50PM +0200, Rémi Denis-Courmont wrote: > > > Hello, > > > > > > Le tiistaina 21. tammikuuta 2025, 2.36.47 UTC+2 Michael Niedermayer a écrit : > > > > Hi > > > > > > > > On Mon, Jan 20, 2025 at 10:38:17AM -0600, Marth64 wrote: > > > > > All this time people send back and forth emails attacking each other or > > > > > the > > > > > project could have spent toward investing in modern DevOps infrastructure > > > > > or discussing other advancements. > > > > > > > > > > It’s energy-draining to both read and write. > > > > > > > > > > > > > > > It makes me wonder do folks actually get enjoyment out of the drama? > > > > > > > > not me > > > > > > > > but what can i do? > > > > > > For example, you actually could: > > > > > > - Stop complaining about FFmpeg community members attending conferences and > > > discussing FFmpeg (e.g. VDD 2024). > > > > I have not complained about "FFmpeg community members attending conferences and > > discussing FFmpeg". Your statement suggests i did that, which i think is not ok > > > > > > > - Stop making inflammatory metaphores about community members (ditto). > > > > Can you provide links to your implied accusation ? > > > > > > > - Stop attacking conference organisers and hosts for not accomodating you > > > (e.g. Kwangwoon university faculty). > > > > I have not attacked "Kwangwoon university faculty", this is a strange way > > to deflect blame for VDD2024. In a room with several dozend > > microphones noone recorded the meeting, its not the fault of the room or > > who provided the room. > > Also it is not an attack (you can also see that i very intentionally do > > not name anyone personally). FFmpeg is a free software project. We have a > > open community and are welcoming to new members, meetings should be > > open to everyone local and remote and should be recorded so everyone can > > listen to them even when they are unable at the exact moment the meeting > > happens > > > > > > > - Stop posting insulting AI-generated pictures about other OSS projects on > > > social media (e.g. VideoLAN, on X). > > > > I have not done that. > > I had posted one joke on my personal twitter that i deleted a few hours later > > as people seem to have misunderstood it. > > > > Its interresting how a joke on my personal twitter that maybe less than 5 people > > saw before it was deleted is used here. > > (not to mention it is a copyright violation to spread my art/joke in a way it > > was not intended. It was intended to make people smile and have a laugh. And > > maybe think about issues but not to hurt people) > > > > > - Stop making seemingly false claims about colleagues (e.g. Josh and Marvin), > > > > Can you provide links to your implied accusation ? > > > > > > [...] > > > > > - Stop making utter lame excuses for the previous point (ditto, and causing > > > James to figuratively lose it). > > > > That sounds like an insult to me > > > > > > > - Stop defending ... > > > > not sure i did but really, defending someone is reason i get attacked? > > > > > > > - Stop victimising yourself on the mailing list (e.g. this thread). > > > > That sounds like an insult to me > > > > > > > - Stop misconstruing people defending themselves, others or their different > > > opinion as "attacks" against you. > > > > That sounds like an insult to me > > > > > > > - Stop criticising some of your business and/or business partners on the > > > mailing list (i.e. FFlabs). > > > > seriously, really, criticising buisness partners is the problem ? > > > > > > > - Stop demeaning the GA members, or the active voters within it, > > > > I dont think i have done that > > I complain about the structure not the people within. > > > > > > [...] > > > > > As far as I can tell, most actual attacks against you on this mailing list in > > > recent times were in response to your own critics or complaints. > > > > Looking just at the mail you wrote here. Did i cause you to write it ? > > > > thx > > > > [...] > > -- > > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > > > I do not agree with what you have to say, but I'll defend to the death your > > right to say it. -- Voltaire > -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Dictatorship naturally arises out of democracy, and the most aggravated form of tyranny and slavery out of the most extreme liberty. -- Plato [-- 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-01-26 15:06 UTC|newest] Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20250102141731.GR4991@pb2> [not found] ` <20250102163807.GB7285@haasn.xyz> [not found] ` <20250114170615.GD4991@pb2> [not found] ` <eafdd773-0055-4619-b1e2-bf4d4266ee4e@gmail.com> [not found] ` <20250117173914.GN4991@pb2> [not found] ` <f5f57e16-8f34-4836-9b46-f31a753dd990@gmail.com> 2025-01-20 1:28 ` Michael Niedermayer 2025-01-20 6:21 ` Kieran Kunhya via ffmpeg-devel 2025-01-20 15:45 ` Soft Works 2025-01-20 16:15 ` Marth64 2025-01-20 16:38 ` Marth64 2025-01-21 0:36 ` Michael Niedermayer 2025-01-24 19:36 ` Rémi Denis-Courmont 2025-01-24 21:02 ` Nicolas George 2025-01-25 6:21 ` Rémi Denis-Courmont 2025-01-25 7:55 ` Vittorio Giovara 2025-01-25 20:26 ` Michael Niedermayer 2025-01-25 21:08 ` Rémi Denis-Courmont 2025-01-25 21:39 ` Rémi Denis-Courmont 2025-01-25 22:13 ` Marth64 2025-01-25 23:23 ` Kieran Kunhya via ffmpeg-devel 2025-01-25 22:40 ` Marth64 2025-01-26 15:06 ` Michael Niedermayer [this message] 2025-01-26 15:11 ` Kieran Kunhya via ffmpeg-devel 2025-01-26 16:35 ` Rémi Denis-Courmont 2025-01-26 17:34 ` Marth64 2025-01-26 18:07 ` Marth64 2025-01-26 18:43 ` Gyan Doshi 2025-01-26 18:51 ` Marth64 2025-01-26 19:17 ` Michael Niedermayer 2025-01-26 19:39 ` Kieran Kunhya via ffmpeg-devel 2025-01-26 20:40 ` Rémi Denis-Courmont 2025-01-26 20:51 ` Kieran Kunhya via ffmpeg-devel 2025-01-26 21:20 ` Kieran Kunhya via ffmpeg-devel 2025-01-26 22:01 ` Marth64 2025-01-28 18:21 ` Michael Niedermayer 2025-01-29 6:40 ` Zhao Zhili 2025-01-29 12:39 ` Nicolas George 2025-01-29 15:16 ` Niklas Haas 2025-01-29 16:12 ` compn 2025-01-29 16:22 ` Vittorio Giovara 2025-01-29 17:02 ` Soft Works 2025-01-29 17:41 ` Marth64 2025-01-29 18:26 ` Marth64 2025-01-29 19:36 ` Kieran Kunhya via ffmpeg-devel 2025-01-29 20:20 ` Marth64 2025-01-29 20:54 ` Nicolas George 2025-01-29 21:08 ` Marth64 2025-01-29 21:45 ` Nicolas George 2025-01-30 6:12 ` Vittorio Giovara 2025-01-30 8:02 ` Nicolas George 2025-01-30 9:45 ` Vittorio Giovara 2025-01-31 0:03 ` Soft Works 2025-01-31 0:14 ` Vittorio Giovara 2025-02-01 13:50 ` Michael Niedermayer 2025-01-29 20:04 ` Ronald S. Bultje 2025-01-29 21:27 ` Niklas Haas 2025-01-29 21:39 ` Nicolas George 2025-02-01 14:15 ` Michael Niedermayer 2025-01-29 20:51 ` Nicolas George 2025-01-29 21:21 ` Niklas Haas 2025-01-29 21:36 ` Nicolas George 2025-01-30 6:08 ` Vittorio Giovara 2025-01-29 23:26 ` Soft Works 2025-01-30 6:35 ` Vittorio Giovara 2025-01-30 23:21 ` Soft Works 2025-01-31 0:14 ` Vittorio Giovara 2025-01-31 1:07 ` Soft Works 2025-01-30 9:50 ` Vittorio Giovara 2025-02-01 14:46 ` Michael Niedermayer 2025-02-01 14:48 ` Kieran Kunhya via ffmpeg-devel 2025-02-01 15:03 ` Michael Niedermayer 2025-02-01 16:10 ` Kieran Kunhya via ffmpeg-devel 2025-02-01 15:11 ` James Almer [not found] ` <dffa122a-f13a-4e95-8210-9053a6832e6a@e-blokos.com> 2025-02-01 16:03 ` James Almer 2025-02-01 20:18 ` Nicolas George 2025-02-01 13:44 ` Michael Niedermayer 2025-02-01 20:20 ` Nicolas George 2025-02-01 21:00 ` Soft Works 2025-01-29 9:45 ` Vittorio Giovara 2025-01-29 10:32 ` Soft Works 2025-01-29 10:51 ` Vittorio Giovara 2025-01-29 11:52 ` Soft Works 2025-01-29 14:38 ` Vittorio Giovara 2025-01-29 15:24 ` Soft Works 2025-01-29 16:24 ` Vittorio Giovara 2025-01-29 16:44 ` Soft Works 2025-01-30 8:02 ` Tobias Rapp 2025-01-29 16:58 ` Marth64 2025-01-29 17:06 ` Soft Works 2025-01-29 17:14 ` Marth64 2025-01-29 17:22 ` Soft Works 2025-01-29 17:38 ` Vittorio Giovara 2025-01-29 18:13 ` Soft Works 2025-01-29 18:23 ` Marth64 2025-01-29 17:15 ` Soft Works 2025-01-26 21:24 ` Michael Niedermayer 2025-01-26 21:41 ` Kieran Kunhya via ffmpeg-devel 2025-01-27 9:03 ` Vittorio Giovara 2025-01-20 17:44 ` Soft Works 2025-01-20 18:14 ` Gyan Doshi 2025-01-20 21:04 ` Nicolas George 2025-01-21 0:41 ` Michael Niedermayer 2025-01-21 6:52 ` Soft Works 2025-01-25 18:04 ` Michael Niedermayer 2025-01-24 20:01 ` Rémi Denis-Courmont 2025-01-20 17:59 ` Nicolas George 2025-01-20 18:18 ` Marth64 2025-01-20 18:46 ` Soft Works 2025-01-20 20:57 ` Nicolas George 2025-01-20 21:08 ` Marth64 2025-01-20 22:20 ` Marth64 2025-01-20 18:23 ` Marth64 2025-01-20 20:50 ` Nicolas George 2025-01-20 21:00 ` Soft Works 2025-01-21 0:55 ` Michael Niedermayer 2025-01-21 4:29 ` Marth64 2025-01-22 20:51 ` Nicolas George 2025-01-22 22:00 ` Soft Works
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=20250126150628.GW1904408@pb2 \ --to=michael@niedermayer.cc \ --cc=cc@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=marth64@proxyid.net \ /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