Allow for test targeting specific hardware
Every so often we find ourselves in a situation where a new piece of code targets specific hardware; we are then with the only option of broadcasting a request for testers indiscriminately. We should start creating a repository of different hardware that has been registered (via checkbox, for example). If the poster allows for it, we could then target special test requests much more productively.
This is an ambitious project, and will probably span more than one cycle. It also touches a series of other blueprints/ideas: storing/publishing test results, hardware database, community involvement, etc. The idea is not to reinvent the wheel, but to try to build a hardware database integrating exisiting tools/projects.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- C de-Avillez
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Informational
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
* use checkbox (or whatever) to collect & save hardware configuration to a database
* make this database searchable (by components, by manufacturer, by uploader, perhaps drilling down)
* allow hardware configuration uploaders to opt in to future test requests (by using the reporter's LP id)
* allow for classification (experimental hardware should not be published, for example)
* develop programmes to mine data
