On 08/26/2010 11:13 AM, ext Attila Csipa wrote: > I'm not sure if I'm reading this right, but it sounds a bit like > deprecating the > (provisionally named) Meego-Harmattan API for community apps right off > the bat ? Or, put in a different perspective, where do community apps go > that > want to take advantage of, say, Ovi services, or squarely target the > Harmattan > device/release ?
Ask the same question from a generic point of view, imaging several MeeGo vendors with several own APIs that can be used when targeting MeeGo vanilla or other vendors devices: Does the MeeGo Community OBS want to have specific targets for those vendors (implying potential incompatible APIs, closed binaries and EULAs mixed in the OBS) or does the community infrastructure stay true to MeeGo vanilla, fully compatible and open source? One thing is to consider a one-time exception for Maemo 5 for the reasons explained. Another thing is to open the door to any MeeGo vandor having their own particular closed source stuff. In the case of MeeGo-Harmattan specific APIs, if someone wants to rely on them I guess they could simply use the Nokia SDK and the Ovi store. -- Quim _______________________________________________ MeeGo-community mailing list [email protected] http://lists.meego.com/listinfo/meego-community
