#2138 Non-responsive maintainer mitr (m2crypto)
Closed: Invalid 3 months ago by churchyard. Opened 3 months ago by ngompa.

I've been trying to get m2crypto fixed in Fedora for a couple of months now1. Unfortunately, the maintainer (mitr) has been rather unresponsive, despite contact via email2 and through the Red Hat Bugzilla3.

The m2crypto package has been broken since Fedora 29, and I'd like to take it over and fix it as it's a dependency for a couple of my packages.

Metadata Update from @churchyard:
- Issue tagged with: nonresponsive maintainer

3 months ago

Looking over the history here, I'm forced to agree. @mitr appears to be non-responsive and we should put his packages up for alternate maintainers. Note that some of these packages are critical to the operating system.

It looks like he's only the sole admin of m2crypto and python-gtkextra. The rest appear to have other maintainers (primary or otherwise)...

+1. @mitr also said at https://src.fedoraproject.org/rpms/m2crypto/pull-request/2#comment-22968 that it would be OK for someone else to take the package.

I’m sorry about the late response. m2crypto is now transferred to @ngompa .

As for the other packages on https://src.fedoraproject.org/user/mitr/projects,
- audit-viewer will die with the Python 2 removal; I don’t know about anyone interested in porting it to Python 3
- python-gtkextra still exists, but it is a wrapping for an upstream-unmaintained (http://gtkextra.sourceforge.net/cms/index.php?option=com_content&view=article&id=63:new-maintainer-searched&catid=3:news) , AFAICS GTK2-only, widget set (and locally patched to benefit audit-viewer).

(all the rest are either dead.packaged or have different primary owners).

I expect the two packages above to die sooner or later; if FESCo wants them orphaned right now, I’m fine with that.

I personally recommend to orphan them if you know you don't have time to take care of them. Either somebody else will or they will get retired.
However, since you responded, I don't think FESCo should decide that.
The m2crypto issue has been resolved, thank you.

Metadata Update from @churchyard:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

3 months ago

Login to comment on this ticket.