From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] CC statement on alleged insults against the GSoC student et al Date: Tue, 4 Mar 2025 19:02:44 +0100 Message-ID: <20250304180244.GO4991@pb2> (raw) In-Reply-To: <CAAhd_PWCem9ZaXtLRc6Q0rHvFqpgwJLjjPRFx7eSbWOBYpZwKw@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 2091 bytes --] Hi Marth64 first, thanks for publically explaining the decission this allows me to comment. On Tue, Mar 04, 2025 at 09:35:09AM -0600, Marth64 wrote: > Hello, > > The FFmpeg Community Committee (CC) has received a complaint regarding > alleged insults from Kieran against Yigithan and Michael. > > After careful review, the CC did not find any recent comments from > Kieran that would constitute an insult against either of the alleged > targets. The CC did not even find any criticism of Yigithan from > Kieran or anyone else. Kieran did negatively criticise Michael for Lets first quote what was said: Yiğithan Yiğit said: > I want to give some feedback before GSoC’25 as GSoC’24 participant. > I speak for myself but I know some of other colleagues are sharing > similar thoughts with me. > First of all community has incredible talented people and I am not > even single percent of those people. However I tried my best during > the qualification stage and after that. My main problem was finding > answer's inside a huge codebase. I might come stupid ideas, bad > implementations but to be honest when I asked about something in IRC > I couldn’t get any answers, even in my volumedetect(qual patch) > I couldn’t get a proper review from community. This is a polite and honest critique, pointing at true problems in FFmpeg people not reviewing patches, people not replying to students Kierans reply later refered back to this: > OMG a GSoC contributor is complaining about how hard the contribution This reply is not appropriate from an FFmpeg developer to a gsoc contributor who reported issues he found Its disencouranging, its belitteling and it may even violate GSoC guildlines or at least the vibe and spirit of GSoC Also see: https://google.github.io/gsocguides/mentor/best-practices thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB I have never wished to cater to the crowd; for what I know they do not approve, and what they approve I do not know. -- Epicurus [-- 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-03-04 18:02 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-03-04 15:35 Marth64 2025-03-04 15:56 ` Kieran Kunhya via ffmpeg-devel 2025-03-04 16:04 ` Rémi Denis-Courmont 2025-03-04 18:02 ` Michael Niedermayer [this message] 2025-03-04 19:00 ` Kieran Kunhya via ffmpeg-devel 2025-03-04 18:13 ` Michael Niedermayer 2025-03-04 19:15 ` Marth64
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=20250304180244.GO4991@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