maemo LinuxTag update

01Jun08

Audio and slides of the maemo update at LinuxTag. Main talk points: Diablo, Fremantle, Harmattan, GTK+/Qt, maemo.org brainstorm & maemo summit on September 19, also in Berlin.

  • Start – Slide 1: maemo LinuxTag update
  • 00:17 – 2: The story continues
  • 01:34 – 3: Diablo
  • 04:00 – 4: Fremantle
  • 05:50 – 5: Harmattan
  • 08:05 – 6: UI framework progression
  • 12:54 – 7: Honoring good ideas and discussion
  • 14:30 – 8: New community roles for maemo.org
  • 15:25 – 9: maemo.org brainstorming
  • 17:55 – 10: maemo summit
  • 19:50 – 11: Ready? (my weird sound is due to slow drawing of the new slide) πŸ™‚

Questions

  • 21:10 – Reasons for not using E and G in the release names?
  • 22:05 – Availability of N800 & N810 devices in India?
  • 23:35 – How long the N800 will be supported?
  • 25:05 – Are you doing backports to keep supporting previous devices i.e. the 770?
  • 31:00 – Possibility for the community to maintain software for legacy devices?
  • 35:30 – Opening power management and WiFi could enable others to do new things
  • 38:52 – EOF


15 Responses to “maemo LinuxTag update”

  1. 1 Ryan Abel

    Thanks, Quim, the presentation was great! I’m looking forward to hearing the audio from the rest of the speakers.

  2. Hell Quim; would it be possible for you to upload the slides someplace that do not require to log in to download them ? Thanks.

  3. 3 qgil

    Weird, I thought slideshare.net was open to view and download files!

    ???

  4. Good talk. Nice picture on slide #7πŸ™‚

    One thing which concerns me is that you’re obviously very enthusiastic about increasing community involvement and ownership. However, the commercial realities (or the *perceived* commercial realities) of working in a large corporation like Nokia mean that the long-term planning of fremantle and harmattan is still undertaken without any direct community involvement.

    Indeed, once the planning has been largely completed, the community is *still* kept in the dark, apart from the direction of the GUI frameworks and their codenames!

    If I were in the audience, I’d’ve asked, “how can you reconcile the level of community involvement you want, with the level of control and secrecy that Nokia seem to require?”

    We’re not involved at the high-levels (planning, speccing, design reviews); and there’s very little involvement at the low-levels in terms of patches for apps etc. I think the reason for this is not unrelated to this disparity: without any clear vision on the detailed technical direction of the project – at all levels – no-one will spend the time writing a patch and submitting it: it’s not clear if any Nokia-led work will be duplicated, whether the patch would be accepted, whether the improvement would be compliant with the near-mythical “UI specification” and so on. In fact, thinking about it, I don’t believe there’s a documented patch policy at all!

    You ask the community to take the lead on some of this, but one of the points (no pun intended) of my triangle is to show that a rudderless ship will run aground. Nokia can’t keep its cards so close to its chest *and* expect an open community to operate.

    Now, it may be perfectly adequate to have an open community ecosystem for developers – but if that’s the desire, let’s focus our energies on that, rather than trying to open the maemo development process (and, hence, IT OS). Whether maemo itself is open or closed then becomes irrelevant – or, at worst, a distraction.

  5. 6 qgil

    Nokia will keep planning the official releases based on its own strategy. Community feedback through maemo.org, upstream projects and other channels help defining this strategy, but still Nokia plans to be the main driver of the official releases. The participation of the community in this development process can be increased, though.

    On top of -or apart from- the official & supported releases, the maemo comunity can be involved and empowered to keep their own agendas extending, complementing and subverting the official maemo platform with additional software and variants.

    > β€œhow can you reconcile the level of community involvement you want,
    > with the level of control and secrecy that Nokia seem to require?”

    Ah, I missed more questions like this! We still had a high amount of known “old” questions. No problem: the materials are out, the brainstorm is progressing and questions are taken anyways.

    A possible answer (late on Sunday, bare with me):

    Disclosing as much and as early as possible the information relevant to open source developers. Releasing soon and often the core platform. Keeping information about new devices, hardware features, commercial services and applications out of this open community game.

    But in the same way that you want to check how serious and how far Nokia wants to go, Nokia also wants to do a similar check to the maemo community to see what are you really up to. What the community think is urgent and important.

    > without any clear vision on the detailed technical direction of the project
    > – at all levels – no-one will spend the time

    Let’s improve what needs to be improved in order to see more smart and creative people having a great time contributing to maemo.

    > one of the points (no pun intended) of my triangle is to show that a
    > rudderless ship will run aground. Nokia can’t keep its cards so close to its
    > chest *and* expect an open community to operate.

    We know, and this is why your triangle was honored in the presentation. πŸ™‚

  6. BTW, did you know you can sync audio and slides also on slideshare into combined “video”?

  7. 8 qgil

    No! I was looking for an easy solution. Thanks for the tip.

  8. 9 DJS

    Hi,
    what counts today is money.
    As Nokia is so powerful global corporation,
    so why not to donate maemo developers with Nokia shares
    with new emission directed to developers only.
    Money is what makes ppl to work harder and in more efficient way.

  9. 10 Ryan Abel

    Darius, is that you?

  10. 11 pupnik

    In reply to Andrew Flegg: I think the degree of hierarchy is a balancing act between several goals. The community does not speak with one voice, and I’d submit that most community members have a fairly narrow scope of maemo-relevant experience and expertise.

    Opening up too many things to discussion is a recipe for not getting anything done.

    Jaffa’s idea of a Community Council would help there by allowing the community to nominate/vote-on non-Nokia people who have generally perceived qualifications or wisdom in various areas – well that’d be my interpretation of it.

    Speaking for myself, I’m not qualified to talk about grand plans. I just have a few issues that I’d like to remind everyone of:πŸ™‚

    1) Onscreen Keyboard not usable for non-hildon apps. Having it generate regular X key events, and be raisable with some buttonpress (or combination? not easy) would be nice for those ‘other’ linux apps.

    2) Open File dialog show only a few files/dirs at once, and only show a few characters of the filename. It would also be nice to be able to disable subdirectory scanning for faster navigation.

    3) SDL doesn’t recognize the N810 ‘FN’ key.

  11. The device is potentially a desktop replacement as all non-GUI apps are eventually ported. The power of the CPU for multitasking can be leveraged by running non-GUI apps where possible. With that in mind, a more ergonomic keyboard is in order. The Psion Series 5mx had a much better keyboard. Some devices have tilting slider keyboards which are more ergonomic than slider-only keyboards.

    Don’t neglect making it easier for Wintards to learn command line operation. For example you include Busybox with no man pages and force users to install original apps like wget and tar. Instead of shying away from the command line, think of the potential of including tutorials — One N810 Per Person so that the entire population of India can chuck their Windows PCs. One day a fashion phone may be a phone that runs BASH.

    The fastest way to exponentially multiply the number of ported apps overnight is to focus on leveraging the command line capabilities of the device.

    Forget backports to old devices. Please port Maemo to the Nokia E90! You can even run an S60 emulator under Linux if you are not ready to discontinue that code yet.

  12. 13 A.T.

    DJS, I guess your idea had been contemplated, but… Nokia has been public company after IPR back in middle of ’90s and since then it has to sell shares on equal to everybody conditions. Hence following your advice most probably will end up with some managers getting in trouble with regulators & law. Well, you are free to ask governments/parliaments to remove that law, but I don’t believe it happens in any foreseeable future.


  1. 1 InternetTabletBlog » Archiv » Linuxtag 2008 (2): Von Schafen, Kalendern und Programmkatalogen
  2. 2 maemo.org brainstorm, evolution, summit and future « flors

%d bloggers like this: