infra/tickets
24
11
Fork 1
Code Issues 80 Projects Wiki Activity Actions

Need to delete user account in FAS that has been already deleted in Discourse (discussion.fedoraproject.org) due to violations (spam, AI, etc.) #13131

New issue
Closed
opened 2026-02-10 09:56:21 +00:00 by py0xc3 · 91 comments
py0xc3 commented 2026-02-10 09:56:21 +00:00
Copy link

Description of request

This is the follow-up ticket of: https://pagure.io/fedora-infrastructure/issue/12091

### Description of request This is the follow-up ticket of: https://pagure.io/fedora-infrastructure/issue/12091
py0xc3 commented 2026-02-10 09:58:03 +00:00
Author
Copy link

Please disable bantuanbb1230 (spam) and matuphumkuldee (unclear if spam or rant, with elements of both, maybe just an AI in training)

Please disable `bantuanbb1230` (spam) and `matuphumkuldee` (unclear if spam or rant, with elements of both, maybe just an AI in training)
zlopez commented 2026-02-10 10:12:10 +00:00
Owner
Copy link

The original ticket is still around, but opening a new one makes sense.

Disabled both users.

The [original ticket](https://forge.fedoraproject.org/infra/tickets/issues/12091) is still around, but opening a new one makes sense. Disabled both users.
py0xc3 commented 2026-02-10 10:45:32 +00:00
Author
Copy link

Thanks :)

Please disable also salman786 -> spam.

Thanks :) Please disable also `salman786` -> spam.
py0xc3 reopened this issue 2026-02-10 10:45:32 +00:00
zlopez commented 2026-02-10 13:26:31 +00:00
Owner
Copy link

User disabled

User disabled
py0xc3 commented 2026-02-12 12:17:41 +00:00
Author
Copy link

Please disable techxnegi and sharmahrsh137 (spam)

Please disable `techxnegi` and `sharmahrsh137` (spam)
py0xc3 reopened this issue 2026-02-12 12:17:41 +00:00
zlopez commented 2026-02-12 12:30:16 +00:00
Owner
Copy link

Both users disabled in FAS.

Both users disabled in FAS.
py0xc3 commented 2026-02-12 13:24:23 +00:00
Author
Copy link

Please disable suhana -> spam (all spammers of today came from the same location, so they might be all the same)

Please disable `suhana` -> spam (all spammers of today came from the same location, so they might be all the same)
py0xc3 reopened this issue 2026-02-12 13:24:23 +00:00
zlopez commented 2026-02-12 16:51:34 +00:00
Owner
Copy link

Uesr disabled in FAS.

Uesr disabled in FAS.
py0xc3 commented 2026-02-14 16:59:23 +00:00
Author
Copy link

Please disable saracenbot -> spam

Please disable `saracenbot` -> spam
py0xc3 reopened this issue 2026-02-14 16:59:23 +00:00
kevin commented 2026-02-15 21:59:14 +00:00
Owner
Copy link

User disabled.

User disabled.
kevin closed this issue 2026-02-15 21:59:14 +00:00
py0xc3 commented 2026-02-20 10:15:07 +00:00
Author
Copy link

Please disable letras -> spam

Please disable `letras` -> spam
py0xc3 reopened this issue 2026-02-20 10:15:07 +00:00
zlopez commented 2026-02-23 09:46:41 +00:00
Owner
Copy link

User disabled.

User disabled.
py0xc3 commented 2026-02-26 11:28:01 +00:00
Author
Copy link

Please disable brimobri -> spam

Please disable `brimobri` -> spam
py0xc3 reopened this issue 2026-02-26 11:28:02 +00:00
zlopez commented 2026-02-26 11:54:22 +00:00
Owner
Copy link

User disabled.

User disabled.
py0xc3 commented 2026-02-28 11:55:57 +00:00
Author
Copy link

Please disable hagarluke -> spam

Please disable `hagarluke` -> spam
py0xc3 reopened this issue 2026-02-28 11:55:57 +00:00
kevin commented 2026-02-28 17:46:32 +00:00
Owner
Copy link

User disabled.

User disabled.
kevin closed this issue 2026-02-28 17:46:33 +00:00
py0xc3 commented 2026-03-02 13:35:34 +00:00
Author
Copy link

Please disable jacksparrow0203 -> spam

