With a stable SDK released and a new product in the shops, this is the time when I would start shifting internally to the next product iteration. In fact this is what I’m doing now as well, but this time swimming upstream. In practice this means that I´m less conditioned by Nokia products (although they still pay my salary) and closer to the work of a wide community of organizations and individuals putting their bets in Qt.

My work keeps combining the big topics of community, openness, sustainability and fun – also understood by some as marketing & communication applied to OSS development. This is how I started contributing to the free software community around 2003, this is why Nokia recruited me for the Open Source Software Operations in 2007 and this is what I have done best since then.

At the beginning there was GNOME

I was introduced to the Nokia 770 in GUADEC 2005 by no less than the great Guillem Jover. In 2004 I wanted to recruit him but he had just moved to Helsinki to work for... Nokia! Two years later I would follow the same path.

Once a full time GNOME community contributor (founded by the Catalan government to assure a great GUADEC 2006 in Vilanova), my approximation to Qt has been directly related to the steps taken by Nokia in that direction. One day Ari Jaaksi (then the boss of my boss, Valtteri Halla) started to suggest the possibility to shift our basically GNOME Mobile compliant Maemo to Qt. A big debate followed and I contributed my dose of voice and brain. My strong arguments were that GNOME had a distributed setup combined with a more suitable license, plus Nokia was lacking the skills in house. Our team moved to Qt but I was never proven wrong. One morning we read in the news that Nokia was acquiring Trolltech, getting a big load of Qt skills in house. “Fair enough”, I told surprised to myself. Then the LGPL license came (a change I had been lobbying for since the Nokia-Trolltech deal was announced). And finally the Qt Project is here, willing to reach a diversified open governance setup like the Linux kernel, WebKit or GNOME itself.

My closer approach to Qt matters started after the Nokia N900 was released. As said, that was the time when I would start shifting to the next big iteration (Harmattan, a name that I had the honor to propose). The Qt 4.6 libraries were available for Maemo 5 and I felt it was the time to test the cross-platform compatibility promise. I proposed the Miniature project with only three hard requirements: chess, mobile & Qt. At the time C++ & QGraphicsView was the way, and good that Michael Hasselman was around, otherwise I wouldn’t have progressed at all. Things were not that easy yet.

Calling the Harmattan wind

By that time Peter Schneider was my manager and I was learning from him the usefulness of keeping activities and messages simple and focused (in this case in Qt). One day I started getting some tasks related to a project that one day would be introduced to the World as MeeGo. The fundamentals of that project were for me a dream come true: standard Linux & freedesktop.org stack plus Qt toolkit and development environment, developed openly by multiple parties, targeting multiple form factor devices.

Qt Quick started to emerge between the two equivalent frameworks that Maemo and Symbian were building. I became an internal advocate almost instantly, not because of any technical analysis (I’m not the guy for these things) but because of the basic principle of following and supporting the way proposed upstream, as opposed to attempting to create shortcuts on your own. It took a while, but one day a CEO called Stephen Elop made the call that no top manager had made before: focus on Qt Quick, other alternatives to be deprecated. In the meantime other old discussions had settled with similar trends: Qt Mobility, Qt Creator and the WebKit alignment.

Next Billion, no less

Between #feb11 and the Nokia N9 launch on #jun28 a lot happened and a lot was said, inside and outside Nokia. Everybody updated their CVs and so did I. Working in the USA as a foreigner with family and a visa tied to your company can be distressing in times of company changes. One morning I got a call from Daniel Kihlberg, who tomorrow will become my new manager. In short, he described a space where different dimensions needed to be combined successfully: Nokia’s Next Billion strategy, a truly open Qt Project and a rich Qt global ecosystem across different industries. Like all real-life equations, there are more factors, more dimensions and a lot of entropy. All in all the proposal fits my views and the type of game where I feel motivated and useful.

And here I am, ready for the next step. I’m permanently thankful to Carlos Guerreiro (and Zara) who actually pulled us to Helsinki. It has been a pleasure to be involved in ideas/projects like the Nokia open devices, the Hacker Editions, the Maemo Downloads (more than 100M!) and the Summits. It has been an extreme pleasure to work together with great people inside Nokia and out in the community, including brilliant unsung heroes like Soumya Bijjal or Niels Breet.

