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

Re: [PATCH] add a Code of Conduct document

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Sep 24, 2019, 23:37 UTC
Message-ID
<20190924233728.6iueqaktlhhfwn7k@camp.crustytoothpaste.net>
In-Reply-To
<20190924064454.GA30419@sigill.intra.peff.net>
On 2019-09-24 at 06:44:54, Jeff King wrote:
Show 19 quoted lines
> We've never had a formally written Code of Conduct document. Though it
> has been discussed off and on over the years, for the most part the
> behavior on the mailing list has been good enough that nobody felt the
> need to push one forward.
> 
> However, even if there aren't specific problems now, it's a good idea to
> have a document:
> 
>   - it puts everybody on the same page with respect to expectations.
>     This might avoid poor behavior, but also makes it easier to handle
>     it if it does happen.
> 
>   - it publicly advertises that good conduct is important to us and will
>     be enforced, which may make some people more comfortable with
>     joining our community
> 
>   - it may be a good time to cement our expectations when things are
>     quiet, since it gives everybody some distance rather than focusing
>     on a current contentious issue
I wholeheartedly agree with this assessment.
> If people are on board with this direction, it might be fun to pick up a
> bunch of "Acked-by" trailers from people in the community who agree with
> it. It might give it more weight if many members have publicly endorsed
> it.

I've already mentioned that I think this is a good idea, and I appreciate your thorough rationale in the commit message.

Acked-by: brian m. carlson <sandals@crustytoothpaste.net>
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
Previous: Johannes SchindelinNext: Elijah Newren
Message 27 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.