Jump to Navigation

BOF: Quality and The Compliance Specification

Session Summary: 
Learning from mistakes of the past, http://tinyurl.com/2dtzon9 , I would like to make sure we embody as many as possible quality originated guidelines and mandatory conditions in either the UI/UX guidelines guide and the compliance spec. This session will discuss what sort of these or specs embody if at all, and decide on first actions and new items to be inserted into it.
Session Abstract: 

Embodying quality guidelines into our compliance and UX/UI specs could serve as a groundbreaking workflow compared to other similar platform, such as the Android platform. Currently there is a problem in the Android world where the compliance spec is merely a "type" definition in the essence that it just specifies the "results" part of the interface. By making ours also determine that certain parts and process inside the core must exist (for example, certain storage scheme and format for PIM) , we can achieve better quality and streamlined deployment over all our range of supported devices. Learning from Android and some of our SDK experiences, it's easier to test the api is there, and still has the right signature but most of the imes, nothing tests that it does something meaningful. We should strive to lead this with MeeGo making it far more attractive platforms for OEMs and hardware vendors.