• GUARD disabled: ChanServ does not inhabit channel. /cs set #<channel> GUARD off
• SECURE enabled: Users without +o flag cannot gain operator status /cs set #<channel> SECURE on

• freenode channel modes

All channels shall have the following configuration set:

• Channel modes: +cCgnt-iljks set via /cs set <channel> MLOCK
• Channel ban list: +b $j:#freebsd (all channels inherit #freebsd banlist, see https://freenode.net/kb/answer/extbans (TODO)
  • Exception: #freebsd (by definition, it inherits its own ban list)

• #freebsd channel modes: Baseline + +Frf #freebsd-irc
• #freebsd-ops channel modes: Baseline + +i (and remove -i) #TODO

• #freebsd-commits and #freebsd-src channel modes: Baseline + -nc (and remove +nc)

All #freebsd* channels:

• SHOULD be registered by IRC Admin, in the standard configuration.

If they are not registered by IRC Admin,

• IRC Admin MUST have access to the channel for management purposes. (TODO)
• IRC Admin MUST be set as a successor (+s) to the channel in the access list (TODO)
• MUST have channel founders or managers that are active. (TODO)

We regularly obtain a list of channels matching #freebsd* from freenode staff (ask in #freenode) to audit channels within our namespace that have been registered with channel services (ChanServ)

Any channels found in the list not meeting the criteria above are marked for pruning and deregistered accordingly. Other reason classes for de-registration include:

• Defunct, stale, out-of-date.
• No longer in use, lack of activity
• Inappropriate, abusive, trolling or reputation affecting

Information that is used to determine channel state can include:

• Channel registration information: cs info #<channel>
  • Registration date
  • Last used date
  • Registrant (known/unknown)

• User activity (number of used currently, over time)
• Current topic or entry message