Please disable ` jacksparrow0203` -> spam
py0xc3 reopened this issue 2026-03-02 13:35:34 +00:00
zlopez commented 2026-03-02 14:03:11 +00:00
Owner
Copy link

User disabled.

User disabled.
py0xc3 commented 2026-03-07 12:43:18 +00:00
Author
Copy link

Please disable kuchi121sharma -> spam.

Also, can we maybe move the account disabling to Discourse (or somewhere else) temporarily until the Forge migration is done? At the moment, 2/3 of the time I invest in disabling a user is re-logging in to FAS in order to post a line on forge.fp with 2fa etc. It's trivial, but I would be happy to exploit simple means to reduce time investment at the moment, as it makes currently 10 seconds to 1-2 minutes, especially if I then get the Bad Requests etc along with it. Would be cool, but not critical of course :)

Please disable `kuchi121sharma` -> spam. Also, can we maybe move the account disabling to Discourse (or somewhere else) temporarily until the Forge migration is done? At the moment, 2/3 of the time I invest in disabling a user is re-logging in to FAS in order to post a line on forge.fp with 2fa etc. It's trivial, but I would be happy to exploit simple means to reduce time investment at the moment, as it makes currently 10 seconds to 1-2 minutes, especially if I then get the Bad Requests etc along with it. Would be cool, but not critical of course :)
py0xc3 reopened this issue 2026-03-07 12:43:18 +00:00
zlopez commented 2026-03-09 08:45:31 +00:00
Owner
Copy link

I disabled the user in FAS.

But regarding the Discourse disable user process I don't even know how that is working or who actually set it up. So I'm not sure if fedora infra is the correct place to ask about the process change.

EDIT: After some thinking I found out I misunderstood. By forgejo access you probably mean this ticket. We talked about this on today standup and it could be probably automated, but it needs more thinking.

I disabled the user in FAS. But regarding the Discourse disable user process I don't even know how that is working or who actually set it up. So I'm not sure if fedora infra is the correct place to ask about the process change. EDIT: After some thinking I found out I misunderstood. By forgejo access you probably mean this ticket. We talked about this on today standup and it could be probably automated, but it needs more thinking.
py0xc3 commented 2026-03-09 10:43:12 +00:00
Author
Copy link

But regarding the Discourse disable user process I don't even know how that is working or who actually set it up. So I'm not sure if fedora infra is the correct place to ask about the process change.

EDIT: After some thinking I found out I misunderstood. By forgejo access you probably mean this ticket. We talked about this on today standup and it could be probably automated, but it needs more thinking.

Yes, I just meant this ticket. So our exchange. E.g., that until forge.fp is able to remain logged in, that we not exchange details in this ticket but in a topic in Discoourse. I guess it is OK to push you temporarily to TL3 so that you can access the mod area, and then we can create a ticket there until the forge issues are solved?

> But regarding the Discourse disable user process I don't even know how that is working or who actually set it up. So I'm not sure if fedora infra is the correct place to ask about the process change. > EDIT: After some thinking I found out I misunderstood. By forgejo access you probably mean this ticket. We talked about this on today standup and it could be probably automated, but it needs more thinking. Yes, I just meant this ticket. So our exchange. E.g., that until forge.fp is able to remain logged in, that we not exchange details in this ticket but in a topic in Discoourse. I guess it is OK to push you temporarily to TL3 so that you can access the mod area, and then we can create a ticket there until the forge issues are solved?
zlopez commented 2026-03-09 11:09:40 +00:00
Owner
Copy link

Could you open a separate ticket with the request to automate it? We were discussing it and there seems to be few options we can got with.

Could you open a separate ticket with the request to automate it? We were discussing it and there seems to be few options we can got with.
👍 1
ankursinha commented 2026-03-11 11:25:59 +00:00
Copy link

Please disable jadipansn12 -> spam, blocked from discussion.fp.o

Please disable `jadipansn12` -> spam, blocked from discussion.fp.o
kevin commented 2026-03-11 18:43:22 +00:00
Owner
Copy link

User disabled.

User disabled.
py0xc3 commented 2026-05-30 16:58:03 +00:00
Author
Copy link

For the future, we use this topic again, as documented in the guidelines (to be published likely next week)

