Day One has arrived, and both intel and nokia have released sources and is opening up Meego for development. What is now available? Everything from the kernel to the middleware stack was released today.

The UI Experience Framework will be released later in May; this is when Meego actually goes for it’s first release.

Also, for downloads (images of the base system, terminal only) of Meego for N900, Intel Atom Netbooks and the Intel Atom Handset (Moorestown), they are now available at http://meego.com/downloads

Full details are here.

Anyways, initial writeup for the draft of mission and scope of the team will be presented to the TSG the meeting after the TSG’s meeting on Wednesday.

I’m still getting the hang of how things are done in meego, but I’m sure I’ll get there soon enough.

Just to let you know what was discussed (at least some of it – had a flakey connection and got cut off on some portions):
1. All apps in Meego repository makes use of official or community provided APIs.
2. If a proprietary vendor has proprietary APIs it will have a proprietary store.
3. Some suggestions were made about splitting libraries into Stable and Experimental/Unstable. Stable is where official APIs and few well supported community APIs are placed. The experimental/unstable stuff is where not well maintained but useful libraries are placed.
4. Apps should avoid forking at all costs. External dependencies on the apps should mostly be Qt based.
5. A possible problem seen would be on how to deal with vendor APIs.
6. lbt (coming from the maemo side, .deb) and th0br0 (Fedora packager, rpm) will be the coordinators/representatives to the TSG for now.

There are other stuff mentioned, but basically all draft – all have to be presented to TSG. Since there is so little info yet on the Build System, all these things will most probably be subject to change in once TSG guidelines for meego emerges.

I am basing it on Moblin/Meego, but should mostly work on Fedora/RedHat too.

I am assuming that you have already installed the development tools of Moblin in your installed Moblin distribution by using this command:

sudo yum groupinstall “Development Tools”

To start, we install the createrepo package – we can get it from the Manage Apps application in the Moblin Applications->Settings tab.

Once installed we can now create the repository using the commands:

mkdir -p /[path of your moblin repository root]/Moblin/[moblin-release version]/{SRPMS,i586}

We use i586, because Intel atom processors are basically of arch type i586.

You may want to create i386 generic files for whatever use you want, so you can use {SRPMS,i386,i586} instead above.

If you do so, you may want to automate the process by creating a bash script named createrepo.sh and writing in the following code:


#!/bin/sh
destdir="[path of your moblin repository root]/[moblin-release version]"
for arch in i386 i586
do
pushd ${destdir}/${arch} >/dev/null 2>&1
createrepo .
popd >/dev/null 2>&1
done


Every time you add a package, call this script and it will create the metadata using the createrepo tool in the i386 and i586 directories.

Upload this directory structure to the server where you’ll be hosting your repository.

The .repo file you will create will most like be similar to this:

[mymoblinrepo]
name=My Repository
baseurl=http://myserver.com/repo/Moblin/2/$basearch
enabled=1

$basearch will be the arch type of the distribution. For Moblin you can hardcode it to i586 instead.

Anyways, that’s about it. Cheers!

I’ve been working on getting my small, but hopefully growing moblin (but soon to be meego) rpm repository hosted somewhere. It’s still not final yet, but I’ll keep you posted.

Exciting times indeed.

Update: The kind guys at ibiblio have decided to host my little repository on their mirror list. I’ll be recompiling and re-uploading those files soon to the new location.

From the blog, it states that they “are taking the best pieces from these two open source projects and are creating the MeeGo software platform. Both teams have worked for a long time to support the needs of the mobile user experience – and MeeGo will make this even better.”

As I knew that Maemo’s interface was more suited for the mobile phone area for Meego, I decided to look into Moblin itself and see how it would serve the role of addressing the netbook part of the new platform.

As we see it currently, the pre-built Moblin live image is a largely Fedora 10 based distribution. It can however be built from Fedora 12, and Ubuntu 9.10. It is interestingly enough that the resulting build with be rpm based, not deb based.

Installing the live image to harddisk on my Benq Joybook was simple enough – it was actually similar to the Fedora/RedHat installs that I am used to.

Booting up was a treat: compared to Ubuntu Netbook Remix, the interface was intuitive and smooth.

The Miser interface upon first boot shows practically a wonderful display of your tasks, favorite apps, documents opened and other stuff that you’ve just used.

Different tabs allows the user to navigate through different sections of Moblin – easily categorized into media, internet, status, applications, zones, people and pasteboard.

The way that Moblin is organized is, in my opinion, one of the best interfaces that I’ve seen in a linux distribution for netbooks. It simply is the best optimization of space for 8″ to 12″ screens.

There are drawbacks however.

For one thing, NTFS is not supported in moblin. And due to licensing issues, the MP3s and H264 video is not supported out of the box, as well as proprietary codecs.

Another thing is that Moblin’s repository is still rather small. Understandable though, because this distribution is meant for netbooks.

There are a number of hacks you can do though, one is you can use the Fedora 10 (and sometimes 11) repository to download other programs.

Another option is to compile the source rpms from the fedora repositories yourself. The trick is to enable the development tools of moblin by typing in the command:

sudo yum groupinstall “Development Tools”

If you’re a little lazy to compile gstreamer yourself, you can use a repository created by a Moblin user named Matthi. The repository, albeit small, includes some nice programs to install for Moblin, such as WINE, Blender, and the gstreamer plugins to make your Moblin distribution run codecs supported by ffmpeg. You can get instructions for his repository here.

What is the Moblin’s future as Meego? I would say, rather bright. Seeing how the interface really compliments the Intel Atom netbook specifications nicely, I believe that most of the GUI Moblin has implemented will be carried on in the netbook versions of Meego. A possible challenge will be on how to implement the user experience on the Qt toolkit (Meego will be based on it, rather on GTK that Moblin uses). Since Moblin uses the Mozilla codebase for it’s integrated browser, it is not farfetched to assume that Meego will implement the Webkit browser as it’s integrated browser for the Qt for it’s WM/Miser interface.

As Qt has integrated media, browsing, APIs, as well as a compositing engine compared to GTK (Gnome still uses Compiz as it’s compisiting engine), we would probably see a more integrated architecture internally, when Meego reaches it’s final stages of development into stable.

Nokia and Intel would benefit each other, because for one reason, Nokia has a netbook. Also, Nokia’s design principles are horrible and clunky (see the S60 interface on symbian as an example) and is also seeing pressure on their interface designs from competitors like Google and Apple. One thing that Nokia has, is that they’re great at hardware R&D (especially mobile), and it is my belief that Intel is also looking into the mobile sector, especially considering that OSes like chrome, and android run on ARM processors and are indirectly competitors with Intel on this space.

All in all, I would say that if both Intel and Nokia play their cards right, Meego will be a very good competitive platform for mobile and netbook apps in the future.