git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Documentation/CommunityGuidelines

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Jun 11, 2013, 05:16 UTC
Message-ID
<CAMP44s3ZSTZQ5juNnwRTC_tSSe68wvjvOi=MBwu3g9pTbPBNqA@mail.gmail.com>
In-Reply-To
<7vzjuxj21b.fsf@alter.siamese.dyndns.org>
On Mon, Jun 10, 2013 at 12:42 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 36 quoted lines
> "Robin H. Johnson" <robbat2@gentoo.org> writes:
>
>> On Mon, Jun 10, 2013 at 04:04:29PM +0200,  Matthieu Moy wrote:
>>> Célestin Matte <celestin.matte@ensimag.fr> writes:
>>>
>>> > Le 10/06/2013 15:28, Ramkumar Ramachandra a écrit :
>>> >> 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.
>>> >
>>> > "Herself"?
>>> > Typo I guess :)
>>>
>>> Not necessarily. It's quite common in english to use "she" when the
>>> gender is not known.
>> Could you please use "themself" instead?
>
> I think "himself or herself" is the politically correct form ;-)
>
> But more seriously.
>
> The intent behind the document might be a noble one, but I am afraid
> that the text is too broad and vague and does not address the real
> issue to be of practical use.
>
> Taking one bullet point from the top for example:
>
>     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.
>
> What does saying "we are all rational people" help when "the
> attacker" poses a risk to destroy the community?  What does "we are
> all rational people" even mean in this sentence?

Science shows that humans are in fact, not rational people. It's simply one of our countless limitations. We acknowledge we have physical limitations, but we forget our mental limitations.

We should aim to be rational people, yes, but we are not.
Show 8 quoted lines
> It does not address the real cause of flamewars---why do rational
> people feel the need to respond when an irrational comment is made,
> e.g. when a reasonable review comments were responded not with
> either "Yeah, you are right, thanks." or "Not really, because you
> missed this case, I think..."  but with nitpicks with immaterial
> details or repetition without justification that takes account that
> the reviewer is in disagreement and there must be some reason behind
> it, i.e. a poisonous behaviour?

First of all, you should not refer to it as "poisonous behavior". Maybe you think it's poisonous, maybe everyone else in the mailing list agrees it's poisonous, but talk doesn't make things real, otherwise there were a lot of real witches in the past.

You should refer to it as 'what could be considered poisonous behavior'. That is accurate.

Calling it "poisonous behavior" at best can be considered a logical fallacy, and at worst could even be described as a poisonous comment itself.

Show 9 quoted lines
> I suspect it mostly has to do with the desire to make sure that
> bystanders do not get an impression that the one who speaks last
> gives the conclusion to the discussion, so stating "The attacker
> being the one who speaks last in the discussion does not mean the
> conclusion is his." explicitly might be one way to make it more
> practically useful by alleviating the urge to respond, instead of
> saying "no matter what".
>
> I dunno.

I think we all know at some level why flame war arise, as XKCD makes it comically succinct[1].

If somebody wants to argue for the sake of arguing, they should go to some forum, or reddit, or something else other than the mailing list.

In the mailing list you should avoid flamewars. If you have identified a flamewar, don't poke it, and ask for others to do the same; don't throw lumber unto the flames.

I know you worry that somebody is wrong on the Internet, and you worry that somebody else might read that, and think the person that is wrong is actually right. But you cannot fix that. Move on. If the reader is smart, they'll understand the signal "Don't throw lumber unto the flames." followed by silence from other members of the community.

Trying to "correct" somebody often sends the wrong signal; you validate the other person's point of view as something worth arguing about. If you truly think a flamewar is taking place, resist your urge to participate in it, and mute it.

Maybe it's not really flamewar, and something important is being discussed, but you should leave the people that do not think a flamewar is taking place to argue with each other, and stay out of that. If you think it's a flamewar, and you comment in it, you are making it worst, and perhaps turning it into a real flamewar if it wasn't.

In general; do not participate in a flamewar. Period.
[1] http://xkcd.com/386/
-- 
Felipe Contreras
Previous: A Large Angry SCMNext: Ramkumar Ramachandra
Message 11 of 63 in “Documentation/CommunityGuidelines”
  1. Documentation/CommunityGuidelinesRamkumar Ramachandra, Jun 10, 2013
  2. Célestin MatteJun 10, 2013
  3. Matthieu MoyJun 10, 2013
  4. Robin H. JohnsonJun 10, 2013
  5. Junio C HamanoJun 10, 2013
  6. Jonathan NiederJun 10, 2013
  7. Ramkumar RamachandraJun 10, 2013
  8. A Large Angry SCMJun 10, 2013
  9. Ramkumar RamachandraJun 10, 2013
  10. A Large Angry SCMJun 10, 2013
  11. Felipe ContrerasJun 11, 2013
  12. Ramkumar RamachandraJun 11, 2013
  13. Michael HaggertyJun 11, 2013
  14. Felipe ContrerasJun 11, 2013
  15. Ramkumar RamachandraJun 11, 2013
  16. Felipe ContrerasJun 11, 2013
  17. Thomas RastJun 11, 2013
  18. Ramkumar RamachandraJun 11, 2013
  19. Michael HaggertyJun 11, 2013
  20. Felipe ContrerasJun 11, 2013
  21. Ramkumar RamachandraJun 11, 2013
  22. Michael HaggertyJun 11, 2013
  23. Ramkumar RamachandraJun 11, 2013
  24. Junio C HamanoJun 11, 2013
  25. Felipe ContrerasJun 11, 2013
  26. Felipe ContrerasJun 11, 2013
  27. Brandon CaseyJun 11, 2013
  28. Theodore Ts'oJun 12, 2013
  29. Ramkumar RamachandraJun 12, 2013
  30. Felipe ContrerasJun 12, 2013
  31. Felipe ContrerasJun 11, 2013
  32. Thomas RastJun 11, 2013
  33. Felipe ContrerasJun 11, 2013
  34. Thomas RastJun 11, 2013
  35. Felipe ContrerasJun 11, 2013
  36. Junio C HamanoJun 11, 2013
  37. Michael HaggertyJun 11, 2013
  38. John KeepingJun 11, 2013
  39. Ramkumar RamachandraJun 11, 2013
  40. John KeepingJun 11, 2013
  41. Ramkumar RamachandraJun 12, 2013
  42. John KeepingJun 12, 2013
  43. Michael HaggertyJun 11, 2013
  44. John KeepingJun 11, 2013
  45. Philip OakleyJun 11, 2013
  46. John SzakmeisterJun 12, 2013
  47. Jakub NarebskiJun 12, 2013
  48. Philip OakleyJun 12, 2013
  49. Felipe ContrerasJun 11, 2013
  50. Jeff KingJun 11, 2013
  51. Junio C HamanoJun 11, 2013
  52. Felipe ContrerasJun 11, 2013
  53. Theodore Ts'oJun 12, 2013
  54. Felipe ContrerasJun 12, 2013
  55. Ramkumar RamachandraJun 12, 2013
  56. Junio C HamanoJun 12, 2013
  57. Michael HaggertyJun 13, 2013
  58. Junio C HamanoJun 13, 2013
  59. Felipe ContrerasJun 11, 2013
  60. Ramkumar RamachandraJun 11, 2013
  61. Thomas AdamJun 13, 2013
  62. Felipe ContrerasJun 13, 2013
  63. Christian CouderJun 14, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.