8 August 2011

  1. Front Page
  2. Applications
  3. Development
  4. Community
  5. Devices
  6. Maemo in the Wild
  7. Announcements
  8. Download issue

Other Issues

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

In this edition...

  1. Front Page
    • Linux Foundation will not permit apps.meego.com
    • Should, or could, "ForMeego.org" expand to solve many of the management problems of MeeGo?
    • Restructure MeeGo - thoughts on getting some direction
  2. Applications
    • Next-generation gPodder user interface mockups
    • Nintendo 64 emulator running on Nokia N950
  3. Development
    • OBS down for fourth weekend in a row, with no explanation
    • Open source replacement for Maemo 5 clock application under development
    • Token details for Harmattan Aegis security
  4. Community
    • QA dashboard for MeeGo
    • Why the Maemo Community Council aren't the people to come up with the plan to "save" maemo.org
    • Brute-force cloning of Maemo 5 repositories shows misunderstanding of Nokia situation
    • ...and 3 more
  5. Devices
    • N9 launch in Sweden: September 23
  6. In the Wild
    • Nokia switches device naming scheme once again
  7. Announcements
    • Cordia Tab open source device running MeeGo & Cordia's port of Maemo's Hildon-Desktop
    • Minifile - minimal file browser for Harmattan
    • FlowPlayer, cover-flow style music player
    • ...and 6 more

Front Page

Linux Foundation will not permit apps.meego.com

MeeGo is a project of The Linux Foundation, a non-profit organisation which "promotes, protects and standardizes Linux by providing unified resources and services needed for open source to successfully compete with closed platforms". It provides the hosting and infrastructure for meego.com, as well as owning the overall governance structure and trademarks of the project.

apps.meego.com was to be the equivalent of maemo.org's Extras - a place for open source code to be available for multiple MeeGo devices, with a web-based frontend (and on-device client). For the last couple of weeks, the apps.meego.com team (that is, David Greaves and Niels Breet) have been working with the Community Office (Dawn Foster), the Technical Steering Group (Imad Sousou) and Linux Foundation representatives concerned over potential legal risks and issues with hosting apps.meego.com. Due to a lack of movement, David has publicised the issue:

The Linux Foundation have told us in private conversations that they will not permit apps.meego.com to be served from the MeeGo.com infrastructure hosted by them. They do not have the resource at this time to provide a statement giving their reasons. We can not assess what other services may be impacted in the future.

An alternative, apps.formeego.org has been given appropriate blessing and work is continuing on the apps.meego.com infrastructure - but with the intent of hosting the web-based frontend on apps.formeego.org instead. Nokia, as a large vendor with a MeeGo(ish) device on its way out, is partly sponsoring the requisite hardware, and is hoping that other parties interested in seeing a vibrant open source application ecosystem on MeeGo will also do the same. The service which would be building the source code, and hosting both that and the resulting binaries, the Community OBS, is currently believed not to be at risk - although David has noted the Linux Foundation's communications on the matter have been somewhat lacking.

Should, or could, "ForMeego.org" expand to solve many of the management problems of MeeGo?

As noted above, the Linux Foundation "own" MeeGo. However, neither they - nor the TSG - have been visible in trying to publicly work out a solution. Architecture decisions, quality assurance processes and many other facets of the project are also problematic to see transparency in. This led to a discussion on IRC about potentially expanding "ForMeeGo.org" to encompass all the aims of the N9x0 Community Edition, to be a reference vendor and be a "downstream" of MeeGo Core.

This would effectively isolate all the problems to one or more upstream projects, allowing hardware manufacturers to realise the true potential of MeeGo, that of a differentiatable ecosystem-in-a-box. Manufacturers would be able to take "ForMeeGo.org"'s deliverables, its ecosystem of open source applications and build a unique user interface on top of it. A few choice quotes:

Maybe we could set up a ForMeeGo organisation & council ;-)

the only place the project really works is on the factory floor, management seems missing and invisible

I'd rather see a restructure than a fork. But yeah, things like not having an active TSG, invisible working groups etc, doesn't give a good impression atm.

A restructure/fix of The MeeGo Project requires the participation of those leading the project.

Carsten Munk said, on Twitter, in response to this discussion "you know management is causing bad effects when forking out of frustration seems acceptable". Hopefully, the project leadership will put in place mechanisms to solve these problems (or the appearance of them) within the existing project.


Restructure MeeGo - thoughts on getting some direction

Following on from the above discussion, David Greaves posted some draft blog posts he'd had kicking around for a while: I've just published a series of articles that reflect my thoughts on improving MeeGo and setting some directon. [...] Whilst the MeeGo Project has the potential to be incredibly beneficial to the Linux device market it can and must do more to fulfill that aspiration. MeeGo is in danger of becoming "Yet Another Linux Distro". As with any venture; in order to succeed MeeGo must first identify and focus on satisfying its customers. Identification is not too hard : organisations involved in building devices based on MeeGo.