Open development/Why the closed packages

(new request)
(Cleanup, markup)
Line 1: Line 1:
-
== General reasons ==
 
Open source is the licensing model preferred by Nokia in the development of Maemo. There are some reasons to have exceptions, though:
Open source is the licensing model preferred by Nokia in the development of Maemo. There are some reasons to have exceptions, though:
-
- '''Brand''': Nokia wants to keep a strong brand and identity avoiding any risks of dilution.
+
* '''Brand''': Nokia wants to keep a strong brand and identity avoiding any risks of dilution.
 +
* '''Differentiation''': Nokia wants to gain competitive advantage in certain areas by keeping the related software closed.
 +
* '''Legacy''': Nokia keeps some components minimally maintained - the work of opening them has an unclear outcome.
 +
* '''IPR & licensing issues''': Nokia avoids serious risks brought by patents, copyrights or complicated licensing situations.
 +
* '''Security''': Nokia avoids safety risks and liabilities that could be caused by freeing access to certain hardware components.
 +
* '''Third party''': Nokia does not own the code and therefore does not decide on the license.
-
- '''Differentiation''': Nokia wants to gain competitive advantage in certain areas by keeping the related software closed.
+
== Specific reasons for packages ==
-
- '''Legacy''': Nokia keeps some components minimally maintained - the work of opening them has an unclear outcome.
 
-
 
-
- '''IPR & licensing issues''': Nokia avoids serious risks brought by patents, copyrights or complicated licensing situations.
 
-
 
-
- '''Security''': Nokia avoids safety risks and liabilities that could be caused by freeing access to certain hardware components.
 
-
 
-
- '''Third party''': Nokia does not own the code and therefore does not decide on the license.
 
-
 
-
== Specific reasons for packages ==
 
* '''[https://bugs.maemo.org/show_bug.cgi?id=1832 tablet-browser-ui]''': At the beginning there was a proprietary browser. In Maemo 4.0 the Mozilla based browser came, with an open engine (MicroB) but still a closed UI provided by tablet-browser. The main reason was the default rule to have the Maemo applications UI closed for differentiation. The context in mobile browsing has changed significantly and now there are better reasons to offer also an open browser UI. This is the plan for Fremantle.
* '''[https://bugs.maemo.org/show_bug.cgi?id=1832 tablet-browser-ui]''': At the beginning there was a proprietary browser. In Maemo 4.0 the Mozilla based browser came, with an open engine (MicroB) but still a closed UI provided by tablet-browser. The main reason was the default rule to have the Maemo applications UI closed for differentiation. The context in mobile browsing has changed significantly and now there are better reasons to offer also an open browser UI. This is the plan for Fremantle.
* '''[[Questions_for_Nokia#Bookmark_manager_engine|Bookmark manager]]''': Closed because of legacy and the default rule to have the UI application layer closed. However, the licensing of this component is being reviewed and it could be opened in Fremantle. Filing an enhancement request and seeing the interest and potential use cases would be something the community could do. Deadline: Fremantle beta SDK release.
* '''[[Questions_for_Nokia#Bookmark_manager_engine|Bookmark manager]]''': Closed because of legacy and the default rule to have the UI application layer closed. However, the licensing of this component is being reviewed and it could be opened in Fremantle. Filing an enhancement request and seeing the interest and potential use cases would be something the community could do. Deadline: Fremantle beta SDK release.
Line 86: Line 81:
== Opened ==
== Opened ==
 +