For the future, we use this topic again, as documented in the guidelines (to be published likely next week)
computersavvy commented 2026-05-31 05:07:51 +00:00
Copy link

Please delete user juragan99 SPAM blocked in d.fp.o

Please delete user `juragan99` SPAM blocked in d.fp.o
zlopez commented 2026-06-01 11:57:28 +00:00
Owner
Copy link

Disabled in FAS.

Disabled in FAS.
py0xc3 commented 2026-06-02 12:29:42 +00:00
Author
Copy link

Please disable jameswill8520 -> spam

Please disable `jameswill8520` -> spam
py0xc3 reopened this issue 2026-06-02 12:29:50 +00:00
zlopez commented 2026-06-02 12:37:11 +00:00
Owner
Copy link

User disabled.

User disabled.
py0xc3 commented 2026-06-10 13:22:05 +00:00
Author
Copy link

Please disable royalcrystalevent -> spam

Please disable `royalcrystalevent` -> spam
py0xc3 reopened this issue 2026-06-10 13:22:05 +00:00
humaton commented 2026-06-10 14:17:47 +00:00
Member
Copy link

User disabled

User disabled
computersavvy commented 2026-06-13 12:46:50 +00:00
Copy link

Please disable knox76 --> spam

Please disable knox76 --> spam
humaton commented 2026-06-13 14:29:16 +00:00
Member
Copy link

User disabled

User disabled
ankursinha commented 2026-06-15 12:58:15 +00:00
Copy link

Please disable digitaldeep, petergrew, -> spam on discussion.fp.o

Please disable digitaldeep, petergrew, -> spam on discussion.fp.o
computersavvy commented 2026-06-15 13:37:57 +00:00
Copy link

please disable youcinez --> spam on d.fp.o

please disable youcinez --> spam on d.fp.o
kevin commented 2026-06-18 18:39:44 +00:00
Owner
Copy link

Sorry for the delay.

All disabled.

Sorry for the delay. All disabled.
❤️ 1
ankursinha commented 2026-06-23 12:43:33 +00:00
Copy link

Please disable techpamx -> spam on discussion.fp.o

Please disable `techpamx` -> spam on discussion.fp.o
humaton commented 2026-06-23 12:48:35 +00:00
Member
Copy link

The user was disabled.

The user was disabled.
computersavvy commented 2026-06-30 01:30:30 +00:00
Copy link

Please disable robin0292 --> spam on d.fp.o

Please disable robin0292 --> spam on d.fp.o
zlopez commented 2026-06-30 08:53:24 +00:00
Owner
Copy link

User disabled.

User disabled.
py0xc3 commented 2026-07-03 11:01:04 +00:00
Author
Copy link

Please disable cryptovendurew -> spam.

I assume it is already known, but just in case it is not: I'm back to re-logging in to Forge on every start of Firefox, which is at least once a day (other fedoraproject.org services are not affected).

Please disable `cryptovendurew` -> spam. ----- I assume it is already known, but just in case it is not: I'm back to re-logging in to Forge on every start of Firefox, which is at least once a day (other fedoraproject.org services are not affected).
py0xc3 reopened this issue 2026-07-03 11:01:05 +00:00
kevin commented 2026-07-04 17:20:23 +00:00
Owner
Copy link

Disabled.

Disabled.
kevin closed this issue 2026-07-04 17:20:23 +00:00
py0xc3 commented 2026-07-07 15:37:25 +00:00
Author
Copy link

Please disable footurist -> spam

Please disable `footurist` -> spam
py0xc3 reopened this issue 2026-07-07 15:37:25 +00:00
kevin commented 2026-07-07 19:59:32 +00:00
Owner
Copy link

Disabled.

Disabled.
kevin closed this issue 2026-07-07 19:59:32 +00:00
py0xc3 commented 2026-07-14 07:51:02 +00:00
Author
Copy link

Please disable bscho -> spam

Please disable `bscho` -> spam
py0xc3 reopened this issue 2026-07-14 07:51:02 +00:00
zlopez commented 2026-07-14 07:56:19 +00:00
Owner
Copy link

User disabled in FAS.

User disabled in FAS.
computersavvy commented 2026-07-17 13:54:28 +00:00
Copy link

Delete user ccb2517. Spam with AI content in discussion.fp.o

Delete user ccb2517. Spam with AI content in discussion.fp.o
kevin commented 2026-07-17 16:43:04 +00:00
Owner
Copy link

