openSUSE admin

Hello,

currently this machine/service does not seem to be maintained. The "pagure" category in this tracker shows 11 open tickets waiting for maintainer input [0].
As per our policy [1], a service maintainer must monitor their tickets and respond to emails in a timely fashion.
I'm afraid this does not seem to be the case with pagure01, not even critical tickets [2] [3] related to this machine see a response. That, combined with the service not working out of the box [2], makes me see the machine in violation of three policies: 4, 5, 8.
I understand that it is not always possible to ensure consistent coverage, and me and other administrators tried to make up for this situation in the past, but motivation seems to have faded.

@Pharaoh_Atem - you are the listed maintainer for this machine. What are the plans for this machine and service? Are you still interested in maintaining it and want to spend the needed time and effort to do so?
If yes, please mitigate the mentioned concerns which currently cause poor user experience and increased maintenance burden on other administrators.
If no, then either a different maintainer needs to be found [4], or the machine and service need to be decommissioned. I understand that https://code.opensuse.org is a relatively widely used service with the openSUSE community, making the latter a rather difficult decision - we would need to offer users alternative options and should consider migration paths.

[0] https://progress.opensuse.org/projects/opensuse-admin/issues?set_filter=1&sort=id%3Adesc&f%5B%5D=status_id&op%5Bstatus_id%5D=o&f%5B%5D=category_id&op%5Bcategory_id%5D=%3D&v%5Bcategory_id%5D%5B%5D=799&f%5B%5D=&c%5B%5D=subject&c%5B%5D=project&c%5B%5D=status&c%5B%5D=assigned_to&c%5B%5D=fixed_version&c%5B%5D=is_private&c%5B%5D=due_date&c%5B%5D=relations&group_by=&t%5B%5D=
[1] https://en.opensuse.org/openSUSE:Infrastructure_policy
[2] https://progress.opensuse.org/issues/177195
[3] https://progress.opensuse.org/issues/181646
[4] There has been a brief period of interest from a different user (@wombelix) to help with maintenance, but this seems to not have lasted, as the tickets they took now no longer see a response either.