On 26/08/10 19:13, Attila Csipa wrote:
On Thu, Aug 26, 2010 at 8:22 PM, Quim Gil <[email protected]
<mailto:[email protected]>> wrote:
> * There won't be a community builder for Maemo 6 specific APIs.
The discussion about MeeGo-Harmattan (provisional name for what was
called Maemo 6 before the MeeGo launch) integration with MeeGo services
hasn't started yet. There are no community apps being developed for
MeeGo-Harmattan at this point and, as opposed to Maemo 5, there is no
legacy to consider. We have the chance to define the community rules
now.
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 ?
So I'm jumping in at this point in the thread whilst the focus is still
objectives/requirements lead and not constrained by possible technical solutions.
I agree with Attila.
My objective is to get the *entire* Maemo development community to have a
trivial and natural evolution/migration to MeeGo.[1]
To this end I think we need
* OBS to be the Maemo community build infrastructure for (full) Fremantle
* ditto for Harmattan
* the build process and systems to be seamless for Fremantle/Harmattan/MeeGo
The Maemo community could close the autobuilder and Fremantle builds would be
fully community-supported on the OBS. Extras for Fremantle and Harmattan would
be a natural by-product.
So this would put all of the Maemo devs onto the OBS. Ideally the MeeGo OBS.
Peeking ahead in the thread; this doesn't preclude a Free-mantle target being
pursued (or a target for a pure MeeGo API subset of Harmattan) but it does
require a fully supported Fremantle (and Harmattan) target with closed binaries
and all.
Keeping this activity in one place under shared management seems the most
efficient thing to do.
Can we take this as the primary goal?
Constraints and preferences include things like "prefer not to have closed
binaries on MeeGo infra", Nokia redistribution legals, technical workings of
tools and systems that effect distribution and trigger clauses etc. These can be
changed but each has a cost of some sort.
The question then becomes: What's the simplest and most cost effective way to
achieve this?
David
[1] I hope I'm not presuming too much on behalf of the Maemo community.
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
_______________________________________________
MeeGo-community mailing list
[email protected]
http://lists.meego.com/listinfo/meego-community
