14 June 2010

  1. Front Page
  2. Applications
  3. Development
  4. Community
  5. Devices
  6. Announcements
  7. Download issue

Other Issues

  1. 30 January 2012
  2. 23 January 2012
  3. 16 January 2012
  4. 9 January 2012
  5. 2 January 2012
  6. 19 December 2011
  7. 12 December 2011
  8. 5 December 2011
  9. 28 November 2011
  10. 21 November 2011
  11. 14 November 2011
  12. 7 November 2011
  13. 31 October 2011
  14. 24 October 2011
  15. 17 October 2011
  16. 10 October 2011
  17. 3 October 2011
  18. 26 September 2011
  19. 19 September 2011
  20. 12 September 2011
  21. 5 September 2011
  22. 29 August 2011
  23. 22 August 2011
  24. 15 August 2011
  25. 8 August 2011
  26. 1 August 2011
  27. 25 July 2011
  28. 18 July 2011
  29. 11 July 2011
  30. 4 July 2011
  31. 27 June 2011
  32. 20 June 2011
  33. 13 June 2011
  34. 6 June 2011
  35. 30 May 2011
  36. 23 May 2011
  37. 16 May 2011
  38. 9 May 2011
  39. 2 May 2011
  40. 25 April 2011
  41. 18 April 2011
  42. 11 April 2011
  43. 4 April 2011
  44. 28 March 2011
  45. 21 March 2011
  46. 14 March 2011
  47. 7 March 2011
  48. 28 February 2011
  49. 21 February 2011
  50. 14 February 2011
  51. 7 February 2011
  52. 31 January 2011
  53. 24 January 2011
  54. 17 January 2011
  55. 10 January 2011
  56. 3 January 2011
  57. 20 December 2010
  58. 13 December 2010
  59. 6 December 2010
  60. 29 November 2010
  61. 22 November 2010
  62. 15 November 2010
  63. 8 November 2010
  64. 1 November 2010
  65. 25 October 2010
  66. 18 October 2010
  67. 11 October 2010
  68. 4 October 2010
  69. 27 September 2010
  70. 20 September 2010
  71. 13 September 2010
  72. 6 September 2010
  73. 30 August 2010
  74. 23 August 2010
  75. 16 August 2010
  76. 9 August 2010
  77. 2 August 2010
  78. 26 July 2010
  79. 19 July 2010
  80. 12 July 2010
  81. 5 July 2010
  82. 28 June 2010
  83. 21 June 2010
  84. 7 June 2010
  85. 31 May 2010
  86. 24 May 2010
  87. 17 May 2010
  88. 10 May 2010
  89. 3 May 2010
  90. 26 April 2010
  91. 19 April 2010
  92. 12 April 2010
  93. 5 April 2010
  94. 29 March 2010
  95. 22 March 2010
  96. 15 March 2010
  97. 8 March 2010
  98. 1 March 2010
  99. 22 February 2010
  100. 15 February 2010
  101. 8 February 2010
  102. 1 February 2010

In this edition...

  1. Front Page
    • Major, and avoidable, recent mistakes from Nokia
    • Despite MeeGo, is Nokia getting more closed?
  2. Applications
    • Extras enabled out-of-the-box on Nokia's next device?
    • Pelota Fifa Widget shows World Cup scores as they happen
    • Hermes updated - now with LinkedIn, Facebook, Twitter, Gravatar and find-as-you-type matching
    • Chromium removed from maemo.org repos, due to ongoing legal action
  3. Development
    • MeeGo Community Builder taking shape
    • Clarifying differences between Qt and "MeeGo Touch" framework
    • Packaging Java applications for Maemo
  4. Community
    • Discussion around Texrat's list of "Maemo Missteps"
    • Why community testing of PR1.2 didn't repeat that done for PR1.1
    • MeeGo evangelism fund
  5. Devices
    • MeeGo-Harmattan (probably) has a better name coming to reduce confusion
    • Possible N900 successor leaked?
  6. Announcements
    • AutoDisconnect closes "idle" radio connections
    • Show WiFi signal strength in summary bar
    • AutoComplete Editor allows tidying up of suggested words

Front Page

Major, and avoidable, recent mistakes from Nokia

Randall Arnold, one of our Maemo Community Council representatives, has post a new blog article outlining his view on many of the missteps Nokia has made with Maemo recently. The release of MeeGo 1.0 was accompanied by some resolution to Maemo, not all of it with positive consequences. The long-awaited PR1.2 update was officially released at around the same time, which was a welcome relief, but excitement over the improvements it brought were tempered by less-than-genius developments.There's an unfortunate legacy of dropped balls in the Maemo closet, usually involving operating system evolutions so rough that they evoked more feelings of abandonment than joy. I'm not going to rehash all of the legacy, but will instead focus on this year. Dealing with issues such as Harmattan branding, lack of communication at a corporate level and the privacy-busting "MyNokia" SMS (amongst others), Randall clearly lays out some of most eye-watering mistakes which could've been avoided.

The community discussion on talk.maemo.org is interesting, and is summarised later in this issue.

Despite MeeGo, is Nokia getting more closed?

In addition to Randall's list above, a number of senior (that is, old ;-)), maemo.org community members are expressing similar thoughts about openness, Nokia and MeeGo. Amongst others, Stephen Gadsby, Ryan Abel, Attila Csipa, Faheem Pervez, Andrew Flegg, benny1967 and Reggie Suplido have all expressed some form of disappointment with how things seem to be going. Mostly, the feeling of general malaise can be focused around two points: a feeling of having the collective wisdom of the last 5 years of Maemo be ignored with the focus on MeeGo and the "big reveal" mentality for something as fundamental of the basis of the handset UI (bugs which included screenshots of the UI have now been locked down). Stephen expresses it as eloquently as ever: MeeGo is still too much in the shadows, running silent and deep. Nokia dropped Elephanta as too small a step and rushed Fremantle out to hold everyone over during the wait for Harmattan, but these repeated waits for the next big, double-secret thing have worn the community's goodwill thin in a growing number of spots. Stephen also points out that the activity of Nokians in the community has reduced over the last five years, after a peak in around 2008. Familiar names like ragnar, Igor Stoppa and Eero Tamminen are seen a lot less frequently these days. People are busy, this is understood - of course; however if things take (say) a week longer, but you carry the community with you, isn't that a price worth paying?

Two of the names above are your editors; but this growing feeling is being expressed increasingly frequently.