Code is Code is code, move your repos into a different eco-system that runs on 
top of the open linix kernel, and beam yourself up dude & dudettes, Best George

George Ingram Computer Scientist
Winner Intel Coders Challenge 2010
http://www.linkedin.com/in/georgeingramcom/

503 East Nifong Blvd I Suite 167
Columbia Missouri 65201-3792

Voice 804-464-7257

-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of Angel Perles
Sent: Saturday, October 01, 2011 10:15 AM
To: [email protected]
Subject: Re: [MeeGo-dev] [MeeGo-community] MeeGo as a vehicle for Qt-based 
products?


I consider that a kind of reference UI experience and "demo" is fundamental for 
Meego. Probably a good starting point could be the incorporation of KDE + 
Wayland in this area.

Also, it could be interesting to talk to guys at projects like Openmoko, GPE, 
etc to join efforts and to avoid fragmentation of efforts.


An important issue is the lack of drivers from modern pieces of 
hardware, for example TIs OMAP 3xxx has not public drivers (open or 
closed) for hardfp's ARM Meego 1.2.

Hardware manufactures (TI, Qualcom, Samsung, ...) must deal with the 
requisites of its customers (Nokia, Microsoft, Google, Samsung-2, ...) 
and not provide drivers for this kind of projects.

As we all assume, Microsoft has blocked Meego project with its alliance 
with Nokia. Well done, Microsoft.

Its is not necesary to continue with the name of Meego, it could be
something similar to OpenOffice->FreeOffice. If "trademark" problems.


Regards,
Àngel




El 29/09/11 17:37, Robin Burchell escribió:
> Hi,
>
> On Thu, Sep 29, 2011 at 5:20 PM, Nasa<[email protected]>  wrote:
>>> So I'll shed some light on how I see this and how we should proceed:
>>>
>>> 1) Concentrate on the handset and *ONLY* on it from now onward. "Do
>>> one thing and do it best (tm)".
>>>
>>
>> Why would you exclude 4/5 of the people involved in the meego project?
>> Handsets weren't even the largest part of the project...
>
> Personal area of interest, perhaps. Anyway, we don't need to exclude
> anyone here - anyone can come and play ball. In my view of the ideal
> MeeGo universe, UX is entirely seperate projects from MeeGo itself -
> MeeGo Core is just the basics needed to boot and get to a display,
> hardware adaptations and user interfaces are outside of scope there.
>
> All the best,
>
> Robin
> _______________________________________________
> MeeGo-dev mailing list
> [email protected]
> http://lists.meego.com/listinfo/meego-dev
> http://wiki.meego.com/Mailing_list_guidelines
>

-- 

*************************************************************
Angel F. Perles Ivars

Departament d'Informàtica de Sistemes i Computadors - DISCA
Universitat Politècnica de València - E.U.Informàtica
Cami de Vera s/n. 46022-Valencia
Edifici 1G Despatx 2S-13
e-mail: [email protected]
Telf.+34 963877007 Ext. 75775 Fax.+34 963877579
http://www.disca.upv.es/aperles
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines


_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

Reply via email to