Hi, On 14.04.2012 15:41, Stefano Zacchiroli wrote: > 1) notify the last maintainer of a orphaned package when requesting its > removal (that could happen automatically --- if someone provides the > appropriate patch to the appropriate piece of infrastructure --- or > simply documented as a best practice in devref)
Or, simply require packages to go through sunset phase before being
effectively removed unless there is some urgency required. I don't think
we need to rush through removal requests that fast. If a package is
orphaned for years already a few more days won't matter.
Maybe we could establish some best practices for package removals like
filing a RC bug against the package assigned beforehand and reassign to
ftp.d.o a few days - say 10 or so - later. If conditional package
subscriptions would be possible already ("subscribe me to RC bugs
against package X") everyone who bothers a bit but not enough to get all
the noise of unimportant issues could be warned in advance and act if
desired.
Moreover, these bugs could be filed with a specific user tag to allow
everyone to track them easily. That's helpful for both parties: Those
who want to get rid about a package and those who possibly want to safe
a package.
Just as a random idea, maybe someone comes up with something better
which would allow a graceful removal.
--
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D
signature.asc
Description: OpenPGP digital signature
