Taking a quick look, this should be able to run without issue on any distribution. They're using Docker to run all the components. No Ubuntu-specific dependencies.
It is more oriented to teaching, so it's more classroom style: there is a main presenter and many listeners, it had a whiteboard, things like these. It's quite feature-packed, while Jitsi is maybe more minimal.
This seems interesting, but the fact that the officially supported distro is still Ubuntu 16.04 is alarming. There is no good excuse for actively developed software to require an outdated operating system.
I get that it's a LTS platform, but so is 18.04. 16.04 only has ~1 year of support left, so deploying infrastructure on it now is idiotic.
At this point they should at least be recommending 18.04 and should be testing on betas of 20.04 while considering compatibility issues to be high priority.
Seems like a set of ~8 or something core contributors working on this open source project. You talk about it like it's a professional product. Ubuntu 16.04 is still everywhere and I'm sure they have their reasons for not having time to deploy on multiple platforms / architectures / beta lines in order to test changes.
I think you best shot at fixing this problem that has "no good excuse" and using it would be "idiotic" would be to contribute yourself. The least you can do is open a thoughtful issue asking the same things you asked here, but in a way better tone. Even better would be to contribute code but eh, Java.
Edit: another comment in this thread: "That readme is 17months old. and the reference to 16.04 is atleast 3 years old. So it may just not have been properly updated." https://news.ycombinator.com/item?id=22611533
> Why does an open source project has to be mutually exclusive to being a professional product?
It doesn't, there are plenty of open source professional products. This doesn't seem to be one of them though, as I would expect a company with for-profit motives behind it if that's the case. This seems to be a project that is merely supported by a company to support the development, which is also fine.
You don't have to use it, but your criticism is excessive. As a casual bystander providing nothing but commentary, you really don't get to choose the priorities and schedule of an open source project.
That's right. Although I tried to setup self hosted both BBB and Jitsi Meet, and was not rally satisfied. Both had quite some problems with audio and video streams, which either didn't start or froze later. I think that both software are better than I could setup, because I've seen them working pretty good, but I'm not sure what is the secret ingredient.
The secret sauce in jitsi is NAT traversal so make sure you don’t have an overzealous firewall on the hosting server. Second it relies on google STUN servers, changing to different servers or using ips instead of dns may help fix problems on the client end.
Jitsi is amazing when setup properly (I have some deploy scripts somewhere out there, Jitsi is not truely open source as it seems)
Do you have some link to documentation explaining how to setup/debug this kind of things? I tried to deploy Jitsi Meet on a EC2 instance with all access permitted, but it still had quite a few problems. Did not try to tinker with STUN, though.
It's quite great ! It supports audio and video and is quite reactive for us.