inactive maintenance
Hello, mentors
I'm wondering if there is a practice to force package to be orphaned in a
case of chronic lack of maintenance?
Perhaps, for some package there was no maintainer activity for several
years, but only NMU's, wich purpose was not to fix some critical bugs but
just to update a very old software version.
The situation is even worse: the maintainer is popping up from time to time
and permitting to do a NMU with "so much changes in the package". In
result, there is possible to upload to 'experimental' keeping all old
technical garbage and crooks and not to improve the packaging quality.
Should exist some way to fix that.
--
Regards,
Al Nikolov jid: alnikolov@jabber.ru irc: clown uin: 312108671
pgp fingerprint: 4B50 F1E3 080C 21A2 91F4 8BF0 CD60 3B5A 2ECF 984B
Reply to: