The Chapter Playbook

A chapter is three or more people in one city who do this work, meeting regularly enough that they recognise each other.

That's the whole definition. Everything below is scaffolding to make the first three meetups happen, because the first three are the only hard ones.

Before you start

You need three people, not thirty. The most common way a technical meetup dies is starting too big — booking a venue for fifty, getting eleven, and quietly not scheduling another. Six people around a table having a real conversation is a successful first event. A half-empty auditorium isn't.

You don't need a company sponsor. A café, a co-working common area, or someone's office after hours is fine. Sponsorship introduces obligations early, and those obligations shape the chapter before it knows what it is.

You don't need to be an expert. You need to be the person who sends the message. Every community organizer discovers this and most never quite believe it.

The first event

Format that works, roughly two hours:

1. Introductions, ten minutes. Name, what you deploy, what is hard about it right now. That last part is what makes people talk.
2. One person tells one real story, twenty minutes. A deployment that went badly is better than one that went well. No slides required.
3. Open discussion, sixty minutes. This is the actual event. The first two parts exist to start it.
4. Fix the next date before anyone leaves. Not "we should do this again." An actual date in an actual calendar. This single step is the difference between a chapter and a one-off.

Topics that reliably produce good discussion at a first meetup:

• The worst blocker you've hit that wasn't technical
• How your organization decides what stays bespoke and what becomes product
• Where the framework doesn't match your job
• What you wish someone had told you in your first ninety days

That third one is genuinely useful to us. Chapter disagreement with the framework is one of the main ways it improves.

Keeping it alive

Same day of the month. Second Thursday. Don't make people re-learn the schedule.

Rotate who speaks after event two. A chapter with one voice becomes that person's audience, and it ends when they get busy.

Write it down afterwards. Even three paragraphs. Post it as an article — it's how someone in another city discovers there's a chapter worth starting in theirs.

Let it be small. A chapter of eight consistent people is more valuable than one with two hundred on a list and eleven in a room.

Recognition

There's no formal ambassador programme yet, and inventing one before there are chapters would be theatre. What exists now:

• Your chapter and your name on the chapters page
• Commit rights on the repository after two events
• A say in the chapter council once there are three active chapters — see Governance

When there are enough chapters for a real programme, the people running chapters will design it. That's the correct order.

What you get from us

• This playbook, and someone to ask
• Your chapter page and event listings on the site
• Slides and an intro deck you can adapt, in the repository
• Introductions to other chapter leads as there are others to introduce you to

What we can't yet offer: money, venues, or swag. When that changes it will be written here rather than promised in a conversation.

The path

Propose → add your city to content/chapters/ with status: proposed Forming → you have a date for a first event Active → you've run two