On 03/12/16 11:42, Mattia Rizzolo wrote: > On Fri, Dec 02, 2016 at 10:56:07PM +0500, Andrey Rahmatullin wrote: >> * So, the final question: how much time should pass since the last >> maintainer upload (since removal from testing, since the first still >> unfixed RC bug, how many NMUs should exist since the last maintainer >> upload) to be able to just do a QA upload (without changing the Maintainer >> field as it's prohibited on the https://wiki.debian.org/Teams/MIA page) >> instead of finely-crafting minimal diffs and fixing only things allowed by >> devref 5.11.1? > > We discussed several times internally in the MIA team during the year > how to just "declare" a maintainer gone based on the current state > (last upload, gpg key ok, number of RCs, number of NMUs, etc), but the > consensus has been that it's just plain hard/impossible to give an > appropriate answer good for all cases. We shall discuss this again at > DebConf instead.
I would suggest to come up with some algorithm to determine if a package is effectively unmaintained, and implement it in an automatic way that gives maintainers prior notice and a chance to react, like we do with auto-removals. Then if nothing happens in a reasonable time frame, the package gets orphaned. I think we should also have an auto-removals-from-sid[1] (the crowd applauded when I mentioned that in my Debconf talk), which would solve/help your high number of orphaned packages. Cheers, Emilio [1] With a *very* conservative criteria. We don't want to remove a package from the archive after 30 days because of 1 RC bug.
