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. 16 September 2013
  2. 9 September 2013
  3. 26 August 2013
  4. 5 August 2013
  5. 29 July 2013
  6. 22 July 2013
  7. 15 July 2013
  8. 1 July 2013
  9. 24 June 2013
  10. 17 June 2013
  11. 10 June 2013
  12. 3 June 2013
  13. 27 May 2013
  14. 20 May 2013
  15. 6 May 2013
  16. 29 April 2013
  17. 22 April 2013
  18. 8 April 2013
  19. 25 March 2013
  20. 18 March 2013
  21. 11 March 2013
  22. 4 March 2013
  23. 18 February 2013
  24. 4 February 2013
  25. 28 January 2013
  26. 21 January 2013
  27. 14 January 2013
  28. 7 January 2013
  29. 17 December 2012
  30. 3 December 2012
  31. 26 November 2012
  32. 12 November 2012
  33. 29 October 2012
  34. 22 October 2012
  35. 15 October 2012
  36. 8 October 2012
  37. 1 October 2012
  38. 24 September 2012
  39. 17 September 2012
  40. 10 September 2012
  41. 3 September 2012
  42. 27 August 2012
  43. 20 August 2012
  44. 13 August 2012
  45. 6 August 2012
  46. 30 July 2012
  47. 23 July 2012
  48. 16 July 2012
  49. 9 July 2012
  50. 2 July 2012
  51. 25 June 2012
  52. 18 June 2012
  53. 11 June 2012
  54. 4 June 2012
  55. 28 May 2012
  56. 21 May 2012
  57. 14 May 2012
  58. 7 May 2012
  59. 30 April 2012
  60. 23 April 2012
  61. 16 April 2012
  62. 9 April 2012
  63. 2 April 2012
  64. 26 March 2012
  65. 19 March 2012
  66. 12 March 2012
  67. 5 March 2012
  68. 27 February 2012
  69. 20 February 2012
  70. 13 February 2012
  71. 6 February 2012
  72. 30 January 2012
  73. 23 January 2012
  74. 16 January 2012
  75. 9 January 2012
  76. 2 January 2012
  77. 19 December 2011
  78. 12 December 2011
  79. 5 December 2011
  80. 28 November 2011
  81. 21 November 2011
  82. 14 November 2011
  83. 7 November 2011
  84. 31 October 2011
  85. 24 October 2011
  86. 17 October 2011
  87. 10 October 2011
  88. 3 October 2011
  89. 26 September 2011
  90. 19 September 2011
  91. 12 September 2011
  92. 5 September 2011
  93. 29 August 2011
  94. 22 August 2011
  95. 15 August 2011
  96. 1 August 2011
  97. 25 July 2011
  98. 18 July 2011
  99. 11 July 2011
  100. 4 July 2011
  101. 27 June 2011
  102. 20 June 2011
  103. 13 June 2011
  104. 6 June 2011
  105. 30 May 2011
  106. 23 May 2011
  107. 16 May 2011
  108. 9 May 2011
  109. 2 May 2011
  110. 25 April 2011
  111. 18 April 2011
  112. 11 April 2011
  113. 4 April 2011
  114. 28 March 2011
  115. 21 March 2011
  116. 14 March 2011
  117. 7 March 2011
  118. 28 February 2011
  119. 21 February 2011
  120. 14 February 2011
  121. 7 February 2011
  122. 31 January 2011
  123. 24 January 2011
  124. 17 January 2011
  125. 10 January 2011
  126. 3 January 2011
  127. 20 December 2010
  128. 13 December 2010
  129. 6 December 2010
  130. 29 November 2010
  131. 22 November 2010
  132. 15 November 2010
  133. 8 November 2010
  134. 1 November 2010
  135. 25 October 2010
  136. 18 October 2010
  137. 11 October 2010
  138. 4 October 2010
  139. 27 September 2010
  140. 20 September 2010
  141. 13 September 2010
  142. 6 September 2010
  143. 30 August 2010
  144. 23 August 2010
  145. 16 August 2010
  146. 9 August 2010
  147. 2 August 2010
  148. 26 July 2010
  149. 19 July 2010
  150. 12 July 2010
  151. 5 July 2010
  152. 28 June 2010
  153. 21 June 2010
  154. 14 June 2010
  155. 7 June 2010
  156. 31 May 2010
  157. 24 May 2010
  158. 17 May 2010
  159. 10 May 2010
  160. 3 May 2010
  161. 26 April 2010
  162. 19 April 2010
  163. 12 April 2010
  164. 5 April 2010
  165. 29 March 2010
  166. 22 March 2010
  167. 15 March 2010
  168. 8 March 2010
  169. 1 March 2010
  170. 22 February 2010
  171. 15 February 2010
  172. 8 February 2010
  173. 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.