Let me say Big Thank You for these great years – even if I’m just moving downstairs.

// Skippable background

This was my debut at programming, preceded only by HTML web pages in 1995-97 and a Basic sketchy game with 3 sprites that never went beyond the Commodore 64 we had at home around 1983. In fact as a teenager my vocation was always split between natural and artificial languages, and only after a close tie I started my studies in Communication Sciences – Journalism branch. Since then I’ve written a lot and I’ve learned to describe, specify and instruct by putting words one after another (still not as good in English as I would wish).

For what is worth I’m not a designer either. At the university I devoured the splendid collection of comic books of my faculty but I didn’t succeed at drawing my own strips. Still, I had the luxury of living surrounded by creative, practical and pragmatical people with a varied range of skills and tastes. Over the years I have developed some sense of how new things could look like and behave. Conscious of the big amount of time it takes me to use Gimps, Adobes and the likes only to come up with mediocre results, most of the times I resort to concepts on paper.

But let’s go back to the chess program.

// Skippable background about the chess program

Two years ago I had convinced the great Michael Hasselman (mikhas) and a few others to create the Miniature project, being my main tools of persuasion a plan on a wiki page plus a pencil draft. Not being a programmer or a designer, these are the weak arguments you have at reach to get things done. Miniature had a short and unstable life in the Maemo extras-devel repository for adventurous N900 users. You could say we didn’t succeed… yet some of my best moments with the N900 (and I had many) had Miniature running in the foreground. For instance, playing late night with the also great Iván Frade in Meritähti, the cozy and nutritious bar no tourist guide will recommend if you ever visit Helsinki.

After the N9 launch I saw with despair that proper mobile chess was still absent in the Qt catalog. I made a second call, and almost miraculously mikhas answered again, but this time stating clearly that he would focus on the backend and somebody else would need to work on the UI. I looked around. I looked myself in front of the mirror (mentally, I mean). The first Miniature had to deal with Qt 4.6 and QGraphicsView with no cutton or oil. Hardcore stuff. Now the declarative and Javascript friendly Qt Quick was at the forefront, waiving the slogan of Programmers and Designers Unite! I decided to give it a try, getting a tacit permission from my manager to call some of this time “training”.

And yes, this is great training! Sitting in front of tutorials and code examples for the sole purpose of learning is boring – at least for me. Trying out things, copypasting code from somewhere, asking on IRC and forums, building and rebuilding until the damn thing works is überexciting – at least for me.

// Finally some actual stuff

These are some pros and cons found during the first stages of this trip. I hope they are useful for others like me, getting started in Qt Quick and in programming. They are all mixed since frequently a con leads to a pro and vice versa. In some cases it’s not even clear whether the thing is a pro or con, but it’s remarkable anyway:

The Qt SDK is such a beast
And I got my way with relative ease. Accessing documentation while writing code, connecting to the device… The first time I couldn’t believe my dummy rectangle was showing up in the N9, an icon was added to the app grid and a .deb package was sitting in a local folder of my laptop.

But Qt Designer can’t be used yet
I had so much hope in Qt Designer for my first steps. I had played with it and it reminded me the old good Macromedia Fireworks, with the additional advantage of generating actual code. Then I found out that it was basically of no use here and now for MeeGo development.

Neither the Simulator, and even the emulator…
Qt Simulator didn’t digest MeeGo either, here and now. QEMU could but… Good that I had a device because the simu/emu would have required a lot more time for someone new like me, needing to see how things progress every 2 new lines.

Getting started with Qt Quick is really simple
Without Designer I quickly realized that typing directly the code in a proper SDK was simple enough and probably lead me to cleaner and more solid structures. I started to learn how QML thinks, and starting to guess what would and would not work even before pressing the build & deploy button.

