Yes, some have an active maintainer but some don't. It was just an example which came to my mind as first. For the examples of cooktimer and backupmenu, we can easily ask why the maintainer hasn't uploaded it to extras-testing. For some not, for example many of D-ivill themes are stuck in extras-devel while we all know he left the scene and there's nothing wrong with these themes either


Before I start doing this, I want to have a chat with someone how to do this transparently as I can't crunch through all devel-packages alone, there thousands of them. Of course I will try to "test" as much packages as possible but I can't "test" them all alone.

I would like to have list of all packages including version number in extras-devel. From that list we mark packages as ready for testing.
(If it's ready for testing some kind of super-tester should promote it to testing from there the voting system should do it's job again to get it into extras. )


Maybe a wiki page would be good for this purpose. Everyone with an account can access and add info to it if needed.

After we completed the list we could contact all maintainers asking why they didn't promote their package. If they don't answer within 2 months or don't promote we do it ourselves?