I don't see any user with that username... can you doublecheck please?

I don't see any user with that username... can you doublecheck please?
computersavvy commented 2026-07-17 17:11:35 +00:00
Copy link

I potentially swapped characters in that user name. Maybe ccb2715?
The user has been deleted in discussion so we will have to wait and see if they post again.
Thanks, and I need to keep better notes !

I potentially swapped characters in that user name. Maybe ccb2715? The user has been deleted in discussion so we will have to wait and see if they post again. Thanks, and I need to keep better notes !
❤️ 1
kevin commented 2026-07-17 17:35:26 +00:00
Owner
Copy link

Found it in the discourse logs... it's ccb3517 :)
Disabled.

Found it in the discourse logs... it's ccb3517 :) Disabled.
❤️ 1
py0xc3 commented 2026-07-17 17:50:50 +00:00
Author
Copy link

The user has been deleted in discussion so we will have to wait and see if they post again.

Unfortunately, the discourse implementation is bad for us in this respect (I think it was never intended for an integration like ours): once deleted in Discourse, we can no longer see the user name in our interface.

I solved this by radically starting the deletion process always with copy/pasting the username from the Discourse user URL (avoiding typos etc) into a text editor or so (I mostly have a text editor open anyway, and tend to do a lot of copy/pasting, risking to accidentally override it before its final use). Then, I go ahead with the deletion process and just copy/paste it at the end here. The reason for this is that I found myself already in this situation :)

It's just a minor issue with little impact, but maybe that's somehow useful, and you are definitely not the first one who ends up with this issue ;)

> The user has been deleted in discussion so we will have to wait and see if they post again. Unfortunately, the discourse implementation is bad for us in this respect (I think it was never intended for an integration like ours): once deleted in Discourse, we can no longer see the user name in our interface. I solved this by radically starting the deletion process always with copy/pasting the username from the Discourse user URL (avoiding typos etc) into a text editor or so (I mostly have a text editor open anyway, and tend to do a lot of copy/pasting, risking to accidentally override it before its final use). Then, I go ahead with the deletion process and just copy/paste it at the end here. The reason for this is that I found myself already in this situation :) It's just a minor issue with little impact, but maybe that's somehow useful, and you are definitely not the first one who ends up with this issue ;)
py0xc3 commented 2026-07-19 08:32:32 +00:00
Author
Copy link

Please disable ispot99989 -> spam

Please disable `ispot99989` -> spam
py0xc3 reopened this issue 2026-07-19 08:32:32 +00:00
kevin commented 2026-07-19 16:39:24 +00:00
Owner
Copy link

Disabled.

Disabled.
kevin closed this issue 2026-07-19 16:39:24 +00:00
computersavvy commented 2026-07-22 16:50:01 +00:00
Copy link

Please disable user developer-salah.
Spam advertising in discourse

Please disable user developer-salah. Spam advertising in discourse
kevin commented 2026-07-22 18:40:21 +00:00
Owner
Copy link

disabled.

disabled.
computersavvy commented 2026-07-25 15:14:52 +00:00
Copy link

Please delete user 'chocolate' per user request.

Please delete user 'chocolate' per user request.
zlopez commented 2026-07-27 08:09:11 +00:00
Owner
Copy link

Disabled.

Disabled.
computersavvy commented 2026-08-03 14:43:38 +00:00
Copy link

please delete user 'lasttyper'
User posted AI spam as first post in discussion and has been deleted in d.fp.o

please delete user 'lasttyper' User posted AI spam as first post in discussion and has been deleted in d.fp.o
kevin commented 2026-08-03 16:56:27 +00:00
Owner
Copy link

User disabled.

User disabled.
py0xc3 commented 2026-08-10 10:49:04 +00:00
Author
Copy link

Please disable northbyte -> spam

Please disable `northbyte` -> spam
py0xc3 reopened this issue 2026-08-10 10:49:04 +00:00
zlopez commented 2026-08-10 12:03:57 +00:00
Owner
Copy link

User disabled.

User disabled.
ankursinha commented 2026-08-10 19:56:11 +00:00
Copy link

Please disable user vbertulucci for spam on discussion. Cheers,

