From: Jeff King <email@example.com>
To: Eric Wong <firstname.lastname@example.org>
Cc: Taylor Blau <email@example.com>, Carmen Andoh <firstname.lastname@example.org>,
email@example.com, Jonathan Nieder <firstname.lastname@example.org>
Subject: Re: Git Inclusion Summit
Date: Tue, 28 Jul 2020 12:44:54 -0400 [thread overview]
Message-ID: <20200728164454.GA2650362@coredump.intra.peff.net> (raw)
On Tue, Jul 28, 2020 at 10:07:26AM +0000, Eric Wong wrote:
> > Hopefully everybody should have a good-enough internet connection to
> > stream a low-quality audio-only feed so that they can listen in and
> > participate via the chat feature. This is what we did at the
> > Contributor's Summit in March (I know we had a number of text-only
> > participants in time-zones where it was late, etc.).
> > What are your thoughts?
> Jitsi w/ audio-only certainly seems to be a step in the right
> direction and would be more inclusive.
> Is there any speech-to-text transcription done for the hearing
> (or extremely bandwidth) impaired?
> It'd ideally go to #git on IRC (or something that doesn't
> require a browser to trigger swap storms on old systems).
Whether we have automatic speech-to-text conversion or not, I think it
would be good for people involved to take and publish notes summarizing
the conversation. One of the important things about our usual async
written communication is that it gives people time to organize their
thoughts and say what they want succinctly. Live conversations are often
full of false starts and rambling. That's OK, and a necessary part of
the process. But if you want a wider audience to follow along, it helps
to turn that into something more time efficient for readers.
prev parent reply other threads:[~2020-07-28 16:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 19:30 Git Inclusion Summit Carmen Andoh
2020-07-23 20:59 ` Jonathan Nieder
2020-07-23 22:26 ` Junio C Hamano
2020-07-24 12:55 ` Carmen Andoh
2020-07-26 4:02 ` Eric Wong
2020-07-27 15:10 ` Taylor Blau
2020-07-28 10:07 ` Eric Wong
2020-07-28 16:25 ` Taylor Blau
2020-07-28 17:15 ` Kaartic Sivaraam
2020-07-29 17:00 ` 24 hours to respond with date/duration preferences for inclusion summit Carmen Andoh
2020-07-29 18:25 ` Junio C Hamano
2020-07-29 19:29 ` Carmen Andoh
2020-07-28 16:44 ` Jeff King [this message]
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:
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 \
* 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
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).