In accordance with FESCo's Inactive Packager Policy[1], packagers that have been identified as inactive have a ticket in the find-inactive-packagers repo[2]. One week after the final release, packagers who remain inactive will be removed from the packager group. (Note that pagure.io is one of the systems checked for activity, so commenting on your ticket that you're still around will prevent you from showing up in the second round.)
If you have suggestions for improvement, look for the open feature issues[3] and file an issue in the find-inactive-packagers repo[4] if it's not there already.
For the curious, here are the stats from today's run:
### Found 1391 users in the packager group. ### ### Found 557 users with no builds in Koji over the last year. ### ### Found 481 users with no activity in forge.fedoraproject.org in the last year. ### ### Found 369 users with no activity in src.fp.org over the last year. ### ### Found 353 users which didn't post any message in Fedora Discussion over the last year. ### ### Found 322 users which also show no activity in Bodhi over the last year. ### ### Found 302 users which also show no activity in mailing lists over the last year. ### ### Found 226 users which also show no activity in Bugzilla over the last year. ###
[1] https://docs.fedoraproject.org/en-US/fesco/Policy_for_inactive_packagers/ [2] https://forge.fedoraproject.org/packaging/find-inactive-packagers/issues?q=&... [3] https://forge.fedoraproject.org/packaging/find-inactive-packagers/issues?q=&... [4] https://forge.fedoraproject.org/packaging/find-inactive-packagers/issues/new
domenica 23 agosto 2026 18:24, Artur Frenszek-Iwicki suve@fedoraproject.org ha scritto:
Note that pagure.io is one of the systems checked for activity, so commenting on your ticket...
Don't know if the opening paragraph is populated by a script or just copy-pasted, but this line should be updated to reflect the forge.fp.o migration.
Yes, I copy/pasted the text from previous email and that part slipped to my attention. I'll have to remember to fix it in the next run, thanks.
Mattia
Dne 23. 08. 26 v 12:56 odp. Mattia Verga via devel-announce napsal(a):
In accordance with FESCo's Inactive Packager Policy[1], packagers that have been identified as inactive have a ticket in the find-inactive-packagers repo[2]. One week after the final release, packagers who remain inactive will be removed from the packager group. (Note that pagure.io is one of the systems checked for activity, so commenting on your ticket that you're still around will prevent you from showing up in the second round.)
If you have suggestions for improvement, look for the open feature issues[3] and file an issue in the find-inactive-packagers repo[4] if it's not there already.
I find this report very hard to review. If I want to check if the report include me or some people from my team, I can only go to
https://forge.fedoraproject.org/packaging/find-inactive-packagers/issues?pag...
and that include several pages that I have to click through.
Is is possible to produce the list of usernames in plain text in this email?
lunedì 24 agosto 2026 10:13, Miroslav Suchý via devel devel@lists.fedoraproject.org ha scritto:
Dne 23. 08. 26 v 12:56 odp. Mattia Verga via devel-announce napsal(a):
In accordance with FESCo's Inactive Packager Policy[1], packagers that have been identified as inactive have a ticket in the find-inactive-packagers repo[2]. One week after the final release, packagers who remain inactive will be removed from the packager group. (Note that pagure.io is one of the systems checked for activity, so commenting on your ticket that you're still around will prevent you from showing up in the second round.)
If you have suggestions for improvement, look for the open feature issues[3] and file an issue in the find-inactive-packagers repo[4] if it's not there already.
I find this report very hard to review. If I want to check if the report include me or some people from my team, I can only go to
https://forge.fedoraproject.org/packaging/find-inactive-packagers/issues?pag...
and that include several pages that I have to click through.
Is is possible to produce the list of usernames in plain text in this email?
I could... but I didn't, since the list is usually 150 / 250 names long. I thought it was more handy to go to the ticket list webpage and use the filter to search for usernames. But if there's request to list all affected usernames here, I'll modify the template the next time.
Mattia
Dne 24. 08. 26 v 12:02 odp. Mattia Verga via devel napsal(a):
But if there's request to list all affected usernames here, I'll modify the template the next time.
I will welcome that. Putting 10 names in search box and submitting them is significantly slower than scrolling through 250 (sorted) names.