[MeeGo-dev] MeeGo Reconstructed - a plan of action and direction for MeeGo
delcasse at gmail.com
Tue Oct 4 14:38:58 UTC 2011
2011/10/4 Samuel Stirtzel <s.stirtzel at googlemail.com>:
>> Before it was just big companies that could create their own Linux distros
>> (before that everyone had their bespoke UNIX distro) nowadays fragmentation
>> is brought to you by every Tom, Dick and Harry with an OBS login.
>> I've been down the fragmentation road before. It always ends with retracing
>> your path back to the main highway.
> There seems to be much standardization work going on in the Yocto
> Project / OpenEmbedded Core (see , also Carsten already mentioned
> the Yocto Project in context of governance), anyone evaluated it?
> The Yocto Project / OpenEmbedded was discussed before in the IVI
> mailing list (see ), but it lacks any technical explanations and
> arguments why it cannot be used / or get adapted, also OpenEmbedded
> progressed into the new OpenEmbedded Core Project (the next release is
> just one step away).
> On a technical point of view it is possible to port over to Yocto
> Project, and it would make sence to concentrate the development of
> embedded linux distributions to unify them into a single development
> base instead of fragmenting the communities.
Well, I think that would make sense if the Mer project didn't want to
stay close to Tizen if possible, integrating Tizen features. Mer as a
standalone project can take these directions unilaterally, where it
would be more difficult to make it happen in another project. That
doesn't mean that efforts on some parts cannot be shared (the same way
like with Tizen), but IMO, the direction, philosophy and basis of Mer
as I undestand it justify that it stays independent.
More information about the MeeGo-dev