git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: "René Scharfe" <l.s.r@web.de>
Cc: git@vger.kernel.org, git@sfconservancy.org,
	Derrick Stolee <stolee@gmail.com>,
	Emily Shaffer <emilyshaffer@google.com>,
	Jonathan Nieder <jrnieder@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Junio C Hamano <gitster@pobox.com>,
	garimasigit@gmail.com
Subject: Re: [PATCH] add a Code of Conduct document
Date: Tue, 24 Sep 2019 17:09:18 -0400	[thread overview]
Message-ID: <20190924210918.GC20858@sigill.intra.peff.net> (raw)
In-Reply-To: <89c6f5b7-aeab-740c-06b6-e50232266fd4@web.de>

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. Is the manpage
generator too mean? I don't think so (I think it's quite funny). I guess
somebody could. But at some point all of these terms are open to
interpretation, and we're going to have to rely on discussion and
precedent.

I don't think step 1 would ever be "report the manpage generator to the
committee, and get it banned!". For one thing, we have no control over
their domain, and it really exists outside of our development community.
So at most we say "yeah, we don't like that; please don't". But more
importantly, I think step 1 is somebody saying "hey, this kind of seems
in poor taste", and then we all have a discussion about it.

> "Personal and political attacks" sound really scary and don't seem to
> match trolling and insulting in severity.  Perhaps I don't understand
> the intended meaning.  In any case, I also wouldn't want anyone to be
> beaten up or swatted, get a lower social credit score or be forced out
> of public office over participation in our project.

I take political attacks to be things like "Everyone from Country X is a
moron", or "People who support political party X are jerks". You might
even have a legitimate complaint about somebody's politics, but if
they're not bringing their politics into the project, it seems wrong to
attack them over it.

I do think there's some grey area there, though, because there _is_ some
intersection of politics (e.g., a discussion about licensing could
easily get into discussion of laws and IP). But if people are talking
constructively about it, and not attacks like "the party you support has
a dumb interpretation of the GPL", that seems fine to me.

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.

> > +* Other conduct which could reasonably be considered inappropriate in a
> > +  professional setting
> 
> This is very vague.  It could match eating at your desk, tipping, not
> tipping, not wearing a tie, or talking back to a senior developer.

Here I'd go back to "discussion and precedent" from above. Community
norms are a moving target to some degree. Wearing a tie was
unprofessional at one point, and now that is very much not the case, at
least in the programming profession. I think we have to stay somewhat
vague and rely on the social interactions of the community to resolve
things (and again, this is more or less what the status quo is; the
document is mostly a commitment from project leadership to take
seriously discussion and complains about behavior within the project).

-Peff

  reply	other threads:[~2019-09-24 21:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-24  6:44 [PATCH] add a Code of Conduct document Jeff King
2019-09-24  9:01 ` SZEDER Gábor
2019-09-24 13:20   ` Johannes Schindelin
2019-09-24 15:50     ` Jeff King
2019-09-25  6:39     ` Daniel Stenberg
2019-09-24 14:40   ` Phillip Wood
2019-09-24 12:13 ` Derrick Stolee
2019-09-24 15:51   ` Jeff King
2019-09-24 14:13 ` Phillip Wood
2019-09-24 16:53 ` Garima Singh
2019-09-24 16:56   ` Deb Nicholson
2019-09-24 17:12 ` Denton Liu
2019-09-24 20:05   ` Pratyush Yadav
2019-09-24 20:10     ` Doug Maxey
2019-09-24 20:52     ` Jeff King
2019-09-24 20:46   ` Jeff King
2019-09-24 23:52   ` Emily Shaffer
2019-09-26  7:20     ` [PATCH] CODE_OF_CONDUCT: mention individual project-leader emails Jeff King
2019-09-26 12:16       ` Derrick Stolee
2019-09-26 21:37       ` Emily Shaffer
2019-09-27 18:58       ` CB Bailey
2019-09-24 17:23 ` [PATCH] add a Code of Conduct document Jonathan Tan
2019-09-24 17:40 ` Thomas Gummerer
2019-09-24 20:14 ` René Scharfe
2019-09-24 21:09   ` Jeff King [this message]
2019-09-25 12:34     ` Johannes Schindelin
2019-09-24 23:37 ` brian m. carlson
2019-09-26 17:42 ` Elijah Newren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190924210918.GC20858@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=emilyshaffer@google.com \
    --cc=garimasigit@gmail.com \
    --cc=git@sfconservancy.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --cc=l.s.r@web.de \
    --cc=stolee@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).