From 349fa4963516e28cf6bcf80925c4c4534576eedf Mon Sep 17 00:00:00 2001 From: Dajuan Mcdonald <16410995+FIOpwK@users.noreply.github.com> Date: Sun, 11 Jun 2023 17:35:35 -0400 Subject: [PATCH 1/4] Update irc.md Minor grammatical fixes for native English speakers. --- docs/irc.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/irc.md b/docs/irc.md index 9306a45ba..23da0dab6 100644 --- a/docs/irc.md +++ b/docs/irc.md @@ -176,7 +176,7 @@ Kernel rebuilds are not recommended nor supported for Rocky Linux. Before buildi * **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) -As a final warning, you 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. +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 @@ -227,7 +227,7 @@ So you have a VPS and you've discovered `dnf` is not working as it should. This The above tend to only install parts of Rocky Linux on their virtual servers and some are known for entirely removing `dnf` from the system entirely or altering the settings entirely. Typical changes are that they exclude locally modified packages from our base repositories. You can verify this by running `grep -ir exclude /etc/{yum,dnf}*` which will show what they are excluding. Some will also manage the box outside of the package manager. -Why these provides do this is unclear. Regardless of their reasons, this approach is seen negatively as `dnf` has mechanisms to protect specific packages from change. +Why these providers do this is unclear. Regardless of their reasons, this approach is seen negatively as `dnf` has mechanisms to protect specific packages from change. Before you try anything, please **STOP** and ask your provider **why** they removed `dnf` and how are you supposed to keep your system up to date/secure without it. From 9ec647c25278c9eabc8238a9003190b97b8aa0f9 Mon Sep 17 00:00:00 2001 From: Neil Hanlon Date: Thu, 22 Jun 2023 00:03:59 -0400 Subject: [PATCH 2/4] add warning about git.c.o no longer being available --- docs/archive/legacy/mqtt_bus.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/archive/legacy/mqtt_bus.md b/docs/archive/legacy/mqtt_bus.md index 763b3313a..d23b8b1e9 100644 --- a/docs/archive/legacy/mqtt_bus.md +++ b/docs/archive/legacy/mqtt_bus.md @@ -1,6 +1,13 @@ --- title: CentOS MQTT message bus --- + +!!! danger + As of 2023-06-21, [updates are no longer published to git.centos.org](https://www.redhat.com/en/blog/furthering-evolution-centos-stream). This page will eventually be replaced with documentation on the Fedora MessageBus which contains the events for publishing into gitlab.com/redhat/centos-stream, and how we have implemented inside our build system. + + As such, the information below should be considered historical and may move to the Archive at some time in the future. Proceed with caution. + + CentOS provides a message bus which can be used for subscribing to certain messages on their git repository. More information, and setup on subscribing to their message bus can be found at [https://wiki.centos.org/Sources?highlight=%28mqtt%29#Message_Broker_.28MQTT.29](https://wiki.centos.org/Sources?highlight=%28mqtt%29#Message_Broker_.28MQTT.29). From aeda8fa37d022e91888fcd36455adaee1b0d0da2 Mon Sep 17 00:00:00 2001 From: Neil Hanlon Date: Mon, 24 Jul 2023 09:50:46 -0400 Subject: [PATCH 3/4] add section on removing mattermost accounts --- docs/team/infrastructure/idm_pdr.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/team/infrastructure/idm_pdr.md b/docs/team/infrastructure/idm_pdr.md index c99fa8fe0..7b1e23116 100644 --- a/docs/team/infrastructure/idm_pdr.md +++ b/docs/team/infrastructure/idm_pdr.md @@ -10,7 +10,7 @@ As a user within the Rocky Linux and Rocky Enterprise Software Foundation ecosys | **Owner** | Infrastructure Team & Identity Management Team | | **Email Contact** | infrastructure@rockylinux.org | | **Email Contact** | identitymanagement@rockylinux.org | -| **Mattermost Contacts** | `@label` | +| **Mattermost Contacts** | `@label` `@neil` `@tgo` | | **Mattermost Channels** | `~Infrastructure` | ## General Information @@ -28,9 +28,13 @@ If your intention is to keep your account active and hide your personal informat 2. Select the checkbox for `Private` 3. Save. +## Mattermost Accounts + +While we are working to integrate Mattermost with Rocky Account Services, at this time, Mattermost accounts are still separate and are not included in a typical PDR Delete Request. If you wish to have your Mattermost account removed, you may follow the instructions below and indicate which account you would like to be removed. If submitting via email, please send from the address associated with the account you wish to have removed. If a different email address is used, the request will need to be validated with the account's proper address prior to actioning the request. For security reasons, we are not able to reveal the email address associated with any account name. + ## Submitting a Request -To submit a request, you may either [email](mailto:identitymanagement@rockylinux.org?cc=infrastructure@rockylinux.org&subject=PDR%20Delete%20Request&body=%23%23%23%23%20Personal%20Data%20Request%20-%20Remove%20%23%23%23%23%0D%0A%0D%0AThis%20ticket%20is%20for%20the%20removal%20of%20my%20Personal%20Data%20that%20is%20attached%20to%20my%20(%7Buser%7D)%20account.%0D%0A%0D%0A%23%23%23%23%20Provide%20the%20following%20information%20%23%23%23%23%0D%0A%0D%0APlease%20fill%20in%20the%20following%20information%20to%20authorize%20the%20removal%20of%20your%20personal%20information.%0D%0A%0D%0AUsername%3A%20%3CUSER%3E%0D%0ADate%3A%20%3CDATE%3E%0D%0AEmail%20Address%3A%20%3CEMAIL%3E%0D%0A%0D%0A%23%23%23%23%20Information%20%23%23%23%23%0D%0A%0D%0ACreating%20this%20ticket%2FSending%20this%20email%2C%20I%20am%20aware%20of%20the%20following%3A%0D%0A%0D%0A*%20During%20processing%2C%20my%20account%20will%20be%20disabled%20and%20I%20will%20no%20longer%20be%20able%20to%20login%0D%0A*%20During%20processing%2C%20my%20account%20will%20be%20removed%20from%20all%20applicable%20groups%20in%20Account%20Services%0D%0A*%20During%20processing%2C%20my%20account%20will%20be%20set%20to%20%22private%22%20in%20Account%20Services%0D%0A*%20Signatures%2Fconsent%20to%20the%20agreements%20(such%20as%20the%20Rocky%20Open%20Source%20Contributor%20Agreement)%20will%20be%20remain%20for%20record%20keeping%0D%0A*%20The%20ticket%20filed%20for%20this%20request%20will%20be%20set%20to%20private%20and%20I%20will%20be%20notified%20of%20its%20closure.%0D%0A%0D%0A%23%23%23%23%20Comments%20%23%23%23%23%0D%0A%0D%0A(If%20you%20have%20additional%20comments%2C%20you%20may%20leave%20them%20here.)) us or you may open a ticket at our [Bug Tracker](https://bugs.rockylinux.org) +To submit a request, you may either [email](mailto:identitymanagement@rockylinux.org?cc=infrastructure@rockylinux.org&subject=PDR%20Delete%20Request&body=%23%23%23%23%20Personal%20Data%20Request%20-%20Remove%20%23%23%23%23%0D%0A%0D%0AThis%20ticket%20is%20for%20the%20removal%20of%20my%20Personal%20Data%20that%20is%20attached%20to%20my%20(%7Buser%7D)%20account.%0D%0A%0D%0A%23%23%23%23%20Provide%20the%20following%20information%20%23%23%23%23%0D%0A%0D%0APlease%20fill%20in%20the%20following%20information%20to%20authorize%20the%20removal%20of%20your%20personal%20information.%0D%0A%0D%0AUsername%3A%20%3CUSER%3E%0D%0ADate%3A%20%3CDATE%3E%0D%0AEmail%20Address%3A%20%3CEMAIL%3E%0D%0A%0D%0A%23%23%23%23%20Information%20%23%23%23%23%0D%0A%0D%0ACreating%20this%20ticket%2FSending%20this%20email%2C%20I%20am%20aware%20of%20the%20following%3A%0D%0A%0D%0A*%20During%20processing%2C%20my%20account%20will%20be%20disabled%20and%20I%20will%20no%20longer%20be%20able%20to%20login%0D%0A*%20During%20processing%2C%20my%20account%20will%20be%20removed%20from%20all%20applicable%20groups%20in%20Account%20Services%0D%0A*%20During%20processing%2C%20my%20account%20will%20be%20set%20to%20%22private%22%20in%20Account%20Services%0D%0A*%20Signatures%2Fconsent%20to%20the%20agreements%20(such%20as%20the%20Rocky%20Open%20Source%20Contributor%20Agreement)%20will%20be%20remain%20for%20record%20keeping%0D%0A*%20The%20ticket%20filed%20for%20this%20request%20will%20be%20set%20to%20private%20and%20I%20will%20be%20notified%20of%20its%20closure.%0D%0A%0D%0A%23%23%23%23%20Comments%20%23%23%23%23%0D%0A%0D%0A(If%20you%20have%20additional%20comments%2C%20you%20may%20leave%20them%20here.)) us or you may open a ticket at our [Bug Tracker](https://bugs.rockylinux.org). ### Ticket Request From 2112b9e9b94f5209cff22d1b22ba8d1ca2b6b755 Mon Sep 17 00:00:00 2001 From: Neil Hanlon Date: Mon, 24 Jul 2023 09:54:20 -0400 Subject: [PATCH 4/4] support opening tickets on infra/meta --- docs/team/infrastructure/idm_pdr.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/team/infrastructure/idm_pdr.md b/docs/team/infrastructure/idm_pdr.md index 7b1e23116..30a63331a 100644 --- a/docs/team/infrastructure/idm_pdr.md +++ b/docs/team/infrastructure/idm_pdr.md @@ -50,6 +50,10 @@ Click the [following link](https://bugs.rockylinux.org) to open our bug tracker. 7. Fill out the form appropriately. Do not remove data that starts that contains `{}` and ensure you have read the "Information" section. You may fill in comments as you see fit. 8. Click `Submit Issue` at the bottom +#### Alternative Ticket Process + +The bug tracker above provides a private way to ask for account deletion. For any account-related actions, up to and including deletion, we also welcome tickets to be created on the [infrastructure/meta](https://git.resf.org/infrastructure/meta/issues) issue tracker on git.resf.org. You may sign-in with keycloak to this service using your Rocky Account Services account, which we can additionally use to validate your ownership of the account. When creating a new issue, you may select the 'Account Requests - Personal Data Request' as the template. + ### Email Request Click the [following link]( mailto:identitymanagement@rockylinux.org?cc=infrastructure@rockylinux.org&subject=PDR%20Delete%20Request&body=%23%23%23%23%20Personal%20Data%20Request%20-%20Remove%20%23%23%23%23%0D%0A%0D%0AThis%20ticket%20is%20for%20the%20removal%20of%20my%20Personal%20Data%20that%20is%20attached%20to%20my%20(%7Buser%7D)%20account.%0D%0A%0D%0A%23%23%23%23%20Provide%20the%20following%20information%20%23%23%23%23%0D%0A%0D%0APlease%20fill%20in%20the%20following%20information%20to%20authorize%20the%20removal%20of%20your%20personal%20information.%0D%0A%0D%0AUsername%3A%20%3CUSER%3E%0D%0ADate%3A%20%3CDATE%3E%0D%0AEmail%20Address%3A%20%3CEMAIL%3E%0D%0A%0D%0A%23%23%23%23%20Information%20%23%23%23%23%0D%0A%0D%0ACreating%20this%20ticket%2FSending%20this%20email%2C%20I%20am%20aware%20of%20the%20following%3A%0D%0A%0D%0A*%20During%20processing%2C%20my%20account%20will%20be%20disabled%20and%20I%20will%20no%20longer%20be%20able%20to%20login%0D%0A*%20During%20processing%2C%20my%20account%20will%20be%20removed%20from%20all%20applicable%20groups%20in%20Account%20Services%0D%0A*%20During%20processing%2C%20my%20account%20will%20be%20set%20to%20%22private%22%20in%20Account%20Services%0D%0A*%20Signatures%2Fconsent%20to%20the%20agreements%20(such%20as%20the%20Rocky%20Open%20Source%20Contributor%20Agreement)%20will%20be%20remain%20for%20record%20keeping%0D%0A*%20The%20ticket%20filed%20for%20this%20request%20will%20be%20set%20to%20private%20and%20I%20will%20be%20notified%20of%20its%20closure.%0D%0A%0D%0A%23%23%23%23%20Comments%20%23%23%23%23%0D%0A%0D%0A(If%20you%20have%20additional%20comments%2C%20you%20may%20leave%20them%20here.)) to open an email draft to us to start the process.