Talk:Objective:Release early, release often

Moved from

To be processed
Moved from 2010 Agenda

Openness, openness, openness

 * Developing maemo towards an operating system, not depending on proprietary components to be usable
 * Core libraries developed in the open by Nokia employees and maemo.org community contributors.
 * Non-Nokia specification writing and approval, worked on by Nokia employees and maemo.org community contributors; discussed on public mailing lists.
 * The ability to build a complete, flashable image by maemo.org community for beta testing of open components in development. (May be less necessary in an SSU-based world: TBC)
 * The ability to strip a maemo-based OS down to its base and build it up again differently (for example, KDE and no Hildon).
 * By 2010, installing completely different UIs should be achievable through the Application Manager.
 * There are different big topics here, worth spliting them to further discuss: open development by Nokia teams, collaboration between Nokia and community developers, ability to build and distribute maemo OS variants.--qgil 08:53, 2 June 2008 (UTC)

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)
 * ''The SDK releases need to go out of this task. Let's discuss this further in the 2010 Agenda. Even if that Fremantle SDK will be available before that year, it is simply not feasible to have it within the 100 Days. In any case the topic to be discussed is not the specific release of an SDK but the compromise to have weekly releases of whatever SDK is being developed.--qgil 19:49, 5 June 2008 (UTC)