Cordia : Maemo5 UI on top MeeGo Core
 

Following my Anemo idea and Carsten's suggestion on porting Hildon to MeeGo I started working on my own MeeGo image.

The goal is to build MeeGo core based Fremantle clone. Possibly with relevant parts of Harmattan once it is released. Anyone interested is welcome to join.

I have some hardware resources I could chip in and some spare development time. I will work on this even if I have to work alone, but some help and/or experience would be appreciated.

UPDATE: See http://codex.xiaoka.com/wiki/cordia:start for details and status.

Re: Fremantle on community led MeeGo fork
 

Two comments, because I think there might be a duplication of efforts:

Paths were moved around to make way to permanent solution for having repositories in the right place from 1.0 and onward. Codedrop was never meant to be permanent. The two directory patterns were incompatible and the first one didn't scale. A choice had to be made and that's the scalable version now seen on repo.meego.com.

Why build your own OBS when work and servers are underway for exactly these types of things in the combined MeeGo and maemo.org community OBS?

Besides that - if you want to make an alternative Hildon or LXDE UX on top of MeeGo Core or spin your own MeeGo deriative, go ahead!

Re: Fremantle on community led MeeGo fork
 

I wanted to safeguard from sudden changes in conception by setting separate repository, which would be more hesitant to removing files.
Setting up non-deleting rsync/wget shouldn't be to much effort.

From what I understood it's not easy to get access to MeeGo OBS.

Re: Fremantle on community led MeeGo fork
 

MeeGo OBS (product one) is restricted to people who's in any given MeeGo team that works directly on the product (ie, 'commit bit'). It is comparable to upload right to Debian build farms. Resources are limited hence access is limited. Team 'commit bits' are gained by merit by anyone.

Community OBS is something else, http://wiki.meego.com/Community_Application_Support - where the intent is actually having a open OBS.

Regarding repositories, I recommend taking a look at http://wiki.meego.com/Release_Engineering

and

http://wiki.meego.com/Release_Engineering/Process

and

http://wiki.meego.com/Release_Engine...lease_Timeline

-- that'll give you an idea of what you'd like to mirror for instance.

Re: Fremantle on community led MeeGo fork
 

I'll help with what's needed. Good at testing and all.

Question: Is this fork going to be a fully working build with gps, gsm, fm trasmitter and all other N900 functions?
Or just something similar to the Mer project?

Re: Fremantle on community led MeeGo fork
 

As long as the closed components can be redistributed (I think that is the case) then we should get a fully functioning device.

@smoku: I'm glad you started this thread I thought I was being paranoid when I was reading the developer's mailing list.

For an open-source project they seem very protective of any information and a very closed-knitted bunch.

I'm skeptical of the "openess" of the project and waiting to see what happens with the next release.

Re: Fremantle on community led MeeGo fork
 

He can probably set up a .ks that drags in MeeGo Core for ARMv7 + MeeGo for N900 hardware adaptation (open and closed bits) + his own UX.

Publishing images of that is another question but solvable..

Re: Fremantle on community led MeeGo fork
 

Good news is that QEMU is fixed and I finally managed to boot self-built MeeGo image using QEMU. :D

Re: Fremantle on community led MeeGo fork
 

What about user space apps? Application Manager, Settings and all of that Jazz. I'm willing to help but we need a clear idea of exactly what will be required to know how much effort is going to be involved. There's a lot more closed in maemo than just a few drivers.

Re: Fremantle on community led MeeGo fork
 

For N900 we may adopt Moebian approach and just symlink these binaries from NAND.

But this is a short term solution. These would need to be reimplemented/replaced if we want to move to non-nokia platform.

For now I am focusing of repackaging Gitorious available software for MeeGo and well see where it leads us.

Mer achieved a point of usable system. FreGo should get there too.