You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/irc.md
+4-13
Original file line number
Diff line number
Diff line change
@@ -2,12 +2,12 @@
2
2
title: General Chat and IRC
3
3
---
4
4
5
-
This page goes over General Chat and IRC/Matrix general information and etiquette.
5
+
This page goes over General Chat and IRC general information and etiquette.
6
6
7
7
!!! note
8
-
IRC (libera.chat) and Matrix are no longer bridged by default. You will find that if you join the Matrix channels, they are quiet. It is recommended that you join us via [Mattermost](https://chat.rockylinux.org) or via [IRC](https://libera.chat).
8
+
IRC (libera.chat) and Matrix are no longer bridged. You will find that if you join the Matrix channels, you will be asked to join us in other ways. It is recommended that you join us via [Mattermost](https://chat.rockylinux.org) or via [IRC](https://libera.chat).
9
9
10
-
IRC and Matrix are common communication tools used in the open source community. Several channels of Mattermost, Libera IRC channels, and a matrix space are bridged together to ensure the community can communicate effectively and not be splintered. The Rocky Linux teams manage and maintain the mattermost channels and the various Libera IRC channels such as `#rockylinux` and `#rockylinux-social`. A list of our channels can be found in `Bridge Information` on the left hand side of this wiki page.
10
+
IRC is a common communication tool used in the open source community. Several channels of Mattermost and Libera IRC channelsare bridged together to ensure the community can communicate effectively and not be splintered. Rocky Linux Infrastructure and other teams manage and maintain the mattermost channels and the various Libera IRC channels such as `#rockylinux` and `#rockylinux-social`. A list of our channels can be found in `Bridge Information` on the left hand side of this wiki page.
11
11
12
12
More information about Libera can be found [here](https://libera.chat).
13
13
@@ -28,7 +28,7 @@ More information about Libera can be found [here](https://libera.chat).
28
28
Current mappings are below. Note that this is not an all inclusive list.
29
29
30
30
!!! note
31
-
As matrix and IRC are no longer briged, the Matrix section has been removed.
31
+
As matrix and IRC are no longer briged, the Matrix section has been removed. There are no plans to bridge Matrix. If you wish to request or provide any kind of knowledge or help in maintaining a bridge, please [file a ticket](https://git.resf.org/infrastructure/meta/issues).
@@ -159,15 +159,6 @@ Once you have registered and you are identified with `NickServ`, you can type `/
159
159
160
160
Note that subsequent logins will require you to identify. `/msg nickserv identify password` will help you to ensure you don't get locked out of the `#rockylinux*` channels.
161
161
162
-
### Matrix
163
-
164
-
!!! note
165
-
Matrix and IRC is no longer bridged. This means to have communication with the Rocky Linux community, you are recommended to join us on Mattermost or Libera IRC.
166
-
167
-
If you are a user of Matrix, most of the above still applies to you. You may need to login through the bridge on matrix to login with NickServ on Libera. After that, you will be able to communicate in the `#rockylinux*` channels through your matrix client.
168
-
169
-
~~The Rocky Linux matrix space can be joined [here](https://matrix.to/#/!rHvPOeKWNBOYSKTiBr:matrix.org?via=matrix.org).~~
170
-
171
162
### IRC Cloaks for libera.chat network
172
163
173
164
Cloaks allow you to show your association with the Rocky Linux project and protect your hostname from being seen from others. Cloaks can be received from a project or just by the network upon request.
Copy file name to clipboardexpand all lines: docs/special_interest_groups/index.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ We expect SIGs to satisfy some basic requirements, such as:
24
24
* The group should be related to Rocky Linux, a use-case for Rocky Linux or Enterprise Linux, or related to Enterprise Linux as a whole
25
25
* There must be feedback and control into the Rocky Linux community
26
26
* All communication as to the work of the SIG should be public - Some matters may have to be private, and as such should be out of band
27
-
* It is expected that each SIG will have a public channel as `SIG/name` in mattermost. Optionally an IRC or Matrix channel can also be assigned.
27
+
* It is expected that each SIG will have a public channel as `SIG/name` in mattermost. Optionally an IRC channel can also be assigned.
28
28
* Code produced within the SIG must be compatible with a FOSS license presently used by Rocky Linux - If a new license is wanted, consult with Release Engineering/Core or the `~Legal` channel in mattermost.
29
29
* All documentation and information of the SIG should be on a wiki produced in the [RESF Git Service](https://git.resf.org).
30
30
* All documentation produced within the SIG must be a compatible documentation license
@@ -47,7 +47,7 @@ The following rules apply for SIG membership:
47
47
* Mailing lists of SIGs are open and can be joined freely
48
48
* SIG members are appointed/approved by SIG sponsors/leaders - The sponsors/leaders typically have write permissions to relevant wikis and git repos
49
49
* SIG sponsors/leaders may be asked to be a mailing list moderator
50
-
* SIG channels will be public under a name such as `SIG/name` with an optional IRC and Matrix channel to be bridged.
50
+
* SIG channels will be public under a name such as `SIG/name` with an optional IRC channel to be bridged.
51
51
* Optionally: define if work with CentOS Stream will be applicable for the SIG
0 commit comments