On Jul 8, 2010, at 18:21, Carsten Munk wrote:
> To deal with this in terms of compliance, I suggest we establish a
> MeeGo oompliance baseline for SDKs and community OBS to follow for
> applications. It doesn't have to be what Core is compiled for in
> MeeGo.com if we want to encourage MeeGo use on many different
> processors and devices.
>
> Your thoughts?
I'm not certain that creating a compliance path for SDKs and community build
systems is the way to go - it seems like an undue burden to force compliance
upon the tools a developer uses. Compliance should be centered around APIs
perhaps instead, although even this is kind of hard. If you change a part of a
low-lying API, for example, that can impact dozens of applications.
In any case, shouldn't there be a separate mailing list for compliance? There
is a lot of strategy and standards discussion there that may be orthogonal to
development.
Jeremiah
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
