Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:2945 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 27883 invoked from network); 28 Jun 2003 14:43:18 -0000 Received: from unknown (HELO milton.schell.de) (217.160.72.35) by pb1.pair.com with SMTP; 28 Jun 2003 14:43:18 -0000 Received: (qmail 6334 invoked by uid 501); 28 Jun 2003 14:43:17 -0000 Received: from unknown (HELO eco.foo) (80.143.47.226) by kdserv.de with SMTP; 28 Jun 2003 14:43:17 -0000 Received: from localhost (localhost [127.0.0.1]) by eco.foo (Postfix) with ESMTP id 44ED92FE96; Sat, 28 Jun 2003 16:43:17 +0200 (CEST) Date: Sat, 28 Jun 2003 16:43:17 +0200 (CEST) X-X-Sender: sas@eco.foo To: Jani Taskinen 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: sascha@schumann.cx (Sascha Schumann) > I think I get now what you're after and I already am thinking > of some ways to improve this. This mail has some nice ideas we could > adopt: These points are interesting from my pov as a lazy developer. (a) make bug reports automatically vanish after some time (eliminates luser reports) (b) screen bug reports and put them into second db (c) post a single notice to bugs- once per screened bug report (d) provide email/nntp interface > Especially the "screening" part, we already do that by setting > bugs we can verify. It might be a good idea to make a list > of those, instead of just all the "open" reports and send that > to internals@lists.php.net. I bet most, if not all, just delete > that current summary that gets send every now and then. :) I always ignore/delete summaries and the stupid reminders.. - Sascha