Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:2948 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81485 invoked from network); 28 Jun 2003 15:57:14 -0000 Received: from unknown (HELO netphobia.fi) (213.243.181.8) by pb1.pair.com with SMTP; 28 Jun 2003 15:57:14 -0000 Received: from localhost (jani@localhost) by netphobia.fi (8.11.6/8.11.6) with ESMTP id h5SFvBl14544; Sat, 28 Jun 2003 18:57:12 +0300 X-Authentication-Warning: netphobia.fi: jani owned process doing -bs Date: Sat, 28 Jun 2003 18:57:11 +0300 (EEST) Sender: jani@netphobia.fi Reply-To: Jani Taskinen To: Sascha Schumann cc: internals@lists.php.net In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] Re: networking bugs and bugme.osdl.org (fwd) From: sniper@iki.fi (Jani Taskinen) On Sat, 28 Jun 2003, Sascha Schumann wrote: >> But if the summaries contain only screened (== verified) reports, >> and sent one per category? Better ideas would be appreciated, of course. > > Well, I pretty much embrace the idea that reports ought to > fall through the cracks, if they don't bother developers > enough to address them. Otherwise, reports just accumulate > and accumulate without having any effect. Currently you don't get any mails from the reports unless someone touches them. So they do 'fall through the cracks' already, sort of. By adding the 'rotting' feature will make this a bit more effective. Just thinking whether or not there should be a notification for the submitter when a report rots. Comments? Getting all the emails from php-bugs@lists.php.net is really too much traffic, that's why I was thinking about adding some headers to the mails to make it easier to filter out those you really want to see. Some short cut URLs would do this already though, using the web interface and search..but it's not quite the same. :) --Jani