On Thursday 13 June 2002 17:17, Alan Hourihane wrote: > On Thu, Jun 13, 2002 at 04:03:05PM +0100, Keith Whitwell wrote: > > Alan Hourihane wrote: > > >On Wed, Jun 12, 2002 at 11:13:40PM +0200, Dieter Nützel wrote: > > >>On Wednesday 12 June 2002 20:53, Alan Hourihane wrote: > > >>[-] > > >> > > >>>We really need to clean up the stuff on SF now. Probably about 90% > > >>>don't even apply now, or should at least be re-tested. > > >> > > >>Yes, let's start with that. > > >>There are even several bugs for which the sender asked for closing but > > >>never happend... Maybe we can change the maintenance so that the > > >> original poster can close it himself? > > > > > >What would be great, is if someone assigned the bugs to relevant > > >developers. Once someone is assigned to the bug report, they get > > >emails whenever it's updated. But that someone needs to know who > > >to charge with that bug report. > > > > > >Someone who would standup to maintain it would be GREAT! > > > > But even so it makes fixing bugs *slower* -- there's extra accounting > > work to do. I never use the sf website except to add new developers CVS > > access... > > > > I really think the mailing list is the best place for bug discussions. > > It gives new developers a chance to dive in, for instance. > > Understood, but there's a lot of users out there that don't want > to receive emails from dri-devel. They just want to submit a bug, > walk away, then get some response back to say it's fixed, or someone's > working on it, or it won't be fixed etc. > > But with the SF bug tracking system we are currently sending bug > reports, patches etc to the dri-patches mailing list. Maybe we should > re-route them to dri-devel to get more feedback. > > The problem we're facing is that there's no formal process to assigning > the bug report, so no-one else knows whether someone could be working > on it or not, thus duplicating effort. > > Development is ideally what we all want to be doing, but there's a > few admin type tasks we really do have to bear - and that's the uphill > struggle.
So as I'm currently not having developers CVS access I'll offer to help, here. But be patient with me if I sometimes assign the "wrong" developer to the "right" bug...;-) Due to the fact that I haven't read dri-patches for some time I'm not sure if all bug reports have reached the mailing list. Is it working? -Dieter BTW I'm not loving SF bug tracking, too. http://bugs.kde.org/wizard/index.php is much more advanced. _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
