Marth64 (HE12025-02-12): > 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.
You neglect that part of the conflict is that the CC itself is not seen as trustworthy by several members of the project, suspected of bias and overreach. Your mere presence in it will help, but it is not enough to make all that go away immediately. Therefore, my constructive feedback is: First: do not shroud your activities in secrecy, it feeds the suspicion on bias. Second: promptly and public reject and condemn anything that would be overreach and strictly limit yourself to things directly related to the code of conduct. Regards, -- Nicolas George _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