The documentation is extensive, but still not consolidated
QML and Qt Quick have evolved a lot in a short amount of time, and different audiences with different background are meeting there almost for the first time together. All in all it feels that whatever is different from Qt/C++ is explained in detail (e.g. anchors or pure UI elements) while other parts closer to traditional Qt are mentioned with more brevity. This is surely fine for Qt/C++ developers, but this is also where the less experienced or more web oriented developers might get stuck. In some points I have missed more basic descriptions, wider code examples… oh, and many more screenshots showing how demo apps and components are supposed to look like without having to run them in the SDK.

The community is savvy and very helpful
Whenever you get stuck in something you start looking for help. I didn’t rely (much) on the professional developers sitting few steps away from my desk (except for really embarrassing basic questions). I put my immediate hopes in IRC, but being August and typing from PST got me more silence than expected in #qt-qml. Still I got some great answers from e.g. special and frals. #harmattan was a second resource but the Scratchbox – Python – middleware angle of that group is noticeable. #miniature is obviously useful but I didn’t want to exhaust the patience of mikhas… Then I decided to become a Lab Rat (now a Ant Farmer) in the Qt Developer Network and since then the forum hasn’t disappointed me once. Getting the attention of a troll, a certified specialist or just the right person with the same (solved) problem is just a luxury.

The veterans don’t have always the right advice for you
These days I’ve got many Qt answers to my QML questions… since I was asking to Qt savvy developers. That helped me understanding better my own questions, and finding out where to find the QML centric answers. Like for instance “how to put a link to a web page opened by the device browser?”. Sure, Qt and DBus can do wonders for you – but actually the right answer for me was something a lot simpler: Qt.openUrlExternally(). The feeling was familiar: years ago GNOME desktop developers would answer my questions with “open terminal and type…” when actually the desktop itself offered solutions not involving a console.

Backend and UI can really be developed in parallel
While mikhas has been working hard on a C/C++ backend containing abstract models, internal logics, capacity to talk to the Free Internet Chess Server via telnet and to plug into GNU Chess, I was able to define a UI with all its interactions almost autonomously. I actually started with an own QML project separate from Miniature, until mikhas liked what he saw and decided to integrate it. I just had to leave comments in the code: // FIXME this is a static string, the backend should hook here with a real variable. Now we are basically at the point where mikhas has a backend that play games you can’t see, while I got a nice UX that doesn’t know any chess. Sewing is happening as we speak.

Open source development is just great
If I started with Qt Quick from scratch one morning, on the afternoon I was already learning how to get that code and package out of my system, to be seen and tried by others. I didn’t get much attention at the beginning, but only the fact of writing publicly brought me to structure things as good as I could (still crappy, I know) and to comment a lot more and better that I would comment just for myself. Again the Qt SDK was useful here, generating packages that install and bridging with git nicely. Additional thanks go to the maintainers of paste.debian.net and to the various authors of little but useful code snippets borrowed here and there. Every time I said “I can’t be the first one having to do XYZ” turned out to be true. Someone had gone through that and was sharing the result with the World. Thank you, thank you very much.

// This is getting longer than expected. Again.

CONCLUSION
I feel a lot better, even if these days I’m suffering a lot more. Playing with ListModel, GridView, states and animations hasn’t been always funny but after many trials and errors I got exactly the behavior and the effects I was looking for. Now a new Miniature contributor can come willing to implement the logics for e.g. chess by email and I know I will be able to help providing a decent UX. In the meantime Qt5 and myself are getting closer to deeper Javascript support, which looks promising and a sure continuation of the fun!

I’m about to start my second month of Qt Quick programming. Miniature 0.4, here we go!

[Disclaimer: The opinions expressed here are mine.]

There has been a lot of discussion about MeeGo and its future, now reinforced with the launch of the Nokia N9 – a great product that seems to leave nobody indifferent. Here you have some thoughts cooked between #feb11 and tonight (even if Helsinki has little night to offer to mid-Summer visitors).

One problem in this discussion is that a lot of focus is being put in the word “MeeGo” when actually it’s a label that can mean different things to different audiences in different contexts. In fact though, the label doesn’t count as much as the actual software underneath and the projects involved in its development.

