Marketing Meet.coop

[wouter]

@chris

We will need to seek permission to provide example.meet.coop sub-domains to organisations that are co-operatives themselves, we are not be allowed to provide sub-domains to organisations that are not co-operatives, for non-cooperative organisations we would need to use a sub-domain on their existing domain or perhaps buy another domain for this, see the .Coop Third-Level Domain Policy which contains:

Maybe for simplicity we could stick to cooperatives being in charge of production, and those actors who fall outside the social and solidarity economy can only be user members. Which producer member right now is not a cooperative, but still in the SSE? Maybe Remix and Autonomous? If they really want to manage GL containers, they either co-produce them with us or do it under another domain (but that’d require maybe some more time to agree how exactly).

If we focus now on getting our service out, what do we need to agree on and get up in the air?

1. GL containers for those producer members who want to resell, like Webarchitects, possibly femProcomuns with CommonsCloud, who else wants that?
2. we need a “reseller” agreement, to define how we handle responsibilities and which part of the contribution stays at the producer coop and which part goes to the collective.
3. If we follow OSB’s proposal to have a Meet.coop account on OpenCollective, with OpenCoop as fiscal host, we could treat this as a collectively produced service (where some of us agree to share responsibility for account management), which is more centrally displayed at the meet.coop website. About the hassle of account management (I know from CommonsCloud), I think we could define routines between a few of us to handle the onboarding of the first say 100 members, until we get a decent onboarding and account management system.
4. For 3) we’d need to agree more finegrained about responsibility and sharing the proceeds. Nothing impossible IMHO.