Re: F44 Spins/Labs Keepalive

Hey Timothée,

Thanks for pointing out the Atomic Desktops are missing and for your thoughts on the wiki page with the new toml file (ttps://pagure.io/fedora-kiwi-descriptions/blob/rawhide/f/maintainers.toml#_72). I am happy to retire the wiki, but was unsure if there were any references to that page that should be updated before deprecating the wiki page.

Also, another question for you if you don't mind. I was using https://fedoraproject.org/spins and https://fedoraproject.org/labs as my source of truth for all Spins/Labs. It seems it makes sense now to also use that toml file for these as well. Reading that file, would it be safe to say we  should use the name that prepends the architecture for each? IE for this section, create a ticket for onyx? 

# Budgie Atomic
	[onyx.x86_64]
	fas = [ "joshstrobl" ]
	maintainers = [ "Joshua Strobl" ]
	[onyx.aarch64]
	fas = [ "joshstrobl" ]
	maintainers = [ "Joshua Strobl" ]

Thanks!
Allison

On Fri, Jan 9, 2026 at 10:47 AM Timothée Ravier <travier@redhat.com> wrote:

Hey Alisson,

The first batch looks good but I think we are missing all the Atomic Desktops, so we would need tickets for each Atomic Desktops variant as well.

As you found out in https://pagure.io/fedora-pgm/schedule/issue/238, it appears that we have two sources for the Spin maintainers: https://fedoraproject.org/wiki/SpinsandLabs & https://pagure.io/fedora-kiwi-descriptions/blob/rawhide/f/maintainers.toml

It would be good to retire the Wiki page and use only the one from the fedora-kiwi-descriptions repo.

Thanks

On Wed, Jan 7, 2026 at 7:39 PM Allison King via devel-announce <devel-announce@lists.fedoraproject.org> wrote:

FESCo previously approved a requirement[1] that Spin/Labs owners send a
keepalive request in order to keep building the spin or lab. I have
opened Pagure issues[2] for all Spins and Labs for this release,

If you are the owner of one of those spins and labs, please reply in
the appropriate ticket by January 14, 2026 to indicate the spin should
continue to be produced. Note, I am working out permissions issues to

be able to set the Assignee of these tickets, but wanted to send this email

since many of you have already began commenting on the tickets.

If there is a spin or lab that does not have
an open ticket, please create one[3].

For the full list of Spins and Labs with maintainer assignments, see[4].

The reasoning for this is to not ship spins that are not actively
maintained. Future improvements to the release process that will allow
for teams to self-publish solutions will eventually remove the need
for these keepalives.

[1] https://pagure.io/fesco/issue/1972
[2] https://pagure.io/fedora-pgm/schedule/issues?status=Open&tags=spins+keepalive
[3] https://pagure.io/fedora-pgm/schedule/new_issue
[4] https://fedoraproject.org/wiki/SpinsandLabs

Thanks,
Allison

--
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

--

Timothée Ravier

CoreOS Team Lead

Red Hat

travier@redhat.com

--

Allison King

Senior Technical Project Manager, In-Vehicle OS

Red Hat

alking@redhat.com