Task:2010 Agenda

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

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.
 * There are different big topics here, worth spliting them to further discuss: open development by Nokia teams, collaboration between Nokia and community developers, ability to build and distribute maemo OS variants.--qgil 08:53, 2 June 2008 (UTC)

IdeaStorm

 * 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.
 * Isn't this more of a 100 Days action?--qgil 08:54, 2 June 2008 (UTC)
 * I think it's quite a big task, if you want it to be user-friendly, and with a voting system that provides useful feedback -- FelipeC 12:43, 2 June 2008 (UTC)

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. Newcomers need the experience.
 * It is sensible to introduce a point about community Localization in the 2010 Agenda: what is expected, what would be ideal. The discussion and specific planning would be better in a specific page, though.--qgil 09:05, 2 June 2008 (UTC)


 * 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.
 * Introducing newcomers to the platform is definitely a core case, since we expect lots of them coming. And not with a Linux and open source background necessarely. Again, what is expected and ideal, then the details to be worked out in separate pages.--qgil 09:05, 2 June 2008 (UTC)


 * Development Framework. ???
 * 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!)
 * Let's take what is relevant of these points for the maemo.org community and online infrastructure. For instance "Better feedback on testing of packages" and "make simple system for ideas to be tried".--qgil 09:05, 2 June 2008 (UTC)

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
 * This is out of scope in the 2010 Agenda call. API and developer offering in general will improve and we might organize similar a similar brainstorming for that.--qgil 09:05, 2 June 2008 (UTC)

Becoming the best-in-class community for innovation on mobile devices running Linux
What does it take to become the de-facto community to innovate open source for Linux-based devices? Obviously, we are not alone when it comes to development on Linux on mobile devices. Development communities for Android platform and LIMO platform are likely to grow in the next 2 years. So, how do we ensure that we keep on getting the greatest brains to our community? Only through continuous growth and fresh community members from around the globe we can ensure that we get new ideas and new challenges from which we all can learn. Only through continuous learning we can create better software and better user experiences.

So again, what does it take to be a major force in open source for Linux-based mobile devices?
 * a vision, a strategy, and mid-term objectives for the community
 * clear and transparent rules of engagement and recognition of contributions in the community
 * a virtual meeting place i.e. maemo.org but also community events for people to meet in person
 * a powerful core operating system incorporating the latest versions of open source upstream projects
 * best-in-class open devices for rapid prototyping on latest hardware
 * easy to use tools to create, prototype, and rewrite applications on top of the SDKs
 * tools for contributors to software "below" the SDK to prototype and publish enhancements
 * strong ties with the other open source community projects
 * deep understanding of consumer behavior, preferences, and consumer trends in different cultures
 * a mechanism on how to deliver software from open source innovation to millions of consumers
 * based on a truly international point of view in design of device and software platform as well as community construction, internet communication is global rather than restricted in local region.

But at the end of the day, it's all about people, relationships and networks. The community needs to be able to maintain and extend the network between the people in an efficient, fair, and transparent way.

Only when we have in our maemo.org agenda 2010 answers on how maemo.org can contribute to these above mentioned requirements, then we can succeed to bring open source innovation to millions of people across the globe and change their lives.--peterschneider 10:03, 30 May 2008 (UTC)


 * Something like this is a good start to define the vision and core objectives of this 2010 Agenda. This is where the strategic minds in the community should think big and deep to set the scope and goals they wish for maemo.org.--qgil 09:49, 2 June 2008 (UTC)

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