As per the Non-responsive Maintainer Policy (https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers) I have attempted to contact the maintainer without success.
A bug was filed against the package (https://bugzilla.redhat.com/show_bug.cgi?id=1553215) and was also posted to the devel list (https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/OCPI3MDCTL6OCTGDVTZIQ76JOWZORWLC/).
As there are a number of outstanding issues, and the maintainer cannot be contacted, I wish to take over the package.
This will be discussed at the 2018-04-06 FESCo meeting.
Metadata Update from @sgallagh: - Issue tagged with: meeting
Thanks @sgallagh, I won't be able to make the meeting tomorrow. Is there anything you might need from me further to what's here and in BZ?
+1 for assigning the package to @thomasfedb
@thomasfedb I don't think so. This looks like a clear-cut decision to me. You've followed the process and are offering to take it over, so I doubt there will be any argument.
+1 too
+1 as well
Just to let you know I'm still available. Unfortunately I have missed Thomas' attempts to contact me. I just heard about the unresponsive maintainer ticket today... Since my time is limited at the moment, I'll go over my packages and make a proposal which I'd like to keep maintaining, for which it would make sense to have co-owners and which should be probably orphaned or deprecated.
@chkr very happy to be co-maintainers for anki if that would suit you?
@thomasfedb Yes, it would perfectly. To sync-up regarding anki I'll send you an email later today.
Did anyone see a follow-up on this?
@jsmith well, anki 2.0.50 is in testing. Not sure if @chkr has worked out what's happening with their other packages.
@jsmith Sorry, I was busy updating anki (and scummvm) in the last days.
Basically I want to keep maintaining packages in Fedora, but I'm going to drop maintainership for some packages which I'm not interested anymore and which are already maintained by others. Some packages may get orphaned or deprecated. I'm going to take care of this over the weekend.
If there is anything else I should do now, please let me know.
This was discussed in FESCo meeting today: - anki maintainer is responsive again (tyll, 15:35:27) - AGREED: No additional action is required from FESCo (+5, 0, 0) (zbyszek, 15:36:15)
Metadata Update from @zbyszek: - Issue untagged with: meeting - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @zbyszek: - Issue close_status updated to: None (was: Fixed) - Issue tagged with: nonresponsive maintainer
Login to comment on this ticket.