From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Taylor Blau <me@ttaylorr.com>,
Emily Shaffer <emilyshaffer@google.com>,
"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: Fri, 12 Jun 2020 16:38:46 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2006121637080.56@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqh7vhbp5h.fsf@gitster.c.googlers.com>
Hi Junio,
On Thu, 11 Jun 2020, Junio C Hamano wrote:
> Taylor Blau <me@ttaylorr.com> writes:
>
> > 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.
> >> ...
> >> 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.
>
> By the way, if I sounded like I consider this "virtual summit" to be
> no more than just a place for people with heated head to deflate
> before having a civilized conversation, that was not my intention.
>
> I do agree that it is good to have some gathering (or perhaps a
> couple of them in shifting time to accomodate people from different
> parts of the world) to help make sure everybody is moving towards
> the same goal, and I have nothing against a virtual/video meeting
> for that purpose.
>
> Other than that it may be held on Zoom, where I do not particularly
> like to send people to, after seeing articles like [*1*], that is,
> but there may not be a viable alternative. I dunno.
I heard that concern a couple times. The only reason why I suggested that
platform is because we used it last September, and it worked reasonably
well. And that really was the only reason.
Ciao,
Dscho
>
>
> [Reference]
>
> *1* https://www.ft.com/content/f24bc9c6-ed95-4b31-a011-9e3fcd9cf006
>
prev parent reply other threads:[~2020-06-12 14:38 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
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 [this message]
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=nycvar.QRO.7.76.6.2006121637080.56@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=don@goodman-wilson.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.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).