Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:2946 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 38038 invoked from network); 28 Jun 2003 14:55:44 -0000 Received: from unknown (HELO netphobia.fi) (213.243.181.8) by pb1.pair.com with SMTP; 28 Jun 2003 14:55:44 -0000 Received: from localhost (jani@localhost) by netphobia.fi (8.11.6/8.11.6) with ESMTP id h5SEth214290; Sat, 28 Jun 2003 17:55:43 +0300 X-Authentication-Warning: netphobia.fi: jani owned process doing -bs Date: Sat, 28 Jun 2003 17:55:43 +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: >> 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) Yup, I took that on my TODO already. :) > (b) screen bug reports and put them into second db That's done already. ("Verified" bugs). I don't think there's need for a second database. > (c) post a single notice to bugs- once per screened > bug report That's also in my TODO, I was planning to add some more headers to the mails to make it possible to filter them locally. (per category, status, etc). > (d) provide email/nntp interface Any ideas for the email interface? We do have already some sort of email interface, there are urls to certain quick-resolves in every email coming from the bug db but I guess that's not what you want. >> 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.. But if the summaries contain only screened (== verified) reports, and sent one per category? Better ideas would be appreciated, of course. --Jani