LogoLogo
  • Welcome
  • Note - Draft, prototype status
  • Note - Licensing, quoting
  • Meet meet.coop
    • The online meeting coop - meet.coop
    • Contact us
  • 1 Principles
    • Principles
      • Spaces
      • The toolstack
      • Platform spaces
      • Media spaces
      • Venue spaces
      • Stack of commons
      • Privacy policy
    • Commoning
      • Spaces stewarded as commons
      • Commoning - Three moments
      • Contributing in commons - A governance hybrid
      • Classic FLOSS peer-to-peer governance
      • Classic co-op governance
      • Assemblies - Governance in ‘roots’ movement organisations
      • Full-range commoning - The contribution of care work
      • Commoning as a practice of dual power - Beyond . .
    • Principles & protocols
      • Value and value(ing)
      • Values as practices in working order
      • Coop values, DisCO
  • 2 Political economy
    • Political economy
    • Members and contributions
      • User members, user-member accounts
      • Active user members
      • Operational members
      • Register of members
      • Privileges and obligations
      • Sanctions
      • Fair use of BBB space
      • Contributions
      • Contribution accounting
        • Contribution & recognition
        • Contributions & locations of work
        • Work of valuing, and means of recording and valuing (mapping) contributions
      • Funding contributions
      • Rent
      • Contributions in kind
      • Work contributions
      • Recognition of contributions
      • Voting
    • Commons political economy
      • Ownership, assets and commons
      • Dissolving meet.coop
      • Fiat money, mutual credit, fair wage, sweat equity
      • A commons and its members - Stewarding, contributing, enjoying
      • Dependence - Livelihood, infrastructure, dual power
      • Livelihood, privilege, contribution
      • Provisioning and hosting
      • Employment, federation and voluntary contribution
      • Revenue, surplus and distribution
      • Development funding, investment
      • Value, values, value(ing) and production in-and-of commons
      • Contribution, privilege and justice - The purpose of protocols
  • 3 Social relations
    • Social relations
    • Intentions, principles
    • Actions in three landscapes
    • Dimensions of community
      • Plural community - Three sectors
      • Pluriverse
      • 1 Coop - Transformed economy, making the coop-commons
      • 2 Solidarity - Transformed silos, formación
        • Tools for conviviality
        • Formación - Learning, the dance of knowing
      • 3 Toolstack - Transformed organising capability, infrastructuring
        • Dance of knowing
        • Design justice
      • Multiple languages, plural regions, uneven development
      • Privacy
    • Seven Rs of civil-society activist commitment
      • Rescue
      • Resistance
      • Reporting, recording
      • Re-weaving the economy
      • Reparation, reconciliation, restorative justice
      • Regenerative activism
      • Regime change, revolution
  • 4 Assemblies and deliberations
    • Assemblies and deliberations
      • Circles
        • Community circle
      • Standing assembly (all-hands)
      • commons.hour
      • General assembly
      • Board of stewards
      • The forum
      • Polls
      • Protocols - Time
      • Protocols - Multiple languages
      • Protocols - Facilitation & moderation
  • 5 commons.hour
    • commons.hour - The programme
      • Basic links for commons.hour
      • commons.hour invitation
      • Programme & presenters
      • Defining what meet.coop does - A handbook and a commons
      • Prototyping and collaborating
      • Defining what meet.coop is for
      • Running list of sessions
      • Summary running list
      • Design and prototyping in commons.hour
      • commons.hour - the venue
    • commons.hour protocols
      • Session protocols
      • Session pre- and post-protocols
      • commons.hour methodology
    • Design principles
      • Design justice - note
      • Plural community
      • Coop principles
      • commons.hour ‘specials'
  • 6 Constitution
    • Constitution
      • Conventional outline of a constitution
      • A design approach to a constitution - an assemblage of protocols
      • Protocols vs rules
      • The handbook and the constitution
      • Core protocols aka principles of meet.coop
      • Draft constitution
  • 7 Code of conduct
    • Code of conduct
      • In platform spaces
      • In media spaces
      • In venue spaces
      • Operational members
      • User members
      • Making the coop-commons economy
      • Provisioning and mobilising tools and capability
      • Cultivating solidarity and mutuality
  • 8 Terminology
    • Terminology
      • BBB - Big Blue Button
      • Containers
      • Discourse
      • FLOSS - Free-libre open-source software
      • gitBook
      • Greenlight
      • Markdown
      • Matrix/Element
      • NextCloud
      • Sweat equity
      • Sysadmins aka ‘admins’
  • 9 Supporting materials
  • Supporting materials
    • meet.coop
    • Other organisations
      • Open Credit Network - Membership Agreement
