From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: [NTG-context] regular online meet-up
Date: Fri, 9 Jun 2023 13:29:40 +0200 [thread overview]
Message-ID: <dd47796b-f77b-9ef4-58f2-7a11dd11c4e3@fiee.net> (raw)
You’re invited to join on Wednesday, June 14th, 15:00 CEST (UTC+2)
at https://lecture.senfcall.de/hen-rbr-rku-oke
(same, but shorter: https://v34h.de/ctxmtg)
ConTeXt users of all levels are welcome!
Next meeting will be on July 12th.
(Same blurb as every time:)
[Howto]
* No special software installation required; most modern browsers should
work (WebRTC required).
* Open the above URL, accept the privacy statement,
* enter your name,
* click "join" (or "start" if you’re the first),
* click "with microphone", allow your browser to access it, check the audio.
* Your microphone is muted if you join. Activate microphone and/or
camera with the buttons at the bottom.
* Minimize the default presentation with the "screen" button, bottom right.
* If you’d like to share your screen or upload a file, you can make
yourself the presenter: Click on your user name, change the setting,
then you’ll see the "screen sharing" button beside the camera button;
also there’s now "manage presentations" behind the "plus" button.
Beware there is only one presenter at a time, so don’t kill someone
else’s presentation.
[Technical hints]
* Sound is usually better if you use a headset (less noise for everyone).
* Connection problems are mostly due to low bandwidth or high latency on
your side, e.g. with mobile connections.
* If audio/video doesn’t work for you, you can still use the text chat.
* Screen sharing needs a lot of bandwidth.
* BigBlueButton documentation applies:
https://bigbluebutton.org/teachers/tutorials/
[Netiquette]
* Please use a name that we recognize from here. Some feel uncomfortable
with anonymous lurkers.
* Mute your microphone while you’re not talking.
* It’s nice to show your face at least when you join.
* If there are connection problems, stop camera sharing.
* The room is set to “everyone’s a moderator“, I trust you...
See you, 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
___________________________________________________________________________________
next reply other threads:[~2023-06-09 11:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 11:29 Henning Hraban Ramm via ntg-context [this message]
2023-06-14 9:18 ` Henning Hraban Ramm via ntg-context
-- strict thread matches above, loose matches on Subject: below --
2024-04-07 7:37 Henning Hraban Ramm
2024-03-10 20:51 Henning Hraban Ramm
2024-02-10 22:01 Henning Hraban Ramm
2024-01-06 17:25 Henning Hraban Ramm
2023-12-11 9:49 Henning Hraban Ramm
2023-08-07 10:49 Henning Hraban Ramm
2023-05-07 9:44 Henning Hraban Ramm via ntg-context
2023-05-10 11:00 ` Henning Hraban Ramm via ntg-context
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=dd47796b-f77b-9ef4-58f2-7a11dd11c4e3@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).