git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emily Shaffer <emilyshaffer@google.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
	Simon Pieters <simon@bocoup.com>,
	Don Goodman-Wilson <don@goodman-wilson.com>,
	git@vger.kernel.org
Subject: Virtual Inclusion Summit (was: Re: Rename offensive terminology (master))
Date: Wed, 10 Jun 2020 15:27:19 -0700	[thread overview]
Message-ID: <20200610222719.GE148632@google.com> (raw)

On Wed, Jun 10, 2020 at 11:30:31PM +0200, Johannes Schindelin wrote:

> Encouraged by Emily in #git-devel (who pointed out that a subject like
> this is much better discussed seeing each others faces and hearing each
> others voices), I would like to organize another Virtual Contributor
> Summit, this time focused on inclusive language in Git, what we can do
> about it, and what we should do about it (or not).
> 
> Tentatively, I would like to propose having this meeting in the coming
> week, via Zoom, just like we did the Virtual Contributor Summit last
> September.
> 
> Could I ask all interested parties to reply to this email?

The Google contingent is interested in attending.

One note I'd like to make is that the Git community already suffers from
a lack of diversity; it will be hard for us to make meaningful changes
if just those of us who already contribute attend, because many of us -
myself included! - come from privilege and don't have much or any
firsthand experience with microaggressions (or overt discrimination). I
think it's a good idea to expand the attendance of this summit beyond
the current contributor base and try to include more diverse voices and
experts in building inclusive products.

To that end, I'm going to see what kind of interested parties we can
find to invite within Google - and I hope others will do the same within
their own network. I think the risk of us coming up with meaningless
changes far outweighs the risk of us having too many people in the Zoom
call. :)

 - Emily

             reply	other threads:[~2020-06-10 22:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10 22:27 Emily Shaffer [this message]
2020-06-10 22:48 ` Virtual Inclusion Summit Junio C Hamano
2020-06-11  1:10   ` Taylor Blau
2020-06-11  2:13     ` Junio C Hamano
2020-06-11  2:35       ` Taylor Blau
2020-06-11  8:58         ` Don Goodman-Wilson
2020-06-12 14:22           ` Derrick Stolee
2020-06-12 14:33           ` Johannes Schindelin
2020-06-11 15:25         ` Junio C Hamano
2020-06-12 14:38           ` 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

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

  git send-email \
    --in-reply-to=20200610222719.GE148632@google.com \
    --to=emilyshaffer@google.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=don@goodman-wilson.com \
    --cc=git@vger.kernel.org \
    --cc=sandals@crustytoothpaste.net \
    --cc=simon@bocoup.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 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 NNTP newsgroup(s).