The Nokia N9 is powered by MeeGo 1.2 Harmattan, the OS equipped with this UX that has impressed to many. Now, let’s have a look under the hood to see what parts of it really matter to the MeeGo project, the OSS community, the developers and users interested in the N9:

Linux Kernel

We are talking about the mainline Kernel. Needless to say this project will continue to live and evolve. Nokia may keep contributing to this project and using it for R&D and future products – nothing announced at this point beyond this reference of ‘MeeGo’ in relation to the ‘future disruptions’ strategy.

Qt

This is another rich label meaning the toolkit, API, SDK, a variety of technologies involved… The project is in good shape with a promising future based on Qt Quick, the innovations and open governance model being implemented for Qt5 as we speak. The Nokia N9 is a Qt champion product, there are 100 million Qt-enabled Symbian devices (a lot more are expected) and Nokia just announced that Qt will have a central role in its ‘next billion’ strategy. Beyond Nokia, Qt also continues its growth.

WebKit

Another key OSS project where Nokia is a veteran contributor. Plays a key role connected to the increasing relevance of HTML5 (yet another vague label) in the mobile industry. Both WebKit upstream and the team(s) working on it at Nokia have a bright and busy future.

swipe UX

It doesn’t even aim to become a label, but has captivated already the attention of many when seen in action in the Nokia N9. As a happy user and earliest tester I’m proud of what we have achieved.  Stephen Elop has said that it will live forward and evolve in future Nokia products.

In my opinion that’s it. This is what really matters about MeeGo 1.2 Harmattan when it comes to discuss about future products, platforms and ecosystems. Note that these four pieces are very versatile and flexible, they can play with each other and they can also head towards other paths, offering many possibilities for future products.

The rest of technologies involved in MeeGo 1.2 Harmattan are also crucial in terms of functionality and success of a product, but they are more the sort of interchangeable glue, technology in motion that may change because of life cycles, hardware, providers, technology selections, etc. The projects and companies developing the myriad of pieces know this well and work hard & fast to either push new releases or jump wagon to whatever is the new future greatness.

Now, it turns that the rest is very important today for the MeeGo project when it comes to define what is a MeeGo compliant product. According to this definition, if you miss the rest then you don’t have a MeeGo product, unless you propose and obtain a trademark exception.

(((Another approach would be to simply define MeeGo = Kernel mainline + Qt + WebKit, syncing app developers around the OpenGL, Qt and Web APIs – but this is not the reality today)))

With all this background in mind, you can put a vague question in more precise terms:

Since #feb11 Nokia has a clear software strategy where high-end smartphones are covered by the collaboration with Microsoft on Windows Phone, therefore the consequent answer is the one already given by Stephen Elop: No.

However, look back at the four essential pieces above and keep in mind that Nokia is investing in all of them. Even if working on them is really fun, you may guess that Nokia is not paying the teams for the fun of it. It is sensible to expect more to come in a form or another.

Considering that Linux Kernel and WebKit will continue evolving no matter what Nokia decides and assuming that the swipe UX will continue evolving in Nokia products, in reality the concern about “the future of MeeGo at Nokia” is tied to the future of Qt: Nokia’s investment and leadership, involvement of other parties in a wide community, usefulness addressing the mobile and cross-platform challenges, increase of the developer base, increase of the quantity and quality of Qt apps… There is a direct correlation between the success of the Qt project and the satisfaction of the future N9 users, even if most of them won’t know ever.  :)

Qt was relevant before Nokia acquired Trolltech. Nowadays is more relevant than ever, and is evolving fast. It’s a great piece of open source technology that can compete side by side with the leading toolkits. I only expect a bright future for it, sitting between the Linux stack and WebKit, powered by its championing capacity to support multiple platforms and enable multiple UXs.

For all these reasons I’m really happy about the arrival of the Nokia N9 and its role in this interesting chess game. About the future, since I joined the mobile industry in 2007 only one true has prevailed: no matter what your prediction is, the reality in 12 months will be different and unexpected today. Enjoy!

N9

