Task:Maemo Community distribution - Revision history

sjgadsby: /* Sort out a repository */ "exposure" -> "exposed"

2009-01-28T20:21:01Z

Sort out a repository: "exposure" -> "exposed"

← Older revision		Revision as of 20:21, 28 January 2009
Line 9:		Line 9:
	== Sort out a repository ==		== Sort out a repository ==

-	It would be preferable to simply distribute all packages in Extras, but this adds complexity and may simply be impossible to do cleanly, as these packages are likely to interfere with SSU and confuse users. Extras-devel is probably more appropriate, but that would force users wanting to use the community distribution to be ~~exposure~~ to unstable software. Not ideal. The simpler and cleaner option is to use a separate repository either on repository.maemo.org or a 3rd party repository somewhere else.	+	It would be preferable to simply distribute all packages in Extras, but this adds complexity and may simply be impossible to do cleanly, as these packages are likely to interfere with SSU and confuse users. Extras-devel is probably more appropriate, but that would force users wanting to use the community distribution to be exposed to unstable software. Not ideal. The simpler and cleaner option is to use a separate repository either on repository.maemo.org or a 3rd party repository somewhere else.

	We have 3 options for handling packages:		We have 3 options for handling packages:

sjgadsby: /* Recovery mode */ braking up run-on sentence

2009-01-28T20:19:35Z

Recovery mode: braking up run-on sentence

← Older revision		Revision as of 20:19, 28 January 2009
Line 80:		Line 80:
	==== Recovery mode ====		==== Recovery mode ====

-	The bootmenu should offer a number of recovery modes in addition to the existing USBNet recovery~~, the~~ recovery mode should offer the option to make backup images (to put on one of the cards or other mass storage ~~devices~~), restore backup images, and maybe offer some sort of framebuffer console for use with a hardware keyboard.	+	The bootmenu should offer a number of recovery modes in addition to the existing USBNet recovery. The recovery mode should offer the option to make backup images (to put on one of the cards or other mass storage device), restore backup images, and maybe offer some sort of framebuffer console for use with a hardware keyboard.

sjgadsby: /* Remove */ "bed" -> "be"

2009-01-28T20:17:30Z

Remove: "bed" -> "be"

← Older revision		Revision as of 20:17, 28 January 2009
Line 39:		Line 39:
	=== Remove ===		=== Remove ===

-	Useless and proprietary stuff to ~~bed~~ removed.	+	Useless and proprietary stuff to be removed.

	* '''gizmo-installer''': Remove proprietary advertising.		* '''gizmo-installer''': Remove proprietary advertising.

generalantilles: Resorting sections

2008-10-03T02:47:44Z

Resorting sections

← Older revision		Revision as of 02:47, 3 October 2008
Line 7:		Line 7:
	Provide a community distribution less encumbered by Nokia's corporate policies that is more flexible in its packaging, bundles community software, and modifies Nokia software and packaging with community patches.		Provide a community distribution less encumbered by Nokia's corporate policies that is more flexible in its packaging, bundles community software, and modifies Nokia software and packaging with community patches.

-	~~== Tasks ==~~	+	== Sort out a repository ==
-		+
-	~~To get to a workable distribution, we first need to consider a number of problems.~~	+
-		+
-	=== Sort out a repository ===	+

	It would be preferable to simply distribute all packages in Extras, but this adds complexity and may simply be impossible to do cleanly, as these packages are likely to interfere with SSU and confuse users. Extras-devel is probably more appropriate, but that would force users wanting to use the community distribution to be exposure to unstable software. Not ideal. The simpler and cleaner option is to use a separate repository either on repository.maemo.org or a 3rd party repository somewhere else.		It would be preferable to simply distribute all packages in Extras, but this adds complexity and may simply be impossible to do cleanly, as these packages are likely to interfere with SSU and confuse users. Extras-devel is probably more appropriate, but that would force users wanting to use the community distribution to be exposure to unstable software. Not ideal. The simpler and cleaner option is to use a separate repository either on repository.maemo.org or a 3rd party repository somewhere else.
