Getting started
Before your first event, get three things in place: at least two leaders, a Luma calendar for the chapter under the DiagDebug account (we set it up for you), and a first topic worth an hour of people's evening. Don't wait for a perfect venue or a big list. A good virtual session with ten of the right people beats a half-full room.
Read the network policies and the code of conduct first. Both are short.
Cadence
The pattern that works: monthly online, quarterly in the room. Tight enough to stay useful, light enough that nobody burns out running it. The minimum is four events a year.
- Virtual, monthly. One hour, one topic, screen shares and real configs. This is the backbone that keeps the community warm between in-person nights.
- In person, quarterly. Where the relationships actually get built. Rotate venues around the metro so the same people aren't always the ones driving.
Whatever you pick, publish it and hold it. A predictable cadence is worth more than an ambitious one you can't keep.
Running an event
Luma is the system of record. Every event lives on your chapter's DiagDebug calendar, with the public guest list turned off. A workable run of show for an in-person night:
- 5:30Doors and foodPeople arrive, grab food, and settle in. No program yet.
- 6:00SessionA leader opens with the house rules and the code of conduct, then hands off to the speaker.
- 6:45Open Q&ANot recorded. If it turns into a roundtable, announce the Chatham House Rule.
- 7:00NetworkingThe real value. Keep it going as long as the room wants to.
Order food for about two thirds of your RSVPs. Free events lose a lot of registrants, and smaller ones lose more. Luma's reminders help; a personal note from a leader the day before helps more.
From Launching to Active
Get approved
Fill out the interest form and have the intro call. Once approved, your chapter is listed as Launching and gets its page and calendar.
Hold your first event
Virtual is fine. After it runs, tell the founders and the chapter is marked Active.
Keep a light record
Dates, topics, and rough attendance. Not a report, just enough that the next leader knows what worked.
House rules in practice
Two rules, and here's what keeping them looks like on the ground.
Do
- Open every session with the house rules and the code of conduct
- Welcome Fortinet and partner speakers for technical and roadmap talks
- Keep RSVPs in the chapter's Luma calendar, guest list hidden
- Announce the Chatham House Rule before any roundtable
Don't
- Hand an attendee list to a sales team, sponsor, or recruiter
- Let a sponsor pick the topic or the speaker
- Let a session turn into a product pitch or pricing talk
- Record Q&A or roundtables
Roles
- Leaders. Two to five per chapter. They pick topics and speakers, run the room, and keep the cadence. Customers make up at least half.
- Founders. Approve new chapters, keep the policies, and run the shared site and calendars.
- Advisory group. All chapter leaders, meeting quarterly to compare notes and shape what the network does next.
- Fortinet contact. Optional. Helps with venue, food, and speakers when a chapter asks.
Spinning up your chapter site
While a chapter is forming or launching, it has a page on the network site at diagdebug.com/chapters/[slug]/, which the network maintains. Once the chapter is Active it can have its own subdomain (for example pugetsound.diagdebug.com). Chapter sites link the network's base stylesheet, so they match the rest of the network out of the box, and add a small local stylesheet for anything specific to the chapter.
Every chapter site carries a How Meetings Work page. It's the clearest thing you can show a first-timer: how a session runs, what the house rules mean for them, and what to expect. The network provides a template so you aren't writing it from scratch.
Going inactive
If a chapter goes four months without an event, the founders check in and the leaders have 14 days to reply with a plan. If you know you can't keep going, say so sooner. The chapter is set to Inactive rather than left looking active, and nothing is deleted. Restarting later works the same way as starting.
Back to resources. To save a copy, use your browser's print function and choose "Save as PDF".