# What services can we offer from 1st July 2020?

**URL:** https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130
**Category:** Platform tools
**Tags:** tech, time-deliberating, prod
**Created:** [19 June 2020 08:56 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130 "2020-06-19T08:56:42Z")
**Posts on this page:** 20
**Page:** 3

<div class="post-metadata">

### Author: ![hng](https://forum.meet.coop/user_avatar/forum.meet.coop/hng/32/83_2.png) [@hng](https://forum.meet.coop/u/hng)
#### Post date: [13 July 2020 13:19 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130/41 "2020-07-13T13:19:51Z")

</div>

I am also not available from 15:00 to 16:00 CEST but before and after.

---

<div class="post-metadata">

### Author: ![benhylau](https://forum.meet.coop/user_avatar/forum.meet.coop/benhylau/32/12_2.png) [@benhylau](https://forum.meet.coop/u/benhylau)
#### Post date: [13 July 2020 14:42 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130/42 "2020-07-13T14:42:42Z")

</div>

Does this work for y’all?

- #product-strategy-and-services Circle
  - 11:30 - 12:30 CEST @hng @wouter @osb @chris @benhylau
  - Agenda: service levels & reseller model

- #organizational-operations Circle
  - 12:30 - 13:30 CEST @benhylau @mikemh @wouter @aaronhirtenstein
  - Agenda: membership amendments & decision making

Of course others are welcome to join, I am just listing the ppl I see who has been in these discussions.

---

<div class="post-metadata">

### Author: ![hng](https://forum.meet.coop/user_avatar/forum.meet.coop/hng/32/83_2.png) [@hng](https://forum.meet.coop/u/hng)
#### Post date: [13 July 2020 14:53 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130/43 "2020-07-13T14:53:43Z")

</div>

works for me 🙂

---

<div class="post-metadata">

### Author: ![osb](https://forum.meet.coop/letter_avatar_proxy/v4/letter/o/d9b06d/32.png) [@osb](https://forum.meet.coop/u/osb)
#### Post date: [13 July 2020 15:11 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130/44 "2020-07-13T15:11:51Z")

</div>

will try - may have to juggle / stay muted if baby can not be distracted with toys!

---

<div class="post-metadata">

### Author: ![freescholar](https://forum.meet.coop/letter_avatar_proxy/v4/letter/f/e36b37/32.png) [@freescholar](https://forum.meet.coop/u/freescholar)
#### Post date: [13 July 2020 19:58 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130/45 "2020-07-13T19:58:11Z")

</div>