The Nokia N9 is the ultimate Qt-powered mobile device. I find it a pleasure to watch and play with. Its polymer unibody chassis complemented by a strong and scratch-resistant curved glass makes it both solid and smooth in the hand. Multitasking is pushed forward with a combination of open tasks, events and apps. You navigate through these views with a simple gesture, a swipe of a finger. Get a grasp of this beautiful (and open!) product at http://swipe.nokia.com.

N950

While the N9 becomes publicly available, Nokia has produced a limited edition of N950 devices for the most devoted Qt and MeeGo developers with apps in the works. We are offering 250 devices to open source community developers through the MeeGo Community Device Program. Nokia Developer has more for champions, partners and other professional developers.

MeeGo 1.2 Harmattan

Nokia’s implementation of the MeeGo platform has been released. It combines a playful multitasking UX with an efficient OS that shares the same API and architecture pillars of MeeGo upstream. It’s a great demonstration of what can be done with the MeeGo platform on a mobile device. Check http://www.developer.nokia.com/swipe/ux/.

Qt updates

The Qt SDK has been updated with a Harmattan target including the Qt Quick UI Components. The way for Qt developers to target MeeGo, Symbian and other platforms is being paved. Nokia is also making Qt core to its strategy to take the Internet to the ‘next billion’. Qt is a star in the OSS stack and is at the backbone of all these announcements. The Qt5 governance plans becoming reality as we speak make it even brighter. More at http://qt.nokia.com.

MeeGo Community Edition

The community team that has brought usable MeeGo upstream releases to the Nokia N900 will add now the new devices in its scope. The planning and work will happen in the open, just like the rest of the Community Edition activities. Remember that these are not Nokia official releases, but fun R&D experimentation open to all community contributors. More at http://wiki.meego.com/ARM/N900

The wait is over for MeeGo developers. Now it’s time to show off your apps!

San Francisco and Dallas are also growing a Local MeeGo Network, followed by Buenos Aires, Cambridge and Delhi.

Helsinki & Oulu, now what are you waiting for? Same for Bangalore, Manaos, Oslo, Berlin, Beijing, London, Portland, New York, San Diego and whoever else is reading this invitation with a genuine interest in MeeGo stuff.

All what you need is 5 ameegos happy to meet once a month. Let it grow if it wants to grow. See http://wiki.meego.com/Community_Office/Marketing/Local_MeeGo_Networks

If you want to start a Local MeeGo Network I’m happy to help you. Let’s reach that critical mass.

Here you can track MeeGo related activities in San Francisco Bay Area. Propose genuine MeeGo meetups or casual meetings after interesting events.

First meetup on September 14 @ San Francisco:

MeeGo Developer Day – The After Meetup

Running MeeGo Handset UX in the N900 has been possible (technically) since few weeks ago, but now the N900 hardware adaptation team has started releasing full raw images containing some essential hardware related binaries. The result is a simpler installation process for patient power users and a more functional software as a reward.

The simplest way to run MeeGo in the N900 without loosing Maemo 5 and all your data is to boot from Micro-SD. Nice simple dual-boot is supposed to come at some point but it’s too hackish at this point. In the meantime you might want to do this:

1. Download the latest raw image and kernel from the Nokia server.
2. Install the raw image in a Micro-SD card of 2Gb or more (Linux and Windows instructions).
3. Insert the card to your N900.
4. Load the kernel to your N900.

E voilà! MeeGo should be booting in your device, starting with the Tux and a booting log like in the old good times. Give it some more time and a MeeGo homescreen should appear, with MeeGo characters at the front, the Qt powered MeeGo Touch Framework operating in the back, a task launcher, settings, device lock… and little else at this point:

• Pictures, People and SMS have some functionality in place. Testing and feedback is definitely welcome here.
• Browser and Phone seem to be there but I couldn’t boot them.
• The rest of apps are placeholders in this week’s version. This is the current list of apps (maybe there is a way to take a screenshot already, will try in future versions). Don’t pay too much attention to the list, I guess there will be changes before MeeGo 1.1 final:
  • First screen: SMS, Clock, People, Chat, Camera, Pictures, Music, Videos, Maps, App-Up, Help, Calendar.
  • Second screen: RSS Reader, Stocks, Trailers, Lock, Fortune.

