From: wkt at tuhs.org (Warren Toomey)
Subject: [COFF] [TUHS] Also, a video service
Date: Sun, 9 Feb 2020 12:02:46 +1000 [thread overview]
Message-ID: <20200209020246.GA19979@minnie.tuhs.org> (raw)
In-Reply-To: <20200209004854.GB7353@minnie.tuhs.org>
On Sun, Feb 09, 2020 at 10:48:54AM +1000, Warren Toomey wrote:
> All, I've also set this up to try out for the video chats:
> https://meet.tuhs.org/COFF
> I just want to test it to confirm that it works.
It works, thanks to the four or five who popped in to test it.
I'm thinking of a weekly rotation through these timezones:
UTC Brisbane New Jersey
Week 1: 8am 6pm 3am
Week 2: 1pm 11pm 8am
Week 3: 10pm 8am 5pm
We'd need a volunteer from each timezone to start up the channel
and to (try to) keep some order. Any takers?
Cheers, Warren
next prev parent reply other threads:[~2020-02-09 2:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 0:48 [COFF] " wkt
2020-02-09 2:02 ` wkt [this message]
2020-02-09 22:56 ` grog
2020-02-09 23:21 ` [COFF] [TUHS] " bakul
2020-02-10 3:35 ` wobblygong
2020-02-13 23:41 ` [COFF] jitsi on FreeBSD (was: Also, a video service) grog
[not found] ` <alpine.LRH.2.22.394.2002092151450.22679@waffle.shalott.net>
2020-02-13 23:43 ` [COFF] Video service " grog
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=20200209020246.GA19979@minnie.tuhs.org \
--to=coff@minnie.tuhs.org \
/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).