Utilizing ubuntu friendly for testing
Discussing ways to integrate the ubuntu friendly database for testing needs.
-Creating a testing hardware database for targeted testing
-Identifying and communicating with people with specific hardware for iso testing, feature testing, and hardware enablement and/or bug fixing
-Make available the testing pool/results to developers (upstreams?)
Ubuntu Friendly Quick Overview (ara? :-) )
hw cert tool, checkbox
started in oneric
Discussions of previous efforts (Carlos? :-) )
Changes needed to ubuntu friendly site?
uf can aggregate results from testing, provide views
database schema lp:launchpad-results
Actions to take?
expand uf for testing, or create a new frontend?
should we collect (on an opt-in basis) basic untested hardware info?
utilize big data? hadoop? ontology?
Ideas from whiteboard
When installing a Development Release, have the installer create and upload a hardware profile (optionally?)
[nskaggs] what about those who upgrade? Is prompting to run checkbox enough?
Work Item Assignments! :-)
[komputes] Utilizing ubuntu friendly for testing
-Hardware Database submissions can be done with launchpad API, checkbox is not necessarily required.
-pgraner suggests making HEXR Public as an empty database
-ev is working on whoopsie submitting data of a successful install to a database, this can be use to build demographic/
-Increasing data submission: SEO, keywords, knowing the demographic of the people who use the site
[gema] research database design for results tracker: POSTPONED
[gema] Impacts of LAVA hardware and ubuntu friendly -- can they interact?: POSTPONED
[nskaggs] Meet with HEXR group to discuss viability of deploying public HEXR: DONE
[nskaggs] Create a blog entry and publicize ubuntu friendly within the QA community: POSTPONED
[nskaggs] Research applicability of HEXR to allow for a community hardware db: DONE
[nskaggs] Meet with ev to discuss integration ideas with whoopsie: DONE
[nskaggs] Blog about how whoopsie works and share public web site errors.ubuntu.com: DONE
* Blueprints in grey have been implemented.