Non-responsive maintainer: benzea #3672

Closed
opened 2026-08-05 00:12:22 +00:00 by ngompa · 20 comments
Owner

FAS username of the non-responsive maintainer

benzea

Names of package(s) with unaddressed issues

thermald, libfprint, fprintd, fwts

No response

Unaddressed issues

No pull requests have been addressed and merged by the maintainer in well over a year (other people have been doing it instead).

This can be seen in https://src.fedoraproject.org/rpms/thermald/pull-requests?status=Merged

This pattern exists in other packages mentioned above.

Link to mailing list post for the non-responsive maintainer process

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/PHWTVQHYV3BCD2KP3QYC2XVF7FUH2BKR/

Affected package co-maintainers (if any)

No response

Submitter is interested in comaintaining the package(s):

  • Yes

Additional notes

I'm filing this because I discovered benzea's email address is not valid and not having a proper maintainer for thermald et al is a problem. I'm fine stepping up for this purpose.

This is a ticket for the Fedora's Policy for nonresponsive package maintainers.

### FAS username of the non-responsive maintainer benzea ### Names of package(s) with unaddressed issues thermald, libfprint, fprintd, fwts ### Link to non-responsive maintainer bug _No response_ ### Unaddressed issues No pull requests have been addressed and merged by the maintainer in well over a year (other people have been doing it instead). This can be seen in https://src.fedoraproject.org/rpms/thermald/pull-requests?status=Merged This pattern exists in other packages mentioned above. ### Link to mailing list post for the non-responsive maintainer process https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/PHWTVQHYV3BCD2KP3QYC2XVF7FUH2BKR/ ### Affected package co-maintainers (if any) _No response_ ### Submitter is interested in comaintaining the package(s): - [x] Yes ### Additional notes I'm filing this because I discovered benzea's email address is not valid and not having a proper maintainer for thermald _et al_ is a problem. I'm fine stepping up for this purpose. This is a ticket for the Fedora's [Policy for nonresponsive package maintainers](https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/).
gotmax23 added the due date 2026-08-25 2026-08-05 04:11:54 +00:00
Owner

benzea is maintainer of rpms/bolt
benzea is main admin of rpms/fprintd
rpms/fprintd co-maintainers: @smallorange
benzea has a bugzilla override on rpms/fprintd
benzea is main admin of rpms/fwts
benzea has a bugzilla override on rpms/fwts
benzea is maintainer of rpms/gamemode
benzea is main admin of rpms/gnome-network-displays
rpms/gnome-network-displays co-maintainers: @lorbus
benzea has a bugzilla override on rpms/gnome-network-displays
benzea is main admin of rpms/libfprint
rpms/libfprint co-maintainers: @smallorange
benzea has a bugzilla override on rpms/libfprint
benzea is maintainer of rpms/libusb-compat-0.1
benzea is maintainer of rpms/libusb1
benzea is main admin of rpms/thermald
benzea has a bugzilla override on rpms/thermald
benzea is maintainer of rpms/umockdev
benzea is maintainer of rpms/upower
benzea is main admin of rpms/uresourced
rpms/uresourced co-maintainers: @smallorange
benzea has a bugzilla override on rpms/uresourced

benzea is maintainer of rpms/bolt benzea is main admin of rpms/fprintd rpms/fprintd co-maintainers: @smallorange benzea has a bugzilla override on rpms/fprintd benzea is main admin of rpms/fwts benzea has a bugzilla override on rpms/fwts benzea is maintainer of rpms/gamemode benzea is main admin of rpms/gnome-network-displays rpms/gnome-network-displays co-maintainers: @lorbus benzea has a bugzilla override on rpms/gnome-network-displays benzea is main admin of rpms/libfprint rpms/libfprint co-maintainers: @smallorange benzea has a bugzilla override on rpms/libfprint benzea is maintainer of rpms/libusb-compat-0.1 benzea is maintainer of rpms/libusb1 benzea is main admin of rpms/thermald benzea has a bugzilla override on rpms/thermald benzea is maintainer of rpms/umockdev benzea is maintainer of rpms/upower benzea is main admin of rpms/uresourced rpms/uresourced co-maintainers: @smallorange benzea has a bugzilla override on rpms/uresourced
Owner

+1

+1
Author
Owner

+1

+1
Owner

+1

+1
Owner

So, I'm not sure "fast-track" is actually a valid choice here. The non-responsive maintainer process has its own deadlines, including shorter ones for users with invalid email addresses.

EDIT: Procedural questions aside (even if fast-track is not applicable here, the request might qualify for the exception procedure in case of urgency): +1

So, I'm not sure "fast-track" is actually a valid choice here. The non-responsive maintainer process has its own deadlines, including shorter ones for users with invalid email addresses. EDIT: Procedural questions aside (even if fast-track is not applicable here, the request might qualify for the [exception procedure](https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/#exception-procedure) in case of urgency): +1
Author
Owner

So, there are serious functionality problems with existing thermald in Fedora stable releases with laptops released in the past year or so, and one was flagged to me privately, which is what drove this. I'd like to be able to take over the packages I listed above as soon as possible so I can resolve these issues now and going forward as part of Fedora Ready work.

