Thanks to Collocall for offering to support this. Majorly appreciated.
My concerns are:
-
AFAIK, it is not clear who is footing the bill for the ca.meet.coop server. If we’re going to invest in keeping this server it needs to be paid for and there needs to be a timeline for how long it will be paid for as most money coming into meet.coop hinges on the idea that there will be a turn-around soon. Those expectations need to be matched up and made transparent.
-
The migration to Collocall apparently involves internal Collocall infrastructure work first (decoupling their tools from their setup) before they can make the move. That involves more work before the maintenance, upgrade and support work can happen. That is a bunch of unpaid work, until when is this sustainable for Collocall without return? That would be good make transparent because AFAIK they are using a different sytem to organise BBB (kubernetes) and that is another skill set and tooling. If in October Collocall need to pull out of the project, another migration needs to be arranged?
I’ve missed the previous discussions but I am wondering if it isn’t an idea to simply scale down, drop all the servers except ca.meet.coop (assuming it is properly funded) and then freeze the BBB version (except when critical security updates are required) and only apply system patches. Basically, a “tech freeze” with only a single server to keep an eye on until there is more capacity.
I can’t put more unpaid time into this so I am just throwing this into the mix, I hope it is helpful.