Maemo Wiki Mirror - User contributions [en]

Task:100Days

2008-05-30T07:36:54Z

212.116.129.162:

The '''maemo.org 100 Days Action Plan'''

{| style="background-color:#f4f09c; border: 1px silver solid; padding: 10px;"
| [[Image:50px-Nuvola apps important yellow.svg.png|50px|left]]
|
* '''Please login''' before making any changes. '''Thank you'''.
* Please keep things '''on-topic'''.
* Avoid asking for end-user applications unless there's a '''good reason''' why they need to be tied into the underlying OS.
* Don't put things which aren't feasible in '''3 months'''. For long term suggestions, consider adding them at [[2010_Agenda|maemo.org 2010]].
|}

==Get the server and bandwidth infrastructure up to speed==
*Mirror the repository.maemo.org to ensure good uptime.
*Mirror tablets-dev.nokia.com to ensure good uptime.
*Improve the hardware and bandwidth availability behind *.maemo.org to ensure quick response—maemo.org is too slow!

== [http://www.internettablettalk.com Internet Tablet Talk] Syndication ==
* Provide an automatic way to re-list applications at the Internet Tablet Talk Software Section (itTSS).
* Each application (version) that is re-listed at Internet Tablet Talk, starts a new thread in the forums so end-users get notified of new apps as well as provide a way to give feedback to the developers. Developers themselves can also join in the discussion. This hope to help better the quality of applications.
* Provide a way for developers to easily add a bug at the application's Garage page for confirmed bugs reported in the discussion thread.

== Update developer libraries ==
* gcc-4.x, glib, powervr, it's important to give developers much more time to play with newer tools than short before a major upgrade takes place (of course with disclaimer that nothing is guaranteed to be shipped in a certain way)
*add IPv6 support!
**''Already in Diablo, not relevant to ''maemo.org'' [[User:generalantilles|generalantilles]] 23:36, 29 May 2008 (UTC)''

== Focus developers and users on the right channels ==
* Today we have too many channels (ITT, maemo.org...). Maybe have some more focus like: maemo.org for developers and ITT for end users and something that link they so software releases can be announced automatically on ITT and users from ITT can easily post bugs on garage bugzilla for example.
** ''Perhaps develop a plan, but this isn't specific enough to achieve in 3 months, IMHO --[[User:jaffa|jaffa]] 22:10, 29 May 2008 (UTC)''

* Develop a recommended usage policy for garage.maemo projects, taking into account turning off GForge modules not needed (perhaps defaulting in a subset rather than all, for new projects). Further discussions on whether non-core bugs should be in central Bugzilla and garage trackers merged/closed.

* Close misnamed (and now misused) maemo2midgard-discuss mailing list and create maemo-web alongside existing mailing lists for overall discussions about maemo.org sites.

== Increase Openness ==
* Identify all closed components in ITOS at each layer:
** Initfs/direct hardware access
** Firmware used by kernel modules
** Low-level system daemons
** User-space applications
* For each package:
** Outline purpose in a dedicated wiki page
** Describe rationale for it being closed source
*** ''Will need some form of mediawiki template for such pages --[[User:jaffa|jaffa]] 22:26, 29 May 2008 (UTC)''
* Document in wiki the process for petitioning for opening of a component, or its specifiation.
* Document in wiki the process for ensuring any new closed packages get a wiki page containing this information.

== Beautification and format/style unification of maemo.org ==
=== Beautification ===
* Maemo.org can benefit from some face lifting - right now on 1280x1024 (this resolution seems to be very common to developers) only half of the real screen estate is used. With some loose block positioning both 800x480 and bigger resolutions can be supported. Maybe even specialized tablet finger-friendly look for those preferring it.
** ''Resolution seems fine to me at the moment, and it works fine on the tablet without requiring the extra effort of maintaining a separate tablet style. Perhaps reducing the min-width to not require horizontal scrolling with the tablet browser windowed would be useful, though. [[User:generalantilles|generalantilles]] 21:02, 29 May 2008 (UTC)''
*** ''There won't be any extra effort on the resolution maintainment - this can be done with minor CSS modifications. As for the separate tablet style - this really requires extra effort and if done should be entirely optional. [[User:bundyo|bundyo]] 21:26, 29 May 2008 (UTC)''
* More relevant information displayed on front page, preferably customizable blocks like Netvibes and iGoogle. Since the content is gzipped, that won't be too harming to the traffic. Blocks can be optionally auto updated for those that like to keep their browser pages open (and if Prizm is ported - even in the tray). For instance new bugs section with voting on the fly will boost bugzilla usage.

=== Unification of format and style ===
* Format and style need to be unified across as much of the site as possible (excluding things like Garage and Bugzilla). Take, for instance [http://maemo.org/news/planet-maemo/ Planet] and [http://maemo.org/news/ News], two pages that should be very similar, if not the same. Perhaps take News's style and format and apply it to Planet (add the contributor's avatar to the upper right of each article? Much like [http://slashdot.org slashdot] does with their article category images.), as the News style seems to off a cleaner look that better utilizes the available space.
* For the outliers like Garage and Bugzilla, at least the style should largely be unified with the main site—using the same fonts, same colors, etc.

== Improve Documentation ==
* Provide a better guide / ruleset for developers
** Define types of applications that will be useful on the Internet Tablet
** Stress the fact that the Internet Tablet is not a PC and apps should be created/ported with the tablet form in mind. Don't just do a direct port of an existing app. Aim for quality and Internet Tablet usablity.
** Focused discussion/guide on User Interface so apps will have a consistent look as well as provide a similar way to interface with the user
== Growing the community through better information for newcomers ==
* Currently, maemo.org structure is less than favourable for newcomers to get familiar on what maemo software and maemo.org is. If we want to grow the community we need to provide better introduction to the community and the software assets. Hence, the content of the Intro section should be refreshed and restructured.
* To create more clarity, I would suggest to remove the "Tips for tablet users" because the link to OS2008 web page is already on the home page. I would furthermore move the "Roadmap" page to the "development" section. The gallery page should be moved to "downloads" and someone should clean up the gallery to contain only relevant content. The presentation section is to some degree outdated and should also be cleaned up. The "White Paper" page should be really give a quick overview of what maemo software is. The "trademark" and "licenses" pages should be moved to "Terms of Use". And the "Links" should be moved to "Development".
* After all these changes, our intro section should include "Who is the maemo community?, What is the maemo platform? The maemo software architecture, How does maemo.org work? Quick start guide to develop on maemo software, and presentations"

Task:2010 Agenda

2008-05-30T07:36:05Z

212.116.129.162:

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]]
|
* '''Please login''' before making any changes. '''Thank you'''.
* '''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.
--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.

== 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 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

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 Agenda 2010 answers on how we provide the above mentioned characteristics to ourselves, then we can succeed to bring open source innovation to millions of people across the globe and change their lives.