general updates to irc page

rocky-linux · Jan 30, 2024 · 50332a8 · 50332a8
1 parent 95cf535
commit 50332a8
Show file tree

Hide file tree

Showing 2 changed files with 43 additions and 34 deletions.
diff --git a/docs/irc.md b/docs/irc.md
@@ -28,32 +28,30 @@ More information about Libera can be found [here](https://libera.chat).
 Current mappings are below. Note that this is not an all inclusive list.
 
 !!! note
-    Since matrix and IRC are no longer bridged, the mapping is no longer 1:1.
-
-| IRC                         | Mattermost                                                                         | Matrix (no longer bridged)                                                          |
-|-----------------------------|------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|
-| #rockylinux                 | [~general](https://chat.rockylinux.org/rocky-linux/channels/town-square)           | [Rocky Linux General / Support](https://matrix.to/#/#rockylinux-support:matrix.org) |
-| #rockylinux-devel           | [~development](https://chat.rockylinux.org/rocky-linux/channels/development)       | [Rocky Linux Development](https://matrix.to/#/#rockylinux-development:matrix.org)   |
-| #rockylinux-docs            | [~documentation](https://chat.rockylinux.org/rocky-linux/channels/documentation)   |                                                                                     |
-| #rockylinux-infra           | [~infrastructure](https://chat.rockylinux.org/rocky-linux/channels/infrastructure) | [Rocky Linux Infrastructure](https://matrix.to/#/#rockylinux-infra:matrix.org)      |
-| #rockylinux-legal           | [~legal](https://chat.rockylinux.org/rocky-linux/channels/legal)                   | [Rocky Linux Legal](https://matrix.to/#/#rockylinux-legal-bridge:matrix.org)        |
-| #rockylinux-security        | [~security](https://chat.rockylinux.org/rocky-linux/channels/security)             |                                                                                     |
-| #rockylinux-sig-altarch     | [~altarch](https://chat.rockylinux.org/rocky-linux/channels/altarch)               | [Rocky Linux SIG AltArch](https://matrix.to/#/#rockylinux-sig-altarch:matrix.org)   |
-| #rockylinux-sig-kernel      | [~sig-kernel](https://chat.rockylinux.org/rocky-linux/channels/sig-kernel)         | [Rocky Linux SIG Kernel](https://matrix.to/#/#rockylinux-sig-kernel:matrix.org)     |
-| #rockylinux-social          | [~off-topic](https://chat.rockylinux.org/rocky-linux/channels/off-topic)           | [Rocky Linux Social](https://matrix.to/#/#rockylinux-social:matrix.org)             |
-| #rockylinux-testing         | [~testing](https://chat.rockylinux.org/rocky-linux/channels/testing)               | [Rocky Linux Testing](https://matrix.to/#/#rockylinux-testing-channel:matrix.org)   |
-| #rockylinux-www             | [~web](https://chat.rockylinux.org/rocky-linux/channels/web)                       |                                                                                     |
-
-The Rocky Linux matrix space can be joined [here](https://matrix.to/#/!rHvPOeKWNBOYSKTiBr:matrix.org?via=matrix.org), which will provide easier access to the Rocky Linux matrix channels.
+    As matrix and IRC are no longer briged, the Matrix section has been removed.
+
+| IRC                         | Mattermost                                                                         |
+|-----------------------------|------------------------------------------------------------------------------------|
+| #rockylinux                 | [~general](https://chat.rockylinux.org/rocky-linux/channels/town-square)           |
+| #rockylinux-devel           | [~development](https://chat.rockylinux.org/rocky-linux/channels/development)       |
+| #rockylinux-docs            | [~documentation](https://chat.rockylinux.org/rocky-linux/channels/documentation)   |
+| #rockylinux-infra           | [~infrastructure](https://chat.rockylinux.org/rocky-linux/channels/infrastructure) |
+| #rockylinux-legal           | [~legal](https://chat.rockylinux.org/rocky-linux/channels/legal)                   |
+| #rockylinux-security        | [~security](https://chat.rockylinux.org/rocky-linux/channels/security)             |
+| #rockylinux-sig-altarch     | [~altarch](https://chat.rockylinux.org/rocky-linux/channels/altarch)               |
+| #rockylinux-sig-kernel      | [~sig-kernel](https://chat.rockylinux.org/rocky-linux/channels/sig-kernel)         |
+| #rockylinux-social          | [~off-topic](https://chat.rockylinux.org/rocky-linux/channels/off-topic)           |
+| #rockylinux-testing         | [~testing](https://chat.rockylinux.org/rocky-linux/channels/testing)               |
+| #rockylinux-www             | [~web](https://chat.rockylinux.org/rocky-linux/channels/web)                       |
 
 ## General
 
-It is likely that there will be a lot of boxes running Rocky Linux and thus there will be many folks who will occasionally look for help in the main Rocky IRC channel `#rockylinux` or `~General` on mattermost, typically on what the distribution ships. It is important to maintain focus on a Rocky Linux specific matter as the channel does not have the ability nor bandwidth to support non-Rocky Linux topics.
+It is likely that there will be a lot of boxes running Rocky Linux and thus there will be fair amount of people who will occasionally look for help in the main Rocky Linux Mattermost `~General` channel or Rocky Linux main IRC channel `#rockylinux`, typically on what the distribution ships. It is important to maintain focus on a Rocky Linux specific matter as the channel typically does not have the ability nor bandwidth to support non-Rocky Linux topics.
 
 Here is a general rule of thumb:
 
-* **Unless a question or thread is about an application or program supplied by Rocky, it is likely off topic** (see the exceptions section)
-* **Discussing the usage of non-Rocky packages or problems (which the Rocky project has no control over) are off-topic** (see [exceptions](#exceptions))
+* **Unless a question or thread is about an application or program supplied in Rocky Linux, it is likely off topic** (see the exceptions section)
+* **Discussing the usage of non-Rocky Linux packages or problems (which the Rocky Linux project has no control over) are off-topic** (see [exceptions](#exceptions))
 * **Polling for general usage/preferences or other opinion matter is considered off-topic**
 * **Requesting support or discussing the usage of other distributions is considered off-topic** (more info [here](#what-is-not-supported))
 
@@ -63,11 +61,15 @@ There are cases where it may do more harm than good to deny or to not provide as
 
 * **If the question is related to software in EPEL**
 
-    * If a problem is reproducible or its an issue out of our control, it is recommended to go `#epel`
+    * If a problem is reproducible or its an issue out of our control, it is recommended to go `#epel` or [EPEL's Matrix Channel](https://matrix.to/#/#epel:fedoraproject.org).
 
 * **If the question is related to drivers from elrepo or rpmfusion**
 
-    * It is common for users to be using hardware that is either not supported in a current Rocky release or needs a better driver (e.g., nouveau -> nvidia). Providing general assistance for getting such drivers should be considered semi-topical. Most users will support one another in this scenario. elrepo volunteers will be in the channel as well assist users. Other issues should go to `#elrepo` or where topical, such as their [Bug Tracker](https://elrepo.org/bugs).
+    * It is common for users to be using hardware that is either not supported in a current Rocky Linux release or needs a better driver (e.g., nouveau -> nvidia). Providing general assistance for getting such drivers should be considered semi-topical. Most users will support one another in this scenario. elrepo volunteers will be in the channel as well assist users. Other issues should go to `#elrepo` or where topical, such as their [Bug Tracker](https://elrepo.org/bugs).
+
+* **If the question is related to CentOS Stream as it pertains to Rocky Linux**
+
+    * There may be cases where discussion of CentOS Stream may occur. This typically happens when trying to determine behavior changes or what it may take to make a behavior change upstream that would then affect Rocky Linux. These should be treated as semi-topical. Note that CentOS Stream specific support may be found in `#centos-stream` on Libera IRC and channels within Matrix if they exist.
 
 ### What is not supported?
 
@@ -77,8 +79,8 @@ There are cases where it may do more harm than good to deny or to not provide as
     * This includes, but is not limited to RHEL, OEL, Alma, Springdale, SL
 
 * **[Broken "V" Servers](#broken-v-servers)**
-* **Old minor/point releases of Rocky Linux**
-* **Upgrades or upgraded Rocky Linux systems (e.g., upgrading 8 to 9)**=
+* **Old minor/point releases of Rocky Linux (See our [version policy](rocky/version.md))**
+* **Upgrades or upgraded Rocky Linux systems (e.g., upgrading 8 to 9)**
 * **Upgrades of the default python version (e.g. python 3.6 to 3.9 or python 3.9 to 3.11)**
 * **Politics or Profanity**
 * **Distro X is better/worse than Rocky**
@@ -89,7 +91,7 @@ There are cases where it may do more harm than good to deny or to not provide as
 
 ## Etiquette
 
-This section goes over general etiquette expected of all users of Mattermost or IRC/Matrix on the bridge.
+This section goes over general etiquette expected of all users of Mattermost or IRC.
 
 ### How to ask questions
 
@@ -159,9 +161,12 @@ Note that subsequent logins will require you to identify. `/msg nickserv identif
 
 ### Matrix
 
+!!! note
+    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.
+
 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.
 
-The Rocky Linux matrix space can be joined [here](https://matrix.to/#/!rHvPOeKWNBOYSKTiBr:matrix.org?via=matrix.org).
+~~The Rocky Linux matrix space can be joined [here](https://matrix.to/#/!rHvPOeKWNBOYSKTiBr:matrix.org?via=matrix.org).~~
 
 ### IRC Cloaks for libera.chat network
 
@@ -182,9 +187,10 @@ Kernel rebuilds are not recommended nor supported for Rocky Linux. Before buildi
 * Are you willing to maintain your own security posture?
 * **Are you sure**? Rocky Linux and most other EL derivatives were designed to function as a complete environment. Replacing critical components can affect how the system acts.
 * **Are you ABSOLUTELY sure**? 99.9% of the users no longer need to build their own kernel. You may simple need a kernel module/driver, in which case, you can use [elrepo](https://elrepo.org) or build your own kernel module (kmod/dkms)
-* **Are you sure you don't just want a newer kernel version**? Newer kernels can be found at [elrepo](https://elrepo.org)
+* **Are you sure you don't just want a newer kernel version**? Newer kernels can be found at [elrepo](https://elrepo.org) and soon [SIG/Kernel](https://sig-kernel.rocky.page/).
 
-As a final warning, if you break the kernel, you are on the hook for your system. Rocky Linux volunteers or developers are unable to assist you with these issues.
+!!! warning
+    As a final warning, if you break the kernel, you are on the hook for your system. Rocky Linux volunteers or developers are unable to assist you with these issues.
 
 ### Upgraded Systems
 
@@ -200,24 +206,27 @@ System Upgrades are generally unsupported. There are quite a few methods out the
 
 Regardless of the method, a system that has been "upgraded" is generally considered unsupported, and you will be recommended to build a new system and restore from backups. Users may try to help or assist with your system, but it may be difficult to do so.
 
-**Note**: While the tool ELevate exists to help users transition from one major release of an Enterprise Linux to another, we have not formally tested it and we cannot officially provide assistance or feedback to the tool or an upgraded system. There may be users in the channel who have done so and can assist, but at this time it's still an unsupported system setup.
+!!! note
+    While the tool ELevate exists to help users transition from one major release of an Enterprise Linux to another, we have not formally tested it and we cannot officially provide assistance or feedback to the tool or an upgraded system. There may be users in the channel who have done so and can assist, but at this time it's still an unsupported system setup.
 
 ### Outdated or End of Life Releases
 
-Outdated or End of Life releases are not generally supported.When you do not update, you are leaving your system in a vulnerable state, prone to bugs and effectively lower security posture. Do not be surprised if community members, volunteers, and channel regulars ask you to run:
+Outdated or End of Life releases are not generally supported. When you do not update, you are leaving your system in a vulnerable state, prone to bugs and effectively lower security posture. Do not be surprised if community members, volunteers, and channel regulars ask you to run:
 
 * `cat /etc/os-release`
 * `cat /etc/rocky-release`
 * `dnf repolist`
 * `dnf update`
 
-Only the latest available `X.Y` of a given version is supported at a given time. Check out the [Rocky Linux](../rocky/) section for more information.
+Only the latest available `X.Y` of a given version is supported at a given time. Check out the [Rocky Linux](../rocky/) section for more information for the latest available releases and our version policies.
+
+If you are stuck on a release due to vendor software locking or certifying only on a certain release, it is recommended that you speak with your software vendor and request information on when they plan on supporting/certifying a supported release for their software.
 
 ### Broken V Servers
 
-Our distribution, like others, use a variant of `yum`/`dnf`. All Rocky Linux releases are shipped with `dnf` and a certain set of matching configuration files (like `.repo` files). This allows your system to work with the mirror system provided by Rocky. Some downstream forks break these configurations and make their system incompatible with what we provide off the shelf.
+Our distribution, like others, use a variant of `dnf`. All Rocky Linux releases are shipped with `dnf` and a certain set of matching configuration files (like `.repo` files). This allows your system to work with the mirror system provided by Rocky. Some downstream forks break these configurations and make their system incompatible with what we provide off the shelf.
 
-Regulars (developers/volunteers) will decline to help in this type of scenario. Below are examples of "broken V servers" where `dnf` is either missing, misconfigured, or outright crippled.
+Regulars (developers/volunteers) will typically decline to help in this type of scenario. Below are examples of "broken V servers" where `dnf` is either missing, misconfigured, or outright crippled.
 
 #### VPS
 

diff --git a/docs/rocky/repo.md b/docs/rocky/repo.md
@@ -89,7 +89,7 @@ All SIG repositories can be found [here](https://dl.rockylinux.org/pub/sig)
 The vault is a historic archive of previous Rocky Linux releases. These previous releases, including ISOs and other images, are typically moved into the vault area of our tier 0 mirror between a day and a week once a new minor release version is available. The vault can be found [here](https://dl.rockylinux.org/vault/rocky).
 
 !!! warning
-    The vault is meant as a historic archive of previous releases of Rocky Linux. These are versions that are NOT supported and NOT recommended for general use as they contain unfixed bugs and unpatched security vulnerabilities.
+    The vault is meant as a historic archive of previous releases of Rocky Linux and not for general use. These are versions that are NOT supported and NOT recommended for general use as they contain unfixed bugs and unpatched security vulnerabilities.
 
     The community may not be able to assist you with issues with these releases, so it is recommended that you keep your systems up to date.