Talk:Objective:Release early, release often - Revision history

imported_>generalantilles: Talk:Objective:Release soon and often moved to Talk:Objective:Release early, release often: More appropriate?

2008-12-30T00:21:16Z

Talk:Objective:Release soon and often moved to Talk:Objective:Release early, release often: More appropriate?

← Older revision	Revision as of 00:21, 30 December 2008
(No difference)

imported_>qgil: /* Weekly SDK releases */

2008-07-20T18:38:37Z

Weekly SDK releases

← Older revision		Revision as of 18:38, 20 July 2008
Line 18:		Line 18:
	=== Weekly SDK releases ===		=== 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. --[[User:xfade\|xfade]] 12:57, 4 June 2008 (UTC)		* 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. --[[User:xfade\|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~~.--[[User:qgil\|qgil]] 19:49, ~~5 June~~ 2008 (UTC)		:Covered in the list of tasks in the main page.--[[User:qgil\|qgil]] 18:38, 20 July 2008 (UTC)

imported_>qgil: /* Openness, openness, openness */

2008-07-20T18:37:49Z

Openness, openness, openness

← Older revision		Revision as of 18:37, 20 July 2008
Line 13:		Line 13:
	* The ability to strip a maemo-based OS down to its base and build it up again differently (for example, KDE and no Hildon).		* 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.--[[User:qgil\|qgil]] 18:37, 20 July 2008 (UTC)		: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.--[[User:qgil\|qgil]] 18:37, 20 July 2008 (UTC)
	** By 2010, installing completely different UIs should be achievable through the Application Manager.		*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.--[[User:qgil\|qgil]] 18:37, 20 July 2008 (UTC)		: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.--[[User:qgil\|qgil]] 18:37, 20 July 2008 (UTC)

imported_>qgil: /* Openness, openness, openness */

2008-07-20T18:37:27Z

Openness, openness, openness

← Older revision		Revision as of 18:37, 20 July 2008
Line 4:		Line 4:
	=== Openness, openness, openness ===		=== Openness, openness, openness ===
	* Developing maemo towards an operating system, not depending on proprietary components to be usable		* 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.--[[User:qgil\|qgil]] 18:37, 20 July 2008 (UTC)
	* Core libraries developed in the open by Nokia employees and maemo.org community contributors.		* Core libraries developed in the open by Nokia employees and maemo.org 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.--[[User:qgil\|qgil]] 18:37, 20 July 2008 (UTC)
	* Non-Nokia specification writing and approval, worked on by Nokia employees and maemo.org community contributors; discussed on public mailing lists.		* Non-Nokia specification writing and approval, worked on by Nokia employees and maemo.org community contributors; discussed on public mailing lists.
			:Can you explain this, please?--[[User:qgil\|qgil]] 18:37, 20 July 2008 (UTC)
	* 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 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)
			: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.--[[User:qgil\|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).		* 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.--[[User:qgil\|qgil]] 18:37, 20 July 2008 (UTC)
	** By 2010, installing completely different UIs should be achievable through the Application Manager.		** 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~~.--[[User:qgil\|qgil]] 08:53, ~~2 June~~ 2008 (UTC)''		: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.--[[User:qgil\|qgil]] 18:37, 20 July 2008 (UTC)

	=== Weekly SDK releases ===		=== 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. --[[User:xfade\|xfade]] 12:57, 4 June 2008 (UTC)		* 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. --[[User:xfade\|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.--[[User:qgil\|qgil]] 19:49, 5 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.--[[User:qgil\|qgil]] 19:49, 5 June 2008 (UTC)

imported_>qgil at 17:54, 20 July 2008

2008-07-20T17:54:59Z

← Older revision		Revision as of 17:54, 20 July 2008
Line 1:		Line 1:
	~~Moved from~~


	== To be processed ==		== To be processed ==
	Moved from [[2010 Agenda]]		Moved from [[2010 Agenda]]

imported_>qgil: Moved from 2010 Agenda

2008-07-20T17:54:26Z

Moved from 2010 Agenda

New page

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.--[[User:qgil|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. --[[User:xfade|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.--[[User:qgil|qgil]] 19:49, 5 June 2008 (UTC)