opendev
/
system-config
Code Issues Proposed changes

Explain when to add admins and ops with accessbot 

We're happy for teams to manage their individual IRC channel access
lists through our accessbot configuration if they want, so explain
the situations in which they might choose to add channel ops or
admins, and the differences between them.

Change-Id: I4ae4463fe5017176d2d93cbaac6820fe11350899
This commit is contained in:
Jeremy Stanley 2021-06-03 19:18:26 +00:00
parent c6137dce82
commit 05c9b06f24
1 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/source/irc.rst
View File

@ -243,14 +243,19 @@ Accessbot
=========
Accessbot defines access that should apply to all channels. Teams can add new
channel to accessbot/channels.yaml and optionally set additional channel admins
or ops, or specific mode overrides:
channels to accessbot/channels.yaml and optionally set additional channel
admins or ops, or specific mode overrides.
For typical day-to-day actions like updating channel topics or banning
disruptive users, volunteer ops are sufficient. If the team wishes to retain
deeper control over channel settings which aren't handled via accessbot, then
having some volunteer admins can occasionally be useful. In either case, our
global volunteers are also happy to assist with any of these activities, so
feel free to ask for help in the #opendev channel.
Accessbot's configuration is in :config:`accessbot/channels.yaml`
Example:
::
Example::
- name: foo
mode: +bar