Actually I have just realised that I have another meeting at 3pm BST which is 4pm CEST, could the meeting be moved to be an hour later?
Request: can we convert agreed upon date/times for meetings into threads like Weekly progress meeting: Thursday 2/July which show up on the shared calendar and make it easier to catch when a meeting is coming up? That would be nice since it is hard to catch all the comments, thanks!
any time between midday and 2 would be best for me ā¦ otherwise I will be juggling baby (again!_) but will still try to make itā¦
Between noon and 2pm BST is fine for me.
Letās make it 12:00 BST (13:00 CEST) at https://ca.meet.coop/b/wou-cyy-wpt since that works for @chris @osb and a possible time for Toronto.
2020-06-30T11:00:00Z ā 2020-06-30T12:00:00Z
@decentral1se I am not sure how to do that. I wonder if ^ would do it.
Works! Thanks
I ended up changing it at the top, replacing last weekās event. I hope I didnāt screw anything up
thanks, @benhylau! By changing the event we lost last weekās event. Maybe for next time we could open a new topic with the event?
I will see you in a few hours then, looking forward.
I just started drafting a proposal for that āone-pagerā (or two pages if needs be ;-)) on a pad. Itās co-creation, please jump in, or if you consider weād better do it different, go ahead. During the meeting we can tweak and afterwards we can move it into the wiki.
https://pad.femprocomuns.cat/meetcoop-model
After 24 hours gestation I feel that although we had a good meeting yesterday : and clarified some dimensions, we havenāt yet nailed the complex relationships between
- membership classes and service-user accounts
- worker contributions and consumer/beneficiary obligations
- circle-organisation of workers, and the mechanisms of autonomy/executive action
- governance mechanisms for both passive and active coop members (forum/circle/assembly)
- administration of arrangements for service-supply, from operational coops (Hypha, Koumbit, WebArch plus a front-desk coop tba) to room account holders (ābeneficiariesā)
- relationship between accounts admin (payments, reception desk, creating container accounts on servers, etc) and admin of rooms-per-member organisation, by an organisationās āroom adminā person
I feel what matters most is how things look from the user end - the account-holding organisationās admin role. But we spend so much time - for understandable reasons - focusing on server admin and software tool behaviour on the server, rather than account admin and platform-facilitated capability out there in the world of non-geek cooperators (= āuse casesā).
I feel we need to develop a well-matched three-way focus on
- the front office . . . accounts, reception desk, server ops, financial transactions with account holders (who mostly will be passive consumers), legal obligations and limitations of service-providing coops, statutory stuff (GDPR, data security, etc); and
- the back office . . . agile multi-stakeholder circles of enthusiastic paid and unpaid worker-contributors doing executive work, internal work organisation/agile division of labour across circles, cultivation of the evolving multi-discipline community of coproducers (ie folks collaborating at least weekly), āpermanent assemblyā in Discourse (as an agile, circle-support function); and
- formal governance in terms of voting in whole-coop (annual?) assemblies - weighted according to contribution, as distinct from shareholding and simple, generic membership classes (where financial contribution by account-holders is just one kind of important - minority - contribution).
Some gloss on all of this will be needed to make a convincing marketing pitch to early-adopter account-holder members in the alpha phase - bcos its the whole vision and long-term intention (and ability to contribute to this) that will attract the kinds of collaborating/coproducing participants that we need in the medium and long term (ie for beta relaunch). We would need to be able, for example, to have a discussion around this with MayFirst, or social.coop. Or the (UK) Coop University. All, significant potential users of meet.coop accounts, all quite large and complex, all wanting more than just a room or two occasionally.
The front-office stuff is about ensuring reliable service delivery according to fair-use service-level agreements, for paying account holders: so that when they turn the tap on, water comes out. Even among committed ānew economyā activists, this is what account holders mostly will want - they said this at Open2020. They might be willing to pay premium, crowdfunder rates for services. This is basically āconsumer coopā stuff.
The back-office stuff is about nitty-gritty worker coop coproduction, teamwork and capability to nail operational problems, evolve better working arrangements, and meet actual user needs thro multi-stakeholder co-design of nonāgeek oriented digital tool bundles. In familiar coop terms this is basically worker-coop culture - this makes meet.coop mutli-stakeholder, with heavy worker loading.
The assembly stuff is about stewarding commons of digital infrastructure, and their strategic contribution to an evolving commons-cooperative economy . . which is all a new kind of practice (beyond typical coop scope), and needs puzzling out.
All of this is basic launch pitch? The practice will take years to evolve but the picture is short-term urgent, to bring in the early-adopter visionary-contributors, to become development partners (back-office coproducers) for the long haul?
If this seems like an issue in Thursdayās meeting, Iād be willing to do a presentation-for-starters that attempts to (visually) pinpoint these things, and with others here, to co-host a 90min discussion session (maybe Sunday/Monday?). If this seems too āfutureā oriented rather than ānowā . . Iāll shut up and stop striving for design-thro-protocols (to enable organisation-hacking in the medium term) as distinct from a short-term āalpha stack-hackā to get some users on the servers and money in the kitty.
I consolidated what we discussed so far, and from yesterdayās meeting, into this that I hope to receive feedback on Thursday. If we can get this sorted, we can move on to drafting what our Circles are and decision-making and voting in the next Governance meeting.
Proposed one pager
Meet.coop, The Online Meeting Co-operative, is a meeting and conferencing platform powered by BigBlueButton, stewarded by co-operatives across the world.
We have two types of membershipsāOperational Members and Beneficiary Members. One may apply to one or both membership types as an organization or as an individual.
Operational Members steward all operational aspects of Meet.coop.
- To apply, you must commit a minimum of 500 in Euros, equivalent resources, or 40 hours of voluntary labour in work areas defined by the Co-operative.
- In turn, you may participate in the Co-operativeās working Circles and are eligible to apply for waged positions defined by the Co-operative. An Operational Member may also self-elect to become a Beneficiary Member as well, without an application process or paying annual membership fees as long as they remain an active Operational member.
- To maintain active membership, you must be contributor to at least one Circle and participate in at least 50% of our All Hands meetings.
Beneficiary Members use the Meet.coop platform for internal meetings or resell Greenlight accounts.
- To apply, you must commit a minimum of 200 in Euros per year.
- In turn, you will get a set of Greenlight containers as according to our defined Service Levels, which you can manage for reselling our BigBlueButton server capacity. You may also participate in the Co-operativeās working Circles.
- To maintain active membership, you must maintain good standing with annual membership fees and from your resale revenue, pay a percentage set by the Co-operative to Meet.coop to cover its operation costs, and provide best-effort oversight to your Greenlight accounts in compliance with the Co-operativeās Fair Use Agreement.
All membership starts with an application to contact@meet.coop. Upon approval, in addition to the responsibilities and rights for the type of membership, the new member may also participate in the Assembly, Forum, and other member spaces. All memberships carry voting rights with voting strengths as according to membership type and level of participation.
Current membership as according to above
Currently, the following organizations and individuals meet the application criteria above based on Contributions page:
Operational Members
- Autonomic Cooperative (40h from Luke)
- Collective.tools (50-100ā¬/month for renting servers + hours from Petter)
- Digital Life Collective (2x E5440 @ 2.83GHz (8 core) 16GiB ram 2TB machine at 198.204.235.226/29)
- femProcomuns (40h from Wouter, David)
- FOSSHOST.org (VPS dev.meet.coop + TURN/STUN turn.fosshost.coop)
- Hypha (40h from Ben, Yurko, Elon)
- Webarchitects (40h from Chris)
- Mike Hales (individual) (ā¬120 + hours)
Beneficiary Members
- Animorph Co-op (ā¬500)
- Free Knowledge Institute (ā¬500)
- May First Movement Technology (Ā£225)
The following organizations and individuals are unclear:
- Agile collective
- Koumbit (our main server is with Koumbit and SĆ©bastien has spent time on Meet.coop)
- Melissa (individual)
- Remix the Commons
- Yasu (individual)
SĆ©bastien, Melissa, and Yasu are all involved, itās just unclear from the Contributions page whether they intend to commit to the threshold of being an Operational Member.
really liking this
not sure if u missed The Open Co-op or left it out for some reason?
Think we need to define what a All Hands meeting isā¦?
Not sure about the ā¬ levels or where these came from / what they are based onā¦?
I was not assuming that an individual Beneficiary member got anything other than a room to make video callsā¦ i.e. they might just pay ā¬10/month as per What services can we offer from 1st July 2020? (not needing to commit to ā¬200 / year - this is too much it will put individuals off ) - plus they donāt need reseller abilitiesā¦ etc
I am basing most data on Contributions page on wiki. Thatās why The Open Co-op isnāt in there, we can easily clear that up. The orgs are for example, as I imagine contributors like Melissa would also qualify, just not evident based on the wiki pageās info.
The All Hands is meet.coop - The Online Meeting Cooperative but we can change the cadence later.
Operations Member ā¬500 also from the wiki, and for Beneficiary Members I feel the barrier to entry can be low as involves a rev share. This also allows us to honour our commitment to May First.
Then they are not a member. Instead, they should register an account resold by a Beneficiary Member. Meet.coop doesnāt want to manage all these little accounts (@chrisā point all along).
This is looking really good to me @benhylau - more heroic labour Hope youāre logging hours on these key contributions?
This goes a long way to resolving what above I called front office issues - service levels remain the key thing to be defined there? So yes, we then can focus in on back office (circle work organisation and priorities) and assembly protocols (all-hands weekly, discourse forum, annual confluence, etc).
When we have a one-pager in each area, we can then expect to seriously recruit membership, and have proper discussions with organisations that have already become Beneficiary members (eg MayFirst) to clarify our relationship. With these early adopters, it will be important to recruit them to our medium-to long term development purposes (an economic capability project) and not just to ad-hoc room use. They will be our prime source of outcome-oriented back office volunteer workers, and medium-term steering at circle and assembly levels.
In this draft I feel only one area needs critical focus and that is reselling. I think we should not leave any door open to profit making on the back of our precious server infrastructure and back-office labour. I feel it should be dedicated for the use of movement and coop organisations in enabling federated coworking, as part of a distinctive economic project, and not seep into the gig economy or private enterprise.
I also believe reselling should be under the meet.coop brand and meet.coop governance - so reselling would be on an āagency basisā, I guess, as a federated arm of the meet.coop project rather than some other kind of project. Discussion with ppl like MayFirst would be important in getting this right? They would have a very firm stance on roots community support, private profit and federation, for example.
Great groundwork ben
Yep. Cascade this down to a beneficiary member.
Hypha members are tracking time here Time tracking with Kimai - #7 by benhylau someday I may have to import into the Meet.coop thing
Yup! I agree. I think we can even encode this into the Fair Use Policy. e.g. never sell service to Amazon and fascists. Until we have this codified, I think we should trust Beneficiary Members, by approving only value-aligned membership applicants. Later, we can be more specific.
By yea, I agree one key discussion point is service levels and restrictions around reselling so it doesnāt become a price competition (at the moment we fix the service levels everyone must adopt, but clearly they are too restrictive) or private enterprise (how do we share the clients).
Looking forward to cancelling my Zoom account this week, on the basis of member status now being clear. Actually, Iām an organisation/beneficiary in this context (Living Economy college network) rather than an individual worker member. Waiving a complimentary account as an operational member (committed 40 hours) with a ā¬120 annual crowdfunding contribution to the project. (my organisational Zoom subscription).
[Edit] Were going to need some clear book keeping, straight away. The contribution accounting circle needs to kick in asap?
On Matrix chat I asked @hng:
I wonder if this thinking around membership could work for you Governance Model - #53 by benhylau obv thereās a line between ācollocall businessā vs. āmeet.coop businessā as you have own well developed pipeline alrdy
His response was:
Yes Iāve just read it and I think this would work for us
@mikemh do you want to take a stab at drafting out the circles here before the meeting? Like names + one sentence to describe scope of responsibilities. I feel like you have some ideas on what they would be. Maybe having this in the meeting notes will help us concretize what āCirclesā are and how together they will serve all of Meet.coop operations.