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

Re: [PATCH] add a Code of Conduct document

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Sep 25, 2019, 12:34 UTC
Message-ID
<nycvar.QRO.7.76.6.1909251424380.15067@tvgsbejvaqbjf.bet>
In-Reply-To
<20190924210918.GC20858@sigill.intra.peff.net>
Hi,
On Tue, 24 Sep 2019, Jeff King wrote:
Show 10 quoted lines
> On Tue, Sep 24, 2019 at 10:14:55PM +0200, René Scharfe wrote:
>
> > > +* Trolling, insulting/derogatory comments, and personal or
> > > political attacks
> >
> > Hmm.  Trolling can be helpful, if done right.  I consider this to be
> > a good example: https://git-man-page-generator.lokaltog.net/.  Wrote
> > some texts that look like that..
>
> I suppose one man's joke is another man's troll. [...]

And we could now try to dive into that rabbit hole and discuss every detail about it, but...

Show 6 quoted lines
> [...]
>
> Again, I really think the point here is not to enumerate all
> possibilities. It's to set some general expectations, and to make it
> clear that we value the idea of having a genial atmosphere for
> communication that we have a document and a reporting mechanism.

This is a very important point. No CoC can be complete, ever, just like Git will probably never be complete.

The proposed solution is to give power to a committee of trusted members of the Git developer community. The key word here is _trust_. I don't think there can be any doubt that Junio, Peff, Christian and Ævar have earned the trust of the Git developer community.

For those two reasons, I am totally fine with leaving mostly hypothetical scenarios a little vague. Because I trust that committee.

Ciao, Dscho

Previous: Jeff KingNext: brian m. carlson
Message 26 of 28 in “add a Code of Conduct document”
  1. add a Code of Conduct documentJeff King, Sep 24, 2019
  2. SZEDER GáborSep 24, 2019
  3. Johannes SchindelinSep 24, 2019
  4. Jeff KingSep 24, 2019
  5. Daniel StenbergSep 25, 2019
  6. Phillip WoodSep 24, 2019
  7. Derrick StoleeSep 24, 2019
  8. Jeff KingSep 24, 2019
  9. Phillip WoodSep 24, 2019
  10. Garima SinghSep 24, 2019
  11. Deb NicholsonSep 24, 2019
  12. Denton LiuSep 24, 2019
  13. Pratyush YadavSep 24, 2019
  14. Doug MaxeySep 24, 2019
  15. Jeff KingSep 24, 2019
  16. Jeff KingSep 24, 2019
  17. Emily ShafferSep 24, 2019
  18. CODE_OF_CONDUCT: mention individual project-leader emailsJeff King, Sep 26, 2019
  19. Derrick StoleeSep 26, 2019
  20. Emily ShafferSep 26, 2019
  21. CB BaileySep 27, 2019
  22. Jonathan TanSep 24, 2019
  23. Thomas GummererSep 24, 2019
  24. René ScharfeSep 24, 2019
  25. Jeff KingSep 24, 2019
  26. Johannes SchindelinSep 25, 2019
  27. brian m. carlsonSep 24, 2019
  28. Elijah NewrenSep 26, 2019

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.