= phenomenon = Hi
According the Policy for nonresponsive package maintainers, I created this issue because the maintener of the poco package is not responding and all reasonable efforts to contact the maintainer have failed.
I a willing to become a co maintener since I have already build a valid rpms in the isolated sandbox for the latest official release of poco https://github.com/pocoproject/poco/releases/tag/poco-1.6.1-release
I am part of the upstream Poco team contributors
= background analysis =
= implementation recommendation =
We'll discuss this in the meeting tomorrow at 17:00 UTC on #fedora-meeting
According packagedb, poco has a single maintainer which is unhealthy. https://admin.fedoraproject.org/pkgdb/package/rpms/poco/
Moreover, he seems inactive for a while: /fedora_active_user.py --user udushlivy FAS password for hguemar: Last login in FAS: udushlivy 2011-11-03 Last action on koji: Thu, 17 Sep 2015 package list entry created: poco in f23_Beta by ausil [still active] Last package update on bodhi: ERROR:active-user:'updates'
Since reporter is willing to maintain this package and is upstream core contributor, I suggest. 1. +1 to sponsor him through the comaintainership process (I recommend finding comaintainers) 2. have a provenpackager do the update if required.
I can sponsor him and do the update in rawhide when I'm back home if nobody does it.
udushlivy was maintaining a single package in Fedora and hadn't touched since june, 2010.
+1 to orphan this poco package and if reporter is interested then let him own this after he gets sponsored in packager.
+1 to orphan poco and sponsor reporter to own it.
+1
+1 to orphan and have hguemar sponsor them so they can maintain.
With that I see +5, so I have orphaned the package.
Login to comment on this ticket.