Le 23 novembre 2024 14:12:19 GMT+01:00, Michael Niedermayer <mich...@niedermayer.cc> a écrit : >Signed-off-by: Michael Niedermayer <mich...@niedermayer.cc> >--- > doc/community.texi | 14 ++++++++++++++ > 1 file changed, 14 insertions(+) > >diff --git a/doc/community.texi b/doc/community.texi >index 97a49f15ede..8c24faef95e 100644 >--- a/doc/community.texi >+++ b/doc/community.texi >@@ -162,6 +162,20 @@ Looking at issues from a different perspective assists >development. > Do not assume malice for things that can be attributed to incompetence. Even > if > it is malice, it's rarely good to start with that as initial assumption. > >+Stay On-Topic: Ensure your messages relate to software development or the >specific purpose of the mailing list. Avoid unrelated discussions.
Nobody wants off-topic discussions, but that rule sounds ripe for abuse. >+ >+Be Respectful: Treat all members with courtesy and respect. Personal attacks, >insults, or harassment of any kind are not tolerated. This is just dumb. If the CC can't do its job, adding more subjective rules is going to make things worse, not better. And indeed people often take criticism about their work as personal attacks, so this would make negative reviews impossible. Lastly insults are typically illegal anyway, so no point adding a rule for them. >+ >+Avoid Provocation: Refrain from posting inflammatory, controversial, or >intentionally provocative messages. Focus on constructive discussions. This is very subjective and completely unenforceable. >+ >+No Trolling: Messages intended to provoke an emotional response or disrupt >the discussion are prohibited. Ditto. >+ >+Professional Language: Use clear, professional, and inclusive language. Avoid >offensive or derogatory remarks, even in jest. That's fine *guideline*. It can't be a hard rule. >+ >+Constructive Criticism Only: Offer feedback in a constructive and >solution-oriented manner. Criticize ideas, not people. This is just dumb. Reviewers aren't typically paid. We can't require them to write constructive feedback every time (if ever). And the TC is already there to arbitrate technical disagreement. Again, this is a fine guideline but it can't be a hard rule. >+Handle Disagreements Professionally: Disagreements are normal but should be >handled respectfully. Assume good intentions and avoid escalating conflicts. That's even worse. We can't control people's opinions to have them assume good intentions. That doesn't belong at all. > Stay friendly even if someone acts contrarily. Everyone has a bad day > once in a while. > If you yourself have a bad day or are angry then try to take a break and reply This is begging for faintly plausibly deniable sarcastic abuses. Terrible idea. -1 _______________________________________________ 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".
