All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Emily Shaffer <emilyshaffer@google.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	"brian m. carlson" <sandals@crustytoothpaste.net>,
	Simon Pieters <simon@bocoup.com>,
	Don Goodman-Wilson <don@goodman-wilson.com>,
	git@vger.kernel.org
Subject: Re: Virtual Inclusion Summit
Date: Wed, 10 Jun 2020 19:10:40 -0600	[thread overview]
Message-ID: <20200611011040.GB21728@syl.local> (raw)
In-Reply-To: <xmqqwo4eedwc.fsf@gitster.c.googlers.com>

On Wed, Jun 10, 2020 at 03:48:03PM -0700, Junio C Hamano wrote:
> Emily Shaffer <emilyshaffer@google.com> writes:
>
> > 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. :)

To Emily; I would be honored to attend. Please let me know if there is
anything that I can do to help organize such a thing.

> It is OK to have an optional meeting in the hope that a video
> meeting may have a better chance to keep those who easily become too
> aggressive and confrontational in text-only conversation in check
> and instead have civilized conversation.
>
> But I am not sure if it is a good idea to call such a meeting a
> "Summit", given that there are those who prefer not to be seen,
> heard or recorded how they appear and how they sound in a video
> conference.  They would not be able to join the conversation held in
> such a "Summit" held only by those who are privileged enough to be
> able to attend.

I think that this is a very reasonable concern, stated in a very
reasonable fashion. Let's call it something else, sure, and avoid
recording/publishing the event (as we have done in the past at other
in-person events--such as the last Git Merge--which seems like a
lifetime ago ;-).)

> Thanks.

Thanks,
Taylor

  reply	other threads:[~2020-06-11  1:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10 22:27 Virtual Inclusion Summit (was: Re: Rename offensive terminology (master)) Emily Shaffer
2020-06-10 22:48 ` Virtual Inclusion Summit Junio C Hamano
2020-06-11  1:10   ` Taylor Blau [this message]
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=20200611011040.GB21728@syl.local \
    --to=me@ttaylorr.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=don@goodman-wilson.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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 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.