git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Contributor Summit Topics and Logistics
Date: Sat, 02 Feb 2019 13:33:22 +0100	[thread overview]
Message-ID: <86va22qsj1.fsf@gmail.com> (raw)
In-Reply-To: <20190130230702.GA25423@sigill.intra.peff.net> (Jeff King's message of "Thu, 31 Jan 2019 00:07:03 +0100")

Jeff King <peff@peff.net> writes:

> On Tue, Jan 22, 2019 at 02:50:27AM -0500, Jeff King wrote:
>
>> If you're not coming, you can probably stop reading this message now.
>> The rest is all logistics.
>
> Here are a few additional last-minute logistics:
>
>> For people who want to try to join remotely, I don't think we're going
>> to have a particularly fancy AV setup. But there should at least be a
>> big screen (which we typically do not really use for presenting), and I
>> hope we can provide some connectivity. I'll be visiting the venue the
>> day before (Jan 30th) in the late afternoon (Brussels time) and I'll try
>> to do a test run. If anybody wants to volunteer to be the guinea pig on
>> the other end of the line, I'd welcome it.
>
> The remote connection will be done via Zoom, using this URL which will
> become active shortly before 10:00am (Brussels time):
>
>   https://github.zoom.us/j/186903655
>
> You may need to download an app or other software; solutions are
> available for most platforms, and the zoom site should guide you.

Thank you very much for setting this remote connection up.  It did make
it possible for me to watch the Git Contributor Summit 2019 (and take
notes for Git Rev News).  I have had Zoom installed already, so it was
not a problem.  (As I have seen, Szeder Gábor was also spectacting ;-)

The audio was not always clear, which depended on where the person
speaking was positioned; I understand that it is a very difficult
problem to get good acoustic in such unstructured setup.

> Note that this is _not_ configured as a one-way webinar. It's a real
> video-conference where joiners can participate in the discussion. So
> spectators from the community are OK, but please leave your camera/mic
> off if you're not actively participating.

As far as I know it went untested (but then nobody announced that he or
she wants to actively participate remotely).

I didn't stay for the 15-17 breakout session (talking in individual
groups); I wonder how well the remote connection setup would work with
multiple discussions in parallel.


I have noticed a little 'recording' indicator; would recorded session
(video or audio only) be made available at some point in time?  Did
anyone take minutes, or take notes (for example of the Summit agenda
created at the start of the meeting -- when the audio was muted)?  I
would be very interested in your impressions.

> See everybody tomorrow at 9:00am.

The event actually started at 10:00am CET.


Thanks again,
--
Jakub Narębski

  reply	other threads:[~2019-02-02 12:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-22  7:50 Contributor Summit Topics and Logistics Jeff King
2019-01-22  8:26 ` Jeff King
2019-01-22  9:17   ` GSoC 2019 (was: Contributor Summit Topics and Logistics) Christian Couder
2019-01-31  2:02     ` SZEDER Gábor
2019-01-31  6:11       ` Christian Couder
2019-01-22 18:21   ` Contributor Summit Topics and Logistics Stefan Beller
2019-01-22 20:53     ` Jeff King
2019-01-22 18:23 ` Derrick Stolee
2019-01-24  8:57   ` Ævar Arnfjörð Bjarmason
2019-01-29 18:22     ` Derrick Stolee
2019-01-22 20:30 ` Elijah Newren
2019-01-30 20:57 ` Ævar Arnfjörð Bjarmason
2019-01-30 22:26   ` Jeff Hostetler
2019-01-30 22:51   ` Philip Oakley
2019-01-30 23:13     ` Christian Couder
2019-01-30 23:07 ` Jeff King
2019-02-02 12:33   ` Jakub Narebski [this message]
2019-02-04 19:30     ` Elijah Newren
2019-04-23  3:45     ` Jeff King

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=86va22qsj1.fsf@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).