View source for Infrastructure/IRC

As a large amount of communication between contributors takes place over IRC, a number of services are available to the community to facilitate interaction. KDE currently uses the [https://freenode.net/ Freenode] network to host official channels and a list of commonly frequented channels is published on Userbase.

== Official KDE IRC Channels ==

Official channels start with <code>#kde-</code>, and due to the age of KDE however we also have some legacy channels that do not meet the Freenode guidelines. In the future non <code>#kde-</code>* channels may be removed/redirected, all new channels need to start with <code>#kde-</code>

KDE IRC channels are managed by the '''KDE Freenode Group Contact''', currently Kenny Duffus (<code>seaLne</code>). To minimise any problems in the future, with people leaving KDE, official channels are owned by a special <code>KDE_GC</code> account. If you manage an existing channel that <code>KDE_GC</code> doesn’t have <code>+F</code> permissions on please file a [https://go.kde.org/u/systickets ticket] and we can help you give it access.

All KDE projects are entitled to a <code>#kde-</code>* IRC channel. If you represent a project and would like a new channel please file a [https://go.kde.org/u/systickets ticket].

Normally each channel manages itself with established members of the project having “Ops” (Operator Permissions), extra permissions for managing the channel. However sometimes there are problems when no Op in the channel is around. In this case you can try asking for help in <code>#kde-ops</code>, where members of the [[Community%20Working%20Group|https://ev.kde.org/workinggroups/cwg.php]] and people with Ops in all the official channels hang about and are happy to help. This is also a good place if you are a new KDE channel Op and need some help with the use of the freenode network.

In case of urgent need and no KDE channel Ops around, e.g. when some spamming bot entered the channel, there are also the Freenode list staffers. Query their names with the command <code>/stats p</code> and then ping them about the issue.

== Commit notifications ==

To allow contributors to follow the development of KDE projects in real time, a bot known as <code>pursuivant</code> will announce all commits which are published in either Git or Subversion repositories (with the exception of scratch and clone repositories) on KDE infrastructure. This is done for all commits in and <code>#kde-commits</code> but can also be done for a certain subset of commits in other channels.

This subset is created by defining rules in the bot configuration, which use regular expressions to determine if a match exists. Matches can cover the name of the repository, the path changed in the repository and the branch altered. It is also possible for the bot to ignore silent commits, depending on the particular rule.

The repository where the source code for the bot and the configuration is stored is located at <code>sysadmin/irc-notifications.git</code> on <code>git.kde.org</code>. The configuration can be found at <code>gateway/notifications.cfg</code> and can be altered by all holders of a KDE developer account.

= RSS feed announcement =

To allow monitoring of websites within the KDE umbrella, it is also possible to get notifications of changes to RSS feeds announced in particular IRC channels. This service is primarily offered to monitor posts made on the [https://forum.kde.org/ KDE Community Forums] at this time.

Channel operators should file a [https://go.kde.org/u/systickets ticket] to request setup of these notifications.

== Cloak ==

A cloak provides some privacy by hiding the host you are connecting to IRC from and also shows that you are a member of the KDE community. Normal cloaks are of the form <code>kde/developer/identity_username</code>, but developer can be replaced with something more suitable. Members of KDE e.V. may ask for a <code>kde/identity_username</code> cloak.

As a registered project, KDE is able to offer cloaks to KDE contributors. Those people who would like to request a cloak should file a [https://go.kde.org/u/systickets ticket]. It is a requirement that your nick be registered in order for you to receive a cloak.

== BNC ==

Due to the global spread of the KDE community it can be desirable to keep a constant presence on IRC. To provide for this, a bouncer (BNC account) is operated to allow for community members to keep a stable, always on presence.

If you wish to request an account on the BNC, please file a [https://go.kde.org/u/systickets ticket], making sure to include your current Freenode nick. It is required that the nick is registered. More details about the configuration of your bouncer can be found at the [http://community.kde.org/Sysadmin/BNC KDE Community Wiki]

== Matrix Bridge ==

[http://community.kde.org/Matrix Matrix] can be used as IRC bouncer thanks to the native IRC bridge.

== Telegram Bridge ==

Many members of the community prefer using Telegram over IRC. KDE does not register or maintain Telegram groups as a matter of policy, but does provide a service to bridge Telegram groups to IRC channels, through a bot called <code>IrcsomeBot</code>.

To bridge your Telegram group to an IRC channel, please file a [https://go.kde.org/u/systickets ticket] with the name of the Telegram group and the name of the IRC channel. Once we have added the pair to our bot, a nick called <code>IrcsomeBot</code> will join your IRC channel. Invite the <code>@IrcsomeBot</code> bot to your Telegram group, and say something in the group to complete the setup.

It is strongly recommended to bridge Telegram groups to their counterpart IRC channels, because IRC is the only officially supported and endorsed method of communication by the system administrators. For non offtopic channels, actively refusing to use IRC in favour of keeping the entire conversation on Telegram may be found in violation of the [https://manifesto.kde.org/ KDE Manifesto], and will be considered grounds for ejection from the KDE Community.