14 February 2011

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

Other Issues

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

Community

Devices »« Development

Quim Gil thoughts

Quim Gil is Nokia's MeeGo Community Manager, and has been involved in Maemo for years. In a post on talk.maemo.org, he describes his thoughts so far: I have to say that I'm waiting for more news to come in relation to Qt and MeeGo, from Nokia, from my colleagues working in these teams and from other Qt and MeeGo stakeholders. Mobile World Congress hasn't even started and the dust from yesterday's announcements is far from settled.

I understand how someone reading yesterday's headlines and trying to catch up with all the heated feedback and rumors can get to fast conclusions about Nokia and its role around Qt and MeeGo. Even to fast conclusions about Qt and MeeGo themselves. With the news only coming out on Friday, it's obvious that Nokia as an organisation needs to digest the changes before people and projects understand the full impact.

Read more (talk.maemo.org)

What now for MeeGo? Some proposals

Fallout from Nokia's recent announcements is still on its way down, but David Greaves is looking towards the future: So Nokia has dramatically reduced commitment to MeeGo and has cited, amongst other things, MeeGo's inability to deliver a focussed baseline with sufficient speed. I happen to agree with this failure (and given Nokia was a significant part of MeeGo's management I don't think there's a blame issue - more a how do we fix it issue) David goes on to list a focus on providing a base for vendors, and a platform for developers, as realistic deliverables for the MeeGo project; something your editor happens to agree with. MeeGo can target vendors as an open provider of an "ecosystem in a box". This is effectively what Elop wanted, but couldn't wait for MeeGo to deliver. Providing vendors with a ready base, app stores and a slew of developers is the best way forward in your editor's opinion.

Read more (lists.meego.com)
Devices »« Development