ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Re:  ConTeXt meeting 2022 – please register!
Date: Thu, 4 Aug 2022 14:59:54 +0200	[thread overview]
Message-ID: <36b23740-6621-70c1-8850-78c809bf93b8@fiee.net> (raw)
In-Reply-To: <8a4c9101-4c87-89fc-90c6-5ec59e1c0f73@freedom.nl>

Am 04.08.22 um 14:32 schrieb Hans Hagen via ntg-context:
> On 8/4/2022 10:22 AM, Max Chernoff via ntg-context wrote:
>> * The flight would take 14 hours each way (biggest reason)
>> * The flight would cost more than 2 months of rent

Understandable – I won’t ever fly overseas for a conference.

>> * It would be a bad idea for me to miss a full week of classes
> last year we experimented with some remote attendents but also decided 
> that we would only mix that wilt a real meeting with a threshold 
> attendance ... personally i will not sit behind a screen and present 
> something staring in a camera .. it simply works better with real people 
> there ... i don't know what is planned for this year wrt remote

We will do the same as last year, use BigBlueButton for sharing the 
presentation and camera & microphone for the presenter, sometimes an 
additional camera for the room or showing stuff. (No recording, no 
general room camera.)
Someone will watch the chat and relay questions.
We’ll project remote presenters to the screen and use speakers.
Discussion between local and remote participants is always a bit 
difficult, we’ll try again with microphones.

But, also like last year, we have only a household DSL connection. That 
doesn’t limit remote participants, but the locals should not use the 
system as well. I also can’t guarantee that everthings works – last year 
we had big problems with the local DHCP/router.

Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2022-08-04 12:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-31 14:02 Henning Hraban Ramm via ntg-context
2022-08-03  8:50 ` Henning Hraban Ramm via ntg-context
2022-08-04  6:48   ` juh+ntg-context--- via ntg-context
2022-08-04  7:44     ` Henning Hraban Ramm via ntg-context
2022-08-04 12:29     ` Hans Hagen via ntg-context
2022-08-04  8:22   ` Max Chernoff via ntg-context
2022-08-04 12:32     ` Hans Hagen via ntg-context
2022-08-04 12:59       ` Henning Hraban Ramm via ntg-context [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=36b23740-6621-70c1-8850-78c809bf93b8@fiee.net \
    --to=ntg-context@ntg.nl \
    --cc=texml@fiee.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.
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 NNTP newsgroup(s).