From: Ian Kelling <iank@fsf.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: "Bradley M. Kuhn" <bkuhn@sfconservancy.org>
Subject: Re: BBB instances
Date: Thu, 22 Sep 2022 20:03:43 -0400 [thread overview]
Message-ID: <87pmfm993a.fsf@fsf.org> (raw)
In-Reply-To: <87bkr8jyqg.fsf@ebb.org>
FSF is working on helping BBB to move databases. In hindsight, my post
was off-hand and alarmist, and partly plain wrong: I assumed that a free
version of mongo wouldn't work with the latest BBB. After posting, I
actually tested it, and the latest version of BBB (2.5) actually can be
used with a free version of mongodb, (i tried 3.6, which I think is fine
to run for many years from now, even if it is in an older distro
chroot). Thank you to Bradley and SFC for documenting the freedom fix
for BBB 2.3 ( https://k.sfconservancy.org/conservancy-bigbluebutton ). I
note that BBB 2.3 still has an indefinite support timeline, so it is a
fine version to use. I'll be working on getting that and the BBB 2.5
freedom fix upstreamed. As Bradley suggested, if you know about this
issue, BBB is fine. At FSF, we evaluated Jitsi a few years ago and found
BBB to be more reliable, a bit more scalable, and have more features
geared toward presentations and teaching, and we plan to keep using it
including for LibrePlanet 2023.
With my personal FSF sysadmin hat on, I look forward to more and ongoing
collaboration with Sourceware and SFC.
--
Ian Kelling | Senior Systems Administrator, Free Software Foundation
GPG Key: B125 F60B 7B28 7FF6 A2B7 DF8F 170A F0E2 9542 95DF
https://fsf.org | https://gnu.org
next prev parent reply other threads:[~2022-09-23 1:24 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 [this message]
2022-09-25 23:04 ` Mark Wielaard
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=87pmfm993a.fsf@fsf.org \
--to=iank@fsf.org \
--cc=bkuhn@sfconservancy.org \
--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).