Powered by GitBook
On this page

Was this helpful?

  1. 5 commons.hour
  2. commons.hour - The programme

Prototyping and collaborating

Here we describe the collaborative work we'll undertake within the programme, with a stack of spaces that will be evolved into a working ecology of practices and means.

PreviousDefining what meet.coop does - A handbook and a commonsNextDefining what meet.coop is for

Last updated 3 years ago

Was this helpful?

In the course of the commons.hour programme we’re setting out to prototype a number of spaces. Actually, it's an ecology of spaces, which will become part meet.coop working practice. The field of prototypes is outlined in this schema -

Venue spaces

The monthly BigBlueButton gathering, commons.hour itself, is a prototype of a venue space for mutual live engagement across all kinds of members. Particularly it's a space for user-members and operational members to engage and exchange. But in addition to this, the programme needs to design and prototype other live venues: a General Assembly, and a Community Circle. All these venues will be elements in the ongoing governance/stewarding of meet.coop, as a multistakeholder coop.

Media spaces

By no means all of what we need to identify, explore and capture in protocols can be handled in a monthly live gathering. So media spaces are fundamental. Obviously, the handbook is central: this is where the protocols are to be assembled and refined. Less obviously, there will need to be active exchange in threads on the meet.coop forum, between sessions. Both of these media spaces will need their protocols to be refined, and described in the handbook. We’ll record the sessions, and this evolving library of recordings is a media space too.

By no means all of what we need to identify, explore and capture in protocols can be handled in a monthly live gathering. So interaction via (asynchronous) media spaces is fundamental. Obviously, the handbook is central: this is where the protocols are to be assembled and refined. Less obviously, there will need to be active exchange between sessions, in discussion threads in the meet.coop forum. Both of these media spaces will need their protocols to be refined, and described in the handbook. We’ll record the commons.hour sessions, and this evolving library of recordings is a media space too.

Platform spaces

Thirdly, in order to collaborate in these ways we’ll need to use an appropriate set of tools, in addition to BigBlueButton. Above we tacitly referred to gitBook and Discourse - our chosen means (for now) of implementing the handbook and discussion threads.

But we may find we need other tools - for example, for cloud sharing of documents or for instant-messaging chat. Already, we have started using the OpenCollective platform for general communication (about commons.hour) with the entire membership.

But we may find we need other tools - for example, for cloud sharing of documents or direct-messaging chat. Already, we have started using the OpenCollective platform for general communication (about commons.hour) with the entire membership.

It’s very easy for such a combination of platform spaces to get over-complex and confusing to use. At the same time, having well-defined tools, designed to do a specific job of work, is helpful. Figuring out this matter of toolstacks is a third dimension of prototyping in commons.hour. On one hand, there will be folks becoming operationally involved in the Community circle (but not in the same way as operational members?) and, on the other, user members and their associates will be participating in commons.hour, perhaps in a more ad hoc way.

When we’ve got protocols in these three domains figured, and documented in the handbook, we’ll have a resource that we mean to share, open source, as a design for a distributed coop-commons community (and a design methodology). So the handbook is part of a wider media commons too.

Collaborating in commons.hour - Prototypes of collaboration spaces