GNOME IRC Network

The GNOME Community uses IRC as one of its main mediums. The network that hosts all the GNOME channels is called GIMPNet. We expect all the users joining the network to respect the following general rules:

  1. Respect the GNOME Code of Conduct.

  2. No bots are allowed to lurk on any of the GNOME channels without explicit authorization from the GNOME Sysadmin Team.

Support channels

Your points of contact for reporting issues or other related queries are:

  1. #opers, for a direct chat with the Operators Team.
  2. https://bugzilla.gnome.org/enter_bug.cgi?product=sysadmin&component=IRC, for reporting a bug at GNOME's Bugzilla.

Connection details

The GNOME IRC network (irc.gnome.org) or GIMPNet is composed by the following servers:

  1. irc.eagle.y.se
  2. irc.acc.umu.se
  3. irc.gimp.ca
  4. irc.poop.nl

The following capabilities are available on the servers:

  1. IRC services (NickServ, ChanServ)

  2. IPv6 support (on the irc.acc.umu.se and irc.poop.nl servers)
  3. SSL

The servers are reachable on the following ports:

  1. 6697 (for ssl connections)
  2. 6667 (for non-ssl connections)

Servers are using a certificate having one DN (currently being the FQDN of the host) so connecting to either the irc.gnome.org or irc.gimp.org DNS entries with SSL verification turned on will result in an error as the DN won't match. That is expected, in case you are willing to verify the SSL certificate (on XChat make sure the 'Accept invalid certificate' flag is not set, on irssi make sure '-ssl -ssl_verify' is appended to your connect command) make sure to connect to a single server on the list above with the proper flags set.

Registering your nickname

Open a chat window with the NickServ services user with either /msg or /query, then:

register password email

Once done you should be able to identify yourself with:

identify nickname password

Make sure to identify to services before trying to register a channel. You need to be identified for gaining OP or other privileged statuses. Further details and a list of the available commands of NickServ can be retrieved by issuing either help or help command.

Registering a channel

Open a chat window with the ChanServ services user with either /msg or /query, then:

register channel description

Once the channel has been registered your user will be set as the founder of that channel with all the privileges that corresponds to that status. Further details and a list of the available commands of ChanServ can be retrieved by issuing either help or help command.

If you are a GNOME module maintainer or you lead a certain team or group and are interested in registering a channel through ChanServ please do so. Please DO NOT abuse the registration of new channels and please get in touch with the Operators Team for requesting the cancellation of a registered channel / nickname in case an abuse has happened.

Grant OPerator status on a specific channel

Open a chat window with the ChanServ services user with either /msg or /query, then:

access #channelname add nickname 5

Other details: bugbot (aka supybot + Bugzilla plugin, previous Services IRC Bot)

Bugbot allows bug IDs to be auto-expanded into full URLs and descriptions directly on a channel as in:

<av> bug #745525
<bugbot> Bug https://bugzilla.gnome.org/show_bug.cgi?id=745525 normal, Normal, ---, sysadmin-maint, NEW , Bugzilla on RHEL7

Additionally it supports sending bug notifications for a certain GNOME module on a specific channel as in:

<bugbot> New sysadmin bug 749481 filed by marek.sebera@gmail.com.
<bugbot> Bug https://bugzilla.gnome.org/show_bug.cgi?id=749481 sysadmin, major, Normal, ---, sysadmin-maint, NEW , Security of redirect to mirrors

If you are interested in having bugbot on your channel, please request the addition of the bot by filing a bug HERE. Make sure to list what capabilities are you interested in and eventually the module name bugbot should be watching.

Other details: GNOMie (aka MeetBot, previous Services IRC Bot)

If you are interested in having MeetBot managing meetings on your channel, please request the addition of the bot by filing a bug HERE. Instructions on how to run a meeting are available HERE.

Other details: Commits Bot

The GNOME Infrastructure currently hosts an istance of KGB-Bot. Its functionalities are very similar to the now dead CIA.vc project. KGB-Bot is configured through a post-receive hook which triggers a push notification over the IRC Bot, the consequence is a little notification on the pre-configured IRC channel with a little summary of what was done on the relevant git repository together with several other information like the author, commit ID of the change.

If you are interested in receiving notifications for a specific GNOME module on a specific IRC channel hosted at irc.gnome.org, open a request by opening a bug.

Other details: logbot

The GNOME Infrastructure thanks to Byron Jones and his logbot allows interested channel owners to log conversations on a specific channel.

Channel logs for the irc.gnome.org network are currently available HERE. If you are interested in having your channel logged, please e-mail Byron directly at <byron AT glob DOT com DOT au>. When logging is enabled (you should notice logbot hanging out on the channel when this has happened) you should make sure the topic of the channel reflects the fact all the conversations are being logged and publicly available. You should also make sure the public URL of the logs is shown on the topic itself. (i.e "The channel is being logged: http://logs.glob.uno/?c=gnome%23gnome")

Channel logging is particularly useful for support channels where existing contributors might be interested in not repeating themselves when the same question is asked several times by newcomers.

Historical information

Announcement mails for the network switch happened on the 14th of May, 2015:

  1. https://mail.gnome.org/archives/gnome-announce-list/2015-May/msg00005.html

  2. https://mail.gnome.org/archives/gnome-announce-list/2015-April/msg00010.html

Previous Sysadmin/IRC Wiki page is archived HERE.

Sysadmin/IRC (last edited 2015-07-22 14:56:39 by AndreaVeri)