git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: jk/code-of-conduct, was Re: What's cooking in git.git (Oct 2019, #02; Mon, 7)
Date: Tue, 8 Oct 2019 21:36:26 +0200 (CEST)
Message-ID: <nycvar.QRO.7.76.6.1910082111220.46@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqq36g5444k.fsf@gitster-ct.c.googlers.com>

[-- Attachment #1: Type: text/plain, Size: 3052 bytes --]

Hi Junio,

On Mon, 7 Oct 2019, Junio C Hamano wrote:

> Here are the topics that have been cooking.  Commits prefixed with
> '-' are only in 'pu' (proposed updates) while commits prefixed with
> '+' are in 'next'.  The ones marked with '.' do not appear in any of
> the integration branches, but I am still holding onto them.
>
> You can find the changes described here in the integration branches
> of the repositories listed at
>
>     http://git-blame.blogspot.com/p/git-public-repositories.html
>
> --------------------------------------------------
> [...]
> [New Topics]
>
> [...]

I missed a well-ACKed contribution in here: the code of conduct Peff
kindly submitted, with the add-on that clarifies who is in that group of
potential mediators. See

https://public-inbox.org/git/20190924064454.GA30419@sigill.intra.peff.net/

and

https://public-inbox.org/git/20190926072046.GB20653@sigill.intra.peff.net/

As far as I can tell, there was only one critical voice, Gábor, and when
I responded asking for clarifications which part of the code of conduct
exactly would require any change of behavior, there was no response,
which I took as a silent sign of acquiescence.

René also offered concerns about a part of the code of conduct that they
considered to be too vague, but I think both Peff and I explained why it
should remain as-is (again, there was no response, which I, again, am
forced to interpret, and I interpret it as agreeing to the points made
in particular by Peff).

In contrast, the patch won support from the cURL maintainer
(https://public-inbox.org/git/alpine.DEB.2.20.1909250834220.4757@tvnag.unkk.fr/),
and endorsements (also known as ACKs) from myself
(https://public-inbox.org/git/nycvar.QRO.7.76.6.1909241426580.15067@tvgsbejvaqbjf.bet/),
from Stolee
(https://public-inbox.org/git/6a9fb4c2-6c80-4475-03d3-89bdba73095b@gmail.com/),
from Phillip Wood (although I don't dare to interpet this as a full ACK)
(https://public-inbox.org/git/cc8cc0b3-777c-6ef8-202f-ea1d0518bbd3@gmail.com/),
from Garima
(https://public-inbox.org/git/133b46b2-b2e1-4673-820b-5a5ca6ec0269@gmail.com/),
from Jonathan Tan
(https://public-inbox.org/git/20190924172324.104795-1-jonathantanmy@google.com/),
from Thomas Gummerer
(https://public-inbox.org/git/20190924174056.GA55104@cat/), from
brian
(https://public-inbox.org/git/20190924233728.6iueqaktlhhfwn7k@camp.crustytoothpaste.net/),
and from Elijah
(https://public-inbox.org/git/CABPp-BERhEp2At-ABPrkCHcqLfb32t+S0hPHs=d17QjcZR1wPA@mail.gmail.com/).

In other words, the commit message can be augmented by this:

Acked-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Acked-by: Derrick Stolee <stolee@gmail.com>
Acked-by: Garima Singh <garimasigit@gmail.com>
Acked-by: Jonathan Tan <jonathantanmy@google.com>
Acked-by: Thomas Gummerer <t.gummerer@gmail.com>
Acked-by: brian m. carlson <sandals@crustytoothpaste.net>
Acked-by: Elijah Newren <newren@gmail.com>

Junio, would you mind picking it up, please?

Ciao,
Dscho

  reply index

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07  3:38 Junio C Hamano
2019-10-08 19:36 ` Johannes Schindelin [this message]
2019-10-09  0:14   ` Raise your hand to Ack jk/code-of-conduct if your Ack fell thru cracks Junio C Hamano
2019-10-09  0:22     ` Taylor Blau
2019-10-09  1:41     ` Emily Shaffer
2019-10-09  8:07       ` Johannes Schindelin
2019-10-09  1:48     ` Jonathan Nieder
2019-10-09 10:36     ` Christian Couder
2019-10-09 15:13     ` Phillip Wood
2019-10-09 18:29     ` Elijah Newren
2019-10-09 19:37       ` Junio C Hamano
2019-10-09 19:52     ` William Baker
2019-10-09 20:50     ` CB Bailey
2019-10-10  0:18     ` Eric Wong
2019-10-11  5:58       ` Jeff King
2019-10-17 13:56         ` Philip Oakley
2019-10-11  4:39     ` Junio C Hamano
2019-10-11  6:01       ` Jeff King
2019-10-09  1:39   ` jk/code-of-conduct, was Re: What's cooking in git.git (Oct 2019, #02; Mon, 7) SZEDER Gábor

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=nycvar.QRO.7.76.6.1910082111220.46@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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

git@vger.kernel.org list mirror (unofficial, one of many)

Archives are clonable:
	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

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/

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git