From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Kieran Kunhya <kieran618@googlemail.com>, Cc <cc@ffmpeg.org> Subject: Re: [FFmpeg-devel] Vittorio's mailinglist ban, git access removal and message deletion (was: Worsening messages) Date: Wed, 14 May 2025 21:06:37 -0400 Message-ID: <CABGuwEnvy9ea_kbWemDvn4UbTficJNnHvhOzS0of5QkaFa0_3w@mail.gmail.com> (raw) In-Reply-To: <20241231114403.GC4991@pb2> On Tue, 31 Dec 2024, 06:44 Michael Niedermayer, <michael@niedermayer.cc> wrote: > Hi Ronald, Vittorio > > On Mon, Dec 30, 2024 at 11:05:59PM -0500, Ronald S. Bultje wrote: > > Hi Michael, > > > > On Mon, Dec 30, 2024 at 2:13 PM Michael Niedermayer < > michael@niedermayer.cc> > > wrote: > > > > > Hi CC-2024 > > > > > > On Mon, Dec 30, 2024 at 08:31:00AM -0500, Ronald S. Bultje wrote: > > > > Dear Michael, > > > > > > > > The other 4 members of the previous CC (JB, Steven, James, Ronald) > would > > > > like to make it clear that it was never consulted on this decision. > You > > > > (Michael) have - after the fact - asked us (the other 4 previous-CC > > > > members) to look into Vittorio's emails and Kieran's re-post thereof, > > > which > > > > the current CC can pick up from here. If you disagree with their > > > decision, > > > > you can ask the GA to re-evaluate. > > > > > > > > We (the other 4 previous-CC members) recommend that - until a > decision > > > has > > > > been rendered - Vittorio's git commit access gets reinstated and the > > > > deleted email gets restored into the archives. The mailinglist > ban(s) for > > > > Vittorio has already been revoked. > > > > > > As i said in my reply to vittorio, i will re-enable his account > > > once his identity is verified and he explains what he wants to > maintain in > > > ffmpeg. (note iam behind with my mails, so if i didnt react to > something, > > > its > > > because i try to get some distance from this nonsense (not distance > from > > > FFmpeg, > > > that is dear to my heart) but this political stuff) > > > > > > It seems you want to turn this into a political power play. I find this > > > unneeded. > > > You can simply verify that vittorio is himself as you meet him next > time > > > and drink > > > beer with him (which you said you did previously). > > > Its just a simple "yeah i met him after this and he is still in control > > > of his accounts&keys", theres no kyc here, just a statement from you > saying > > > you know him and hes still your good friend vittorio > > > > > > I just had a few beers with Vittorio and can confirm he’s still himself > and > > in control of his keys. > > Thats excelent, thanks alot for confirming and sorry also to you and > especially > to vittorio for the inconveniece. > > iam still quite a bit behind reading emails, I was just pointed to this > one here > > thx > > [...] > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > "I am not trying to be anyone's saviour, I'm trying to think about the > future and not be sad" - Elon Musk > > _______________________________________________ > 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". > Hi Michael, Just to confirm four FFmpeg developers saw Vittorio in New York today and confirm he is a genuine human. It's interesting you want Vittorio to comply with KYC when you say "What is kyc? Its a tool that makes you give out your real ID, while criminals give out a forged ID card." So if I understand correctly, you would like Vittorio to be verified but you don't need verification with the community? Regards, Kieran Kunhya > _______________________________________________ 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".
parent reply other threads:[~2025-05-15 1:07 UTC|newest] Thread overview: expand[flat|nested] mbox.gz Atom feed [parent not found: <20241231114403.GC4991@pb2>]
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=CABGuwEnvy9ea_kbWemDvn4UbTficJNnHvhOzS0of5QkaFa0_3w@mail.gmail.com \ --to=ffmpeg-devel@ffmpeg.org \ --cc=cc@ffmpeg.org \ --cc=kieran618@googlemail.com \ /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