Please disable user `vbertulucci` for spam on discussion. Cheers,
kevin commented 2026-08-10 21:44:28 +00:00
Owner
Copy link

disabled.

disabled.
ankursinha commented 2026-08-14 10:46:02 +00:00
Copy link

Please disable user stswt01 for spam on discussion. Thanks.

Please disable user `stswt01` for spam on discussion. Thanks.
kevin commented 2026-08-14 17:25:21 +00:00
Owner
Copy link

User disabled.

User disabled.
py0xc3 commented 2026-08-15 12:27:31 +00:00
Author
Copy link

Please disable budipratama25 -> spam

Please disable `budipratama25` -> spam
py0xc3 reopened this issue 2026-08-15 12:27:31 +00:00
zlopez commented 2026-08-17 10:14:05 +00:00
Owner
Copy link

User disabled.

User disabled.
computersavvy commented 2026-08-18 09:33:43 +00:00
Copy link

Please disable the following 2 users -- both appear to be the same user and spam flagged by the system.
iusedeeznutsbtw
linussextip

Please disable the following 2 users -- both appear to be the same user and spam flagged by the system. iusedeeznutsbtw linussextip
zlopez commented 2026-08-18 09:38:19 +00:00
Owner
Copy link

Users disabled.

Users disabled.
computersavvy commented 2026-08-18 14:38:40 +00:00
Copy link

Another user to disable as spam
conlactor

Another user to disable as spam conlactor
py0xc3 commented 2026-08-18 16:34:06 +00:00
Author
Copy link

Please disable yarjoyia -> spam

Please disable `yarjoyia` -> spam
py0xc3 reopened this issue 2026-08-18 16:34:06 +00:00
kevin commented 2026-08-18 19:53:37 +00:00
Owner
Copy link

Both disabled.

Both disabled.
kevin closed this issue 2026-08-18 19:53:37 +00:00
py0xc3 commented 2026-08-19 06:44:23 +00:00
Author
Copy link

Please disable jacobjameson -> spam

Please disable `jacobjameson` -> spam
zlopez commented 2026-08-19 10:01:31 +00:00
Owner
Copy link

User disabled

User disabled
py0xc3 commented 2026-08-19 12:28:08 +00:00
Author
Copy link

Please disable flexyagency -> spam.

Please disable `flexyagency` -> spam.
kevin commented 2026-08-19 22:06:57 +00:00
Owner
Copy link

Disabled.

Disabled.
py0xc3 commented 2026-08-22 12:03:27 +00:00
Author
Copy link

Please delete (not disable!) the account gabriel-galiana (do not block their email address)

The user created two accounts. I expect they acted in good faith and lost their credentials or so. They just needed help and seem little experienced with channels/tools like ours.

I told them to stick with one account, use their second one, and that we delete the first.

-> https://discussion.fedoraproject.org/t/audio-not-working-on-asus-vivobook-14-flip-tp3407sa-tp3407sa/199322/6

I leave their first account in discourse so that their topic remains readable.

Thanks :)

Please **delete** (not disable!) the account `gabriel-galiana` (do not block their email address) The user created two accounts. I expect they acted in good faith and lost their credentials or so. They just needed help and seem little experienced with channels/tools like ours. I told them to stick with one account, use their second one, and that we delete the first. -> https://discussion.fedoraproject.org/t/audio-not-working-on-asus-vivobook-14-flip-tp3407sa-tp3407sa/199322/6 I leave their first account in discourse so that their topic remains readable. Thanks :)
py0xc3 reopened this issue 2026-08-22 12:03:27 +00:00
zlopez commented 2026-08-24 10:13:47 +00:00
Owner
Copy link

@kevin What is our policy about deleting accounts?

@kevin What is our policy about deleting accounts?
py0xc3 commented 2026-08-24 10:50:12 +00:00
Author
Copy link

https://docs.fedoraproject.org/en-US/discussion-forum-guidelines-and-rules/

Guidelines 6.

That said, it's not bad faith, but the case was neither approved nor is it justified. The user is ok with deleting the account and agreed to use the other one in future (see the topic; also, the user seems to have no longer access to the account I asked to delete). So one could argue it's also justified to delete the obsoleted account by guideline 14. Or partially through both... But it's not urgent anyway ;)

