2011/3/7 Arjan van de Ven <[email protected]>: > Hi, > > given the events of the last few weeks, the MeeGo architects have, and still > are, revisiting various parts of the MeeGo architecture.
Just to ask so it's clear (I'm sure that there are people that are wondering), the architects are still you, Sunil Saxena from Intel and Sakari Poussa, Mikko Ylinen from Nokia, as back at the MeeGo Conference in Dublin? > it's not like MIkkado where you can pull out one stick at a time. Thanks for publishing this to make the direction more clear - I mostly agree with the choices, but have some comments: > In the long-term, we will re-evaluate the direction we are taking with MeeGo > security with a new focus on *End-User Privacy*. > While we do not intend to immediately remove the security enabling > technologies we have been including in MeeGo, all security > technologies will be re-examined with this new focus in mind.We will revisit > technology choices made for MSSF (as well as non-MSSF > components that have security implications) and make appropriate changes in > these areas given this direction change. > One thought that popped into my mind: In MeeGo Smart TV there would probably be a focus that's different from End-User privacy, with regards to stream protection (which is a market requirements these days, sadly?) and in IVI where there would be regulatory problems. Does this fit well with end-user privacy goal? While I don't like DRM at all, we shouldn't be closing doors in MeeGo in where we would be easily usable to make great products that are open in other aspects.. > To be clear, this does not mean that "tracker" is completely removed; > tracker is still being used (together with tumbler) for indexing media > on the device. At this point we are seeing serious issues > (performance/stability) with this solution, but the first attempt will be to > fix the > deficiencies rather than a replacement. Ironically with performance, at least in terms of startup, this may be partly caused by BMC#1, https://bugs.meego.com/show_bug.cgi?id=1 - which starts scanning instantly at startup, probably trashing initial performance. What are your thoughts regarding the architecture process going forward? Any changes needed? BR Carsten Munk MeeGo Nokia N900 Hardware Adaptation Maintainer _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