> [@benhylau](#):
>
> 200€

Agaric is using an outsourced BBB for 250-300 people on a dedicated server. Things are going well, but we are hoping to move to [meet.coop](http://meet.coop) services ASAP.

---

<div class="post-metadata">

### Author: ![freescholar](https://forum.meet.coop/letter_avatar_proxy/v4/letter/f/e36b37/32.png) [@freescholar](https://forum.meet.coop/u/freescholar)
#### Post date: [13 July 2020 20:03 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130/46 "2020-07-13T20:03:07Z")

</div>

I am using WordPress as a front-end for BBB and am able to make unlimited rooms… so far. I have no GreenLight knowledge. [http://communityBridge.com](http://communityBridge.com)

---

<div class="post-metadata">

### Author: ![benhylau](https://forum.meet.coop/user_avatar/forum.meet.coop/benhylau/32/12_2.png) [@benhylau](https://forum.meet.coop/u/benhylau)
#### Post date: [13 July 2020 21:52 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130/47 "2020-07-13T21:52:19Z")

</div>

Time confirmed, same room.

---

<div class="post-metadata">

### Author: ![Yasuaki](https://forum.meet.coop/user_avatar/forum.meet.coop/yasuaki/32/14_2.png) [@Yasuaki](https://forum.meet.coop/u/Yasuaki)
#### Post date: [14 July 2020 03:53 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130/48 "2020-07-14T03:53:42Z")

</div>

I am looking forward to joining Marketing and Strategy meeting today - I want to promote meet.coop for worker coops in Japan

---

<div class="post-metadata">

### Author: ![chris](https://forum.meet.coop/user_avatar/forum.meet.coop/chris/32/3_2.png) [@chris](https://forum.meet.coop/u/chris)
#### Post date: [14 July 2020 08:17 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130/49 "2020-07-14T08:17:30Z")

</div>

> [@benhylau](#):
>
> @chris maybe you can fill [this table](https://hackmd.io/Jl0CbqhOTtKs2yDcKqtdnQ?both) so we know what that looks like before the Tues meeting?

That pad doesn’t support the `colspan` table cell attribute so I created a [draft MediaWiki prices page](https://wiki.meet.coop/wiki/Prices), I can go into some detail about some of the thinking behind this suggestion at the meeting in an hour.

---

<div class="post-metadata">

### Author: ![benhylau](https://forum.meet.coop/user_avatar/forum.meet.coop/benhylau/32/12_2.png) [@benhylau](https://forum.meet.coop/u/benhylau)
#### Post date: [14 July 2020 12:26 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130/50 "2020-07-14T12:26:07Z")

</div>

The #product-strategy-and-services circle agreed on our service level offerings, @wouter will refine the doc to be presented and hopefully adopted this Thursday.

[Meeting notes here.](https://wiki.meet.coop/w/index.php?title=14_July_2020_Product_Strategy_and_Services_-_Service_levels)

---

<div class="post-metadata">

### Author: ![petter](https://forum.meet.coop/user_avatar/forum.meet.coop/petter/32/11_2.png) [@petter](https://forum.meet.coop/u/petter)
#### Post date: [14 July 2020 12:44 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130/51 "2020-07-14T12:44:57Z")

</div>

oh I missed the new time… anyway, would be happy to join the product strategy circle from now on @benhylau !

---

<div class="post-metadata">

### Author: ![benhylau](https://forum.meet.coop/user_avatar/forum.meet.coop/benhylau/32/12_2.png) [@benhylau](https://forum.meet.coop/u/benhylau)
#### Post date: [14 July 2020 13:24 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130/52 "2020-07-14T13:24:52Z")

</div>

We definitely should set regular times asap. Hopefully we can do that this Thursday, for each Circle.

---

<div class="post-metadata">

### Author: ![wouter](https://forum.meet.coop/user_avatar/forum.meet.coop/wouter/32/318_2.png) [@wouter](https://forum.meet.coop/u/wouter)
#### Post date: [15 July 2020 10:34 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130/53 "2020-07-15T10:34:02Z")

</div>

> [@benhylau](#):
>
> The #product-strategy-and-services circle agreed on our service level offerings, @wouter will refine the doc to be presented and hopefully adopted this Thursday.
> 
> [Meeting notes here.](https://wiki.meet.coop/w/index.php?title=14_July_2020_Product_Strategy_and_Services_-_Service_levels)

I have tried to apply the details we discussed during yesterdays’ Product & Services Circle about the service levels back into the [Service Level page](https://wiki.meet.coop/wiki/Service_levels).  
issues:

- Do we want to talk about “Contribution levels” instead of Service Levels?
- What about the names for the service/contribution levels? Given that we have been changing names per tier between wiki and forum, we can appreciate there not being consensus on that yet 😉 Another possibility would be to change the naming convention altogether. In the second row in the table I’ve pot another option, where “meet10” refers to the level that allows 10 participants and “meet50” max 50 participants. Of course these service level definition will change over time and possibly also their names. In any case, what names make us happy?!
- domain names per service:
- 
  - for the core standard services (up to 50 participants) will we use `meet.coop` or `members.meet.coop` or otherwise?

- 
  - for the custom container (up to 100 participants) will we use a personalised subdomain of [meet.coop](http://meet.coop) like `"entity-name".meet.coop` or would we also allow domain names of user members? Here I think there are two perspectives: a) anything a user member wants is fine, coordinating DNS changes takes some remote support, but we’re happy to make anyone happy; b) we keep things simple, use only [meet.coop](http://meet.coop) subdomains and have a key identifier (the URL) to signal who’s providing the service - that’s great for viral marketing. Any preferences?

- 
  - The completely custom service can allow anything also custom domain names.

Please correct anything that I’ve missed.

---

<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: [15 July 2020 12:29 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130/54 "2020-07-15T12:29:13Z")

</div>

Great stuff @wouter 🙂

> will we use `meet.coop` or `members.meet.coop`

I vote `meet.coop`

> `"entity-name".meet.coop` or would we also allow domain names of user members?

I vote `entity-name.meet.coop`  
. . only [meet.coop](http://meet.coop) subdomains, signal who’s providing the service - we hope to cultivate a community of commons-co-operative-oriented usage, under a common ‘banner’ ?

> completely custom service

I would still be happy to see `meet.coop` here too, for the above reason. It’s still our infrastructure and our service. Even if it’s ‘their’ infrastructure (ie if they directly rent the server) it’s our operational labour and our collective configured capability that constitute the service.

> meet10 / meet50 etc

looks good to me

> Do we want to talk about “Contribution levels” instead of Service Levels?

I would say ‘contribution’ refers to what comes into the coop - labour, or money (funding) - and what we provide to users is ‘service’. I think we should offer **service levels** , expect and require fair-use observance of these, and invite **funding contributions** of X-plus € (with a possibility of “crowdfunding top-up”?) at fair-use level X. Emphasising the level of fair use (aka service) is important I think?

---

<div class="post-metadata">

### Author: ![chris](https://forum.meet.coop/user_avatar/forum.meet.coop/chris/32/3_2.png) [@chris](https://forum.meet.coop/u/chris)
#### Post date: [15 July 2020 12:51 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130/55 "2020-07-15T12:51:47Z")

</div>

> [@wouter](#):
>
> we keep things simple, use only [meet.coop](http://meet.coop) subdomains and have a key identifier (the URL) to signal who’s providing the service - that’s great for viral marketing.

> [@mikemh](#):
>
> I vote `entity-name.meet.coop`

We can only create sub-domains of `meet.coop` for external entities that are co-operatives and then only with agreement, see [the third-level domain policy](https://identity.coop/wp-content/uploads/2020/01/Coop-Third-Level-Domain-Policy-Jan-2020.pdf), for Greenlight containers best use a sub-domain provided by the client.

---

<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: [15 July 2020 13:02 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130/56 "2020-07-15T13:02:56Z")

</div>

> best use a sub-domain provided by the client

Might we also have a non-coop domain that we could freely create subdomains in? Eg `omc`. Keeping our service visible in the url would be good, I think.

---

<div class="post-metadata">

### Author: ![benhylau](https://forum.meet.coop/user_avatar/forum.meet.coop/benhylau/32/12_2.png) [@benhylau](https://forum.meet.coop/u/benhylau)
#### Post date: [15 July 2020 14:15 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130/57 "2020-07-15T14:15:11Z")

</div>

Thanks for pulling this together, looking good!

> [@wouter](#):
>
> “Contribution levels” instead of Service Levels

+1

> [@wouter](#):
>
> names for the service/contribution levels

I don’t like the “Individual/Micro/Small/Organization/Large” and prefer the new names, but tying them to participant limit may be weird as that’s a number that could change in the future.

Since we are using the terms _Members_ and _Contribution Levels_, why don’t we name the tiers like this in two rows, or is it too confusing?

| Columns | | | | | | |
| --- | --- | --- | --- | --- | --- | --- |
| **Contribution** | Free | Level 1 | Level 2 | Level 3 | Organization | Custom |
| **Membership** | None | Individual membership | Individual membership | Individual membership | Organizational membership | Organizational membership |

I wonder when an individual contributes at the Organization/Custom level, are they considered an Organizational User Member, especially in relation to votes, etc. when that gets spec’d out. If not, then using the word “Organization” here at all will make things confusing.

### My suggested footnotes

_1 Membership offers the right to participate as a [User Member at the Online Meeting Cooperative](https://wiki.meet.coop/wiki/Membership), and is part of all Contribution Levels except for Free accounts._  
_2 Recorded rooms will be enabled on the shared cluster in the coming months, when per-room recording can be controlled through the Greenlight interface._  
_3 Members may use our Event Server with dedicated resources for a time duration at additional cost in the coming months._  
_4 A Fair Use Policy applies, where members commit themselves to contribute according to the agreed contribution levels and seek to live together as friendly commoners on the shared platforms._  
_5 BigBlueButton recommends that [no single session exceed 100 users](https://docs.bigbluebutton.org/support/faq.html#how-many-simultaneous-users-can-bigbluebutton-support)._  
_6 Amounts are exclusive of applicable sales tax._

---

<div class="post-metadata">

### Author: ![wouter](https://forum.meet.coop/user_avatar/forum.meet.coop/wouter/32/318_2.png) [@wouter](https://forum.meet.coop/u/wouter)
#### Post date: [15 July 2020 14:45 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130/58 "2020-07-15T14:45:13Z")

</div>

> [@chris](#):
>
> We can only create sub-domains of `meet.coop` for external entities that are co-operatives and then only with agreement, see [the third-level domain policy](https://identity.coop/wp-content/uploads/2020/01/Coop-Third-Level-Domain-Policy-Jan-2020.pdf), for Greenlight containers best use a sub-domain provided by the client.

Thanks, Chris for reminding the dotCoop subdomain policy. I looked through it and one of the requirements is "Users must be members of the second level registrant organization; "

Isn’t this the key thing? The service is ours, to our members. There’s nothing no-cooperative about it that would exclude us. I mean the fact that we would offer [xx.meet.coop](http://xx.meet.coop) to a subgroup of members is still a [meet.coop](http://meet.coop) service, we’re in no way renting out subdomains or something like it.

If the doubt remains, maybe it would be good to check with dotCoop about it?

---

<div class="post-metadata">

### Author: ![wouter](https://forum.meet.coop/user_avatar/forum.meet.coop/wouter/32/318_2.png) [@wouter](https://forum.meet.coop/u/wouter)
#### Post date: [15 July 2020 14:52 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130/59 "2020-07-15T14:52:22Z")

</div>

> [@benhylau](#):
>
> I don’t like the “Individual/Micro/Small/Organization/Large” and prefer the new names, but tying them to participant limit may be weird as that’s a number that could change in the future.

yeap, that’s true, the #participants can change, and possibly we come up with meet150 or whatever when that’d be suitable.

> [@](#):
>
> Since we are using the terms _Members_ and _Contribution Levels_ , why don’t we name the tiers like this in two rows, or is it too confusing?
> 
> | Columns | | | | | | |
> | --- | --- | --- | --- | --- | --- | --- |
> | **Contribution** | Free | Level 1 | Level 2 | Level 3 | Organization | Custom |
> | **Membership** | None | Individual membership | Individual membership | Individual membership | Organizational membership | Organizational membership |

the concept looks very good to me, only I’m not sure the individual / Organisational distinction here: that will depend on the legal form of a given member: if one joins a person, or as an organisation.  
And besides, why would an organisation not be able to go for Level 2 or 3?

> [@](#):
>
> I wonder when an individual contributes at the Organization/Custom level, are they considered an  
> Organizational User Member, especially in relation to votes, etc. when that gets spec’d out. If not, then using the word “Organization” here at all will make things confusing.

for the above reason I agree that “Organisation” here is confusing; I’d rather see another Service / Contribution level. What would you prefer?

> [@](#):
>
> ### My suggested footnotes
> 
> _1 Membership offers the right to participate as a [User Member at the Online Meeting Cooperative](https://wiki.meet.coop/wiki/Membership), and is part of all Contribution Levels except for Free accounts._  
> _2 Recorded rooms will be enabled on the shared cluster in the coming months, when per-room recording can be controlled through the Greenlight interface._  
> _3 Members may use our Event Server with dedicated resources for a time duration at additional cost in the coming months._  
> _4 A Fair Use Policy applies, where members commit themselves to contribute according to the agreed contribution levels and seek to live together as friendly commoners on the shared platforms._  
> _5 BigBlueButton recommends that [no single session exceed 100 users](https://docs.bigbluebutton.org/support/faq.html#how-many-simultaneous-users-can-bigbluebutton-support)._  
> _6 Amounts are exclusive of applicable sales tax._

Yes, please apply these improvements in the wiki, @benhylau

---

<div class="post-metadata">

### Author: ![wouter](https://forum.meet.coop/user_avatar/forum.meet.coop/wouter/32/318_2.png) [@wouter](https://forum.meet.coop/u/wouter)
#### Post date: [15 July 2020 14:54 UTC](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130/60 "2020-07-15T14:54:58Z")

</div>

> [@mikemh](#):
>
> > Do we want to talk about “Contribution levels” instead of Service Levels?
> 
> I would say ‘contribution’ refers to what comes into the coop - labour, or money (funding) - and what we provide to users is ‘service’. I think we should offer **service levels** , expect and require fair-use observance of these, and invite **funding contributions** of X-plus € (with a possibility of “crowdfunding top-up”?) at fair-use level X. Emphasising the level of fair use (aka service) is important I think?

Maybe you’re right, we offer the service level. At the same time members choose a contribution level that comes with a certain service level. Haha, that’s not making it clearer 😜

[Previous page](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130.md?page=2)

[Next page](https://forum.meet.coop/t/what-services-can-we-offer-from-1st-july-2020/130.md?page=4)
