From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] Democratization Date: Sun, 26 Jan 2025 20:17:13 +0100 Message-ID: <20250126191713.GQ4991@pb2> (raw) In-Reply-To: <CA+28BfCaQ2gv2dfy2PKdQMMWoth=U+DfjGEE-=cnQXYJQBA47w@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 3667 bytes --] Hi Marth64 On Sun, Jan 26, 2025 at 11:34:37AM -0600, Marth64 wrote: > Hi Michael, > > > I believe discusion about ffmpeg should be public and on the mailing list > > where everyone can participate > It should be public and people should participate. It can also be > real-time and on IRC. > Clearly this was done in the past. > > Literally on the front page of TRAC, there is a section titled "FFmpeg > Developer Meetings" > with a list of meetings that happened in 2014, 2015, 2016, 2019, 2020. > https://trac.ffmpeg.org/ > Why can't it happen again? Having a meeting between people to talk about a common goal like FFmpeg makes sense. What we have here is different. > > > Also as you say "without interpersonal arguments" I see no reason > > for it not to be on the public mailing list > I see every reason for these to NOT be on the mailing list. > > These types of threads continue to digress into an airing of > interpersonal arguments. > It's not healthy. It makes people look bad. People get upset. > > It is toxic by all accounts. To aggravate this, such email threads > drag on eternally. > This is why I have asked for a real-time session over IRC. I remember such a IRC session before the libav fork. It is very similar to this here 4+ people, who simply accuse me of everything (on IRC though) this serves no purpose. There is no common ground here As long as the people belive or claim iam the cause for them attacking others (and everything else) there is nothing to discuss. They are adults and they have to take responsibility for what they do > > > 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. > When I volunteered to be part of the CC, my opening point was to be an > "effective de-escalator and diplomat". > > That includes applying situational judgement. I am not without a spine > to stand up and say > "Folks, let's have a meeting and hash this out." It is called de-escalating. > > I am trying to request that the community has a healthy discussion and > DIFFUSE tensions. > People do that in the real-world by making an agenda and talking through issues, > setting up frameworks for improvements and meeting in the middle. > > Does it always work? No. > But I also do not see us having tried beyond inflammatory and chronic > email threads. What i see today is people attacking me on the mailing list. (in fact out of teh blue, there was nothing triggering that) And the CC taking no action. The people are not warned, they are not moderated they are not banned. Instead iam being asked to join a chat. This is something i may have considered if for example i saw the people attacking me being banned. As is. No, i see not the slightest sign of the CC doing its job or providing a neutral or normal environment. If the CC is not able or willing to do that on the ML, then it wont on IRC either I will not subject myself to this. Everyone can just take a paper write my name on it and accuse and screem towards it, thats gonna do the exact same. thank you [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Any man who breaks a law that conscience tells him is unjust and willingly accepts the penalty by staying in jail in order to arouse the conscience of the community on the injustice of the law is at that moment expressing the very highest respect for law. - Martin Luther King Jr [-- 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 19:17 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 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 [this message] 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=20250126191713.GQ4991@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