I think the time has come to get together to have come sort of community get together. It’s clear that me, Nick (another freelancer friend of mine) and @Graham aren’t able to do everything we would like to move beyond the bad situation ( Meet.coop update October 2025 - #58 by kawaiipunk ). The attempt to rescue the meet.coop infrastructure has progressed a lot but over the months we have hit massive road blocks.
I’d be happy to host an open call on the new de.meet.coop server for anyone who is interested to drop in and ask questions and generate some fresh ideas.
One area we need help with is communicating with the members and also visioning how to get some skeleton structure together to make decisions about meet.coop once the crisis has abided. Currently it’s just me and @Graham making decisions and we want to be accountable to our community for this and also facilitate more of a collective decision making process when it is appropriate.
@mikemh was also chatting about this in the Matrix chat.
One thing I want to propose is we spend a bit more money to get ourselves to a really spot. We really need someone to triage support emails and do member comms. It’s really affected the technical work.
Obviously it’s not something we can propose without widespread member consensus and checking in with folks who are already doing a bit of that work.
I picture meet.coop continuing with some of the more mundane work of maintenance and implementation being handled by paid members leaving the other members to focus on the decision making. Obviously I would say this as I’m from a worker co-op background!! So really interested to know what others think.
My own sense is that the sysadmin tangles are bing sorted by @kawaiipunk (Autonomic and Tech Care) and Nick. Hero of meet. coop combat medals to you. The SSO server might be the last outpost: Koumbit is implicated there. Welcome contributions also from @anarcat (Tor and Koumbit) @Graham (pivotal meet. coop member-facing role), @chris (really appreciate WebArchitects hanging in here ) @elon (likewise Hypha at the last minute) and @wouter . Issues - and hard paid labour - remain, to retrieve old recordings. But it can be possible. Friends of meet. coop, thank you It was and remains a federation.
Some members have been lost. Tor has migrated elsewhere (but @anarcat is hanging in here ). femProcomuns/commonsCloud @Dvdgmz David Jacovskis have set up a local BBB service in Catalunia but remain in the community. Their rationale for localising the service needs to be kept in mind. The rationale for an international BBB service now may not be the same as it was in the pandemic. Some communities are happy with jitsi (and meet. coop fell back on jitsi during the recent distrurbance). Serving language communities is one rationale among others to be considered; also local network latency, community participation, attack surface & dependency of a centralised service, and digital sovereignty (including US vs Europe hot issues). So its a good time to take stock?
I propose we should convene a General Assembly. But only after the tech crew feels the admin is stable - which I assume could be during February (@kawaiipunk ?). Meanwhile, tech coordination to be pursued in other threads and channels (like the meet. coop general matrix room).
There may be changed possibilities of hosting a ca server with webTV @gcotnoir , even though the v2.0 arrangements came apart. Perhaps a core item on an agenda might be: are we looking at meet. coop v2.2 ish, with updated front-end and back end teams? Or maybe even v3.0 with altered geography, rationale and user-membership scope, five years on?
I’m willing to co-convene such an assembly. Together with @Graham who has access to the current membership contacts details and holds the role for membership communications, @kawaiipunk who has been nursing the tech and @wouter who also has some front-end and back-end access privileges left over from meet. coop v1.0. With an agenda assembled I’d be willing to host the call, since I’m less implicated in tech or membership matters than the above-named and would have less need to speak in the gathering.
We never had a General Assembly. The prototype Board of Stewards has dissipated (but should be called on - @otisyves (Remix) was in the forum not that long ago, I imagine social. coop @mnoyes would have an interest, @anarcat (Tor) is in the flow already ) . How do we vote for an Assembly? Votes here in this forum?
Please respond; regarding whether as Assembly is appropriate, and what the protocols should be for convening one now. Transparency! Federation! Everything in the commons!
Thanks @kawaiipunk for the great nursing and caring of the tech and the community, much needed! @mike sums it up very well. (Small note: David J isn’t working at femProcomuns anymore.)
I think a General Assembly would be best - following a consent-based methodology, and when serious decisions are proposed, then we should make a proposal in the forum and call for people to participate in such decision.
I say this because the current formal membership is certainly precarious, and all of us here willing to participate should be very much valued, until a more mature cooperative community model can be in place. What do others think of that from a governance PoV?
Two weeks becoming three weeks - this is going nowhere fast @Graham please come in. Are you up for a community meeting - an Assembly even? At least a ‘Board + Ops + concerned users’ meeting.
@mikemh I think let’s just organise it! Shall we post a poll for a few evenings first week of March and see if we can get some takers. I think at this point any type of community engagement would be great. I’m feel so burnt out from this work.
Hi. I’m happy to organise a meeting of interested parties. I’ve held off doing that until now because a) I wanted to be clear about the current state of play regarding the work underway to update servers and what was blocking that from happening in a timely manner, and b) because I’ve been very busy elsewhere, both with client work and dealing with a family bereavement, and not able to give sufficient time to meet.coop matters.
What is clear is that a major blocker of progress continues to be the lack of access to - in particular the keycloak server. Despite months of requests for assistance aimed at people and orgs that we think were actively involved in the early days of the project, it has thus far proved impossible to get hold of access credentials. This in turn speaks to poor practice when these developers departed the project, effectively leaving those of us who are working to try to maintain and grow the service, with a ticking bomb.
I propose that we meet at 1400 UTC on March 13. I’ll share a link for that call in due course.
The SSO server might be the last outpost: Koumbit is implicated there. Welcome contributions also from 
). femProcomuns/commonsCloud 