On Wed, Jun 12, 2002 at 02:28:45 -0600, Jens Owen wrote: > "Peter Soetens (Kaltan)" wrote: > > > > On Wednesday 12 June 2002 19:49, Keith Whitwell wrote: > > > > > > The dri-users list was founded on the idea that there might be a class of > > > 'power users' out there who would altruistically help newbies get their > > > setup working so that 'real developers' could concentrate on loftier ideas. > > > > > > That class of power users haven't really emerged, if anything it is the > > > power users who are crying for help in the blackness of dri-users, as > > > everyone else just sucks whatever comes with their distro. > > > > > > Again - I think the people on dri-users would be better off just posting to > > > dri-devel. As it looks like we've got to monitor both lists, why bother > > > having a second list? I know I give less attention to posts with > > > [dri-users] than [dri-devel] -- perhaps I think that people posting there > > > will never do any development, so I won't be "repayed" by spending my time > > > on them. > > > > Please also look it from the other side : do the dri users want to get the dri > > devel mails ? That could just be a bit to much mail pouring into their > > mailboxes that doesn't help them anyway. > > > > If you want my opinion, I vote for users & devel > > Peter has a point, here. Besides, what's the difference between > tracking 20 e-mails on one list and 5 e-mails on a second list; vs 25 > e-mails on a common list? Perhaps I'm showing my lack of sophisticaed > e-mail prowess :-) I'm wondering what dri-users actually serves at the moment. What proportion of the people there are actually compiling up the DRI trunk and actively testing it ? Or are using stock XFree86 4.2.0 and asking questions there instead ?
I suspect that it may be better for those people not using the DRI trunk to post to the xpert list at XFree86 to answer questions like that. That way they get a broader audience. Most(?) of the dri developers are on xpert too. Yes ? I bet most dri developers get a ton of email already. I certainly do. :) And if people are really compiling the DRI trunk, I would appreciate any feedback - bad or good on dri-devel. > > and damn close that bugtracking system. Look at what the KDE > > people use for bug tracking, now that's what i call neat > > (together with the nice KCrash backtracer). > > http://bugs.kde.org/ > > I'm certainly as guilty as anyone for letting the cruft build up in the > SF bug tracker. However, from a TG commercial perspective, I will need > to closely track all bugs specifically related for certain DRI > projects. I can track those on a private internal database, or I can do > it on an open DRI database. Either will work for me. However, I do > think tracking on an open DRI database would be better for the DRI > project; and I would prefer to use the slow SF bug database then take on > the much larger task of setting up a new system. 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. Alan. _______________________________________________________________ Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
