On Fri, 2010-09-17 at 08:58 +0200, Kellomaki Pertti (Nokia-MS/Tampere) wrote: > This may be completely left field, but from the discussion so far it > seems that it could in fact be a lot easier to bless repositories (or > sets therof) as MeeGo compliant, rather than single packages.
Actually I think it's a very relevant comment. A lot of posts are describing a situation Commercial Stores vs Extras/Surrounds when the core question is to restrict application compliance to apps directly based on the official MeeGo API or not. MeeGo Extras/Surrounds would benefit from separate repos for apps depending directly on the official MeeGo API (Qt / WebRuntime) and all the rest. It might make a lot easier for MeeGo vendors to include the 'strict' meego.com repo in their products or marketing. On the other hand, what are the deep issues underneath this long discussion? Let me try: - The belief that the MeeGo official AOPI is not enough to satisfy developers. If this is true then it's a problem in itself and needs to be fixed by improving the API. - The belief that there will be a significant amount of apps using other APIs / toolkits. Which ones, though? PySide? KDE libs? Hildon? This discussion would be better grounded if sustained by real maintainers of these toolkits & bindings. - The belief that having a "Compliant" flag will open the door of these apps not depending directly on Qt / WRT to make it to the AppUp, Ovi and etc. However, I doubt so. For these stores keeping a consistent catalog for Qt & WRT across different UX, architectures, products and vendors is already a considerable headache. They will look at any options helping them to increase number and variety of apps, but probably not before those alternative APIs and toolkits have proven themselves. - Even the perception that the Compliance restrictions go somehow against free software development. I would accept this one if the MeeGo project would refuse the idea of hosting an own Extras/Surrounds repo. But if this exists then developers concerned about software freedom can use them, and users concerned about software freedom can buy devices open enough to run that software. -- Quim _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
