Task:2010 Agenda
jmueller82 (Talk | contribs) m (→maemo developer resources) |
jmueller82 (Talk | contribs) (→Maemo developer resources) |
||
| Line 19: | Line 19: | ||
== Maemo developer resources == | == Maemo developer resources == | ||
* Better localization guidelines for new and existing Developers. | * Better localization guidelines for new and existing Developers. | ||
| + | --keep focused on the core of the project | ||
| + | --stay unified and work out the details later | ||
| + | --focus every module in a step by step instead of a free for all | ||
| + | --delegate. Newbs need the experience | ||
* Development Framework. ??? | * Development Framework. ??? | ||
* Documentation System. (Help system???) | * Documentation System. (Help system???) | ||
| + | --getting started is way to difficult and will detour many great minds | ||
| + | --outsource to the blogger types in the group | ||
| + | --voice record "dictate to the typers" | ||
| + | --video and slide w/audio help for many | ||
| + | --cut out the opinions where are the real facts (make an easy to find location) | ||
* Better GPS resources. (GeoClue???) | * Better GPS resources. (GeoClue???) | ||
* Development Tools and Utilities for Linux, OS X and Windows. | * Development Tools and Utilities for Linux, OS X and Windows. | ||
| + | --GUI development package (reduce learning curve) | ||
| + | --Better feedback on testing of packages | ||
| + | --make simple system for ideas to be tried | ||
* Better modern native languages support - like Vala and D. && how to build a hello world app in C++/Vala in 10 minute (no more!) | * 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 === | === 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 | * 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 | ||
Revision as of 04:27, 30 May 2008
Help defining the maemo.org 2010 Agenda. This is taken to mean the vision the community has for the state of maemo in 2010.
|
Contents |
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.
--keep focused on the core of the project
--stay unified and work out the details later
--focus every module in a step by step instead of a free for all
--delegate. Newbs need the experience
- Development Framework. ???
- Documentation System. (Help system???)
--getting started is way to difficult and will detour many great minds
--outsource to the blogger types in the group
--voice record "dictate to the typers"
--video and slide w/audio help for many
--cut out the opinions where are the real facts (make an easy to find location)
- Better GPS resources. (GeoClue???)
- Development Tools and Utilities for Linux, OS X and Windows.
--GUI development package (reduce learning curve)
--Better feedback on testing of packages
--make simple system for ideas to be tried
- 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 and not relevant to this brainstorming session (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. (???) see discussion
- 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.