https://docs.fedoraproject.org/en-US/discussion-forum-guidelines-and-rules/ Guidelines 6. That said, it's not bad faith, but the case was neither approved nor is it justified. The user is ok with deleting the account and agreed to use the other one in future (see the topic; also, the user seems to have no longer access to the account I asked to delete). So one could argue it's also justified to delete the obsoleted account by guideline 14. Or partially through both... But it's not urgent anyway ;)
kevin commented 2026-08-24 18:16:34 +00:00
Owner
Copy link

We do not normally actually fully delete accounts.
This is for a number of reasons, including things like 'we then have no idea what actions were taken by the account that no longer exists' and 'we can't see some history that would have been associated with the account' and 'someone else might make an account with the same name and then confuse who did what (the old account? the new one? )

IMHO, we should disable this account and if you like you can delete it on the discourse side? discourse does have some logging/ability to see when an account was deleted and what the now deleted account did/was.

Is that acceptable?

We do not normally actually fully delete accounts. This is for a number of reasons, including things like 'we then have no idea what actions were taken by the account that no longer exists' and 'we can't see some history that would have been associated with the account' and 'someone else might make an account with the same name and then confuse who did what (the old account? the new one? ) IMHO, we should disable this account and if you like you can delete it on the discourse side? discourse does have some logging/ability to see when an account was deleted and what the now deleted account did/was. Is that acceptable?
py0xc3 commented 2026-08-24 20:03:29 +00:00
Author
Copy link

My worry was that the user's email address is thus no longer usable in Fedora, no? So it felt like disabling is banning his email address when there was no bad faith. Not a big thing of course, I guess the user will not care as well. So if that's safer on your side, we can do it as you suggest. Deleting on the discourse side is no problem, that's fine for me.

Supplement: on the discourse side, I anonymized the original account, so that the topic remains readable. Implement everything else as you see fit :)

My worry was that the user's email address is thus no longer usable in Fedora, no? So it felt like disabling is banning his email address when there was no bad faith. Not a big thing of course, I guess the user will not care as well. So if that's safer on your side, we can do it as you suggest. Deleting on the discourse side is no problem, that's fine for me. Supplement: on the discourse side, I anonymized the original account, so that the topic remains readable. Implement everything else as you see fit :)
zlopez commented 2026-08-25 07:39:45 +00:00
Owner
Copy link

So I disabled the user in FAS, that is OK for us to do. We can also change the mail to something else if that could be the problem.

So I disabled the user in FAS, that is OK for us to do. We can also change the mail to something else if that could be the problem.
computersavvy commented 2026-08-29 13:54:46 +00:00
Copy link

please disable user trocryptdirect --> spam

please disable user trocryptdirect --> spam
py0xc3 commented 2026-08-31 10:20:10 +00:00
Author
Copy link

please disable wade771 -> spam

please disable `wade771` -> spam
zlopez commented 2026-08-31 12:12:27 +00:00
Owner
Copy link

Both of them are disabled and when searching for trocryptdirect I found another two accounts that had similar mail address, so I blocked them as well.

Both of them are disabled and when searching for `trocryptdirect` I found another two accounts that had similar mail address, so I blocked them as well.
ankursinha commented 2026-09-01 09:03:09 +00:00
Copy link

Please delete wade456 -> spam on discussion.. lots of wades..

Please delete `wade456` -> spam on discussion.. lots of wades..
zlopez commented 2026-09-01 09:27:07 +00:00
Owner
Copy link

User disabled in FAS.

User disabled in FAS.
py0xc3 commented 2026-09-03 07:38:13 +00:00
Author
Copy link

Please disable lucasblake -> spam

Please disable `lucasblake` -> spam
zlopez commented 2026-09-03 07:51:56 +00:00
Owner
Copy link

User disabled in FAS.

User disabled in FAS.
computersavvy commented 2026-09-05 14:11:53 +00:00
Copy link

Please disable user qloudhosts --> spam

Please disable user `qloudhosts` --> spam
kevin commented 2026-09-05 16:24:03 +00:00
Owner
Copy link

User disabled.

User disabled.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
announcement

Archived

  
anubis
Issues related to anubis

  
authentication
Authentication related issues

  
aws
Issues related to Amazon Web Services

  
backlog
Tasks that will take longer then ~4 hours to do

Archived

  
blocked
Issue is blocked

