Re: Re: Bug Summary/Reminders

On Tue, 2004-12-07 at 08:52, bertrand Gugger wrote: > Ryan King wrote: > > > On Dec 5, 2004, at 7:08 PM, Justin Patrin wrote: > > > >> On Sun, 05 Dec 2004 16:39:12 -0500, Greg Beaver <cellog@php.net> wrote: > >> > >>> Helgi Þormar wrote: > >>> > >>>> I think we should sen this out every 2 weeks, that's good time frame, > >>>> not to short and not to long between reminders. > >>> > >>> > >>> one month (30 days is a decent definition), no less. Anything more > >>> frequent would not be as helpful to me, as I sometimes have up to two > >>> weeks of inability to process information. I would be very > >>> surprised if > >>> my situation is unusual since none of us make our living doing this > >>> PEAR > >>> thing. > >>> > >> > >> Sounds like a good time frame, but I think I'd rather every 4 weeks. > >> I'm not sure why, it just seems more "correct" to me. > > > > > > Why not just the 1st of every month? > > So it's coming with the loan, everybody happy... > I don't mind it's effective, as this will produce a bunch of mail in once. > Then poor effect. > Better could be each month anniversary of the bug, > so it's coming back in the flow single. > + no instant overload of servers. each month anniversary, hmm that would mean we'd run the cronjob every day, doesn't sound to bad, but some developers would get rather, uhm constant flow of emails then :-) Well maybe that would make them fix things, but maybe drive them away from PEAR. Ohh yeah btw, about the overload/bunch of emails, like I said, there is one email sent out per package that has bugs, so the email count is around 200 emails, that's not a overload I tell you ;) I could also only email bugs that are older then X in those emails, but that would be little gain since we are sending out those emails anyway. IMHO the approach I took is most efficient and isn't any burden to PEAR not it's developers, being able to opt. out on this would not make sense, since this is very much related to the quality of PEAR :-) I will maybe in the future, when I find the urge to do so, turn this script into 1x email per dev, thus making this even less a problem for people to get this, but I found that 1x per package takes a lot less resources. But well it seems we'll run this once a month, at least as things stand now. - Helgi