(→Timeline (Phase I): Milestone 5.5)
|Line 2:||Line 2:|
''freesmartphone.org)''Openmoko is on freesmartphone.org. FSO the [[Om 2009]]. For more information see http://www.freesmartphone.org, http://docs.freesmartphone.org, and http://trac.freesmartphone.org.
Revision as of 23:19, 20 July 2009
English • العربية • Български • Česky • Dansk • Deutsch • Esperanto • Eesti • Español • فارسی • Suomi • Français • עברית • Magyar • Italiano • 한국어 • Nederlands • Norsk (bokmål) • Polski • Português • Română • Русский • Svenska • Slovenčina • Українська • 中文(中国大陆) • 中文(台灣) • Euskara • Català
|Key pages on:|
FSO (freesmartphone.org) is a project to create a standardized service layer (middleware) for Linux-based phones. It was funded by Openmoko Inc. from January 2008 until March 2009. Focus is on stable highlevel services that you can access from whatever language or UI that supports dbus. The FSO middleware has been integrated into most of the current distributions including SHR, Om 2009, neovento, Debian and Gentoo. For more information see http://www.freesmartphone.org, http://docs.freesmartphone.org, and http://trac.freesmartphone.org.
- Question: Is this an Openmoko-only thing?
- Answer: No. It's going to be available for all kinds of mobile hardware running Linux, i.e. OpenEZX, HTC, Glosfiish, etc.
- Question: Is this a part of the current images yet?
- Answer: Yes. It comes with SHR and Openmoko 2009.x testing images.
- Question: What's the current status?
- Answer: See right below or hop over to http://trac.freesmartphone.org .
- Question: How do I work the Zhone (FSO demo app) UI?
- Answer: FSO UI Tutorial
- Question: What is the easiest way to build it?
- Answer: See Building_FSO for more information. The feeds are now at http://downloads.freesmartphone.org.
- Phase I is about getting the APIs right.
- Phase II is about getting the right APIs fast.
Timeline (Phase I)
- 2009-07-31: milestone 6
- 2009-07-10: milestone 5.5 achieved
- 2009-02-02: milestone 5 achieved
- 2008-11-11: milestone 4 achieved
- 2008-09-10: milestone 3 achieved
- 2008-07-01: milestone 2 achieved
- 2008-06-01: milestone 1 achieved
Timeline (Phase II)
... to be defined ...
- Give people the infrastructure to create solid and exciting software products based on the Openmoko platform
- Support competing UIs while collaborating on developing services
- Encourage framework users (e.g. application developers) to also contribute to the framework
- Make it simple
- Concentrate on core services
- Be programming language agnostic
- Be UI toolkit agnostic
- Try to reuse existing technologies as much as possible, but not at the cost of a bad API
How to achieve that technically
- Choose D-Bus as the collaboration line. Below dbus, we can work together. Above dbus, we can differentiate
- Expose features through dbus APIs implemented by UI-agnostic and language-agnostic services (daemons)
- Optimize for Openmoko devices, but support multiple architectures and purposes through plugin interfaces and suitable hardware abstraction mechanisms
- By not being afraid of reinventing the wheel for a wheelbarrow if all the existing wheels are made for sports cars
- Frameworks exist for conceptual integrity
- Ten ways to make more humane open source software
- FreeSmartPhone.org Wiki
What this is NOT about
This initiative does not cover low level services such as
- Bootloader, Kernel, or System Init.
This initiative does not cover high level services such as
- X-Window-System, Window Manager, UI Toolkits,
- Application Launchers, Applications, or Fancy UIs.
Please see the description at http://www.freesmartphone.org/index.php/Architecture
Known API Consumers
- mdbus -- a dbus introspection and interaction utility,
- cli-framework -- a python dbus command line interface.
- mickeyterm -- a MUXer-aware minimal terminal emulator.
- Example Scripts that work over dbus
How to debug
- log in via ssh
- killall python
- edit /etc/frameworkd.conf and add to the frameworkd section:
- log_level = DEBUG
- log_to = file
- log_destination = /somewhere/where/you/have/space (preferably SD or NFS, etc.)
- Read our documented frameworkd.conf configuration file to learn about the other options.
- relaunch frameworkd (/etc/init.d/frameworkd stop; /etc/init.d/frameworkd start)
- log in via ssh (yes, again)
- export DISPLAY=:0.0
- run your favourite client (zhone, cli-framework, ...)
Attach the logs to the tickets, please.
The role of Python
Where we write new code, we will use Python to implement the dbus services. The reason for that being the rapid prototyping nature of Python and the emphasis on the D-Bus APIs. Using Python, the turnaround times to experiment with APIs are incredibly faster than for using a compiled language such as C or C++.
Once the APIs have been used by application programmers, we can start profiling and possibly reimplement some of the services with daemons written in Vala, if necessary. We might as well succeed in improving performance by using Pyrex/Cython/Ctypes to keep the benefits of Python.
Team & Roadmap
- Michael 'Mickey' Lauer (team leader) -- Openmoko freelancer, working in Frankfurt/Main, Germany.
- Jan 'Shoragan' Luebbe -- Openmoko student, working part-time in Brunswick, Germany.
- Daniel 'Alphaone' Willmann -- Openmoko student, working part-time in Brunswick, Germany.
- Stefan Schmidt -- Openmoko student, working part-time in Brunswick, Germany.
The milestone releases are combined Openmoko Framework and Zhone releases. Remember: A feature that isn't visible, working, and tested in our framework testing application (Zhone) does not exist. Until Framework 1.0.0 (early 2009), we will not use any versioning in components. Afterwards, individual components may see individual releases.
Note: The milestones and tasks moved over to our issue tracker.