fas username: @fab
Spin/lab: security-lab
issues to fix: https://pagure.io/fedora-pgm/schedule/issue/30
comaintainer: @jsimon
I am interested in comaintaining the spin/lab: yes
additional notes:

The Maintainer of the Security Lab has failed to respond to the FESCo Requirement that Spins/Labs confirm they want it to continue. PgM Ticket: https://pagure.io/fedora-pgm/schedule/issue/30

I asked Ben Cotton what the process was, and he said that there isn't a Spin-specific process, so to just go through the normal non-responsive maintainer process. Per Neal Gompa, its a Fesco ticket. I filed that ticket and learned I needed to file a bugzilla ticket.  The forms for nonresponsive package maintainer, nonresponsive container maintainer, and nonresponsive module maintainer dont allow me to continue since a spin/lab are made in the build process and arent listed as a component.  I spoke with Ben Cotton directly and he suggested I file this ticket against the distribution component.  FESCo Ticket: https://pagure.io/fesco/issue/2658

I checked Fab's Fedora activity, and he hasn't done anything with Fedora since April, and I know Fab is active in other projects (according to his github profile activity), so I'm assuming he's moved on. The other comaintainer has had no activity with Fedora within the past year.
It seems to me, although I may be incorrect about this, that both of the maintainers are inactive, as the last commit to the repo was 2 years ago and there are open issues that are 3 years old and a PRs that's 4 years old in the Lab Pagure repo.

In order to maintain the Lab, I'd need to be given access/admin to the Pagure Repo for the Security Lab: https://pagure.io/security-lab

I don't want the Lab to stop since I use it myself for work.

So I'm filing this ticket to start the clock on the process. If there is anything else I should be doing, or something I should do differently, please let me know.