I agree with the concerns of some of those above. If the hardware database is no longer maintained, closing the bug as a wishlist is less than ideal because it doesn't actually address the OP's original concern.
It would be better if there was a hardware database Canonical maintained. This can't be rocket science to build:
* Ubiquity installer makes some queries to the system with the user's permission.
* Installer makes some JSON POST requests to remote server.
* Remote server stores anonymous hardware description in a MySQL or PostgreSQL database.
* Database has a web based front end that shows some pies, tables, a field for queries, etc.
I agree with the concerns of some of those above. If the hardware database is no longer maintained, closing the bug as a wishlist is less than ideal because it doesn't actually address the OP's original concern.
It would be better if there was a hardware database Canonical maintained. This can't be rocket science to build:
* Ubiquity installer makes some queries to the system with the user's permission.
* Installer makes some JSON POST requests to remote server.
* Remote server stores anonymous hardware description in a MySQL or PostgreSQL database.
* Database has a web based front end that shows some pies, tables, a field for queries, etc.
This can probably be put together in a few days.