Practical steps in federating infrastructure
The commons.hour discussion identified a few practical steps that might be taken as meet. coop migrates into an operational rtelationship with WebTV. See notes Nextcloud.
It might be seen as a federating ecosystem with four basic functional areas: back-end tech, front-end membership, front-end community-facing stewardship, community outreach/research/education). Slide here: Nextcloud full slide deck here: Nextcloud . The tech back-end isn’t rocket science: exchanging services, agreeing standard deployment, etc. The front-end org stuff is probably more challenging. @evolution to work on this.
Summary:
- Determine whether meet.coop members subscribing to BBB service can get access to other tools provisioned by WebTV (e.g. nextcloud toolstack). How to enable this: financially (layered subscriptions, an additional service level bundle?), administratively (SSO?). @gcotnoir @evolution
- David @dvdjaco : draft a framework agreement for exchanging (tech?) services between coops.
- Make sure that operational agreements in meet. coop v2.0 (aka
contribution economy) are explicit and available in a ‘book’. @evolution -
- Include documentation for: how to make agreements (provide templates for agreements? agree protocols for making agreements?).
- Create ‘a playbook for how to collaborate’? For example: How to go from 'we have spare resources in this location, which we would be glad to share across regions’ to 'we are a working operational part of the federation’?
-
- meet. coop handbook is intended as ‘a playbook for collaborating’ Handbook evolves - moves into Outline. Not fully available for use yet but a sample is here, on principles for meet. coop . The handbook is where operational protocols for meet. coop v2.0 should be logged/shared. @mikemh @wouter This is a continuation of a function of the meet. coop Org circle.