From: Marth64 <marth64@proxyid.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] GSoC 2025 Date: Wed, 12 Feb 2025 10:23:25 -0600 Message-ID: <CAAhd_PWdvs5-Qgrdg2F-vWW2rXuWXzB1Okus+wL37pPho5oSCA@mail.gmail.com> (raw) In-Reply-To: <Z6xKRHc3qfFUgy45@phare.normalesup.org> Hi Nicolas, I’ll be clear: my decision to funnel the conversation into a more isolated (but project-official) channel was based on experience and best practices, not guesswork. I have over a decade of real-world experience and training managing teams, resolving conflict, and guiding projects to success. If you’d like to understand the reasoning, I suggest looking into the 5 C’s of Conflict Management, which emphasizes the importance of clear communication and collaboration in conflict resolution. I did not see that potential in a wide-open thread like this. In cases of conflict, especially during sensitive moments, it’s a well-established leadership practice to reduce surface area and shift discussions to a focused group where they can be resolved more productively. If you have constructive feedback, I’m happy to hear it, but I won’t engage in unproductive criticism of the CC’s role. Respectfully, Marth64 _______________________________________________ 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-02-12 16:24 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-01-28 2:21 Michael Niedermayer 2025-01-29 15:51 ` Yigithan Yigit 2025-01-29 19:01 ` Michael Niedermayer 2025-01-29 19:31 ` Kieran Kunhya via ffmpeg-devel 2025-01-29 20:01 ` Ronald S. Bultje 2025-01-30 6:36 ` Vittorio Giovara 2025-01-30 10:21 ` Sean McGovern 2025-01-30 18:40 ` Michael Niedermayer 2025-01-30 21:20 ` Koushik Dutta 2025-01-30 14:53 ` compn 2025-01-31 5:01 ` Soft Works 2025-01-31 0:24 ` Vittorio Giovara 2025-01-31 12:51 ` James Almer 2025-02-11 22:30 ` Steven Liu 2025-02-12 0:19 ` Michael Niedermayer 2025-02-12 1:16 ` Kieran Kunhya via ffmpeg-devel 2025-02-12 1:58 ` Kieran Kunhya via ffmpeg-devel 2025-02-12 2:45 ` Marth64 2025-02-12 7:14 ` Nicolas George 2025-02-12 16:23 ` Marth64 [this message] 2025-02-12 16:55 ` Nicolas George 2025-02-12 18:36 ` Marth64 2025-02-12 10:53 ` Vittorio Giovara
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=CAAhd_PWdvs5-Qgrdg2F-vWW2rXuWXzB1Okus+wL37pPho5oSCA@mail.gmail.com \ --to=marth64@proxyid.net \ --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