Archived

  
bodhi
Issues with Bodhi

  
ci
Continuous Integration

  
cloud
Items in FedoraInfraCloud or COmmunishift

  
communishift
issues/questions about os.edorainfracloud.org ( Community OpenShift)

  
copr
COPR system (run by other team)

  
database
Issues related to databases

  
day-to-day
These are small self contained tasks that are part of normal operations, but are async from sprint planning.

  
dc-move
Items related to datacenter move

Archived

  
deprecated
Tools which Infrastructure may not be able to fix

Archived

  
dev
Tasks requiring some dev work

  
discourse
outsourced tool

  
dns
Changes or problems with DNS

  
downloads
rsync,dl.fp.o,AWS,torrents

  
easyfix

Archived

  
epel
Issues relating to epel

Archived

  
firmitas

   
forgejo_migration
Request migration to the new forge

  
Gain
High
 task that gets us a lot / is important / makes many people happy

Archived

  
Gain
Low
 tasks that gets us little / isn't very important / makes only 1 person or few happy

Archived

  
Gain
Medium
 task that gets us some / is somewhat important / makes some people happy

Archived

  
gitlab

   
greenwave
Issues with greenwave

  
hardware
Problem is with Fedora Infrastructure Owned/Leased Hardware

  
help wanted

   
high-trouble
task that is complex/long/difficult

Archived

  
koji
Issues with the build system

  
koschei
Items needing Koschei team

  
lists
issues with lists

  
low-trouble
task that is easy/short

Archived

  
medium-trouble
task that is medium complex / difficult

Archived

  
mirrorlists
Way to tell systems where downloads are

  
monitoring

   
Needs investigation

   
odcs
On Demand Compose Service issues

Archived

  
OpenShift
Issues with OpenShift

  
ops
ops problem now...

Archived

  
outage

   
packager_workflow_blocker
Blocks the packager workflow

Archived

  
pagure
Issues with pagure.io

  
permissions
Items which need permissions set in outside tools

  
Priority
Needs Review
 Priority of Needs Review

Archived

  
Priority
Next Meeting
 Priority of Next Meeting

Archived

  
Priority
🔥 URGENT 🔥
 Priority of 🔥 URGENT 🔥

Archived

  
Priority
Waiting on Assignee
 Priority of Waiting on Assignee

Archived

  
Priority
Waiting on External
 Priority of Waiting on External

Archived

  
Priority
Waiting on Reporter
 Priority of Waiting on Reporter

Archived

  
rabbitmq
issues with the message broker

  
release-monitoring
release-monitoring.org (Anitya)

  
releng
For problems which should be in the releng ticket system

Archived

  
request-for-resources

   
s390x
The secondary architecture hardware and problems related with it

  
security

   
SMTP
Email issues outside of lists (DMARC, SPF, aliases)

  
sprint-0

Archived

  
sprint-1

Archived

  
src.fp.o
Issues related to src.fedoraproject.org

  
staging
Issues in staging

  
unfreeze
Patches to be applied after freeze is lifted

  
waiverdb
Issues with waiverdb

  
websites-general
General items with a website focus

  
wiki
Issues with the Wiki

  
Backlog Status
Needs Review
 Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
 Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

  
chore
Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  
documentation
Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  
points
01
 A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
 This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
 Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
 A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
 Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
 Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

  
Priority
High
 This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
 This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
 This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
 Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
Sprint Status
Done
 Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
 Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
 Work items that are complete but need review, testing, or approval before being marked as done.

  
Sprint Status
To Do
 Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt
Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

  
Work Item
Bug
 Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic
 Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Work Item
Spike
 Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
 Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  
Work Item
User Story
 User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels
announcement
anubis
authentication
aws
backlog
blocked
bodhi
ci
cloud
communishift
copr
database
day-to-day
dc-move
deprecated
dev
discourse
dns
downloads
easyfix
epel
firmitas
forgejo_migration
Gain
High
Gain
Low
Gain
Medium
gitlab
greenwave
hardware
help wanted
high-trouble
koji
koschei
lists
low-trouble
medium-trouble
mirrorlists
monitoring
Needs investigation
odcs
OpenShift
ops
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
release-monitoring
releng
request-for-resources
s390x
security
SMTP
sprint-0
sprint-1
src.fp.o
staging
unfreeze
waiverdb
websites-general
wiki
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
6 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
infra/tickets#13131
No description provided.