Wednesday, May 05, 2010

Harmattan + Meego Here I come

I have moved now away from Fremantle to Harmattan and Meego. This doesn't mean that the maintenance is stopping for Fremantle in any way, just that the coordination effort on OS & MW has lessened and my presence is not needed so much anymore.

I would like to take just a sec also to address the comments about the leaked firmware. It is indeed not the final Pr1.2 firmware, and there are reasons for it. So, if you find severe issues in it, don't be surprised. If it only had minor issues, it would have been published already. We are often finding still some new major issues in the stabilization phase. It's normal for big projects.

So, what am I doing now then? I am looking after the Harmattan Maemo API to make sure we have a solid 3rd party API and there is a clear continuation path for everything that would change for Meego. At the same time I'm working as a catalyst for the Harmattan software program. This catalyst role is naturally a bit vague and I'm often afraid whether I'm doing more harm than good after being so long time away from Harmattan development, but it looks like I'm able to pick issues every day that do push us a clear step closer to the target. Let's see how long this continues. But what I really focus all the time is the Maemo API.

What does the Maemo API work mean in practice? It's about defining together with the architects the Application development APIs and the platform APIs. The distiction between these two is that every single API of the former should stay the same in Meego and maintain API and ABI compatibility. For the latter, we yield that they are needed for development of many applications but we deem those may be subject to change for various reasons (be that that we know a better one is around the corner, the API is unstable or even that we just happen to be uncertain what will happen to the API in the future), and thus if you use those APIs on your app, they might need tuneups before they work on the Meego handheld platform.

In addition to only the pick and mix work of selecting the APIs, I'm also actively trying to look for issues we might have in the APIs that restrict certain types of development. It's a common case that we have been looking solely for our own needs (or Intels) on many cases, but we have forgotten that small detail that would mean the world for some 3rd party developers. I would be naive to think that I can somehow find all the issues and get them miraculously fixed. Indeed not, but I have some talented help and I'm sure every improvement is a step to a better direction.

I'm not exactly certain if I can discuss about the inititives that I have started or the issues I have found, so I'll leave discussion on those until I have chatted with Quim Gil about it. In the meanwhile, please do contact me if you find issues in the APIs that has been published in the SDKs or in the open repos like gitorious for Harmattan Maemo API.

Oh, why is it Maemo API and not Meego? Well, we are still using the low part of the stack from maemo and haven't merged to meego lower levels, we use still different packaging system, and tons of other reasons that have been voiced out probably many times before.

6 comments:

  1. Go Urho! Go MeeGo! Go Maemo! Go Harmattan!

    And don't forget... it all should work on N900 :)

    ReplyDelete
  2. > please do contact me if you find issues in the APIs that has been published in the SDKs

    The API documentation isn't even published online. I know people can build it locally but I won't believe that anybody cares until it's really made visible:
    https://bugs.maemo.org/show_bug.cgi?id=9286
    (There's a link to all public Harmattan bugs here:
    http://qt.gitorious.org/maemo-6-ui-framework )

    libhildon in Maemo Fremantle showed that we need wide feedback earlier rather than later. Nobody can just deliver a finished API.

    ReplyDelete
  3. Imho, the API should remain named Maemo both in order to differentiate it from the MeeGo OS and to retain a little nostalgic history value. ;)

    ReplyDelete
  4. Does this mean all development on the USB control project which is devel repository will be stopped ? Had been waiting for that project to be the next big thing on N900. Or is hacking OTG support not possible at all on N900 ?

    ReplyDelete
  5. @Vijay: OTG is not possible on n900, only n810. It requires some small solderings on n900 to be possible, so it's out of any normal peoples hands (and requires insanely mad skillz)
    @Murray: Indeed, documentation will need to be available in a collected place. I'll have a chat how we can arrange the doxygen docs to be regularily updated to some location.
    @Tim: API in Meego will be called Meego-Handheld, which will separate it slightly from the Meego-Core, however, it will of course have everything of Meego-Core and then some.
    @Hendy: Thanks for the support, yes, wouldn't it be nice if it did. But no comments as to whether it will or will not happen.

    ReplyDelete
  6. @konttori - you know it whether N900 has the future or not, don't you?

    In case N900 gets ignored like the other Nokia Internet Tablets, then don't expect your loyal Nokia users to stick to Nokia.

    Learn from Google/Apple.

    Android has now jumped up to the second place leaving behind the long time second place holder - Iphone.

    Even though the margin between Nokia and Google/Android is huge, Android has the potential to replace the pioneer Nokia in the coming years.

    Nokia now has a fearsome competitor in terms of Google/Android and the war has started with Android replacing Iphone being the first step of Google into the Mainstream.

    ReplyDelete