From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Elena Zannoni <ezannoni@gmail.com>
Subject: Re: BBB instances
Date: Mon, 26 Sep 2022 01:04:34 +0200 [thread overview]
Message-ID: <YzDegpFE4ZGFRWdP@wildebeest.org> (raw)
In-Reply-To: <aebb63ed-b1de-0d2f-ef74-67461bc044ae@gmail.com>
Hi Elena,
On Tue, Sep 20, 2022 at 02:41:06PM -0600, Elena Zannoni via Overseers wrote:
> one of the things that was discussed at Cauldron was that it would be
> good to have BBB easily available for community meetings etc. Imagine a
> group of developers want to exchange ideas about some implementation
> details, etc. If they could just jump onto a BBB room on sourceware it
> would be a cool thing to have.
>
> Any thoughts on doing something like that?
So from experience managing a jitsi server, this isn't really zero
maintenance. BBB (and jitsi) aren't really packaged software and you
must update and tweak the setup regularly because of client changes.
The best we probably could do with the current setup and technical
volunteers is setup a mumble server https://www.mumble.info/ which is
packaged and seems to mostly be zero maintenance.
But that is voice only. For video (and screen sharing) I am happy to
see various people/organisations exchanging their BBB
setup/infrastructure. We should collect all that information and see
which resources are needed and if we can find a (paid) volunteer to
set something up. Creating a clear plan of initial setup cost,
server/bandwidth costs and periodic maintenance costs. The SFC can
then help us setup a crowdfunding campaign for that.
Looking at some of the projects that are already using video chats
(valgrind has a developer chat every couple of months, gccrs a monthly
one, both on meet.jit.si, and glibc has a weekly patch review session
on some proprietary system and the SFC video chats). I would say that
initially we would just need to support one or two simultanious
sessions of 6 till 12 participants (with often just up to 4 using
video at the same time). It would be nice to be able to scale up a
bit. But I think we should not try to make it scale to something
conference size.
Cheers,
Mark
prev parent reply other threads:[~2022-09-25 23:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 20:41 Elena Zannoni
2022-09-21 3:23 ` Ian Kelling
2022-09-21 19:47 ` Bradley M. Kuhn
2022-09-22 19:27 ` Elena Zannoni
2022-09-22 22:23 ` Denver Gingerich
2022-09-23 0:03 ` Ian Kelling
2022-09-25 23:04 ` Mark Wielaard [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=YzDegpFE4ZGFRWdP@wildebeest.org \
--to=mark@klomp.org \
--cc=ezannoni@gmail.com \
--cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).