From Software Heritage Wiki
Revision as of 08:50, 12 April 2021 by Vlorentz (talk | contribs) (IRC access list: add command to op yourself)
Jump to: navigation, search

IRC channels

The following channels have been registered on the Freenode network for Software Heritage usage.

  • #swh-devel: public development discussions
  • #swh-team: private discussions of the core team
  • #swh-sysadm: operations team discussions/bots
  • #softwareheritage: general discussions about the project (currently unused)
  • #swh: ditto, in case we end up preferring the short version

If you use IRC, consider joining the channels.

If you don't use IRC directly, you can still join our chat channels from your web browser via a Matrix bridge by clicking on the channel names in the list above. You will be asked to create a Element account if you don't have one yet.

IRC authentication

You should register their nick with NickServ using:

/nick <USERNAME>
/msg nickserv register <PASSWORD> <EMAIL>

You will then receive an e-mail containing a link to activate you account. After doing so, you need to configure your client to auto-authenticate. The recommended way of doing that is using SASL authentication.

For Weechat:

/set irc.server.freenode.sasl_username <USERNAME>
/set irc.server.freenode.sasl_password <PASSWORD>

For matrix, the relevant docs is here:

Freenode also supports authentication via TLS client certificates.

Matrix bridge

For the Matrix bridge (relevant docs here), you first need to choose you IRC nick by sending this to the bridge appservice:

/msg !nick <USERNAME>

Then send this command to NickServ to register your account:

/msg register <PASSWORD> <EMAIL>

You will then receive an e-mail containing a link to activate you account. You can then identify using:

/msg identify <PASSWORD>

Then, ask the IRC bridge appservice to remember your password so that you get identified automatically:

/msg !storepass <USERNAME>:<PASSWORD>

IRC access list

To auto-voice people with a registered nick (only doable by people with +fA access modes will be able to do it), add them to the channel access list:

/msg chanserv access #swh-devel add zack +V

If you already have the right (+o ChanServ flag), you can make yourself an operator, with:

/msg chanserv OP #swh-devel