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

Re: [PATCH] add a Code of Conduct document

From
DMDoug Maxey <doug@maxeymade.com>
Date
Sep 24, 2019, 20:10 UTC
Message-ID
<939c10b4-d018-82cb-395b-e1d85bfa253b@maxeymade.com>
In-Reply-To
<20190924200533.pfi7zjv73zklaahw@yadavpratyush.com>
On 9/24/19 3:05 PM, Pratyush Yadav wrote:
Show 14 quoted lines
> On 24/09/19 10:12AM, Denton Liu wrote:
>> On Tue, Sep 24, 2019 at 02:44:54AM -0400, Jeff King wrote:
>>> +## Enforcement
>>> +
>>> +Instances of abusive, harassing, or otherwise unacceptable behavior may be
>>> +reported by contacting the project team at git@sfconservancy.org. All
>>> +complaints will be reviewed and investigated and will result in a response
>>> +that is deemed necessary and appropriate to the circumstances. The project
>>> +team is obligated to maintain confidentiality with regard to the reporter of
>>> +an incident. Further details of specific enforcement policies may be posted
>>> +separately.
>> I feel uncomfortable with this being left so wide open. First of all, I
>> know that the power *probably* won't be abused but I don't think
>> probably is good enough.
I can put it more succinctly:
Has anyone ever heard the pebble dropped in this well hit bottom?
Show 23 quoted lines
>>
>> As I said above, I couldn't find a public list of the people who were on
>> the project committee. Perhaps that's because my Googling skills are bad
>> but I feel uncomfortable knowing that *anyone* will be given judge, jury
>> and executioner power, let alone people whom I don't know anything
>> about.
>   
> I agree with this. I would certainly like to know who the people who
> will judge these cases are.
>
> I want to add another question: what will the judgement process be like?
> Will it be an open discussion on this list, or will it be decided behind
> closed doors by the committee, and we just get to hear the results?
>
> While there might be no plans regarding this as of now, I'd _really_
> like an open discussion regarding these issues that arise in the future,
> rather than it being decided behind closed doors with us regular old
> contributors getting no say in it. A closed discussion would be much
> more prone to power abuse, if any.
>
>> I'm okay with leaving it open for now but I think I would be a lot more
>> comfortable if we had the interpretations document to close up the
>> vagueness later.
Previous: Pratyush YadavNext: Jeff King
Message 14 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.