This seems to be possible with the exception process, I think? I assumed the fast track label was used for this, but if it isn't, I'd still like to get this taken care of somehow ASAP.

So, there are serious functionality problems with existing thermald in Fedora stable releases with laptops released in the past year or so, and one was flagged to me privately, which is what drove this. I'd like to be able to take over the packages I listed above as soon as possible so I can resolve these issues now and going forward as part of Fedora Ready work. This _seems_ to be possible with the exception process, I think? I assumed the fast track label was used for this, but if it isn't, I'd still like to get this taken care of somehow ASAP.
Owner

+1

+1
Owner

+1

+1
Owner

After three days: APPROVED (+6, 0, -0)

@ngompa should now be made a co-maintainer admin on thermald, libfprint, fprintd, and fwts.

If there is no further response by 2026-08-25. @ngompa will then be given main admin on those four packages and the rest of the maintainer's packages will be orphaned.

After three days: APPROVED (+6, 0, -0) @ngompa should now be made a co-maintainer admin on thermald, libfprint, fprintd, and fwts. If there is no further response by 2026-08-25. @ngompa will then be given main admin on those four packages and the rest of the maintainer's packages will be orphaned.
Owner

@ngompa should now be made a co-maintainer admin on thermald, libfprint, fprintd, and fwts.

I have processed this now.

> @ngompa should now be made a co-maintainer admin on thermald, libfprint, fprintd, and fwts. I have processed this now.

Benjamin has commented in Workstation Working Group tickets recentlyish, but on pagure.io, not on Forge. Looks like he doesn't have a Forge account.

Benjamin has commented in Workstation Working Group tickets recentlyish, but on pagure.io, not on Forge. Looks like he doesn't have a Forge account.

Hi @ngompa and @catanzaro

If Benjamin agrees, I can take on libfprint, fprintd, and thermald packages. I maintain all three packages in RHEL.

Hi @ngompa and @catanzaro If Benjamin agrees, I can take on libfprint, fprintd, and thermald packages. I maintain all three packages in RHEL.
Owner

@smallorange wrote in #3672 (comment):

I can take on libfprint, fprintd, and thermald packages. I maintain all three packages in RHEL.

Thanks! @ngompa, do you want to add @smallorange as a co-maintainer?

@smallorange wrote in https://forge.fedoraproject.org/fesco/tickets/issues/3672#issuecomment-1268493: > I can take on libfprint, fprintd, and thermald packages. I maintain all three packages in RHEL. Thanks! @ngompa, do you want to add @smallorange as a co-maintainer?
Author
Owner

@gotmax23 wrote in #3672 (comment):

@smallorange wrote in #3672 (comment):

I can take on libfprint, fprintd, and thermald packages. I maintain all three packages in RHEL.

Thanks! @ngompa, do you want to add @smallorange as a co-maintainer?

I am fine with doing so, but I still want to be main admin at the end of this.

@gotmax23 wrote in https://forge.fedoraproject.org/fesco/tickets/issues/3672#issuecomment-1268499: > @smallorange wrote in #3672 (comment): > > > I can take on libfprint, fprintd, and thermald packages. I maintain all three packages in RHEL. > > Thanks! @ngompa, do you want to add @smallorange as a co-maintainer? I am fine with doing so, but I still want to be main admin at the end of this.
Owner

Pinging @benzea as per policy. Mass orphaning is slated for next week.

Pinging @benzea as per policy. Mass orphaning is slated for next week.

Huhu.

@smallorange becoming the main maintainer is the logical thing to happen. We just never did a formal handover years ago. I suppose I can also just do that myself?

For thermald, ARM people seem to have an interest and @aekoroglu. I could imagine making them comaintainer but I have no idea about their credentials (other than they seem to work for Qualcomm)

Huhu. @smallorange becoming the main maintainer is the logical thing to happen. We just never did a formal handover years ago. I suppose I can also just do that myself? For thermald, ARM people seem to have an interest and @aekoroglu. I could imagine making them comaintainer but I have no idea about their credentials (other than they seem to work for Qualcomm)

I gave fprintd, libfprint and thermald to Kate. I do not think that anyone really cares about fwts and would probably propose simply keeping it orphaned or removing it.

I gave fprintd, libfprint and thermald to Kate. I do not think that anyone really cares about fwts and would probably propose simply keeping it orphaned or removing it.
Owner

@benzea thank you for taking care of this.
Is there anything left to do here or can we close the ticket?

@benzea thank you for taking care of this. Is there anything left to do here or can we close the ticket?

Hi,

I noticed the changes and started working on them.
If no issues were found, this issue can be closed.

Thank you :)

Hi, I noticed the changes and started working on them. If no issues were found, this issue can be closed. Thank you :)
Owner
Announced with today's meeting agenda: <https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/LHIPD44PUJMABJZQV5ETBVC33GSOMO4H/>
decathorpe 2026-09-08 13:02:39 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
11 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

2026-08-25

Dependencies

No dependencies set.

Reference
fesco/tickets#3672
No description provided.