On Mon, 2010-09-20 at 09:54 +0200, Stephan Kulow wrote:

Am Friday 17 September 2010 schrieb Vincent Untz:

...

Hi,

I don't know when people started talking about getting Moblin, and then Meego in openSUSE, but it still hasn't happened. Andrew is working on this, but some people need to help him. Else, I'm afraid we'll release 11.4 in the same state.

Would it make sense to have one sprint on Meego? Do we have hardware that we could use for that?

This later question is exactly why I think we shouldn't do it honestly. I have a netbook ordered exactly for helping with netbook stuff (and in case we decided we do it, I'll of course help). But actually: changing software on this thing was the worst idea ever. A usual factory update with it's 700 packages takes ~24 hours because the hard drive performance is so bad and from what I hear this is not specific to my model.

So from what I understand: netbooks are fine for those that take it and run with it, but a nightmare for those that want to play with the software: so no community thing at all - Andrew might be different, but in general I don't think we would boost here, we would simply do the work.

Greetings, Stephan

One of the benefits of MeeGo vs Moblin is that it isn't tied to a specific display size anymore. Previously it would *only* work on 1024x600 where as now it works on >= 1024x600. So hardware per se isn't that big a blocker - the only thing I can work out from a hardware point of view is non-Intel powered graphics don't work, although Michael Meeks reports that Ati's open driver works of a fashion. Nvidia does not though regardless of driver used. I will put my hands up and accept full responsibility for the failure of Moblin in openSUSE. This is partially my lack of knowledge of what exactly was required, and also my lack of time in getting all the components working. I have spent pretty much most of my spare time since MeeGo was announced getting it to work on openSUSE, and as such I have a 98% working set up [0]. The problem is this is based on MeeGo 1.0 and 1.1 has a lot of changes in both names and APIs which is why I'm not pushing it into Factory. I am not expecting you guys to do the work far from it, but what I would like is some help in getting things into shape and importantly educating me in understanding some of the errors that occur. Since Novell switched their product from being SLE based to upstream MeeGo based I have been driving this, but if it wasn't for some help from the community I would still be at the initial stages. My goal is to provide a full MeeGo stack for openSUSE, starting with the netbook UX but also adding the phone/tablet UX. The latter will be dependent on hardware for testing, but I think with enough bribery/begging we could obtain some when available. Fedora have started on their MeeGo spin, and I would hate for them to steal the show as the1st and only main distro offering it. Coolo, I appreciate what you are saying but I want to prove you wrong ;-) Regards, Andy -- Andrew Wafaa IRC: FunkyPenguin. GPG: 0x3A36312F openSUSE: Get It, Discover It, Create It at http://www.opensuse.org