On Mon, Jun 29, 2009 at 8:38 AM, Remco <span dir="ltr"><<a href="mailto:remco47@gmail.com">remco47@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Mon, Jun 29, 2009 at 4:18 PM, Rosanne DiMesio<<a href="mailto:dimesio@earthlink.net">dimesio@earthlink.net</a>> wrote:<br>
> On Mon, 29 Jun 2009 15:48:17 +0200<br>
<div class="im">> Remco <<a href="mailto:remco47@gmail.com">remco47@gmail.com</a>> wrote:<br>
>><br>
</div>>> Ok, I thought everybody got their AppDB updates by mail. But whichever<br>
>> way you receive notice of queued submissions without maintainers,<br>
>> that's where the maintained submissions can be sent after 24 hours.<br>
>><br>
>> Remco<br>
><br>
> Admins can already see all test reports in the queue. That's not the issue. The issue is removing maintainers who aren't doing their job. If we do their job for them, with no consequences to the negligent maintainer, that merely covers up the problem.<br>
<br>
So the issue is not that queued submissions aren't handled, but...<br>
what? I thought the problem was unhandled submissions, caused by<br>
negligent maintainers. But if that problem is not there, what problem<br>
are negligent maintainers causing?<br>
<font color="#888888"><br>
Remco<br>
<br>
</font></blockquote><div><br>It sounds like they're causing too much extra work for the admins.� What if the system checked for "Out of Office" bounces and used that to know that a maintainer was not going to be able to handle the submission for a while?<br>
<br>Erich Hoover<br><a href="mailto:ehoover@mines.edu">ehoover@mines.edu</a><br></div></div>