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

[PATCH] Documentation/CommunityGuidelines

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Jun 10, 2013, 13:28 UTC
Message-ID
<CALkWK0mqk5sRPV8PHz8RqZH-Ln7TUtkHPVbvsJPKuVSXiUOiww@mail.gmail.com>
I've tried to write down a bare minimum, without restating the obvious.
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.
1. You do not take sides or vote.  Do not post emails under the
pretext of agreement: repeating what has already been said does not
strengthen the argument.  Post only if you have something unique to
add to the discussion.
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.
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.
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.
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.

Next: Célestin Matte
Message 1 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.