Test Run for new W3C CCG Meeting System


We're getting very close to a new operational CCG Meeting System (with
video conferencing / screen sharing / high definition audio/video).

You can think of it as a cross between Zoom and the current CCG meeting
system. It's all open source + open standards-based while also being
compliant with accessibility and W3C Intellectual Property Release and
Recording requirements. When fully operational, it will allow us to do
everything we can do with our existing system in addition to some of the
more modern things we've come to expect (like high definition audio,
video, and screen sharing).

It's close enough to take it for a test run at this point. So, as the
W3C CCG Chairs announced earlier today, we're going to do just that
during a W3C CCG after-hours call tomorrow.

Here's what is working so far with the new W3C CCG Meeting System:

1. Connecting via the Web: https://meet.w3c-ccg.org/weekly
2. Connecting via phone.
3. Web Chat (XMPP) <-> IRC bridging.
3. Rewritten ccgbot (manages queue, connections, etc.):
4. Logging to log file, automatically accessible at all times.
5. HD Audio and screen sharing (up to HD 720p).
6. Bot autojoin/leave (fully automated, meeting admins don't have to run
   commands to get the bot to join or leave).
7. Unlimited ad-hoc meeting rooms (without bot/recording).
8. Two W3C Process managed meeting rooms (CCG weekly call, and CCG did-
   resolution call) with ability to add more via simple config file.
   VCEDU room on the way!
9. Admin interface (all rooms required a person trusted by the CCG to
   start the conference).
10. Fully open source / open standards running on infrastructure that
    this group controls.

What isn't working (yet):

1. Automatic screen recording and audio recording. It's halfway there
   and we probably shouldn't switch the regular calls over until it's in
2. Automatic transcription -- haven't tried yet... this is the dream,
   no more fallible human scribes, only the cold unfeeling transcription
   of an artificial neural network. We don't need this to switch over,
   but it's on the road map.
3. SIP dial-in -- don't know if we even want this now. All the
   backchannel communication is done via SIP, so it's doable, just
   need to put some time in to make it work. We don't need this to
   switch over.
4. Fully automated minute publishing and management to save Kim from
   having to manually publish each and every meeting we have.

So, the questions then become, do we want to move over to this new
system? Are the switching costs worth it? How much maintenance are we
expecting to have to put into this system? What is our backup plan?

In order to answer some of those questions, we need to test under load
to see if it will work for our weekly calls. We expect there to be bugs,
but nothing that can't be fixed fairly quickly.

If you have the time, please join us tomorrow to test out the system and
gather feedback from the W3C CCG community. :)

-- manu

Manu Sporny - https://www.linkedin.com/in/manusporny/
Founder/CEO - Digital Bazaar, Inc.
blog: Veres One Decentralized Identifier Blockchain Launches

Received on Tuesday, 4 August 2020 02:50:57 UTC