No DRI developer expressed his interest or opposition, probably because there isn't opposition, or simply no interest. In either case I see no reasons why not proceed, so I'll open a bug to address this. I'll ask that [EMAIL PROTECTED] (the same addressed used on SF BT system) is set as the default owner for DRI bugs.
Also, what's the general mailing list one can subscribe to receive notifications everytime a bug is open? José Fonseca On Wed, Mar 19, 2003 at 12:07:56PM +0000, José Fonseca wrote: > On Tue, Mar 18, 2003 at 08:04:22PM -0500, David Dawes wrote: > > An XFree86 bugzilla is now available at <http://bugs.xfree86.org/>. > > Many thanks to Hewlett-Packard for supplying the hardware, netSweng for > > hosting, and the many developers who helped configure and test it. > > I know that the current policy on DRI is to post bugs on dri-users or > dri-devel, but with XFree86 having a bug database is inevitable that > people will eventually post bugs there too. Therefore what's the > possibility of: > - Setting up a general "owner" for DRI bugs, which probably would be > [EMAIL PROTECTED] > - automatically set the owner of DRI bugs, e.g., by the users adding a > "DRI" keyword, or associating the "XFree86 Server"->"DRI" extension > component. > - Add the possibility to add comments to bugs via e-mail. > > Basically I would like to be possible that: > - An user adds a bug concerning DRI > - The owner is (either manually or automatically) set to > [EMAIL PROTECTED], which receives the bug > - Any developer on the dri-devel list which has an account on > XFree86 Bugzilla can reply and that comment is added to the bug > database. > - Certain maintainence tasks (such as closing the bug, read an > attachment) will require to use Bugzilla web interface, but bugzilla > can be configured to remember our login, so it's straightforward. > > I would appreciate if the XFree86 and DRI developers considered this. _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
