From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Cc: Derek Buitenhuis <derek.buitenhuis@gmail.com> Subject: Re: [FFmpeg-devel] Mailinglist conduct Date: Wed, 17 Apr 2024 17:17:27 -0300 Message-ID: <c8de989c-23cb-478e-881d-f55cb85bf22e@gmail.com> (raw) In-Reply-To: <5b3f8323-c351-45cb-8347-d4060455346d@gmail.com> On 4/17/2024 4:43 PM, Derek Buitenhuis wrote: > On 4/17/2024 8:33 PM, James Almer wrote: >>>> This was an unnecessary personal attack, please don't do that again. Repeat >>>> offense may result in temporary bans on the mailinglist and/or IRC. Please >>>> keep it civil. >>> >>> That does not make it untrue, however. >> >> It's ok to have opinions. But there are better way to express them. > > It is not an opinion if it is true. > >>> I would have preferred a ban. >> >> Let's drop it here, please. > > I will say what I said earlier in private. > > [16:15] <Daemon404> i am tired of the whole thing where the person pointing out the insanity is punished because they were mean > [16:15] <Daemon404> and the people doing long term damage keep on scott free > [16:17] <Daemon404> focusing on Mean Words > [16:17] <Daemon404> instead of deeper issues What i saw were questions that went unanswered a few months ago, and now you being angry with said person that you say gets scott free. Can you please explain the overall situation, from your PoV? I swear a lot of stuff just happens behind curtains and i and others only notice it when it explodes. > > I agree I was out of line, but for the above reason (among others), the CC is a lame duck, One email saying one thing out of the line is no reason for a ban. Why would you want to force anyone to do that? Seriously, there's a lot of missing context here, and my work as part of the CC gets complex. Half the stuff i know about this i learned on IRC only a few hours ago, which apparently was common knowledge for some and news for others. > lacking the ability to enact actual meaningful change. The modus operandi here is to drive > anyone sane into eventually getting angry and saying regretful things. Gaslighting, sort of. > More like [1]. Coupled with the complacent attitude of Please Just Stop So I Can Code from > a chunk of the rest of the community, I find myself screaming into the void. > > I am tired of screaming into the void. This is what i mean when i say things only become apparent when they explode. > > I have taken this opportunity to unsubscribe for a while, as a self imposed temp ban for my > own benefit. I did that last time I felt like [1] here, and it was beneficial. > > - Derek > > [1] https://www.youtube.com/watch?v=HOK6mE7sdvs > _______________________________________________ > 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". _______________________________________________ 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:[~2024-04-17 20:17 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-16 23:21 [FFmpeg-devel] FFmpeg table at NAB Devin Heitmueller 2024-04-17 8:03 ` Paul B Mahol 2024-04-17 13:49 ` Derek Buitenhuis 2024-04-17 13:54 ` James Almer 2024-04-17 13:55 ` Derek Buitenhuis 2024-04-17 19:00 ` [FFmpeg-devel] Mailinglist conduct (was: FFmpeg table at NAB) Ronald S. Bultje 2024-04-17 19:30 ` [FFmpeg-devel] Mailinglist conduct Derek Buitenhuis 2024-04-17 19:33 ` James Almer 2024-04-17 19:43 ` Derek Buitenhuis 2024-04-17 20:17 ` James Almer [this message] 2024-04-17 22:13 ` [FFmpeg-devel] FFmpeg table at NAB Thilo Borgmann via ffmpeg-devel 2024-04-21 8:47 ` Rémi Denis-Courmont 2024-04-21 20:25 ` Thilo Borgmann via ffmpeg-devel 2024-04-22 2:02 ` Rémi Denis-Courmont 2024-04-24 6:07 ` Thilo Borgmann via ffmpeg-devel 2024-04-24 6:36 ` [FFmpeg-devel] Cease and desist Rémi Denis-Courmont
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=c8de989c-23cb-478e-881d-f55cb85bf22e@gmail.com \ --to=jamrial@gmail.com \ --cc=derek.buitenhuis@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