• 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: /mode <channel> +bq $j:#freebsd $j:#freebsd (all channels inherit #freebsd banlist, see freenode/extbans (TODO)
  • Note: +q $j:<#channel> can be set, but doesn't work (but probably should, allowing inheriting quiet lists separately from / in addition to banlists)
  • 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-pulse channel modes: Baseline + -nc (remove +nc), so bots can message channel without joining and with colours for event formatting

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 audit and review channels registered within our namespace (#freebsd*). Any channels found in the list not meeting the criteria above are marked for pruning and deregistered accordingly.

• List channels: /msg alis list *#freebsd*

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