* [https://bugs.maemo.org/show_bug.cgi?id=3635 Alarm framework] is open source, but apparently the sources are lost/missing as explained in the bug.
* [https://bugs.maemo.org/show_bug.cgi?id=3635 Alarm framework] is open source, but apparently the sources are lost/missing as explained in the bug.

Revision as of 07:56, 21 April 2009

Open source is the licensing model preferred by Nokia in the development of Maemo. There are some reasons to have exceptions, though:

  • Brand: Nokia wants to keep a strong brand and identity avoiding any risks of dilution.
  • Differentiation: Nokia wants to gain competitive advantage in certain areas by keeping the related software closed.
  • Legacy: Nokia keeps some components minimally maintained - the work of opening them has an unclear outcome.
  • IPR & licensing issues: Nokia avoids serious risks brought by patents, copyrights or complicated licensing situations.
  • Security: Nokia avoids safety risks and liabilities that could be caused by freeing access to certain hardware components.
  • Third party: Nokia does not own the code and therefore does not decide on the license.

Specific reasons for packages

  • tablet-browser-ui: At the beginning there was a proprietary browser. In Maemo 4.0 the Mozilla based browser came, with an open engine (MicroB) but still a closed UI provided by tablet-browser. The main reason was the default rule to have the Maemo applications UI closed for differentiation. The context in mobile browsing has changed significantly and now there are better reasons to offer also an open browser UI. This is the plan for Fremantle.
  • Bookmark manager: Closed because of legacy and the default rule to have the UI application layer closed. However, the licensing of this component is being reviewed and it could be opened in Fremantle. Filing an enhancement request and seeing the interest and potential use cases would be something the community could do. Deadline: Fremantle beta SDK release.
  • Media player: Currently closed because of the default criteria of UI differentiation. In progress, though. The engine is being opened in Fremantle, in the form of a Media Application Framework also available for third parties. The UI is open for discussion, as you can see in the Comment #5 of the enhancement request. For instance, it would count a lot seeing a will to converge efforts and contribution from the many third party media player projects.
  • Connection applet: Legacy. The applet itself is not much but it unveils all the Connectivity middleware which is also closed. The whole Connectivity framework is having major changes in Fremantle and Harmattan, and the resould could be a much open framework altogether (applet included). Too soon to tell.
  • Display applet: Legacy. Opening it could be considered if really needed. From the comments in the bug report it looks like the need is not that big though?
  • Location framework: Differentiation. Nokia is investing heavily in location software and services, that are planned to be implemented in Maemo during Fremantle and Harmattan.
  • libmetalayer: Legacy. Will be substituted by open source upstream Meta Tracker. See this comment about the possibility to open it still.
  • osso-dsp-modules: DSP component provided by Texas Instruments. Note that the DSP packages provided by Nokia are open source: osso-dsp-loader, osso-dsp-headers. If you are interested in open source DSP development then DSP Gateway (developed by Nokia) might get your attention. However, the introduction of PulseAudio in Fremantle gives an opportunity to platform developers to forget about the DSP completely.
  • dsme: This component covered many areas including power management, which is considered a differentiation area by Nokia. The component has been redesigned and the sensitive functionality has moved to mce, allowing to distribute dsme (soon) with an open license together with related tools and plugins: bootstate, dsmetool, waitfordsme, libdsme.so, libhwwd.so, liblifeguard.so, libprocesswd.so, libstartup.so and libstate.so. Then libtemperature.so will be replaced by another component consisting of several dsme open source plugins. Finally, libcalmodule.so will be dropped.
  • bme - Battery Management Entity: Security. A misuse of the could lead to serious battery damages that could result in liabilities for Nokia. hald-addon-bme is a related package, also closed.
  • mce - Mode Control Entity: Initially closed for differentiation because of its impact in battery life, an area where Nokia strives to excel. Nowadays the differentiation aspect is lighter but legacy plays a role as well.

Not in the device but also relevant:

  • Flasher: Utility to flash the device from a Linux computer. Currently closed for legacy, considering the move to an open project to ease and encourage the development of versions not supported by Nokia e.g. Mac OS X and PowerPC.

Waiting list

If you want to know the specific reasons for a package to be closed please list it below and the Maemo team will answer as time permits. You can also add comments to a certain package to drive attention/priority to it.

Requested at Bug 1584 including comments:

  • File Manager
  • activate_panel
  • bt-cal
  • cal-tool
  • fb-chaimage
  • text2screen
  • wlan-cal
  • wlan-fw-update
  • retu-time
  • show_image
  • battest
  • dspctl
  • the script linuxrc
  • libbmeic.so
  • libcal.so
  • libppu.so
  • libactivitymonitor.so
  • libinactivity-blank.so
  • libperipheral.so
  • BME
  • libi18n-locale-resolver0

These packages are included in the nokia-binaries metapackage offered with the Maemo SDK:

  • hildon-task-navigator-bookmarks
  • osso-bookmark-menu->osso-bookmark-engine->osso-bookmark-user
  • osso-browser-translations-dev
  • libaccounts-dev ->libaccounts0
  • libaccounts-doc
  • libosso-abook-dev ->libosso-abook
  • libosso-rtcom-accounts-dev ->libosso-rtcom-accounts0
  • libosso-rtcom-accounts-doc
  • osso-addressbook ->libcontact-importexport
  • osso-contact-plugin-dev ->osso-contact-plugin
  • osso-mission-control ->libplayback-1-0 ->libimlogger0
  • libconbtui0 ->
  • liblocation-dev ->liblocation0
  • libossoproductinfo0 ->libdsme0
  • libgpsbt-dev ->libgpsbt
  • libgpsmgr-dev ->libgpsmgr
  • libogs1.2-dev ->libogs1.2-1 ->libosso-filemanager-interface
  • id3search -> libmetalayer0 ->libgisds-gtk-dialog0 ->libgisds0
  • osso-global-search
  • osso-applet-certman ->certs ->osso-clock
  • libosso-certman-dev ->libosso-certman1
  • osso-help-ui

Other Requests:

  • mnotify (Webmail Notifier) - Open source could allow it to support other webmail providers, and fix minor issues like bug 2066 as it is apparantly low priority for Nokia.

Opened

  • Alarm framework is open source, but apparently the sources are lost/missing as explained in the bug.