On Fri, 2003-08-01 at 09:20, FACORAT Fabrice wrote: > Le mar 29/07/2003 à 16:12, Buchan Milne a écrit : > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > - know hardware is, was, can be tested > > > - when poeple used it, with what rpm version > > > - the state: ie should it be re-tested (because somethings has changed) > > > - have identifier or id for pci/usb/firewire. > > > > > > About technical stuff, I was thinking to using postgres (because I use it > > > myself) with php, but poeple at mdk prefer perl (I agree if this strange > > > language can works). Do not troll about thoses choice, all can be changed > > > until nothing is done. > > > > > Yes, the hardware database at > > http://www.mandrakelinux.com/en/hardware.php3 needs to be more > > community-powered > > > > IMHO, it needs to be done as follows: > > > > 1)First time wizard should run it > > 2)It should show the user a list of the hardware detected (ie from PCI > > bus, USB bus etc) and ask the user to mark which hardware was: > > - -detected > > - -worked out the box > > - -worked with manual config > > - -needed 3rd-party drivers > > - -did not work at all > > If it worked with manual config or 3rd-party drivers, they should be > > asked to give more information. If they marked "did not work at all", > > then they should be given links to the database which will query for > > their PCI id or USB device id, so they can see if someone else has got > > it working. > > 3)All the infromation collected should then be shown to the user, and > > then they should be able to submit it if they are happy with the > > information being transmitted. > > > > It *must* be easy to: > > - -find out if hardware is supported > > - -what extra steps must be taken > > - -document this information for others. > > indeed this could be a killer features for mdk and newbies/newcomer > should be/feel less lost. But i don't know if mdksoft will be able to > dot it and maintain it as dev are very busy and they are few > >
This would be nice, there should be information about what modules are used for the device and users should be able to voluntarily list themselves as a user with said equipment so developers can ask them to test patches & functionality. -Joe Baker
