From: Jeff King <peff@peff.net> To: Denton Liu <liu.denton@gmail.com> Cc: Derrick Stolee <stolee@gmail.com>, "git@vger.kernel.org" <git@vger.kernel.org>, Emily Shaffer <emilyshaffer@google.com>, Jonathan Nieder <jrnieder@gmail.com>, Johannes Schindelin <Johannes.Schindelin@gmx.de>, "gitster@pobox.com" <gitster@pobox.com>, garimasigit@gmail.com Subject: Re: [DISCUSSION] Growing the Git community Date: Thu, 19 Sep 2019 18:26:07 -0400 Message-ID: <20190919222607.GA25680@sigill.intra.peff.net> (raw) In-Reply-To: <20190919173423.GA70421@dentonliu-ltm.internal.salesforce.com> On Thu, Sep 19, 2019 at 10:34:23AM -0700, Denton Liu wrote: > > 4. Add an official Code of Conduct > > > > So far, the community has had an unofficial policy of "be nice, > > as much as possible". We should add a Code of Conduct that is > > more explicit about the behavior we want to model. This was also > > discussed in the meeting with wide approval. > > From what I've personally read and experienced, I don't think that an > official Code of Conduct is really warranted. Everyone I've interacted > with has been really kind. Perhaps a new contributor might interpret the > curtness of replies here as someone being rude but I quickly learned > that it's more out of necessity since everyone is busy. > > From reading the mailing list archives, I know that in the past, there > have been some flamewars and some abrasive individuals but I think > that's a problem of the past. I've had similar thoughts over the years, but eventually switched my way of thinking. I think part of that switch was coming to the conclusion that most of the value of a Code of Conduct isn't about having a system of enforcement against bad actors (in fact, I think that's the most difficult and potentially problematic part, because it creates a sort of justice system). IMHO the most important part is that it communicates and reinforces norms: - It lets good actors easily understand what the expectations are. - It gives a framework for agreed-upon principles, so that people can more easily and productively discuss the conflicts that do happen. - It advertises our values to people outside the community, which may help make us more inviting for people to join (and ultimately contribute code, or docs, or reviews, etc). > I also see some drawbacks to implementing a CoC as well. First of all, > it just feels like unnecessary bureaucracy. Second, I think it'll > probably cause a stir like it did when the Linux kernel introduced it. > Of course, all that noise will die down eventually but I feel like it'll > bring the wrong kind of attention to Git. I've also been worried about that. And it's easy to think "nobody is behaving too badly right now, so it's all a net negative since we risk a trollish flamewar". But I think it's easy to discount "invisible" negatives of the status quo, like people who are hesitant to join the community because of the lack of a CoC. We in the community don't see that. And even for people who remember what it was like to join, many people have different expectations and experiences. If we can easily make ourselves more inviting to a wider range of people, that seems like a win. -Peff
next prev parent reply other threads:[~2019-09-19 22:26 UTC|newest] Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-09-19 16:30 Derrick Stolee 2019-09-19 17:34 ` Denton Liu 2019-09-19 20:43 ` Emily Shaffer 2019-09-19 22:26 ` Jeff King [this message] 2019-09-20 17:48 ` Junio C Hamano 2019-09-20 15:22 ` Garima Singh 2019-09-20 17:51 ` Junio C Hamano 2019-09-19 18:44 ` Klaus Sembritzki 2019-09-19 19:12 ` Klaus Sembritzki 2019-09-19 20:20 ` Klaus Sembritzki 2019-09-20 5:04 ` Klaus Sembritzki 2019-09-20 5:41 ` Klaus Sembritzki 2019-09-20 6:54 ` Klaus Sembritzki 2019-09-20 7:43 ` Klaus Sembritzki 2019-09-20 10:25 ` Klaus Sembritzki 2019-09-19 21:40 ` Mike Hommey 2019-09-23 21:28 ` Johannes Schindelin 2019-10-01 15:03 ` Jakub Narebski 2019-09-19 22:16 ` Jeff King 2019-09-20 2:17 ` Derrick Stolee 2019-09-20 2:23 ` Jeff King 2019-09-19 22:21 ` Elijah Newren 2019-09-25 13:36 ` Pierre Tardy 2019-09-25 14:02 ` Derrick Stolee 2019-10-04 12:39 ` Jakub Narebski 2019-09-25 14:14 ` Philip Oakley 2019-10-04 10:48 ` Jakub Narebski 2019-11-12 18:45 ` Emily Shaffer 2019-11-12 20:01 ` Johannes Schindelin 2019-11-13 6:45 ` Christian Couder 2019-11-13 15:06 ` Thomas Gummerer 2019-11-14 2:31 ` Emily Shaffer 2019-11-14 6:06 ` Jeff King 2019-11-15 4:48 ` Junio C Hamano 2019-11-14 6:08 ` Pratyush Yadav 2019-11-14 10:01 ` Thomas Gummerer 2019-09-20 10:48 ` Philip Oakley 2019-09-20 14:36 ` brian m. carlson 2019-09-20 15:16 ` Randall S. Becker 2019-10-04 14:27 ` Jakub Narebski 2019-09-20 15:20 ` Garima Singh 2019-09-20 17:43 ` Junio C Hamano 2019-09-20 18:52 ` Junio C Hamano 2019-09-23 12:36 ` Derrick Stolee 2019-09-23 21:46 ` Johannes Schindelin
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=20190919222607.GA25680@sigill.intra.peff.net \ --to=peff@peff.net \ --cc=Johannes.Schindelin@gmx.de \ --cc=emilyshaffer@google.com \ --cc=garimasigit@gmail.com \ --cc=git@vger.kernel.org \ --cc=gitster@pobox.com \ --cc=jrnieder@gmail.com \ --cc=liu.denton@gmail.com \ --cc=stolee@gmail.com \ --subject='Re: [DISCUSSION] Growing the Git community' \ /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
git@vger.kernel.org list mirror (unofficial, one of many) This inbox may be cloned and mirrored by anyone: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V1 git git/ https://public-inbox.org/git \ git@vger.kernel.org public-inbox-index git Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git nntp://news.gmane.io/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git AGPL code for this site: git clone https://public-inbox.org/public-inbox.git