Task:2010 Agenda

2008-05-30T00:19:24Z

70.23.151.36:

Help defining the '''maemo.org 2010 Agenda'''. This is taken to mean the vision the community has for the state of maemo in 2010.

{| style="background-color:#f4f09c; border: 1px silver solid; padding: 10px;"
| [[Image:50px-Nuvola apps important yellow.svg.png|50px|left]]
|
* '''Hardware requests''' are entirely ''out-of-scope'' and will be removed by community members trying to keep this page focused and on-topic.
* '''Software requests''' which would be trivial for a third party to provide—or are already on the roadmap—are ''out-of-scope'' and will be removed by community members trying to keep this page focused and on-topic.
|}

== maemo development process ==
=== Openness, openness, openness ===
* 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.

== maemo developer resources ==
* Better localization guidelines for new and existing Developers.
* Development Framework. ???
* Documentation System. (Help system???)
* Better GPS resources. (GeoClue???)
* Development Tools and Utilities for Linux, OS X and Windows.
* Better modern native languages support - like Vala and D. && how to build a hello world app in C++/Vala in 10 minute (no more!)

=== Ship high level building blocks ===
* Think of media server, VoIP, contact lists, camera, GPS localization. Currently developers only have the low level API's, while mostly they just want a widget that displays the mentioned data and listen to user interaction signal or device signals. This also makes these functionalities look the same in all applications using them

== End-user software wishlist ==
Software requests are really ''out-of-scope'' (or able to be provided by third party developers without maemo.org involvement); however, they are recorded here so they ''do not get duplicated'':
* A PIM system that can be tied into by developers, to provide PC synchronization etc.
** A equivalent to telepathy for calendar and contact list: A well integrated framework.
* Telepathy:
** Better video call support
* Global sync-software
* Office suite. (???)
* Unionfs support built into the kernel (So users don't have to flash initfs and boot from SD, or make symlinks gone wild, just to install a few extra apps)
* a2dp
* Better support for right-to-left languages, such as Arabic, and Hebrew.

Task:2010 Agenda

2008-05-30T00:14:53Z

70.23.151.36:

Help defining the '''maemo.org 2010 Agenda'''. This is taken to mean the vision the community has for the state of maemo in 2010.

{| style="background-color:#f4f09c; border: 1px silver solid; padding: 10px;"
| [[Image:50px-Nuvola apps important yellow.svg.png|50px|left]]
|
* '''Hardware requests''' are entirely ''out-of-scope'' and will be removed by community members trying to keep this page focused and on-topic.
* '''Software requests''' which would be trivial for a third party to provide—or are already on the roadmap—are ''out-of-scope'' and will be removed by community members trying to keep this page focused and on-topic.
|}

== maemo development process ==
=== Openness, openness, openness ===
* 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.

== maemo developer resources ==
* Better localization guidelines for new and existing Developers.
* Development Framework. ???
* Documentation System. (Help system???)
* Better GPS resources. (GeoClue???)
* Development Tools and Utilities for Linux, OS X and Windows.
* Better modern native languages support - like Vala and D. && how to build a hello world app in C++/Vala in 10 minute (no more!)

=== Ship high level building blocks ===
* Think of media server, VoIP, contact lists, camera, GPS localization. Currently developers only have the low level API's, while mostly they just want a widget that displays the mentioned data and listen to user interaction signal or device signals. This also makes these functionalities look the same in all applications using them

== End-user software wishlist ==
Software requests are really ''out-of-scope'' (or able to be provided by third party developers without maemo.org involvement); however, they are recorded here so they ''do not get duplicated'':
* A PIM system that can be tied into by developers, to provide PC synchronization etc.
** A equivalent to telepathy for calendar and contact list: A well integrated framework.
* Telepathy:
** Better video call support
* Global sync-software
* Office suite. (???)
* Unionfs built into the kernel (So users don't have to flash initfs and boot from SD, or make symlinks gone wild, just to install a few extra apps)

Maemo Wiki Mirror - User contributions [en]

Task:2010 Agenda

Task:2010 Agenda