The first MeeGo release [LWN.net]

From:		"Sousou, Imad" <imad.sousou-ral2JQCrhuEAvxtiuMwx3w-AT-public.gmane.org>
To:		"meego-dev-WXzIur8shnEAvxtiuMwx3w-AT-public.gmane.org" <meego-dev-WXzIur8shnEAvxtiuMwx3w-AT-public.gmane.org>
Subject:		Day 1 is here - opening up the MeeGo development
Date:		Wed, 31 Mar 2010 11:27:23 -0600
Archive-link:		Article, Thread

Hi everyone...

Today is the culmination of a huge effort by the worldwide Nokia and Intel
teams to share the MeeGo operating system code with the open source
community. This is the latest step in the full merger of Maemo and Moblin,
and we are happy to open the repositories and move the ongoing development
work into the open - as we set out to do from the beginning.

What are we opening? The MeeGo distribution infrastructure and the operating
system base from the Linux kernel to the OS infrastructure up to the
middleware layer. The MeeGo architecture is based on a common core across the
different usage models, such as netbooks, handheld, in-vehicle, and connected
TV. The MeeGo common core includes the various key subsystems including the
core operating system libraries, the comms and telephony services, internet
and social networking services, visual services, media services, data
management, device services, and personal services. More on this will be
described on meego.com over the next few days.

The downloaded images will boot from a USB stick or directly flashed on the
device from your Linux PC, but since the MeeGo User Experiences for the usage
models mentioned previously are not yet included in today's MeeGo core, these
images will boot into terminal.   
After Day 1, the rest will follow soon - in the next few days, we will post
the next steps leading to the first release of MeeGo in May.

The images available today are: ARM-based Nokia N900, Intel Atom-based
netbooks, and Intel Atom-based handset (Moorestown).  These images can be
downloaded from http://meego.com/downloads 

The corresponding package (RPM) repositories are at repo.meego.com/MeeGo and
the git source repositories are available at http://meego.gitorious.org/.
Bugzilla is at http://bugzilla.meego.com/ 

Please download, test, and provide feedback. The wiki on meego.com
(http://wiki.meego.com) and the MeeGo mailing list
(http://lists.meego.com/listinfo/meego-dev) are excellent ways to share
information and ask questions.

We'll post a proposed timeline soon which should answer your questions about
opening the user experience, applications, and application framework
repositories. For now, please take a look and let us know what you think.
Imad Sousou

Director of Intel's Open Source Technology Center
Co-chair of the MeeGo TSG

(Log in to post comments)

misleading title

Posted Mar 31, 2010 23:48 UTC (Wed) by corbet (editor, #1) [Link]

The word "final" appears ... where ...?

It's a code release, even if it's not a packaged release. Apologies if any confusion was created.

misleading title

Posted Apr 1, 2010 10:53 UTC (Thu) by cowsandmilk (guest, #55475) [Link]

I'm always amazed that in a community with the "release early and often matra", a lot of open source people seem to get upset when you call something a release and it doesn't cover everything they want. That said, the mailing list post does say (in what may be considered contradiction to the article title):

in the next few days, we will post the next steps leading to the first release of MeeGo in May.

misleading title

Posted Apr 1, 2010 16:39 UTC (Thu) by drag (subscriber, #31333) [Link]

The only thing that irritates me in this specific case is that they are farting around with building their own OS in the first place. The only thing people care about with Meego is the user interface and development tools. That is the stuff they need to be concentrating on if they want to have any impact at all.

Until Meego releases a set of API standards (aka dependency requirements) + Development tools + Inititial GUI environments + Good packages for usable Linux systems like Ubuntu/Debian/Fedora then nobody has any reason to give a crap about anything they are doing.

In other words:

If their goal is to make Linux more attractive in the embedded devices-with-advanced-GUI area they should be targetting what people are actually going to use in small Linux systems.

However, if their goal is to make a new Linux OS that they can hang their hat on and say it is their's well the rest of the world ignores them completely then they are going down the right path.