# Evolution 3 - Migrate the membership
**URL:** https://forum.meet.coop/t/evolution-3-migrate-the-membership/1295
**Category:** Strategy
**Tags:** time-deliberating, community-circle, social-relations, evolution
**Created:** [11 February 2023 19:00 UTC](https://forum.meet.coop/t/evolution-3-migrate-the-membership/1295 "2023-02-11T19:00:16Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@mikemh](https://forum.meet.coop/u/mikemh)
#### Post date: [11 February 2023 19:00 UTC](https://forum.meet.coop/t/evolution-3-migrate-the-membership/1295/1 "2023-02-11T19:00:16Z")
The third thread of the evolution project is to migrate meet. coop’s members safely and transparently to another multistakeholder coop, maintaining and developing the social relations of digital commons. This thread below contains the brief, job list, actions log and discussion.
Background and overall project notes are here [Evolution of meet.coop - Background and framework](https://forum.meet.coop/t/evolution-of-meet-coop-background-and-framework/1292/). This thread has parallel threads:
- [Evolution 1 - Find a new home](https://forum.meet.coop/t/evolution-1-find-a-new-home/1293)
- [Evolution 2 - Migrate the platform](https://forum.meet.coop/t/evolution-2-migrate-the-platform/1294)
- [Evolution 4 - Do the learning, evolve the legacy](https://forum.meet.coop/t/evolution-4-do-the-learning-evolve-the-legacy/1296)
It has a sub-thread:
- [Evolution #3 - Migrate membership. Voice of the commons community(ies)](https://forum.meet.coop/t/evolution-3-migrate-membership-voice-of-the-commons-community-ies/1331/)
---
### Author:  [@mikemh](https://forum.meet.coop/u/mikemh)
#### Post date: [11 February 2023 19:03 UTC](https://forum.meet.coop/t/evolution-3-migrate-the-membership/1295/2 "2023-02-11T19:03:54Z")
### Brief - Migrate the membership
As a multistakeholder federation of coops in the digital media sector, and a commons of digital capability, meet. coop aims to facilitate the formaciòn and prefigurative capability of activist movements and groups in the coop-commons economy, the solidarity economy and civil-society rank-&-file organising. Thus, in a major evolutionary step like the present one, there is a need to:
- **Engage members** in an open way (through the forum) for comment, insight and the identification of productive steps that might be taken.
Specifically there is a need to:
- Engage **multi-user members** - organisations that are themselves organising and facilitating communities of practice, and relying on our platform as an element of this practice.
To respect the trust that members are placing in meet. coop we need to:
- Transparently migrate member **subscriptions** to a new coop host organisation; and/or give clear pointers to alternative platform coops with similar ethics and service provisions.
To guarantee our service to members during the transition, when Tech circle hours will be needed to engage with platform-transition tasks, we need to:
- **Freeze the service** at ‘plain vanilla rooms’ in BigBlueButton (no ‘specials’ like streaming services, event servers). - `Done: as of now.`
To ensure that the privacy of our members is preserved and the continuity of their practice is ensured, we need to:
- Make a plan for data privacy through the migration, and into the platform regime of the new host organisation. This includes:
- Safely and securely migrate **members’ account data**
- Safely and securely migrate **members’ files** held in Greenlight (ie, recordings of meetings).
---
### Author:  [@mikemh](https://forum.meet.coop/u/mikemh)
#### Post date: [11 February 2023 19:05 UTC](https://forum.meet.coop/t/evolution-3-migrate-the-membership/1295/3 "2023-02-11T19:05:19Z")
### Migrate the membership - job list
- Write a brief - **above**
- Open job list & logbook - **here!**
- Open public forum thread - **here!**
- Publish & discuss @ forum - started 06feb2023, **here**
-
- Freeze the service @ plain vanilla rooms - as of **now**
- Engage members @ forum
- Engage multi-user members @ forum
- Make a plan for **data privacy** through the migration, and into the platform regime of the new host organisation.
-
- Transparently migrate member subscriptions to a new coop host organisation; and/or give clear pointers to alternative platform coops with similar ethics and service provisions.
- Safely and securely migrate members’ account data
- Safely and securely migrate members’ files held in Greenlight (ie, recordings of meetings).
---
### Author:  [@mikemh](https://forum.meet.coop/u/mikemh)
#### Post date: [4 April 2023 11:14 UTC](https://forum.meet.coop/t/evolution-3-migrate-the-membership/1295/4 "2023-04-04T11:14:27Z")
The four following posts are updates following the mar21st meeting of meet. coop & WebTV [@evolution](https://forum.meet.coop/groups/evolution) @gcotnoir
---
### Author:  [@mikemh](https://forum.meet.coop/u/mikemh)
#### Post date: [5 April 2023 17:43 UTC](https://forum.meet.coop/t/evolution-3-migrate-the-membership/1295/5 "2023-04-05T17:43:18Z")
### Members’ voice
- WebTV can’t add [meet.coop](http://meet.coop) members as members (this conflicts with the articles of WebTV, Montreal coop laws). @gcotnoir to send links to relevant docs, so [meet.coop](http://meet.coop) understands the WebTV legal form better?
- [meet.coop](http://meet.coop) **user members** not seen as just customers. Gabriel ([playback](https://bbb.ca.meet.coop/playback/presentation/2.3/d09801c6bf7dc38751a9c0a8476efcc9e7afbbb4-1679419147426): around 28-40min ) believes it’s important that members of [meet.coop](http://meet.coop) have a voice in how the platform they use is run and evolved. There are questions about what this would look like legally (coop form, coop governance); can think more about this and find a arrangement down the road. What entity would they be members of? See [Evolution #1 - meet.coop Board & WebTV board Define the relationship - #3 by mikemh](https://forum.meet.coop/t/evolution-1-meet-coop-board-webtv-board-define-the-relationship/1330/3).
---
### Author:  [@mikemh](https://forum.meet.coop/u/mikemh)
#### Post date: [5 April 2023 17:46 UTC](https://forum.meet.coop/t/evolution-3-migrate-the-membership/1295/6 "2023-04-05T17:46:43Z")
## Coop front-end - User-member relationships
- WebTV will hire someone to handle **user-member relationships** ; they would work partly on WebTV work and partly on [meet.coop](http://meet.coop). But in the medium term. This is not immediately required, short term.
- Is this role equivalent to [meet.coop](http://meet.coop) Product circle lead? No need to rush into defining and recruiting this. **Priority** short-term is migrate the platform smoothly without interruption of service. If people who are using the service now can continue; this is the most important piece.
- Move from contact@ email to WebTV **ticketing system** for faults. [meet.coop](http://meet.coop) can continue to monitor low level of contact@ traffic on service level enquiries, OC enquiries. etc. Who? @wouter ? A person (not Gabriel) in WebTV (with [meet.coop](http://meet.coop) support)? @gcotnoir to set up ticketing.
- Redirect tech **help enquiries** to WebTV ticketing channel. [meet.coop](http://meet.coop) website : @melissamcnab @wouter
- Accept membership/account enquiries in the forum instead of thro email? Or better, retain old contact@ email for these? **To be explored.**
- Open conversation with someone in WebTV who handles membership relations? @mikemh @gcotnoir
---
### Author:  [@mikemh](https://forum.meet.coop/u/mikemh)
#### Post date: [5 April 2023 17:51 UTC](https://forum.meet.coop/t/evolution-3-migrate-the-membership/1295/7 "2023-04-05T17:51:35Z")
### Cash flows
- [meet.coop](http://meet.coop) members (individuals and organisations) will not directly be members of WebTV. So their **subscriptions** will not as such be WebTV subscriptions. [meet.coop](http://meet.coop) collects subscriptions thro OpenCollective, with Platform6 (Graham) as fiscal host.
- Gabriel isn’t too familiar with OC; so need to get a better sense of how the system works.
- [meet.coop](http://meet.coop) should assemble the **financial numbers** for current subscriptions and outgoings (server rental etc). @mikemh pick this up, with @wouter `Done` [Meetcoop\_financial\_summary Q1 2023.pdf - Nextcloud](https://cloud.meet.coop/s/kWczRkr3ZdSDBKT)
- WebTV could set up its own OC account as **fiscal host** , then the [meet.coop](http://meet.coop) collective could be migrated to that. Then subscriptions could be drawn down directly and transparently into WebTV bank account. A pretty simple transition.
- All the subscription income to flow to WebTV, for platform hosting, users’ tech support, front-end worker? Except: server rentals paid direct from OC as currently? Maybe some income reserved for [meet.coop](http://meet.coop) activity (eg stipend for an ‘ops team’ to field incoming enquiries, outside of WebTV tech support scope)? **To be decided** : [@Stewards](https://forum.meet.coop/groups/stewards) .
- At some point before long, open a conversation between **WebTV accountant @gcotnoir , Platform6 @Graham , [@evolution](https://forum.meet.coop/groups/evolution) team.**
---
### Author:  [@mikemh](https://forum.meet.coop/u/mikemh)
#### Post date: [5 April 2023 18:02 UTC](https://forum.meet.coop/t/evolution-3-migrate-the-membership/1295/8 "2023-04-05T18:02:45Z")
### The front-end toolstack - Members’ services
- Might [meet.coop](http://meet.coop) members have access to **other services** in addition to BBB? For example, within the WebTV Visioweb package, there is Jitsi. In the WebTV Nuage package there is the NextCloud toolstack. Two aspects:
- Might a [meet.coop](http://meet.coop) BBB subscription be supplemented by a user member, giving access to **other services**? At what additional cost? Carried by individual members or by [meet.coop](http://meet.coop)? (_Note: a parallel example: in [social.coop](http://social.coop), members get Mastodon as core, plus for free they can choose to have BBB - which is provided by [meet.coop](http://meet.coop) to [social.coop](http://social.coop), via a multi-user account paid for by [social.coop](http://social.coop))_. **To be explored**
- Will WebTV adopt the meet. coop **SSO** regime? @gcotnoir [Evolution #2 - Migrate the platform. SSO, privacy - #3 by mikemh](https://forum.meet.coop/t/evolution-2-migrate-the-platform-sso-privacy/1334/3)