This is MeeGo Handset 1.1 unstable today. Note that a month ago stevechippy showed in a video a slightly better experience with an Aava prototype, therefore some of the problems found in the N900 might be related to the specific adaptation to this hardware. There are still some weeks to go after the planned feature set before the feature freeze arrives.

Have a look, pick your preferred area to test, find bugs to report (Hardware = “Handset”, Architecture = “ARM”)… Have fun while the battery lasts (power management for the N900 is supposed to be implemented soon). As said, the MeeGo experience in the N900 is very rough at this point. Yet exciting for some people. See you in the download queue of the next unstable release!

Green Dublin Letterbox - Stephens Green Dublin (CC by-sa)

A subdomain is born: conference2010.meego.com

The first MeeGo Conference will be held in Dublin’s Aviva Stadium on November 15-17. The venue has a main room with a capacity of 600 people and we will do our best to fill it up.

Currently “we” are the Linux Foundation, Intel and Nokia, who are providing the basic hands and funds needed to assure the success of the event. Now you can get involved!

• The call for session proposals is open until August 23rd. We welcome proposals about hardware support, platform development, application development, MeeGo project process and progress, and any other MeeGo related topics.
• Sponsors wanted! We expect a very interesting audience and we are putting a strong effort making the event accessible through free registration, sponsored participants, sponsored meals & parties…
• Volunteers are welcome. The meego-community mailing list is the place to be. For instance, testing and feedback about the conference website is very useful at this point.

The event registration will open soon. Early birds are great contributors to the success of the event, allowing better planning and providing louder buzz. Make your plans, see you there!

200 Mathilda Ave @ Sunnyvale

Today an envelop arrived at home containing our passports with US visa stamps expiring on Summer 2013. This was the last step before knowing for certain that our 3,5 years in Finland will be followed by a next phase in California. In short, the plan is to empty our house in Helsinki by the end of June, fly to San Francisco during our holidays in July and go back to work in August at the Nokia offices in Mountain View. A collateral damage of this relocation is that I will miss aKademy, OSCON, GUADEC and the Community Leadership Summit that I was really looking forward to attend. At least now it will be easier to visit Jono, one of my personal local heroes.

I’m keeping the same role (MeeGo Community Office coordinator + open source misc @ Nokia) and the same manager. The MeeGo project and all its network of actual and potential connections has been a major reason for this relocation (great Mexican food being another one…) I’m looking forward for the combination of American timezones and European background when collaborating with all kinds of free software players in the MeeGo context. As usual, I’m ready to learn as much as I’m willing to be helpful.

We are living exciting times in our industry, and the Santa Clara Valley is a very exciting place to be! The second most interesting news this week after our US visas was the announcement of the future location of the Nokia Offices in San Francisco Bay Area: Sunnyvale Downtown. Nokia employees spread in the offices of Mountain View, Redwood City, Menlo Park and San Francisco are supposed to join a common building by the end of the year. Sounds like an interesting time for Nokia in the Bay Area, and I’m almost honoured of contributing my little bit in that process too.

Personal life appendix

200 Mathilda Ave @ Sunnyvale seems to be a location open to many combinations keeping me apart from car commuting – something that I deeply hate and have successfully avoided in my professional career. There are several bus stops and the Caltrain station nearby. Plus most of the valley is flat (the areas where we could afford to live anyway) and most of the year the weather is compatible with cycling, even for a Mediterranean guy like me. Also it turns out that my little kids, German native speakers, will have a good chance to have a soft immersion in the bilingual German international school that happens to be in Mountain View, quite close.

Where will we end up living? Who knows now. After some years of rural Spain and some more of quiet Finnish suburbia, Katja and me start missing a bit more of an urban, active and populated context. San Francisco city would be excellent even with the train commute, if it wouldn’t be for the real family life we are having with our 3 and 5 years old children. Maybe Sunnyvale near Downtown can bring that balance? Maybe something affordable and convenient still exists in Palo Alto? Any tips are welcome!

