feat: expand seed library from 6 to 100 protocols
Added 94 new protocol YAML seed files covering diverse global cultures and practices: Indigenous & traditional: Maori powhiri, Aboriginal yarning, Somali xeer, Moroccan jmaa, Tswana kgotla, Zulu imbizo, Peruvian ronda campesina, Ohlone land-back, Inuit IQ consensus, Haudenosaunee condolence, Navajo peacemaking, Ojibwe pipe ceremony, Polynesian talanoa, Rwandan gacaca, West African palaver tree, Mexican tequio, Javanese musyawarah-mufakat, Tibetan story council, Korean yangban, Filipino utari, Ainu practices Religious communities: Quaker meeting for business, clearness committee, Amish shunning (Meidung), Mennonite discernment, Jewish hevruta, Rastafari nyabinghi reasoning Facilitation: World Cafe, Open Space, Future Search, Six Thinking Hats, Dynamic Facilitation, Socratic Seminar, Delphi method, Copenhagen Consensus, Lean Coffee, Hackathon sprint, Agile retrospective, Stand-up meeting, Pair programming, Roadmap planning Governance: Sociocratic consent selection, Dynamic self-governance, Cooperative consensus, Hackerspace consensus, Mastodon governance, Climate assemblies (x2), Basque asamblearismo Conflict & repair: Restorative conference, circle sentencing, Nonviolent Communication (3 protocols), Active listening mirror, Appreciative apology repair Community & care: Community kitchen, Gratefulness circle, Passing circle, Paired walking, Deep listening dyad, Mutual aid, Permaculture charrette Education: Barefoot College night school, Socratic seminar Everyday: Various greeting, transition, and gratitude protocols All protocols credit original sources. Cultural context noted in descriptions. All YAML files validated.
This commit is contained in:
@@ -0,0 +1,44 @@
|
||||
id: hackerspace-consensus-doctorate
|
||||
title: Hackerspace Consensus Meeting
|
||||
description: >-
|
||||
A governance meeting format used in many hackerspaces and makerspaces
|
||||
where members propose changes and the group works toward consensus or
|
||||
rough consensus, with an explicit "doctorate" of expertise respected
|
||||
but not privileged. Originating in the global hackerspace movement,
|
||||
with Noisebridge (San Francisco) as a notable exemplar.
|
||||
source: Noisebridge / Hackerspace movement
|
||||
source_url: https://www.noisebridge.net/
|
||||
tags: [hackerspace, consensus, governance, open-source, community]
|
||||
forked_from: null
|
||||
image: null
|
||||
steps:
|
||||
- headline: Post the proposal in advance
|
||||
description: >-
|
||||
The proposer posts the proposal on the hackerspace's wiki or
|
||||
discussion board at least a week before the meeting, so members can
|
||||
read and comment before convening.
|
||||
- headline: Present at meeting
|
||||
description: >-
|
||||
At the meeting the proposer presents the proposal. The facilitator
|
||||
takes clarifying questions, then opens discussion.
|
||||
- headline: Discuss concerns
|
||||
description: >-
|
||||
Members raise concerns, which are listed. The proposer amends or
|
||||
responds. The facilitator ensures those with relevant expertise are
|
||||
heard but not privileged over others.
|
||||
- headline: Test for consensus
|
||||
description: >-
|
||||
The facilitator tests for consensus or rough consensus. A block must
|
||||
be reasoned and accompanied by a willingness to help find a
|
||||
solution.
|
||||
- headline: Record and act
|
||||
description: >-
|
||||
The decision is recorded on the wiki with the date and any
|
||||
stand-asides. Action items are assigned to named members.
|
||||
outcome: >-
|
||||
A hackerspace decision is made with members' input, recorded publicly,
|
||||
and acted on by named owners.
|
||||
practice: >-
|
||||
Posting in advance is the discipline — decisions made on the spot
|
||||
exclude those not present. A block is a serious act; at Noisebridge it
|
||||
comes with an obligation to work toward resolution.
|
||||
Reference in New Issue
Block a user