On Sep 16, 2010, at 1:26 PM, ext Arjan van de Ven wrote: > >> that MeeGo will not provide any build, packaging or hosting >> facilities, and that the products of the MeeGo project will start& end >> with the core distribution + specs on what makes up a compliant >> application. The burden of providing a distribution channel& hosting is >> entirely pushed to the vendors. Is that a fair assessment? If it is, >> where do you see community apps being distributed? How would Linpus >> users be able to get at& install applications from the Novell app store? >> >> Perhaps I'm misunderstanding how you see this working in practice. If >> so, perhaps you could clear up my misunderstanding a little? > > I think that in practice, phones will be locked down and the content you > can get on it controlled by the operator and/or OEM. > Yes there will be some people who will buy an unlocked phone (if those > are locked down or not will depend on the OEM), but > the vast majority will be operator subsidized and thus locked down. > Other categories may or may not be more open than that... but the locked > down model also needs to work for compliance. > Compliance is "your app will work on all meego compliant devices" (and > yes "work" will mean "as well as it did on your original device form > factor", not "it'll be perfect even if you move a phone app to your tv"), > not "your app will work on all meego compliant devices except those that > are locked down or do not use Extras".
Sometimes we need to learn from history, do you remember days when operators wanted to control what internet pages you could access and in most cases only their own ones ? iPhone has only one app store, how many there is for android ? Does every operator have own and do they lock down their devices only some fractional fragment limited app store ? I think that app store field fragmentation is no ones advantage. There is better question, how much we would like protection against stupidity in compatibility specs ? Having none is not good. > > now MeeGo extras is a great idea, and I can't wait to see all those > MeeGo Touch Framework apps show up and be available for the meego.com users. > But to be honest, I somewhat doubt that hardware vendors or the > operators will think more than a few seconds and just not enable it, > even if they were to take the OS nearly directly from meego.com We can have three levels of extras extras-devel as in Maemo that is full open and without any quality control and mostly used by developers. Then extras that has quality gate by community. For MeeGo we could add third one, official Meego-extras that has other OC gate by meego.com and having this repo would be requirement to get device as MeeGo compliant. That leaves door open to us quickly react to future needs. Kate _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
