Skip to content
DiagDebug

Resources / Network policies

Network policies

The rules every DiagDebug chapter follows. They're short on purpose, and most are borrowed from user group networks that have been doing this for years.

Version 3. Last updated 2026-11-05.

1. Leaders

  • Every chapter has two to five leaders, so no chapter depends on one person.
  • Customers, meaning people who run Fortinet at their own organization, must equal or outnumber leaders who work for Fortinet or a Fortinet partner.
  • Fortinet and partner employees are welcome as co-leaders.
  • Leaders are listed by name on their chapter page and use diagdebug.com email addresses for chapter business, never a work address.
  • Rotating leaders every two to three years is encouraged, not required.

2. Meetings

  • All chapter meetings are free and open to anyone who works with Fortinet products.
  • Each chapter hosts at least four events a year. Virtual events count. Once a chapter is Active, at least two of those are in person.
  • Events are published on the chapter's DiagDebug Luma calendar, so the calendar and its subscribers stay with the chapter if leaders change.

3. Content

  • Sessions are technical. No sales pitches, pricing discussions, or recruiting.
  • Fortinet and partner speakers are welcome for technical deep dives and roadmap sessions.
  • Chapter leaders choose topics and speakers. Sponsors do not.
  • A session can run under the Chatham House Rule when the leader announces it at the start: use what you hear, but don't say who said it. Roundtables and feedback sessions always run this way.
  • Talks may be recorded only with the speaker's consent. Q&A and roundtables are never recorded.

4. Attendee data

  • RSVPs live in DiagDebug's Luma calendars. Public guest lists are turned off on every event.
  • Attendee lists are never given to sales teams, sponsors, recruiters, or marketing lists, Fortinet's included.
  • Only chapter leaders and the founders can see a chapter's guest list.

5. Sponsors

  • Sponsors can provide venue, food, or giveaways.
  • In return they get logo recognition and a welcome of under two minutes.
  • Sponsors don't choose topics or speakers and don't receive attendee lists.

6. Chapter status

FormingPeople in this metro are interested. Leaders wanted.
LaunchingLeaders approved and the first event is being scheduled.
ActiveHolding events on a regular cadence.
InactiveNo event in four months, or the leaders have stepped away.

7. Going inactive and restarting

  • If a chapter goes four months without an event, the founders check in with its leaders, who have 14 days to reply with a plan.
  • With no reply or no plan, the chapter is marked Inactive. Nothing is deleted, and its calendar and subscribers are kept.
  • Restarting an inactive chapter works the same way as starting a new one.

8. Names and brand

  • Chapters are named "DiagDebug [Metro]," for example DiagDebug Puget Sound.
  • Chapter logos come from the DiagDebug brand kit and are approved by the founders before use.
  • Contact the founders before naming or announcing a new chapter in public, so two groups don't start in the same city.

9. Changes to these policies

The founders can update these policies after asking chapter leaders for input. Changes are posted on this page with the date.

Back to resources. To save a copy, use your browser's print function and choose "Save as PDF".

Ready to start one?

The form is short and every one gets a reply within a week.

Start a chapter