Network policies
The rules every chapter follows: how many leaders, how often to meet, what happens to attendee data, how sponsors work, and when a chapter goes inactive.
Resources
Three short documents, readable right here. Nothing to download and no email wall, because rules you can't read before you sign up aren't worth much.
The rules every chapter follows: how many leaders, how often to meet, what happens to attendee data, how sponsors work, and when a chapter goes inactive.
What's expected of everyone at a DiagDebug event, what isn't okay, and how to report a problem. One page, meant to be posted at events.
How to actually run a chapter: cadence, events on Luma, the run of show, and what the house rules look like on a Tuesday night when someone turns up wanting to demo something.
Need a copy to hand off? Open any page and print it to PDF; the pages are styled for it. The brand kit (logo and color tokens) is still being packaged up, so email hello@diagdebug.com and we'll send what exists.
Read the policies, then fill out the short form. Every one gets a reply within a week.
Start a chapter