github.com/nullne/docker@v1.13.0-rc1/project/IRC-ADMINISTRATION.md (about) 1 # Freenode IRC Administration Guidelines and Tips 2 3 This is not meant to be a general "Here's how to IRC" document, so if you're 4 looking for that, check Google instead. ♥ 5 6 If you've been charged with helping maintain one of Docker's now many IRC 7 channels, this might turn out to be useful. If there's information that you 8 wish you'd known about how a particular channel is organized, you should add 9 deets here! :) 10 11 ## `ChanServ` 12 13 Most channel maintenance happens by talking to Freenode's `ChanServ` bot. For 14 example, `/msg ChanServ ACCESS <channel> LIST` will show you a list of everyone 15 with "access" privileges for a particular channel. 16 17 A similar command is used to give someone a particular access level. For 18 example, to add a new maintainer to the `#docker-maintainers` access list so 19 that they can contribute to the discussions (after they've been merged 20 appropriately in a `MAINTAINERS` file, of course), one would use `/msg ChanServ 21 ACCESS #docker-maintainers ADD <nick> maintainer`. 22 23 To setup a new channel with a similar `maintainer` access template, use a 24 command like `/msg ChanServ TEMPLATE <channel> maintainer +AV` (`+A` for letting 25 them view the `ACCESS LIST`, `+V` for auto-voice; see `/msg ChanServ HELP FLAGS` 26 for more details). 27 28 ## Troubleshooting 29 30 The most common cause of not-getting-auto-`+v` woes is people not being 31 `IDENTIFY`ed with `NickServ` (or their current nickname not being `GROUP`ed with 32 their main nickname) -- often manifested by `ChanServ` responding to an `ACCESS 33 ADD` request with something like `xyz is not registered.`. 34 35 This is easily fixed by doing `/msg NickServ IDENTIFY OldNick SecretPassword` 36 followed by `/msg NickServ GROUP` to group the two nicknames together. See 37 `/msg NickServ HELP GROUP` for more information.