All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emily Shaffer <emilyshaffer@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] CoC: update to 2.0
Date: Mon, 28 Dec 2020 10:40:40 -0800	[thread overview]
Message-ID: <20201228184040.GK3783238@google.com> (raw)
In-Reply-To: <xmqq5z4mjdbq.fsf@gitster.c.googlers.com>

On Mon, Dec 28, 2020 at 04:59:53AM -0800, Junio C Hamano wrote:
> 
> At 5cdf2301 (add a Code of Conduct document, 2019-09-24) we adopted
> a Code of Conduct from www.contributor-covenant.org; back then the
> version adopted, 1.4, was the latest one.
> 
> Version 2.0 tightens language in examples of unacceptable behaviour,
> generalizes the audience from "contributors and maintainers" to
> "community", and enhances the enforcement section.
> 
> The preamble we added to the beginning of the document has been
> kept, but the rest of the test has been replaced in full from the
> "upstream" and then the same customization for our community
> (i.e. the way to contact community leadership teams) has been
> applied.
> 
> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Thanks for pulling the update.

Reviewed-by: Emily Shaffer <emilyshaffer@google.com>
> ---
> 
>  * There was a thread to collect acks from community members at
> 
>     https://lore.kernel.org/git/xmqqd0f6n5a4.fsf_-_@gitster-ct.c.googlers.com/
> 
>    and that was how you now see many acks in the trailer of
>    5cdf2301.  If we were to go ahead with this patch to move us to
>    version 2.0, we'd need a similar "Ack" drive, I guess.

  parent reply	other threads:[~2020-12-28 18:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-28 12:59 [PATCH] CoC: update to 2.0 Junio C Hamano
2020-12-28 15:18 ` Derrick Stolee
2020-12-28 17:02 ` brian m. carlson
2020-12-28 17:17 ` [PATCH v2 0/2] CoC: update to 2.0 with less upstream divergence Ævar Arnfjörð Bjarmason
2020-12-28 17:17 ` [PATCH v2 1/2] CoC: Update word-wrapping to match upstream Ævar Arnfjörð Bjarmason
2020-12-29  3:11   ` Jonathan Nieder
2021-01-04 23:43   ` Junio C Hamano
2020-12-28 17:17 ` [PATCH v2 2/2] CoC: update to version 2.0 + local changes Ævar Arnfjörð Bjarmason
2020-12-28 22:58   ` Junio C Hamano
2020-12-29  2:02     ` Elijah Newren
2020-12-29 18:36     ` Derrick Stolee
2020-12-30  8:20     ` Christian Couder
2021-01-04 23:47     ` Re* " Junio C Hamano
2021-01-07 23:28       ` Johannes Schindelin
2021-01-08  0:41         ` Junio C Hamano
2021-01-08  1:57     ` brian m. carlson
2020-12-29  3:17   ` Jonathan Nieder
2020-12-28 17:32 ` [PATCH] CoC: update to 2.0 Ævar Arnfjörð Bjarmason
2020-12-28 22:43   ` Junio C Hamano
2020-12-28 18:40 ` Emily Shaffer [this message]
2020-12-29  8:54 ` Pratyush Yadav

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

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

  git send-email \
    --in-reply-to=20201228184040.GK3783238@google.com \
    --to=emilyshaffer@google.com \
    --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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.