From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Taylor Blau <me@ttaylorr.com>,
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 20:35:03 -0600 [thread overview]
Message-ID: <20200611023503.GA24130@syl.local> (raw)
In-Reply-To: <xmqq7dwecpsp.fsf@gitster.c.googlers.com>
On Wed, Jun 10, 2020 at 07:13:58PM -0700, Junio C Hamano wrote:
> Taylor Blau <me@ttaylorr.com> writes:
>
> >> 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 ;-).)
>
> I am not opposed to recording and publishing for wider dissemination
> of what was said and agreed on among participants, who join with the
> full understanding of how the video meeting will later be consumed.
>
> What I am hesitant to see is that such an opt-in meeting becomes
> "you got a chance to attend and have your voice heard---if you
> didn't come, that was your choice, and whatever objection you give
> after it does not count" summit.
Ah, thanks for your clarification (and sorry for the misunderstanding).
I figure that any synchronous discussion should augment the on-list
discussion, not replace it.
Thanks,
Taylor
next prev parent reply other threads:[~2020-06-11 2:35 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
2020-06-11 2:13 ` Junio C Hamano
2020-06-11 2:35 ` Taylor Blau [this message]
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
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=20200611023503.GA24130@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).