Difference between revisions of "Meeting Minutes/04-22-2020"
Jump to navigation
Jump to search
AlphaCubed (talk | contribs) (Created page with "3 officers came to the meeting. 2 showed interest but could not come due to academic reasons, which is now marked as attendance. The meeting "started" at 7:30pm. We did some...") |
AlphaCubed (talk | contribs) |
||
| Line 17: | Line 17: | ||
* The desktop app for Jitsi Meet is on [https://github.com/jitsi/jitsi-meet-electron/releases GitHub] (their website gave an IM messaging app which is confusing, we do not recommend using that) | * The desktop app for Jitsi Meet is on [https://github.com/jitsi/jitsi-meet-electron/releases GitHub] (their website gave an IM messaging app which is confusing, we do not recommend using that) | ||
* The screen sharing component runs at about ~3fps which is doable for presentations but not optimal. | * The screen sharing component runs at about ~3fps which is doable for presentations but not optimal. | ||
* Some alternative solutions to fix this problem: | * Some alternative solutions to fix this slow screen sharing problem: | ||
** use a [https://github.com/jitsi/jitsi-meet/wiki/Jitsi-Meet-Instances separate Jitsi Meet instance] which has less traffic than the primary meet.jit.si instance | ** use a [https://github.com/jitsi/jitsi-meet/wiki/Jitsi-Meet-Instances separate Jitsi Meet instance] which has less traffic than the primary meet.jit.si instance | ||
** run our own Jitsi Meet servers, maybe off of someone's Raspberry Pi or actual server hardware if they are willing to volunteer | ** run our own Jitsi Meet servers, maybe off of someone's Raspberry Pi or actual server hardware if they are willing to volunteer | ||
** or use [http://demo.bigbluebutton.org/ BigBlueButton] which has a 60min meeting limit if we don't run it on our own servers | ** or use [http://demo.bigbluebutton.org/ BigBlueButton] which has a 60min meeting limit if we don't run it on our own servers | ||
Latest revision as of 15:27, 22 April 2020
3 officers came to the meeting. 2 showed interest but could not come due to academic reasons, which is now marked as attendance.
The meeting "started" at 7:30pm.
We did some configuration on the BungeeCord part of our Minecraft server and added the Advanced Portals plugin.
We picked a world for the lobby part of our Minecraft server.
We talked about replacing the aging/failing HP servers with a NAS server (probably for OwnCloud?) and using a SATA connector for the hard drives.
- He plans to build a server himself with parts (kind of like building a custom PC) instead of getting one pre-built.
- Nick got an 8TB HDD which used SATA instead of SAS.
- He got an AMD server CPU (I forget the model) and plans to get a second CPU later. The motherboard has 2 SATA lanes (instead of 4 which is typical) but a lot of PCIe slots (which itself is typical).
We "ended" it at 10pm cause we were gettin tired.
Some stuff about Jitsi Meet:
- The desktop app for Jitsi Meet is on GitHub (their website gave an IM messaging app which is confusing, we do not recommend using that)
- The screen sharing component runs at about ~3fps which is doable for presentations but not optimal.
- Some alternative solutions to fix this slow screen sharing problem:
- use a separate Jitsi Meet instance which has less traffic than the primary meet.jit.si instance
- run our own Jitsi Meet servers, maybe off of someone's Raspberry Pi or actual server hardware if they are willing to volunteer
- or use BigBlueButton which has a 60min meeting limit if we don't run it on our own servers