Talk:Objective:Release early, release often

[edit] To be processed

Moved from 2010 Agenda

[edit] Openness, openness, openness

  • Developing maemo towards an operating system, not depending on proprietary components to be usable
The thing is, in order to be "operating" we need some of those proprietary components, at least for the hardware configurations produced by Nokia.--qgil 18:37, 20 July 2008 (UTC)
  • Core libraries developed in the open by Nokia employees and community contributors.
To be more precise: 1) Upstream components are developed upstream and integrated by Nokia - community contributions preferably upstream. 2) Some upstream packages modified by Nokia - community contributions still preferably upstream, unless they are patches against the Nokia specific code (we want to minimize the list of these modified packages). c) Open source components developed by Nokia, community provides feedback - contribution policy to be defined.--qgil 18:37, 20 July 2008 (UTC)
  • Non-Nokia specification writing and approval, worked on by Nokia employees and community contributors; discussed on public mailing lists.
Can you explain this, please?--qgil 18:37, 20 July 2008 (UTC)
  • The ability to build a complete, flashable image by community for beta testing of open components in development. (May be less necessary in an SSU-based world: TBC)
Two levels in the approach: 1) Nokia provides a complete and flashable image and equivalent SDK for beta testing. 2) The community can build their own images - the latter goes beyond technical aspects if we include Nokia/3rd party proprietary software.--qgil 18:37, 20 July 2008 (UTC)
  • The ability to strip a maemo-based OS down to its base and build it up again differently (for example, KDE and no Hildon).
Related with the previous one: one thing is to be able to do this technically, the other thing is to be able to make a flashable image including proprietary pieces and redistribute them.--qgil 18:37, 20 July 2008 (UTC)
  • By 2010, installing completely different UIs should be achievable through the Application Manager.
The idea looks good, but we need to check the architecture to see what this means in reality and what changes need to be made.--qgil 18:37, 20 July 2008 (UTC)

[edit] Weekly SDK releases

  • Weekly releases of updated SDK packages. SSU for SDK. So developers can start to develop for the new platform right away and not have to wait until the new SDK/OS version is released. This 'beta' SDK releases will help developers with application porting and compatibility checks. So they can release their software the day a new OS is released. --xfade 12:57, 4 June 2008 (UTC)
Covered in the list of tasks in the main page.--qgil 18:38, 20 July 2008 (UTC)