From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id CE84B3858CDA for ; Sun, 25 Sep 2022 23:04:35 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org CE84B3858CDA Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org Received: from reform (deer0x0b.wildebeest.org [172.31.17.141]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 521EB3000B37; Mon, 26 Sep 2022 01:04:34 +0200 (CEST) Received: by reform (Postfix, from userid 1000) id 18AED2E820D2; Mon, 26 Sep 2022 01:04:34 +0200 (CEST) Date: Mon, 26 Sep 2022 01:04:34 +0200 From: Mark Wielaard To: Overseers mailing list Cc: Elena Zannoni Subject: Re: BBB instances Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,KAM_INFOUSMEBIZ,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: 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