According to https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers you need to create a bug about the packager being nonresponsive, not just link an ignored bug.

Done https://bugzilla.redhat.com/show_bug.cgi?id=1612087

P.S. But as I understand https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers:
5. After other 7 days (now 3 weeks total), the reporter creates a FESCo issue with the bug link

This "bug link" is the same as in
1. File a bug against the package in Bugzilla asking for the maintainer to respond.

My first bugreport is for asking maintainer to response.

Please also send a message to fedora-devel after the bug is two weeks old and make a note of this here. Assuming that there's no response, we'll finish the procedure here then.

Bug about get response from wolnei already created three weeks ago. Message to fedora devel already send one weeks ago.

@vascom please add a link to the archive with the message that you sent to the ticket. Please also add a new reminder comment to the bug report. IMHO it should be enough then if there is no responsive to consider @wolnei non-responsive.

Link to mail list archive https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/NPSIU34FJX2KA3XVE2DG4APETG53BF5W/#7LETI6B4NKUXXQBNZUPSSVW4R32JWFBU
Reminder to bugreport added.

Do I need any more actions?

@kevin I have commited / builded the pull request, I think @wolnei is temporary out, Can you fix this by keeping @wolnei and adding @vascom as admin to the kio-gdrive package ?

+1 to reassign kio-gdrive to @vascom now.

@kevin I have commited / builded the pull request, I think @wolnei is temporary out, Can you fix this by keeping @wolnei and adding @vascom as admin to the kio-gdrive package ?

IMHO it would be better to just add @wolnei again when he would like to maintain it again. IMHO having inactive maintainers assigned to pkgs makes it unnecessary hard to figure out the maintenance status of pkgs.

Done.

Thanks.