Task:2010 Agenda

Revision as of 20:25, 31 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.

Please login before making any changes. Thank you.
Please keep things on-topic.
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.
Discussion of the 2010 Agenda should be held in the discussion page.
If you think your suggestion should be done in the next 100 days, please post it in the Maemo.org 100 Days Action Plan.

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.

As suggested here and here, set up an IdeaStorm for maemo to cover:
- Software ideas larger in scale than Bugzilla enhancement requests, in particular, acting as a focusing agent for Bugzilla enhancement requests (e.g. IdeaStorm brainstorming session -> multiple Bugzilla enhancement requests).
- Hardware requests outside the scope of Bugzilla.

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. Newcomers 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)
- Clearer UI guidelines for 3rd party developers.
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 emulator on PC. Comes with most default applications of NIT and is based on a newer QEmu (at least one that supports Virtualization Extensions).
Better modern native languages support - like Vala and D. && how to build a hello world app in C++/Vala in 10 minute (no more!)

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

Software requests are really out-of-scope and not relevant to this brainstorming session. Please see the main article.

Revision as of 20:24, 31 May 2008 (edit) generalantilles (Talk \| contribs) (→Ship high level building blocks) ← Older edit		Revision as of 20:25, 31 May 2008 (edit) (undo) generalantilles (Talk \| contribs) (→End-user software wishlist) Newer edit →
Line 55:		Line 55:
	\|}		\|}

-	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)~~. Please see the main article.	+	Software requests are really '''out-of-scope''' and ''not relevant'' to this brainstorming session. Please see the main article.