Start a chapter
Bring DiagDebug to your region
Chapters aren't franchises. There's no contract and no fee. Here's how one actually gets recognized, what the network hands you, and what we'll ask of you in return.
How recognition works
Three steps. The middle one is the only hard one, and it's worth knowing that before you fill in the form.
Interest application
Tell us who you are, what metro you're in, and why you want to run this. We're checking two things: that you're a practitioner rather than a vendor employee, and that you're good with the trust rules.
Three-event probationary period
You run three events on a regular cadence under the charter. This is the part that takes actual work, and it's where you find out whether the room is there.
Steering committee vote
The steering committee votes. If it goes your way the chapter is recognized, and that shows up in the directory and in this site's git history where anyone can read it.
What DiagDebug provides
- The charter template and the chapter playbook
- The DiagDebug brand kit
- A page on diagdebug.com from day one, and your own subdomain (yourmetro.diagdebug.com) once you're recognized
- A Luma calendar under the network account, and help running it
- Venue and food, and Fortinet engineers in the room when you want them
What we ask of you
- A chair who's a practitioner, not a Fortinet employee
- The three trust rules at every meeting, no exceptions
- A real cadence. One event and then silence doesn't count
- Three events before the vote, without trying to skip ahead
Chapter interest application
This starts a conversation and nothing more. Neither side is committing to anything yet. We read every one that comes in and reply by email.
Submitting opens your mail client with the application filled in, so you send it yourself and keep a copy in your sent items. Nothing is posted to a third party. If your mail client does not open, you will get the text to copy instead.