Michael Haggerty wrote: > Thank you for drafting a proposed CommunityGuidelines document; I think > such a document would be helpful. But I don't like the overall flavor > of your proposal; frankly, it sounds to me more like > > Documentation/GuidelinesForCommunityToBendOverBackwardsToLiveWithFCsProvocations
It has nothing to do with Felipe. I've merely documented repeating patterns in fire threads as violations, in an attempt to avoid fires. I have not worked forward from axioms to derive "transcendentally desirable behavior", but rather backwards from a disaster to derive "patterns that have been shown to lead to large fires". Why? Because it's easier to derive unambiguous statements using my approach; as I will show shortly, there are various problems with your arguments. What gives you the impression that I documented everyone else's violations, but not Felipe's? ;) >> 0. You do not take offense, no matter what. If someone attacks you >> irrationally, you do not respond. This is a public mailing list, and >> we are all rational people: the attacker has already humiliated >> herself in public, and everyone can see that. > > This is secondary to the more important rule, "do not attack other > people on the mailing list". Not taking offense is at best a(n > important) fallback position for those regrettable occasions when > somebody else has already violated the primary guideline. The problem with your guideline is that you now need to define some sort of objective basis to determine whether or not someone attacks. What is this transcendental notion of "attack"? I say something, and you take offense, while someone else does not. Have I or have I not attacked you? One possible solution to this dilemma is to use "majority opinion" as a basis. This is a very dangerous road to go down, as fringe behaviors will keep getting eliminated until we're left with a bunch of yes-men on the list. In other words, an extremely suffocating atmosphere. My guideline does not suffer from this problem. It only requires you to believe that you were personally offended, and act accordingly. Whether or not you were justified in being offended is nobody's business. >> 2. You stop pointing fingers. Every heated discussion requires more >> than one participant, and a flamewar requires many participants. If >> you participate, you have implicitly agreed to share the blame for >> whatever happens on the thread. People can judge for themselves who >> is to blame. > > Here your wording "every heated discussion requires more than one > participant" seems to put more of the blame for heated discussions on > participants 2..N and give a pass to participant number one. I'm not going to comment on the issue of wording, since I've already made it clear that this "patch" is not for inclusion. It is unclear who "Participant #1" is, but I'm not giving anyone a pass; everyone must share the blame. >> 3. Thou shalt not commit logical fallacies. The ones that are most >> common on this list: strawman, ad hominem, burden of proof, false >> cause, the texas sharpshooter, and appeal to authority. > > I think putting a rule like this in CommunityGuidelines puts too much > weight on it. In my recollection, pointing out other people's supposed > logical fallacies is far more often used on this list as a nitpicking > diversionary tactic that usually leads a conversation *further* away > from the real issues. I think it would be a mistake to encourage such > formal and stylized argument on the ML. The guidelines serve as a means of educating people on the list about how they can avoid fuelling fires, not for literally quoting and beating up violators. As I have already stated in the final paragraph, there needs to be no consensus on whether or not a rule has been violated: everyone can judge that for themselves. >> 4. Lead by example. If you do not like how someone presents >> themselves on the list, you counter it by presenting yourself nicely >> on the list. Others will follow your example, making that person's >> behavior the minority. It is far more powerful than explicitly >> stating what is "acceptable" behavior and what is not. > > Leading by example is a great approach, and has the effect that you > describe on the majority of people. But I also think it would be > helpful for the community to agree on a few very minimum standards of > behavior that we insist on, and to call people out (preferably in a > private email) if they fall short of these standards. Let's see what your guidelines look like. >> 5. We are a community of programmers, and we are here to collaborate >> on code. The argument that leads to higher efficiency and better code >> has an automatic advantage over the argument that doesn't. >> >> If someone breaks one of these rules, there's a very simple way to >> communicate this to them: you don't respond to their email. >> Optionally, respond to their email off-list calmly explaining what >> went wrong. > > I would prefer a community standards document that looks more like this: > [...] Summary: be a "nice" person, said in a very gentle way. How is it better than the documents various internet communities have spent years writing and perfecting? [1] [1]: http://www.ubuntu.com/about/about-ubuntu/conduct -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
