Re: Maintaining potentially orphaned packages in Debian Commons team

[email protected] wrote:
>
>For clucene-core we have a maintainer who has not uploaded in nearly ten
>years, contact attempts that went unanswered, repeated NMUs, and pending
>fixes from contributors. Yet, as far as I understand, there is currently
>no established procedure that would allow the package to become formally
>orphaned without active involvement from the maintainer.
>
>This is exactly the gap I am trying to discuss. If we believes that such
>packages should become formally orphaned rather than move to Debian
>Commons, what is the practical path to achieve that? 

What am I missing here? This sounds like a classic example of
something that normally gets done with MIA processing.

Is the (non-)maintainer responding at all?