All of lore.kernel.org
 help / color / mirror / Atom feed
From: Deb Nicholson <deb@sfconservancy.org>
To: Garima Singh <garimasigit@gmail.com>, Jeff King <peff@peff.net>,
	git@vger.kernel.org
Cc: 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>
Subject: Re: [PATCH] add a Code of Conduct document
Date: Tue, 24 Sep 2019 12:56:03 -0400	[thread overview]
Message-ID: <1569344163.2309.5.camel@sfconservancy.org> (raw)
In-Reply-To: <133b46b2-b2e1-4673-820b-5a5ca6ec0269@gmail.com>

Hi all, 
Deb here from Git's fiscal home. Let us know if you need any advice or
help finding a professional consultant to take a look at the Code of
Conduct document for you. I'm also happy to perosanlly take a look at
any draft(s).
Best, 
Deb


On Tue, 2019-09-24 at 12:53 -0400, Garima Singh wrote:
> On 9/24/2019 2:44 AM, Jeff King wrote:
> > 
> > 
> > If people are on board with this direction, it might be fun to pick
> > up a
> > bunch of "Acked-by" trailers from people in the community who agree
> > with
> > it. It might give it more weight if many members have publicly
> > endorsed
> > it.
> > 
> > I've cc'd git@sfconservancy.org here, because I think it's
> > important for
> > all of the project committee members to endorse it (and because the
> > document puts us on the hook for enforcing it!).
> > 
> I think this looks really good. I appreciate how it gets the point
> across for
> people to empower each other and welcome new members without being
> too wordy.
> It gets my wholehearted ACK. Thanks for putting it together. 
> 
> Cheers,
> Garima G Singh
-- 
Deb Nicholson <deb@sfconservancy.org>
Software Freedom Conservancy


  reply	other threads:[~2019-09-24 17:05 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 [this message]
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
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

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

  git send-email \
    --in-reply-to=1569344163.2309.5.camel@sfconservancy.org \
    --to=deb@sfconservancy.org \
    --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=peff@peff.net \
    --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. 
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.