MetaGuild: Difference between revisions
Add Category:Guild |
Rewrite MetaGuild as a library of working patterns; drop charter framing |
||
| Line 1: | Line 1: | ||
{{MetaGuild}} | {{MetaGuild}} | ||
{{headerbox}} | {{headerbox}} | ||
'''MetaGuild''' is a library of patterns for starting and sustaining guilds at Noisebridge. | |||
*'''MAINTAINERS:''' [[User: | |||
*''' | For discussion, find us on #metaguild on [[Discord]]. | ||
In the tradition of the [[FractalWorkingGroup]] and the [[Philosophy Guild]]. | |||
*'''PAGE MAINTAINERS:''' [[User:Nthmost|nthmost]], [[User:Lxpk|lxpk]], [[User:Mcint|mcint]] | |||
*'''CHANNEL:''' #metaguild on [[Discord]] | |||
{{boxend}} | {{boxend}} | ||
[[Category:Guild]] | [[Category:Guild]] | ||
''A note on language: "Maintainer" on this page refers to people who tend this wiki page. A guild is a living social organism — it has organizers, practitioners, and members.'' | |||
== Patterns == | |||
=== Create More Masters === | |||
The more people trained who can train others, the more eyes on the guild continuously, the less entropy you'll need to deal with over time. | |||
Encourage people to learn how to run and maintain the tools and practices of your guild. Get a recognition matrix going. Give credit generously and publicly to people who help clean, fix, and train. The goal is multiplication, not concentration. | |||
=== The Watering Hole === | |||
Hold a regular meeting time every week, even if it seems like there's nothing to discuss or work on. Just having that consistent gathering creates community. The [[Infra]] meetup is a good example: everyone now knows they can find someone on Monday nights. | |||
The meeting doesn't need an agenda to be valuable. Showing up is the agenda. | |||
=== Avoid the Bottleneck === | |||
Watch for these warning signs: | |||
* "I'm tired of running trainings" → no one gets trained | |||
* "X is the only person who can fix Y" → Y stays broken when X leaves | |||
* Fewer than 5 people can answer a question in the guild's chat → next biggest problem to solve | |||
Distributed intelligence works well for anarchists. Find a way to track who knows what, and actively work to spread that knowledge around. | |||
== | === Succession Thinking === | ||
If you as an organizer don't feel like you can step away without everything coming to a halt, that's your first problem to solve. | |||
If you start showing up a lot, in a way that people come to rely on you being there, be actively working on distributing that capacity — rather than letting people see you as the central node. | |||
Only add more of your own time if you are actively also looking for people to help you share the load. | |||
=== Avoid All-or-Nothing Thinking === | |||
"Well, they only know how to fix one of the machines" is not a reason to discount someone's contribution. Partial knowledge distributed across many people is more resilient than complete knowledge held by one person. | |||
Find a way to track who knows what. Celebrate incremental skill-building. | |||
== | === Badges === | ||
A fun mechanism from the [[Badges]] concept: collaborate to create DIY badges that require learning a guild skill to make. For a sewing guild, that might mean sew-your-own badges where making the badge *is* the skill demonstration. | |||
[[ | |||
Badges serve double duty: recognition for the person earning them, and a visible signal to the community that this guild has a golden path worth walking. | |||
== See Also == | |||
* [[Guilds]] — the full guild directory and philosophy | |||
* [[FractalWorkingGroup]] — predecessor model | |||
* [[Philosophy Guild]] | |||
* [[Badges]] | |||
Revision as of 10:17, 25 March 2026
| Noisebridge | About | Visit | 272 | Manual | Contact | Guilds | Stuff | Events | Projects | Meetings | Donate | E |
| Guilds (Volunteer) | Maintainers | Meta | Code | Electronics | Fabrication | Games | Sewing | Music | AI | Neuro | Philosophy | Funding | Art | Security | Ham | WGs | E |
| MetaGuild | Recruiting Guilds | Volunteer | Documentation | Outreach | Working Groups | CommunityWG | Badges | E |
|
MetaGuild is a library of patterns for starting and sustaining guilds at Noisebridge. For discussion, find us on #metaguild on Discord. In the tradition of the FractalWorkingGroup and the Philosophy Guild. |
A note on language: "Maintainer" on this page refers to people who tend this wiki page. A guild is a living social organism — it has organizers, practitioners, and members.
Patterns
Create More Masters
The more people trained who can train others, the more eyes on the guild continuously, the less entropy you'll need to deal with over time.
Encourage people to learn how to run and maintain the tools and practices of your guild. Get a recognition matrix going. Give credit generously and publicly to people who help clean, fix, and train. The goal is multiplication, not concentration.
The Watering Hole
Hold a regular meeting time every week, even if it seems like there's nothing to discuss or work on. Just having that consistent gathering creates community. The Infra meetup is a good example: everyone now knows they can find someone on Monday nights.
The meeting doesn't need an agenda to be valuable. Showing up is the agenda.
Avoid the Bottleneck
Watch for these warning signs:
- "I'm tired of running trainings" → no one gets trained
- "X is the only person who can fix Y" → Y stays broken when X leaves
- Fewer than 5 people can answer a question in the guild's chat → next biggest problem to solve
Distributed intelligence works well for anarchists. Find a way to track who knows what, and actively work to spread that knowledge around.
Succession Thinking
If you as an organizer don't feel like you can step away without everything coming to a halt, that's your first problem to solve.
If you start showing up a lot, in a way that people come to rely on you being there, be actively working on distributing that capacity — rather than letting people see you as the central node.
Only add more of your own time if you are actively also looking for people to help you share the load.
Avoid All-or-Nothing Thinking
"Well, they only know how to fix one of the machines" is not a reason to discount someone's contribution. Partial knowledge distributed across many people is more resilient than complete knowledge held by one person.
Find a way to track who knows what. Celebrate incremental skill-building.
Badges
A fun mechanism from the Badges concept: collaborate to create DIY badges that require learning a guild skill to make. For a sewing guild, that might mean sew-your-own badges where making the badge *is* the skill demonstration.
Badges serve double duty: recognition for the person earning them, and a visible signal to the community that this guild has a golden path worth walking.
See Also
- Guilds — the full guild directory and philosophy
- FractalWorkingGroup — predecessor model
- Philosophy Guild
- Badges