225 views
# Meet.coop discovery report ## Meetings Minutes pad: https://pad.autonomic.zone/ZEBydwP8Tgy8qV2Ynxj0Cw?both# ## Servers | Server | Domain | IP Address | Provider | OS Version | Notes | | -------- | -------- | -------- | -------- | -------- | -------- | de.meet.coop | https://de.meet.coop/ | 88.99.213.90 | [Hetzner](https://www.hetzner.com/) (Germany) | bbb.de.meet.coop | https://bbb.meet.coop | 88.99.213.96 |[Hetzner](https://www.hetzner.com/) (Germany) | | | ca.meet.coop | https://ca.meet.coop/ | 199.58.82.75 | [Koumbit](https://www.koumbit.org/en) (Canada) | bbb.ca.meet.coop | https://ca.meet.coop/ | 199.58.82.76 | [Koumbit](https://www.koumbit.org/en) (Canada) | sso.meet.coop | https://sso.meet.coop | 178.128.34.12 | [Digital Ocean](https://www.digitalocean.com/) (U.S.) ## Apps | App | Domain | Provider | Version | Access | Notes | | -------- | -------- | -------- | -------- | -------- | -------- | Wordpress | https://www.meet.coop/ | Web Architects | Debian + Wordpress 6.3.2 (insecure and also plug-in updates needed) | Debian | | Big Blue Button | https://de.meet.coop/ | Hetzner VPS | Ubuntu | | Big Blue Button | https://ca.meet.coop/ | Koumbit VPS | Ubuntu | | Nextcloud | https://nextcloud.meet.coop | Web Architects | Debian | | Discourse | https://forum.meet.coop/ | Web Architects | Debian | | OpenCollective | https://opencollective.com/meet-coop | OpenCollective/Platform Six | | Gitlab | https://opencollective.com/meet-coop | Gitlab Inc | ## Upstream Software * https://bigbluebutton.org/ * https://bigbluebutton.org/hosting/ - (we should be on this list) * https://groups.google.com/g/bigbluebutton-dev - developer mailing list * https://github.com/bigbluebutton/bigbluebutton - code forge * https://docs.bigbluebutton.org/ - upstream Docs * https://github.com/collocall/ - collocall code * https://github.com/collocall/b3scale replaces scalelite Current BBB version: https://github.com/bigbluebutton/bigbluebutton/releases ## Observations ### SSO - Wordpress, Nextcloud, Discourse all also support oauth so we could could create a seperate realm on Keycloak for meet.coop operational members and use SSO for that too. - Is OpenCollective automatically synced with Keycloak? OC do have an API that allows this: https://docs.opencollective.com/help/developers/oauth - I signed up for an account on the forum and the my account directs to https://sso.meet.coop/realms/meet.coop/account/#/, what is the intergration? ![](https://pad.autonomic.zone/uploads/eca53e3b-2a75-4167-b5fe-3702f780b5b3.png) ### Security - Wordpress needs some updates: https://bin.autonomic.zone/?38d0ad818b4e04fa#BVZiFSHnSaHEmFKh1NanSMMZcxRNw6ZdryD1Ta9JPozB - Nextcloud security looking ok: - https://scan.nextcloud.com/results/24ff46ab-e579-45c6-ba1b-e1bd97fe9e40 ![](https://pad.autonomic.zone/uploads/62774c95-276e-46ed-bb93-e1db68b15a97.png) - No 2FA on Wordpress - No 2FA on keycloak - No public docs ### Dev-ops - Big Blue Button deployed using ansible e.g. https://gitlab.com/meet.coop/ansible-role-bigbluebutton - could be complicated ### Design - Keycloak doesn't have a custom theme ### Marketing - We can user the meet.coop Connect feature to communicate with customers. Last post was Wouter on 24th October 2023. ## Questions ### Tech Can I have access to: - [ ] The servers (including sudo) - [ ] The Wordpress admin - [ ] Discourse admin - [ ] Nextcloud admin - [ ] The Keycloak admin - Are there any backups? - Unclear - Is there any monitoring? - Unclear - Are there any email deliverability checks? - Unclear - What is the status of bbb.meet.coop? - Offline, span down? ### Security - What unix users does each server have? - What admin user does each service have? - Shall we write plans/policies for applying security updates? ### Docs - Are there any docs? - Stuff in Nextcloud - Do we need a internal wiki? - Used to have Outline - Do we need a public wiki? ### Dev-ops - How is the (Wordpress) website developed? - How do you communicate with your customers? (OpenCollective does have tools for this) ### Design - Do we have a branding guide? - Do we have a repoistory of art assets? ### Finace - Is there any existing finance stratergy? ## Recomendations ### Tech - Set Wordpress to auto-update core, plug-ins and themes - Work out how a maintainence window would work - What's the update schedule? ### Security - Update all software to latest versions - Audit admin access to servers - Audit admin access to services - Investigate 2FA enforced on all admin accounts - Get some additional contractors to help with maintainence ### Privacy - Move Gitlab code to Codeberg or other ethical git forge - Migrate Digital Ocean server to Hetzner or Koumbit ### Future - Are there any other services you can offer for your existing users? Easily tied in using SSO? e.g. Owncast, Jitsi meet, Etherpad, Hedgedoc, Matrix etc. Stuff that enhances meetings. - Can SSO access be automated from OpenCollective membership ### Finance - We need to make a good finance plan - Investigate a co-op contractor for Big Blue Button and server sysadmin - 60 hours a year at 70 GBP per hour - Investigate a freelancer contractor for orga, project management, comms and a bit of tech at 50 GBP per hour. Hopefully this can be me!!! #### Budget I'm trying to work out how much it would actually cost to run this service well. Note that these numbers are all back of the envelop approximate. Estimated annual budget is currently 8295 GBP. At a rate of 70 GBP p/h that would be 4200 GBP per year for the tech co-op contractor. All updates would be taken care of. That would leave 4095 GBP for orga. This doesn't quite add up yet as it's about 1.7 hours per week which isn't enough for me and Graham. We should find a way to increase this. It might realistically need to be more like 8000 GBP on all the orga/marketing/support to really take this buisness to the next level. Anything on top of that approx estimated expenidture would be profit. There's currently 13944 GBP so with the wages costs deduced, we would still have 5649 GBP in the bank for other costs and emergencies. I haven't done the maths on the other costs yet but it's all on the OC of course. We'd have to get some more clients to start making profit which I think would happen with the right marketing plan. Obviously the overall stratergy is to spend most of the surplus by paying co-ops and co-op adjacent freelancers (moi). There's no point having loads of money beyond a sensible contingency buffer in the bank. I estimate the buffer should be about 5000 GBP which would allow the technical contractor to continue working for one year keeping everything afloat if it all went to shit. We could consider putting the prices up 10% at the end of this year as long as the members are ok with it to generate an extra 829.50 GBP per year. 15% would be 1244.25 GBP. We might have to just give it a push and see if we can make it happen. ## Actions ### Tech - Have setup a uptime monitoring public page: https://uptime.autonomic.zone/status/meetcoop (thanks Autonomic!). We can get uptime notifications sent to us if we need it or even forwarded to the Matrix channel (I would need admin privs on that to set it up). ### Comms/collaboration - I made this pad - Have reached out to Henning for best email for CollCall connection - I have joined the Matrix room and dm'd Graham - I signed up for an account on the forum - I have an account with access to the meet.coop group on the Nextcloud ## Notes > IIRC when someone signs up on OC, Keycloak does create an account for them. They then get an email telling them to reset their password and pointing them to https://www.meet.coop/getting-started/ Graham paying for all the servers - bit clunky but not a big deal German tech co-op - https://collocall.de/de Candian co-op - http://webtv.coop/ Autonomic - Outline wiki span down by Mike Hales - https://autonomic.zone/ ## TODO See: https://forum.meet.coop/t/meet-coop-update-october-2025/1739