BIG NEWS TODAY meego.com + video from MeeGo Steering Group + video from Nokia & Intel

This is a move that many had desired. On the paper it just made so much sense. However, not too many had really thought it would happen. Big companies have quite often big egos and it’s not easy for them to be humble and come together. I’m happy to work in a company that has been able to push and concede together with another company that has been also able to push and concede. 1 + 1 in this case will bring three and more. If these two megacorps could drop some of their priorities in order to reach a common ground, other players can do that too. Including you? (yes, you).

As a Nokia contact with the Maemo community and as an active community member myself, I expect this announcement to be big news for the maemo.org membership. Software freedom and more diversified devices have been two loud and consistent claims since the Maemo project was born in 2005. MeeGo brings that, and a lot more. In fact I think today is an historic day for the Linux and free software communities. Not only for seeing these two companies shaking hands in a Linux Foundation hosted project, but for the rest of handshakes expected to come after today’s launch. Now, where is your hand? 

Intel and Nokia are two major investors and contributors in free software development. Both have big teams in house and collaborate with a wide variety of open source companies, projects and rock stars. Now they are combining strategies and resources in order to kickstart a free Linux mobile platform. Real code will come soon although plenty of it is already available in code repositories from Moblin, Maemo, Qt…

MeeGo is just like you would expect a free Linux OS to be: based on the standard Linux and Free Desktop technologies and developed publicly in a project open to all contributors. As a huge fan of the free software community at large, I’m just amazed by the huge amount of passionate ideas and work it pushes. Every time time someone attempts to encapsulate part of that energy and bring it aside for a mobile platform I think “Nah, you really want to be part of that storm, fuel that powerful entropy and be clever canalizing the energy to your platform and products.” You don’t know how happy I was the day I knew Nokia and Intel wanted to do just that with MeeGo.

Answers in the new community

You can find more details at meego.com . However, don’t look for all answers since there are so many missing. The reason is obvious: many of these answers rely today in the Maemo and Moblin communities. Also in the open source upstream projects feeding the MeeGo architecture. Also in the application developers that ultimately will make this platform successful. Also in the chipset vendors, device manufacturers and other users and stakeholders of this platform called to spin the whole mobile industry.

All these answers are somewhere: we just must find them. It will require the best of our brains. It will be deep, it will be fun. I just couldn’t wait today’s launch in order to start the bootstrapping of MeeGo. The whole thing is actually big and digesting it takes some time. If you want to be part of this I recommend you to go through the website, subscribe to the mailing list and decide the task or area you want to push first. In other words: choose your mission in the MeeGo project.

My preferred mission here and now is to contribute in the evolution of maemo.org and the Maemo community in the new MeeGo context. I have some ideas but, to be honest, I’m biting my tongue in order to let you go first. But still I couldn’t sit just quiet waiting for the launch, so I decided to start a wiki page describing and comparing the most interesting assets of the Maemo and Moblin communities. Please help improving it. It will be useful to figure out all what we could have if we are clever integrating and merging.

And now the personal anecdote

In Autumn 2006 I was a 770 user applying for a job at Nokia. There was this interview with Valtteri Halla (now MeeGo’s Technical Steering Group member) and Ari Jaaksi (now VP and head of Maemo Devices). I was explaining them how great it was working as self-employed or in small cooperatives and living in a lovely house in Andalusia. Ari asked me what were my motivations to leave all that, move to Helsinki and join a big corporation. Well, by that time my second child was born and I really needed a source of income.   But the reason not to hesitate taking such a chance was my explicit agenda of bringing Linux and free software to the real mainstream.

Today, three years after getting that job, I feel this agenda (pushed together with many others in the World: I love you all) is about half the way. Working at Nokia you really learn the meaning of the word “mainstream” and yes it includes your cousin, your neighbor and many people you don’t even think of. MeeGo is a platform to reach them and offer them something useful and exciting for their lives. Software freedom lovers: you know what I mean.