# Evolution of meet.coop - Background and framework

**URL:** https://forum.meet.coop/t/evolution-of-meet-coop-background-and-framework/1292
**Category:** Strategy
**Tags:** time-deliberating, community-circle, platform-space, social-relations, evolution
**Created:** [11 February 2023 12:04 UTC](https://forum.meet.coop/t/evolution-of-meet-coop-background-and-framework/1292 "2023-02-11T12:04:18Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![mikemh](https://forum.meet.coop/user_avatar/forum.meet.coop/mikemh/32/358_2.png) [@mikemh](https://forum.meet.coop/u/mikemh)
#### Post date: [11 February 2023 12:32 UTC](https://forum.meet.coop/t/evolution-of-meet-coop-background-and-framework/1292/3 "2023-02-11T12:32:49Z")

</div>

## Summary of decisions, special All-hands & Board meeting, 02feb2023

- **Decision:** no participant is against the rationale of folding [meet.coop](http://meet.coop/) as it is.
- **Decision:** accumulate some explicit learning. Many people have an interest in what our project has been, and what has worked.
- **Decision** : Collocal absorbing our members and taking over platform ops is a fallback option, not the preferred option. We should notify [@hng](https://forum.meet.coop/u/hng) .
- Migrate platform ops and member base to another multi-stakeholder co-op **with its own strong community** , member-facing front-end and subscription machinery: Commonscloud/femProcomuns, MayFirst, [social.coop](http://social.coop/). **Decision** : This is the option we prefer. Much of the discussion was around [social.coop](http://social.coop/), as a new home for the platform operation and for our members.
- We have a **decision** on freezing our service commitments, providing plain vanilla rooms from now onwards, no more event servers or other ‘special’ services. [@dvdjaco](https://forum.meet.coop/u/dvdjaco) [@Yurko](https://forum.meet.coop/u/yurko)
- Also **decision** to create 1-page documentation of the tech operations aspect, to share with [social.coop](http://social.coop/) tech team (and publicly, thro the forum). [@andia](https://forum.meet.coop/u/andia) [@dvdjaco](https://forum.meet.coop/u/dvdjaco)
- Also **decision** by [@mnoyes](https://forum.meet.coop/u/mnoyes) , to raise within [social.coop](http://social.coop/) the matter of platform-transfer and member-transfer to [social.coop](http://social.coop/) (when the documentation above is to-hand).
- 6 months should be the max time to complete a transition, 2-3 months max to decide. We should start with the tech team at the host organisation, which will be faster, and if they give a green light then we would be looking at a 6-8 month decision time after that. Meanwhile we could include the [social.coop](http://social.coop/) tech team as [meet.coop](http://meet.coop/) volunteers. **Agreed**.
- We can **meet again** in march and see how things are going. March review - run a vote @ forum. Go/no-go with [social.coop](http://social.coop/) (Collocall as fallback).
- What about the **money** we have now in the bank, can we use that to pay a decent salary for the time remaining? We can postpone that decision until the next meeting in march, there has been a lot of unpaid work in meetcoop, let’s all think about this.
- **Timing Decisions:**
  - not running on for months indefinitely. Six months OUTSIDE to complete the transition. Tech transition itself takes some time. so - the decision/negotiation should be three months max
  - the ‘social’ timeline in a recipient coop could be 6-8 months?
  - minimal service now, and thro transition
  - invite tech team @ [social.coop](http://social.coop/) as voluntreers in [meet.coop](http://meet.coop/) tech circle

- **timeline more decisions:**
  - Month 1 - communicate statement to all users, invite them for a short process of discussion in the forum with a decision about the path forward
  - write 1 pager
  - approach SC Tech WG- [social.coop](http://social.coop/) tech team will be YES/NO pretty fast ![]()
  - publish @ OpenCollective
  - open thread(s) @ forum

- **Crash team,** to see this through - who? Decision: [@mikemh](https://forum.meet.coop/u/mikemh) [@mnoyes](https://forum.meet.coop/u/mnoyes) ([social.coop](http://social.coop/)) [@dvdjaco](https://forum.meet.coop/u/dvdjaco) (SHORT discussions, tech style 😉), [@Graham](https://forum.meet.coop/u/graham) (work w members), [@andia](https://forum.meet.coop/u/andia) (comms incl 1-pager). **Action mh** : open a DM thread in forum

---

_[View the full topic](https://forum.meet.coop/t/evolution-of-meet-coop-background-and-framework/1292)._