Line 29:		Line 25:
	After [https://bugs.maemo.org/show_bug.cgi?id=3602 some discussion], it seems like option 3 is likely the most workable. Some scripting could be implemented to help reduce manual overhead, but this is likely a goal for later.		After [https://bugs.maemo.org/show_bug.cgi?id=3602 some discussion], it seems like option 3 is likely the most workable. Some scripting could be implemented to help reduce manual overhead, but this is likely a goal for later.

-	=== osso-software-version-community ===	+	== osso-software-version-community ==

	We need to provide a community version of osso-software-version that has a modified dependencies list that provides the community distribution. A couple considerations should be kept in mind, dependencies on proprietary junk will be removed (skype, gizmo, etc.), dependencies will be setup to allow easy installation of updated system libraries and 3rd-party patches (rotation, 48MHz, etc.), and unnecessary packages that shouldn't be part of the OS-proper will be moved to separate packages that can be uninstalled through application manager (bundled PDFs, images, movies, etc.).		We need to provide a community version of osso-software-version that has a modified dependencies list that provides the community distribution. A couple considerations should be kept in mind, dependencies on proprietary junk will be removed (skype, gizmo, etc.), dependencies will be setup to allow easy installation of updated system libraries and 3rd-party patches (rotation, 48MHz, etc.), and unnecessary packages that shouldn't be part of the OS-proper will be moved to separate packages that can be uninstalled through application manager (bundled PDFs, images, movies, etc.).

-	==== Add ====	+	=== Add ===

	Community enhancements that should be added to the default community distribution.		Community enhancements that should be added to the default community distribution.
Line 41:		Line 37:
	* '''e2fsprogs''': For handling ext2/3 filesystems.		* '''e2fsprogs''': For handling ext2/3 filesystems.

-	==== Remove ====	+	=== Remove ===

	Useless and proprietary stuff to bed removed.		Useless and proprietary stuff to bed removed.
Line 49:		Line 45:
	* '''skype-installer''': Remove proprietary advertising.		* '''skype-installer''': Remove proprietary advertising.

-	==== Modify ====	+	=== Modify ===

	Existing packages that should be enhanced.		Existing packages that should be enhanced.
Line 61:		Line 57:
	* '''preinstalled-videos''': Move to its own package.		* '''preinstalled-videos''': Move to its own package.

-	=== Patches, hacks, and modifications ===	+	== Patches, hacks, and modifications ==

	As a community distribution, we're not burdened by corporate policy and decision making, so we're free to include interesting and useful patches and hacks that Nokia cannot.		As a community distribution, we're not burdened by corporate policy and decision making, so we're free to include interesting and useful patches and hacks that Nokia cannot.

-	==== Application ~~Manager =~~===	+	=== Application manager ===

	A community distribution could serve as an easier way to include community branches of Nokia open source applications. The Application manager is a particularly good candidate for this, and could include patches to:		A community distribution could serve as an easier way to include community branches of Nokia open source applications. The Application manager is a particularly good candidate for this, and could include patches to:
Line 74:		Line 70:
	* Improve the category view.		* Improve the category view.

-	==== bootmenu ====	+	=== bootmenu ===

	Including a modified initfs both increases versatility (by allowing easier multiboot), and gives all users access to recovery modes for when things go wrong. A graphical bootmenu should be put together to increase user-friendliness.		Including a modified initfs both increases versatility (by allowing easier multiboot), and gives all users access to recovery modes for when things go wrong. A graphical bootmenu should be put together to increase user-friendliness.

-	===== Configuration =====	+	==== Configuration ====

	By default, a bundled initfs should boot immediately to the default partition, offering a short window to enter recovery mode, but no partition selection. Users can then add partitions either through a .item system on the console with a "flasher" script that commits the appropriate filesystem changes, or through an easy-to-use control panel.		By default, a bundled initfs should boot immediately to the default partition, offering a short window to enter recovery mode, but no partition selection. Users can then add partitions either through a .item system on the console with a "flasher" script that commits the appropriate filesystem changes, or through an easy-to-use control panel.

-	===== Recovery mode =====	+	==== Recovery mode ====

	The bootmenu should offer a number of recovery modes in addition to the existing USBNet recovery, the recovery mode should offer the option to make backup images (to put on one of the cards or other mass storage devices), restore backup images, and maybe offer some sort of framebuffer console for use with a hardware keyboard.		The bootmenu should offer a number of recovery modes in addition to the existing USBNet recovery, the recovery mode should offer the option to make backup images (to put on one of the cards or other mass storage devices), restore backup images, and maybe offer some sort of framebuffer console for use with a hardware keyboard.

generalantilles: /* Tasks */ Expanding

2008-10-03T02:46:27Z

Tasks: Expanding

← Older revision		Revision as of 02:46, 3 October 2008
Line 23:		Line 23:
	#* Pros: No legal issues, no additional effort for Nokia.		#* Pros: No legal issues, no additional effort for Nokia.
	#* Cons: Increases complexity, reduces control, and exposes users to updates before the community can sanitize them.		#* Cons: Increases complexity, reduces control, and exposes users to updates before the community can sanitize them.
-	# All free components from tableteer are copied to the community repository, and ~~tableteer is reorganized into free and~~ non-free ~~sections~~.	+	# All free components from tableteer are copied to the community repository, and an additional non-free section is added to tableteer.
	#* Pros: Increased control, no legal issues, cleaner.		#* Pros: Increased control, no legal issues, cleaner.
	#* Cons: More effort for Nokia.		#* Cons: More effort for Nokia.
		+
		+	After [https://bugs.maemo.org/show_bug.cgi?id=3602 some discussion], it seems like option 3 is likely the most workable. Some scripting could be implemented to help reduce manual overhead, but this is likely a goal for later.

	=== osso-software-version-community ===		=== osso-software-version-community ===
Line 58:		Line 60:
	* '''preinstalled-sounds''': Move to its own package.		* '''preinstalled-sounds''': Move to its own package.
	* '''preinstalled-videos''': Move to its own package.		* '''preinstalled-videos''': Move to its own package.
		+
		+	=== Patches, hacks, and modifications ===
		+
		+	As a community distribution, we're not burdened by corporate policy and decision making, so we're free to include interesting and useful patches and hacks that Nokia cannot.
		+
		+	==== Application Manager ====
		+
		+	A community distribution could serve as an easier way to include community branches of Nokia open source applications. The Application manager is a particularly good candidate for this, and could include patches to:
		+
		+	* Disable the legal warning.
		+	* Increase the amount of information Application manager provides.
		+	* Move some of the more useful features out of Red Pill and into the application proper.
		+	* Improve the category view.
		+
		+	==== bootmenu ====
		+
		+	Including a modified initfs both increases versatility (by allowing easier multiboot), and gives all users access to recovery modes for when things go wrong. A graphical bootmenu should be put together to increase user-friendliness.
		+
		+	===== Configuration =====
		+
		+	By default, a bundled initfs should boot immediately to the default partition, offering a short window to enter recovery mode, but no partition selection. Users can then add partitions either through a .item system on the console with a "flasher" script that commits the appropriate filesystem changes, or through an easy-to-use control panel.
		+
		+	===== Recovery mode =====
		+
		+	The bootmenu should offer a number of recovery modes in addition to the existing USBNet recovery, the recovery mode should offer the option to make backup images (to put on one of the cards or other mass storage devices), restore backup images, and maybe offer some sort of framebuffer console for use with a hardware keyboard.

generalantilles: Expand, correct

2008-10-02T04:45:53Z

Expand, correct

← Older revision		Revision as of 04:45, 2 October 2008
Line 5:		Line 5:
	== Goals ==		== Goals ==

-	Provide a community distribution less encumbered by Nokia's corporate policies that is more flexible in its packaging ~~of OS files~~, bundles community software, and modifies Nokia software and packaging with community patches.	+	Provide a community distribution less encumbered by Nokia's corporate policies that is more flexible in its packaging, bundles community software, and modifies Nokia software and packaging with community patches.

	== Tasks ==		== Tasks ==
Line 13:		Line 13:
	=== Sort out a repository ===		=== Sort out a repository ===

-	It would be preferable to simply distribute all packages in Extras, but this adds complexity and may simply be impossible to do cleanly. The ~~next~~ option is to use a separate repository either on repository.maemo.org or a 3rd party repository somewhere else.	+	It would be preferable to simply distribute all packages in Extras, but this adds complexity and may simply be impossible to do cleanly, as these packages are likely to interfere with SSU and confuse users. Extras-devel is probably more appropriate, but that would force users wanting to use the community distribution to be exposure to unstable software. Not ideal. The simpler and cleaner option is to use a separate repository either on repository.maemo.org or a 3rd party repository somewhere else.

	We have 3 options for handling packages:		We have 3 options for handling packages:
Line 20:		Line 20:
	#* Pros: Straightforward, easy, controllable.		#* Pros: Straightforward, easy, controllable.
	#* Cons: Legal gray area.		#* Cons: Legal gray area.
-	# All free components from tableteer are copied to the community repository, ~~and~~ non-free components are fetched from tableteer.	+	# All free components from tableteer are copied to the community repository, but non-free components are fetched from tableteer.
	#* Pros: No legal issues, no additional effort for Nokia.		#* Pros: No legal issues, no additional effort for Nokia.
	#* Cons: Increases complexity, reduces control, and exposes users to updates before the community can sanitize them.		#* Cons: Increases complexity, reduces control, and exposes users to updates before the community can sanitize them.
-	# All free components from tableteer are copied to the community repository, and ~~a non-free section of~~ tableteer is ~~created~~ and ~~used for 3rd~~-~~party proprietary packages (flash, etc)~~.	+	# All free components from tableteer are copied to the community repository, and tableteer is reorganized into free and non-free sections.
	#* Pros: Increased control, no legal issues, cleaner.		#* Pros: Increased control, no legal issues, cleaner.
	#* Cons: More effort for Nokia.		#* Cons: More effort for Nokia.
Line 29:		Line 29:
	=== osso-software-version-community ===		=== osso-software-version-community ===

-	We need to provide a community version of osso-software-version that has a modified dependencies list that provides the community distribution.	+	We need to provide a community version of osso-software-version that has a modified dependencies list that provides the community distribution. A couple considerations should be kept in mind, dependencies on proprietary junk will be removed (skype, gizmo, etc.), dependencies will be setup to allow easy installation of updated system libraries and 3rd-party patches (rotation, 48MHz, etc.), and unnecessary packages that shouldn't be part of the OS-proper will be moved to separate packages that can be uninstalled through application manager (bundled PDFs, images, movies, etc.).

	==== Add ====		==== Add ====
		+
		+	Community enhancements that should be added to the default community distribution.

	* '''advanced-backlight''': To replace sound and brightness by default.		* '''advanced-backlight''': To replace sound and brightness by default.
Line 38:		Line 40:

	==== Remove ====		==== Remove ====
		+
		+	Useless and proprietary stuff to bed removed.

	* '''gizmo-installer''': Remove proprietary advertising.		* '''gizmo-installer''': Remove proprietary advertising.
Line 44:		Line 48:

	==== Modify ====		==== Modify ====
		+
		+	Existing packages that should be enhanced.

	* '''hildon-status-bar-display''': Remove from statusbar by default in favor of Advanced Backlight.		* '''hildon-status-bar-display''': Remove from statusbar by default in favor of Advanced Backlight.

generalantilles: Expand and correct

2008-10-01T22:48:32Z

Expand and correct

← Older revision		Revision as of 22:48, 1 October 2008
Line 1:		Line 1:
	{{task\|proposed}}		{{task\|proposed}}

-	A community-provided distribution of Maemo.	+	A community-provided distribution of Maemo can offer the community more freedom, better options, greater customizability, and better stability than the Nokia-provided distribution. This task outlines the process for putting together a community distribution of Maemo.

	== Goals ==		== Goals ==

-	Provide a community distribution less encumbered by Nokia's corporate policies, more flexible in its packaging of OS files, ~~and bundling~~ community software ~~versions~~.	+	Provide a community distribution less encumbered by Nokia's corporate policies that is more flexible in its packaging of OS files, bundles community software, and modifies Nokia software and packaging with community patches.

	== Tasks ==		== Tasks ==

generalantilles: /* Sort out a repository */ Fixing list

2008-10-01T22:45:24Z

Sort out a repository: Fixing list

← Older revision		Revision as of 22:45, 1 October 2008
Line 18:		Line 18:

	# Everything is copied wholesale from tableteer to the community repository.		# Everything is copied wholesale from tableteer to the community repository.
-	** Pros: Straightforward, easy, controllable.	+	#* Pros: Straightforward, easy, controllable.
-	** Cons: Legal gray area.	+	#* Cons: Legal gray area.
	# All free components from tableteer are copied to the community repository, and non-free components are fetched from tableteer.		# All free components from tableteer are copied to the community repository, and non-free components are fetched from tableteer.
-	** Pros: No legal issues, no additional effort for Nokia.	+	#* Pros: No legal issues, no additional effort for Nokia.
-	** Cons: Increases complexity, reduces control, and exposes users to updates before the community can sanitize them.	+	#* Cons: Increases complexity, reduces control, and exposes users to updates before the community can sanitize them.
	# All free components from tableteer are copied to the community repository, and a non-free section of tableteer is created and used for 3rd-party proprietary packages (flash, etc).		# All free components from tableteer are copied to the community repository, and a non-free section of tableteer is created and used for 3rd-party proprietary packages (flash, etc).
-	** Pros: Increased control, no legal issues, cleaner.	+	#* Pros: Increased control, no legal issues, cleaner.
-	** Cons: More effort for Nokia.	+	#* Cons: More effort for Nokia.

	=== osso-software-version-community ===		=== osso-software-version-community ===

generalantilles: /* Sort out a repository */

2008-10-01T22:45:02Z

Sort out a repository

← Older revision		Revision as of 22:45, 1 October 2008
Line 14:		Line 14:

	It would be preferable to simply distribute all packages in Extras, but this adds complexity and may simply be impossible to do cleanly. The next option is to use a separate repository either on repository.maemo.org or a 3rd party repository somewhere else.		It would be preferable to simply distribute all packages in Extras, but this adds complexity and may simply be impossible to do cleanly. The next option is to use a separate repository either on repository.maemo.org or a 3rd party repository somewhere else.
		+
		+	We have 3 options for handling packages:
		+
		+	# Everything is copied wholesale from tableteer to the community repository.
		+	** Pros: Straightforward, easy, controllable.
		+	** Cons: Legal gray area.
		+	# All free components from tableteer are copied to the community repository, and non-free components are fetched from tableteer.
		+	** Pros: No legal issues, no additional effort for Nokia.
		+	** Cons: Increases complexity, reduces control, and exposes users to updates before the community can sanitize them.
		+	# All free components from tableteer are copied to the community repository, and a non-free section of tableteer is created and used for 3rd-party proprietary packages (flash, etc).
		+	** Pros: Increased control, no legal issues, cleaner.
		+	** Cons: More effort for Nokia.

	=== osso-software-version-community ===		=== osso-software-version-community ===

generalantilles: /* osso-software-version-community */

2008-10-01T22:24:56Z

osso-software-version-community

← Older revision		Revision as of 22:24, 1 October 2008
Line 21:		Line 21:
	==== Add ====		==== Add ====

-	* advanced-backlight: To replace sound and brightness by default.	+	* '''advanced-backlight''': To replace sound and brightness by default.
-	* bootmenu: For multiboot and USB recovery.	+	* '''bootmenu''': For multiboot and USB recovery.
-	* e2fsprogs: For handling ext2/3 filesystems.	+	* '''e2fsprogs''': For handling ext2/3 filesystems.

	==== Remove ====		==== Remove ====

-	* gizmo-installer: Remove proprietary advertising.	+	* '''gizmo-installer''': Remove proprietary advertising.
-	* rhapsody-installer: Remove proprietary advertising.	+	* '''rhapsody-installer''': Remove proprietary advertising.
-	* skype-installer: Remove proprietary advertising.	+	* '''skype-installer''': Remove proprietary advertising.

	==== Modify ====		==== Modify ====

-	* hildon-status-bar-display: Remove from statusbar by default in favor of Advanced Backlight.	+	* '''hildon-status-bar-display''': Remove from statusbar by default in favor of Advanced Backlight.
-	* osso-statusbar-presence: Non-mandatory .desktop file	+	* '''osso-statusbar-presence''': Non-mandatory .desktop file
-	* osso-statusbar-sound: Remove from statusbar by default in favor of Advanced Backlight.	+	* '''osso-statusbar-sound''': Remove from statusbar by default in favor of Advanced Backlight.
-	* preinstalled-documentation-rx34/rx44: Move to its own package.	+	* '''preinstalled-documentation-rx34/rx44''': Move to its own package.
-	* preinstalled-images: Move to its own package.	+	* '''preinstalled-images''': Move to its own package.
-	* preinstalled-sounds: Move to its own package.	+	* '''preinstalled-sounds''': Move to its own package.
-	* preinstalled-videos: Move to its own package.	+	* '''preinstalled-videos''': Move to its own package.