Task:Maemo Community distribution

m (→Sort out a repository: Fixing list)
(Expand and correct)
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 ==

Revision as of 22:48, 1 October 2008

Image:Ambox_notice.png
 This task is in the list of maemo.org development proposals, please help planning and getting it ready for a sprint. Put a note on the talk page if you're interested in helping work on this task.
Please see the talk page for discussion.

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.

Contents

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.

Tasks

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. 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:

  1. Everything is copied wholesale from tableteer to the community repository.
    • Pros: Straightforward, easy, controllable.
    • Cons: Legal gray area.
  2. 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.
  3. 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

We need to provide a community version of osso-software-version that has a modified dependencies list that provides the community distribution.

Add

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

Remove

  • gizmo-installer: Remove proprietary advertising.
  • rhapsody-installer: Remove proprietary advertising.
  • skype-installer: Remove proprietary advertising.

Modify

  • hildon-status-bar-display: Remove from statusbar by default in favor of Advanced Backlight.
  • osso-statusbar-presence: Non-mandatory .desktop file
  • osso-statusbar-sound: Remove from statusbar by default in favor of Advanced Backlight.
  • preinstalled-documentation-rx34/rx44: Move to its own package.
  • preinstalled-images: Move to its own package.
  • preinstalled-sounds: Move to its own package.
  • preinstalled-videos: Move to its own package.
Retrieved from "http://wiki.maemo.org/Task:Maemo_Community_distribution"