Hi Tero, your e) solution looks like the perfect balance. It also scales well: if there are other MeeGo vendors with own APIs based on closed components thay are free to offer their own OBS. Linking to those, providing that they are MeeGo compliant, shouldn't be a big deal.
Still, what about distribution? We still would have to deal with this: > > This must come > > together with new repos e.g. meego-extras-$vendor or even > > meego-extras-$vendor-$model since not all of these apps will work in > > all > > of the targets. Or should vendors also deal with their own distribution repos? Note that users have to install them separately anyway, no matter where are they hosted. Note also that Maemo Extras has a non-free branch used for special cases where a community app can't offer all the packages free. See http://repository.maemo.org/extras/pool/fremantle-1.2/non-free/ And finally, how will all this look in the meego.com community Downloads (the equivalent of http://maemo.org/downloads/ ). Users will need to clearly see what works for the device they have. But first of all, can we consider the OBS part agreed? -- Quim _______________________________________________ MeeGo-community mailing list [email protected] http://lists.meego.com/listinfo/meego-community
