MetaGuild

From Noisebridge
Jump to navigation Jump to search
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.

Philosophy

The guild model draws from anarcho-syndicalism: Noisebridge as federation, guilds as syndicates. Everyone who uses a guild's resources is implicitly a member of the syndicate — with both the benefits and the responsibilities that come with that.

See also: User:Nthmost/Guilds_and_AnarchoSyndicalism

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.

Watch for this failure mode: someone does something amazing, you thank them, and they say "Oh, I'm just a guy who knows stuff." It sounds humble. It feels anarchist — no hierarchy, no ego, no authority. But it keeps expertise locked in one head instead of letting it reproduce. When they leave, the knowledge dies. When they burn out, there's no replacement.

"I'm just a guy" is not humility. It's a single point of failure.

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

Ask yourself: "What's my bus number?" — if you got hit by a bus tomorrow, would your work die with you? At Noisebridge, the answer is usually yes. Bus number: 1. Or 0.

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.

The Participation Spiral

Picture a spiral. The core is "master of the guild." The outer ring is the newcomer story: walked in off the street, made something in 10 minutes.

  • The outer ring is easy — Noisebridge is good at welcoming newcomers.
  • The core takes care of itself — deeply committed people find their way there.
  • The middle of the spiral is where guilds most often fail.

The middle is populated by people who have shown up more than once, want to do their part, and don't know how. Their good intentions get wasted by the absence of a golden path: visible next steps from "first time I made something here" all the way through to trusted and highly skilled. This path doesn't require bureaucracy — only culture: words, deeds, examples, expectations, and recognition when things go well.

Communications Channels

Give your guild a home on Discord. A dedicated channel means people can find each other, ask questions, and stay connected between meetups.

Resource Discovery & Networking

Guilds might discover ways to leverage resources outside of Noisebridge in ways that befit their interests — generating organic linkages between Noisebridge and other communities.

Growing Into Their Own Things

It could also be that an individual guild outgrows Noisebridge and decides to fill another space somewhere.

Credit as Infrastructure

Credit is how we coordinate trust at scale without central authority.

Credit answers three questions without a manager, a committee, or a gatekeeper:

  • Who can teach this?
  • Who can vouch for this?
  • Who is responsible for this continuing to exist?

That's not authority — that's coordination.

Without credit, we still answer those questions — just informally and unfairly. Through reputation. Through whispers. Through "ask around." That's not anarchism. That's an invisible hierarchy with no appeal process.

Credit makes those answers public, contestable, and transferable.

When we refuse to document who knows what — when we refuse to keep a ledger of achievement — we are gatekeeping by omission. When someone puts in 200 hours mastering a skill and we don't write it down anywhere, we've erased their achievement.

Jo Freeman wrote "The Tyranny of Structurelessness" and people love to post it like a gotcha against anarchist organizing. But Freeman wasn't arguing against anarchism — she was arguing against spaces that claim to have no structure while actually running on invisible, unaccountable power networks. The solution isn't less structure. It's intentional, visible, accountable structure.

Credit is not hierarchy.
Credit is infrastructure.

It's the scaffolding that lets the next person climb. It's the map that shows newcomers where to start.

See also: User:Nthmost/Create_More_Masters

See Also