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

Re: Raise your hand to Ack jk/code-of-conduct if your Ack fell thru cracks

From
Jeff King <peff@peff.net>
Date
Oct 11, 2019, 05:58 UTC
Message-ID
<20191011055827.GA20094@sigill.intra.peff.net>
In-Reply-To
<20191010001853.h2pepvg7yilevipv@dcvr>
On Thu, Oct 10, 2019 at 12:18:53AM +0000, Eric Wong wrote:
Show 10 quoted lines
> > The project leadership team can be contacted by email as a whole at
> > git@sfconservancy.org, or individually:
> > 
> >   - Ævar Arnfjörð Bjarmason <avarab@gmail.com>
> >   - Christian Couder <christian.couder@gmail.com>
> >   - Jeff King <peff@peff.net>
> >   - Junio C Hamano <gitster@pobox.com>
> 
> All folks that have proven to exhibit good judgement in the past,
> and hope they continue to exhibit that in the future.

I snipped your concerns with some of the language. I do agree with you that a lot of is open to interpretation. But I also think it's impossible to get it 100% airtight. My feeling was that it was a good idea to go with some existing, well-established text, even if it has some wiggle room. And then rely on the existing community and especially the people listed above to do that interpretation.

So...
> Just pointing out some concerns of mine.  No ack from me
> (but it's not a NACK, either).  I'm pretty ambivalent...

For me it is obviously an ack, but I wanted to make clear that I think your concerns (and those of others who spoke up, like René and Gábor) are certainly _valid_. I just think that adopting this CoC is, while not perfect, the least-bad option.

I'd also say that we might consider living with it for a while (6 months? a year?) and seeing if people have an interest in revising it after that point based on experience.

This is the same text used by the kernel, btw. I think somebody mentioned to me (but I think it may have been off-list) that the kernel has an "interpretation" document:

  https://www.kernel.org/doc/html/latest/process/code-of-conduct-interpretation.html

which clarifies a few terms with respect to that specific community. I didn't feel that we particularly needed to do that for our community, but if somebody wants to work up a clarifying document, I'd be happy to review it.

-Peff
Previous: Eric WongNext: Philip Oakley
Message 15 of 19 in “What's cooking in git.git (Oct 2019, #02; Mon, 7)”
  1. Junio C HamanoOct 7, 2019
  2. jk/code-of-conduct, was Re: What's cooking in git.git (Oct 2019, #02; Mon, 7)Johannes Schindelin, Oct 8, 2019
  3. Raise your hand to Ack jk/code-of-conduct if your Ack fell thru cracksJunio C Hamano, Oct 9, 2019
  4. Taylor BlauOct 9, 2019
  5. Emily ShafferOct 9, 2019
  6. Johannes SchindelinOct 9, 2019
  7. Jonathan NiederOct 9, 2019
  8. Christian CouderOct 9, 2019
  9. Phillip WoodOct 9, 2019
  10. Elijah NewrenOct 9, 2019
  11. Junio C HamanoOct 9, 2019
  12. William BakerOct 9, 2019
  13. CB BaileyOct 9, 2019
  14. Eric WongOct 10, 2019
  15. Jeff KingOct 11, 2019
  16. Philip OakleyOct 17, 2019
  17. Junio C HamanoOct 11, 2019
  18. Jeff KingOct 11, 2019
  19. SZEDER GáborOct 9, 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.