Maemo Wiki Mirror - User contributions [en]

Talk:Task:Getting Nokia involved in bugs.maemo.org

2008-11-11T16:45:50Z

24.164.22.34: /* Draft implementation */

== Best practices for everybody ==

There is one assumption that not always becomes true: Bugzilla users know how to deal with bug tracking. This might apply both to users (poor reports, wrong severity/priority, reopening of wontfixes/invalids just because, bad behavior...) and maintainers (harsh resolving, lack of explanations, little knowledge of the possibilities of the tool, bad behavior too...). We see this in most free software projects and bugs.maemo.org is not exempt of this risk.

In fact, having @nokia guys around makes things a bit more difficult sometimes: certain users take the chance to establish a personal war against "Nokia", others might simply ignore the complexity behind a simple bug and a simple Nokia developer commenting on that bug. On the other hand, Nokia employees are busy enough with an internal bug tracker that counts in their internal process, and communicating to the outside makes things more complex: because of wearing the Nokia shirt you can be quoted anywhere and because some (actually many) bug resolutions are related to confidential information.

Also, Maemo gets many newcomers not familiar with free software development practices, both in the user and developer side, which makes the own concept of a public bug tracker strange for some.

For all these reasons it would be good to have a concise 'for dummies' guide for users and maintainers that everybody could refer to when learning how to get involved.--[[User:qgil|qgil]] 11:54, 24 July 2008 (UTC)

== Success (and really wrong) stories ==

Putting the pressure on single developers doesn't help actually. The reality of the average Maemo SW developer is: busy with Nokia internal processes (including automated and human testing) and reporting to a project manager (directly) and a release manager (indirectly) that most probably don't follow the activity in bugs.maemo.org. Considering this setting, the public Bugzilla brings more work in exchange of an unclear outcome. This is why good triaging by the maemo.org bugmasters and the Bugsquad is good, because they help triage what really matters.

However, the real step is to prove that good usage of bugs.maemo.org results in less work and better quality, not more work resulting in worse performance/quality. I'm not saying that this is *the* position of Nokia. What I'm saying is that Nokia processes have been evolving during years and just recently they had to consider something like a public Bugzilla. Coming from an open source background the importance of public bug trackers is clear, and doesn't need further explanation. But on the other hand, device programs and non-free software development programs can also show good success rates with test and error management process done internally, getting user feedback from surveys, controlled tests, etc.. The Maemo SW is in between, affected by device & closed source software development and also by pure open source development.

There are many things that are being changed internally to adapt to this situation, but there is one task where the Maemo community can help: bring the success stories happening in Maemo and elsewhere with a similar setting (e.g. public bugtrackers efficiently handled by companies shipping software preinstalled in devices). Equally useful would be clear stories of things that went wrong or could have gone clearly better if Nokia would have made a better use of bugs.maemo.org.

Being specific and objective, showing statistics and trends, helps a lot convincing not one or two developers but whole teams and management structures.--[[User:qgil|qgil]] 12:08, 24 July 2008 (UTC)

== Improvements in the weekly reports ==

The weekly Bug Jar is just fantastic. It is also a very visual proof about the community capacity to get organized and help. Even if unrelated, it came more or less at the same time than the maemo.org bugmasters joined the team. Both things have cause a very good impact in the internal bug management people and process. Some ideas for improvement in the weekly reports:
* Website bugs out of the Jars. The Website bugs are reasonably well tracked and managed mostly at a community/public level. There are many and they add too much data to the Jars. Data like that is almost pure noise for the average Nokia guy working in Maemo Software.
* Visualizing the progress: now we get a picture every week, but we rely on our own memory to judge whether there is progress or not, small progress or big. Ideally there would be statistics and graphs showing the progress. A very good discovery and proofpoint would be to find out that before bugmasters and jars the lines were pointing trend A, and after that the lines point to much cooler trend B. This might sound stupid but those lines might convince more people inside and outside Nokia, more users and developers and managers, than the most rationalized arguments.
* Bug Jars in this wiki? Forget about this if it's too much extra work, but documenting the reports in the wiki would be useful. It could even be the default interface and then send updates to maemo.org lists and ITt.
--[[User:qgil|qgil]] 07:57, 25 July 2008 (UTC)
: Karsten is also working on porting some weekly summary/overview to Maemo Bugzilla, see [https://bugs.maemo.org/show_bug.cgi?id=3553]. This is on the map for [[100Days/Sprint4]]. Stephen is CC'ed and I naively hope that some code (or at least ideas) can be shared. --[[User:andre|andre]] 18:08, 12 August 2008 (UTC)

== Better organization of products and components ==

If you look inside components like System Software, System Management or Multimedia you will see that there is a bit of inconsistency aka mess in the components. This is not only poor usability for the bug reporters. It also makes life harder for Nokia developers to track where are the reports that affect to their work. Specially if you consider that developers work on teams, and many times teams are mapped to certain products and components. It is easier for Team A to know that they have to follow Product A and forget safely about the rest. This is now clear for e.g. Connectivity or Development Platform, which happen to be products that are reasonably well maintained. System Software would be the opposite case.--[[User:qgil|qgil]] 10:09, 30 July 2008 (UTC)
: I'm going to work on improving this in [[100Days/Sprint4]], see [https://bugs.maemo.org/show_bug.cgi?id=3562]. --[[User:andre|andre]] 18:14, 12 August 2008 (UTC)

: The organization is mostly my fault*, I didn't particularly like the organization used in the internal bug tracker and was trying to aim for something which more closely mapped to what users would see when they used their device. In the n800, that's basically: 1. Browser, 2. Communications, and 3. Desktop. After those come distinct blobs: A. Connectivity, B. Multimedia and C. Games. Then comes a section which is harder to divide. I chose to map things that appeared in/near control panel as "System management" and everything else into "System software". Note that [http://mozilla.org mozilla.org] is currently experiencing a similar growing pain, the current [https://bugzilla.mozilla.org bugzilla.mozilla.org] organization is built around functionality that only the engineers who work on an area understand. This means that if you're an end user, or even an engineer from a different area you have a terrible time trying to find the right place to file a bug. * Except for Internet Tablet Video Converter which someone added on behalf of a different Nokia group. --[[User:timeless|timeless]] 18:51, 3 September 2008 (UTC)

:: Hi, I have been thinking and my conclusion is that we need a structure mapping platform areas and components down to the packages level. This would serve a much better purpose for generating reports and finding out the bugs in a way the Maemo teams at Nokia can process and handle better.--[[User:qgil|qgil]] 06:50, 22 October 2008 (UTC)
:::Package level? That'd be (for example) having components for dsme, bme and mce? Or breaking down "Browser" into microb-eal, microb-engine, tablet-browser-ui, tablet-browser-dialogs, tablet-browser-widgets, tablet-browser-controls, etc, etc? That sounds (to me, and assuming I'm actually reading "packages level" correctly) like hell for triagers and a good way to scare off reporters. —[[User:generalantilles|GeneralAntilles]] 07:01, 22 October 2008 (UTC)
::::Ok, ok, don't take the package level literally always. I agree they make less sense at the application level, where most end users will probably land. My main concern is not the package level but the fact that bugzilla products reflect better platform structure and (as a happy coincidence) Maemo SW team structure. For instance, now "Applications" list in fact "Rest of applications", since Browser or Media Player are elsewhere. At the same time, "Multimedia" is handling both application and platorm components. The Maemo SW team has a clear divide between applications and platform. Users probably will be happier too if they would have an easy way to access the whole application level without having to mess with more obscure platform components. By doing this we can go to deeper levels in the platform since now there is a single component for e.g. "Multimedia Framework" when actually it would be good to know whether a bug is in GStreamer, PulseAudio or some Nokia closed component (for instance, upstream developers could track better what is going on there). No need to go down to the full list of GStreamer related packages, agreed. Let me start drafting a structure... Don't look at the components so much, I have concentrated on the products in this first round. --[[User:qgil|qgil]] 06:08, 23 October 2008 (UTC)

:Overall I like the reorg. Renaming System management to Settings & Maintenance (which is mostly what you did) makes a lot of sense, I'm sorry I hadn't come up w/ that name in my reorg. X-Discontinued is an interesting hack. I'd sooner move it out of Official Applications. At mozilla.org, we have a Graveyard classification for this. That python is listed under discontinued is odd.... splitting some of System software into Desktop platform seems reasonable. DUN=(bt) Dial up networking; ICD=Internet Connectivity Daemon. Splitting Core out may make the Maemo Software Core team happy, but I'm not sure that Internationalization belongs in Desktop platform. I guess from an ownership perspective it does. From someone who usually doesn't pay attention to how Maemo Software (this is an organization in Nokia) works it doesn't. --[[User:timeless|timeless]] 19:14, 10 November 2008 (UTC)

=== Draft structure ===

The 3 levels respond to Classification, Product and Component. What is today "Maemo Software" would be split in Official Applications and Official Platform.

* Official Applications (respond to a structure evident from a user point of view)
** Browser
*** Bookmarks
** Chat & Internet Call ''(was: Communication/IM/Chat and SIP etc - I'd prefer to have Chat and Internet Call in the same category, otherwise I'm running into problems here e.g. with Presence bugs - it's too tied.'' - '''TODO''': rtcomm? what's the status? Never understood that...)
*** Chat
*** General ''(was: Communication/General (9 bugs))''
*** Internet Call ''(was: Communication/Internet Call)''
*** Presence ''(was: Communication/Presence)''
*** SIP ''(was: Communication/SIP)''
*** XMPP ''(was: Communication/XMPP)''
** Contacts ''(was: Communication/Contacts)''
** E-mail ''(was: Communication/Email)'' (Note: Webmail notifier: Under Home applets)
** Games
*** Blocks
*** Chess
*** Mahjong
*** Marbles
** Home applets
*** Battery
*** Clock
*** Connection
*** Contacts
*** Display
*** Getting started
*** Internet radio
*** Internet search
*** RSS feed reader
*** Webmail Notifier ''(was: Applications/Webmail Notifier, 8 bugs)''
** Images & Camera ''(fits better to also have Cam bugs somewhere)''
*** Camera ''(was: Multimedia/Camera)''
*** Image viewer ''(was: Applications/Image viewer)''
** Map ''(see bug 2566)'' '''SETNEWQA''': map-bugs@maemo.bugs
** Media Player ''(was: Multimedia/Media Player)''
** RSS feed reader ''(was: Applications/RSS feed reader)''
** Settings & Maintenance
*** Application manager ''(was: System management/Application manager)''
*** Backup/Restore ''(was: System management/Backup/Restore)''
*** Connection manager UI ''(was: System management/Connection manager)''
*** Control panel ''(was: System management/Control panel)''
*** Startup wizard ''(was: System management/Startup Wizard)''
*** Software updater '''TODO: Add''', see e.g. bugs 3750, 3764. '''SETNEWQA''': software-update-bugs@maemo.bugs
*** Teach handwriting ''(was: System management/Teach handwriting)''
** Utilities
*** File manager ''(was: System management/File manager)''
*** Calculator
*** Clock
*** Help
*** Internet Tablet Video Converter
*** Notes
*** PDF reader
*** Sketch
*** Search
*** X Terminal ''(was: System software/X Terminal)''
* Official Platform (respond to an architectural structure)
** Desktop platform
*** cairo '''TODO: Add''' '''SETNEWQA''': cairo-bugs@maemo.bugs
*** clutter '''TODO: Add''' '''SETNEWQA''': clutter-bugs@maemo.bugs
*** File System UI ''(was: System software/File System UI)''
*** Finger keyboard ''(was: System software/Finger keyboard)''
*** Fonts ''(was: System software/Fonts)''
*** gconf ''(was: System software/gconf)''
*** general ''(was: System software/general)'' '''SETNEWQA''': desktop-platform-general@maemo.bugs ('''TODO''': kill hafqa{at}maemo.org ML)
*** glib ''(was: System software/glib)''
*** gnome-vfs ''(was: System software/gnome-vfs)''
*** gtk ''(was: System software/gtk)''
*** hildon-libs ''(was: System software/hildon-libs)''
*** hildon-thumbnail ''(was: System software/hildon-thumbnail)''
*** Home ''(was: Desktop/Home)''
*** Icons ''(was: Desktop/Icons)''
*** Input method framework ''(was: System software/Input method framework)''
*** Internationalization '''(TODO: move windows cp1252, POSIX data, gettext, localeconv here)''' '''SETNEWQA''': i18n-bugs@maemo.bugs
*** libosso ''(was: System software/libosso)''
*** pango '''TODO: Add''' '''SETNEWQA''': pango-bugs@maemo.bugs
*** sapwood ''(was: System software/sapwood)''
*** startup-shutdown ''(was: System software/startup-shutdown)''
*** Task navigator ''(was: Desktop/Task navigator)''
*** Themes ''(was: Desktop/Themes and System software/hildon-theme)'' '''TODO:''' Merge with System software/hildon-theme
*** Virtual keyboard ''(was: System software/Virtual keyboard)''
*** window-manager ''(was: System software/window-manager)''
** Connectivity
*** Bluetooth
*** DUN ('''???''' - I miss understanding...)
*** ICD ('''???''' - I miss understanding...)
*** Networking
*** Operator Setup Wizard ''(was: System management/Operator Setup Wizard)''
*** WiFi
*** WiMAX '''TODO: Add''' '''SETNEWQA''': wimax-bugs@maemo.bugs
** Core
*** Busybox ''(was: System software/Busybox)''
*** Kernel ''(was: System software/Kernel)''
*** X Server ''(was: System software/X Server)''
** Data '''TODO: Add''' (Versions: >=Fremantle)
*** Meta Tracker '''TODO: Add''' '''SETNEWQA''': metatracker-bugs@maemo.bugs
*** SQLite '''TODO: Add''' '''SETNEWQA''': sqlite-bugs@maemo.bugs
** Development platform
*** Documentation
*** general '''SETNEWQA''': dev-platform-general-bugs@maemo.bugs
*** installer
*** rootstrap
*** SDK
*** Tools
** Flasher
** Location ''(was: Connectivity/Location Framework)''
** Multimedia ('''TODO''': split into more subcomponents)
*** DSP ('''TODO:''' Create and clean up; Though DSP gateway = Kernel) '''SETNEWQA''': dsp-bugs@maemo.bugs
*** Gstreamer ('''TODO:''' Create and clean up) '''SETNEWQA''': gstreamer-bugs@maemo.bugs
*** Media streamer ('''TODO:''' better in applications? --[[User:qgil|qgil]] 19:32, 5 November 2008 (UTC) )
*** Multimedia framework ('''TODO:''' Vague)
*** Pulseaudio '''TODO: Add''' '''SETNEWQA''': pulseaudio-bugs@maemo.bugs
*** Real ('''TODO:''' Create and clean up) '''SETNEWQA''': real-bugs@maemo.bugs
** Real Time Communication '''TODO: Add''' (Versions: >=Fremantle)
*** Telepathy '''TODO: Add''' '''SETNEWQA''': telepathy-bugs@maemo.bugs
** System software
*** application-killer
*** D-Bus ''(was: dbus)''
*** Device lock ''(was: Desktop/Device lock)'' '''???''', '''TODO''': Triage - some bugs belong here, but some are in fact hildon widget bugs)
*** dsme (''was: System Software/dsme AND System Software/Watchdog'', '''TODO''': merge)
*** File system
*** general
*** glibc
*** HAL '''TODO: Add''' '''SETNEWQA''': hal-bugs@maemo.bugs
*** iconv
*** libxml
*** maemo-launcher
*** mmc-and-usb
*** OHM '''TODO: Add''' '''SETNEWQA''': ohm-bugs@maemo.bugs
** Translations
** UI Specification '''TODO:''' Merge with Desktop/User interaction
** User guide & Help content (should get rid off vague "Docu" term)
*** Help content
*** User guide
* X-Graveyard
** X-Discontinued
*** Audio player (770) ''(was: Multimedia/Audio player)''
*** core-initfs ('''TODO''': move 2021, 1855, 3852, 3589 and maybe 3745. Fremantle does NOT have initfs)
*** FM Radio (N800) ''(was: Multimedia/FM Radio)''
*** "Misdirected" product bugs
*** Browser: Opera engine ''(was: Browser/Opera engine (770/N800))''
*** osso-email ''(was: Communication/osso-email)''
*** python ''(was: System software/python)''
*** Video player (770) ''(was: Multimedia/Video player)''

* Nokia (isn't this a bit confusing? All the above is shipped by Nokia as well. I would consider having them under Utilities and Home Applets, respectively. --[[User:qgil|qgil]] 19:32, 5 November 2008 (UTC) )
: '''TODO:''' Get rid of this existing category. @Quim: Probably a better idea, indeed. --[[User:Andre|Andre]] 11:02, 6 November 2008 (UTC) )

[[User:Andre|Andre]]: Getting rid of the "Applications" product is very good. It was often confused with Desktop (e.g. mixing up Applets and Apps with the same name). But having Desktop now in Platform might also be confusing if you're used to the old structure so I changed this to "Desktop Platform".
What I have already done: I've moved Developer Docu from Website to Dev Platform (because it's out of community scope, see bug 3562).
Removed ancient Games/Startscreen subcomponent (only 2 bugs), Removed Desktop/PC connection (1 wrong bug), Desktop/Tableteer Info (0 bugs), Desktop/Desktop Info applet (0 bugs). Removed Communication/Accounts (3 bugs, 2 wrong). Removed System software/libcommon-error (0 bugs).
Removed System management/Teach handwriting (0 bugs). Removed Web shortcut (0 bugs, development stalled since Diablo).

=== Draft implementation ===
[http://blogs.gnome.org/aklapper/2008/11/07/bugsmaemoorg-reorganization Original plan]:
# Create new default QA virtual accounts for new products/components in advance
# Define a good day/time (Sunday?)
# Display info message about reorg one week in advance in /template/en/default/global/banner.html.tmpl
# Disable mail notification
# Implement changes
# Enable mail notification
# Remove banner

[[User:timeless|timeless]] prefers to keep mail notification enabled while doing this, see [http://blogs.gnome.org/aklapper/2008/11/07/bugsmaemoorg-reorganization/#comment-325 discussion]. So far, I disagree. :) --[[User:Andre|Andre]] 12:06, 11 November 2008 (UTC)

100Days/Sprint2

2008-08-18T02:45:47Z

24.164.22.34:

==Planning==
* Kick-off meeting organized in the Freenode #maemo-meeting IRC channel on 2008/06/30 at [http://www.timeanddate.com/worldclock/fixedtime.html?year=2008&month=6&day=30&hour=18&min=0&sec=0 18:00 UTC].
* The '''[http://maemo.org/maemo-meeting/maemo-meeting-2008-06-30.html meeting log]''' contains also the [https://garage.maemo.org/plugins/wiki/index.php?June2008Sprint&id=106&type=g review of the last sprint].
* [[100Days/Sprint3#Backlog|Backlog]] and [[100Days/Sprint3#Proposals|Proposals]] available in the [[100Days/Sprint3|Sprint3]] page.
* Sprint2 review meeting scheduled on 2008/07/22 together with the [[100Days/Sprint3|Sprint3]] planning meeting.

{| class="wikitable"
| style="background:LightGreen" | Completed
| style="background:LightBlue" | Good progress
| Just standing
| style="background:Orange" | Some help needed!
| style="background:Tomato" | Really stuck/delayed
|}

==Tasks==
{| class="wikitable sortable"
|-
! Committed
! Task
! Owner
! %
! Highlights
|- style="background:Tomato"
| 2008-05-10 || Who's who in Maemo || Dave || % || Discussion on implementation details pending
|- style="background:Tomato"
| 2008-05-10 || [[Companies in Maemo development]] || Dave || 60% || Initial group of companies defined, need logos & descriptions, and have list checked
|- style="background:Tomato"
| 2008-06-10 || [[Task:Consolidation of Extras|Consolidation of Extras]] || Niels || 0% || Niels must specify what goes in this sprint
|- style="background:Tomato"
| 2008-06-10 || Extras % maemo.org/downloads integration || Niels || % || Complete and/or document in wiki page
|- style="background:Tomato"
| 2006-06-10 || Registration and sponsorship for [[Maemo summit 2008]] || Oskari/Bergie || 90% || Working, some bugs left
|- style="background:LightGreen"
| 2008-06-10 || [[User:Peterschneider|Update maemo.org/intro]] || Dave || '''DONE''' || Just few pages waiting to be moved - links to be added
|- style="background:Tomato"
| 2008-06-10 || Better extras categories and debtags || Niels || % || Proposal needs to be drafted in wiki page
|- style="background:Tomato"
| 2008-06-10 || Put the [[Bugsquad]] in place || Andre/Karsten || 40% || See [http://lists.maemo.org/pipermail//maemo-developers/2008-June/033719.html this mail] - Done: [https://wiki.maemo.org/Bugs:Triage_guide Triage guide in place]
|- style="background:Tomato"
| 2008-06-10 || Forum interface to mailing lists released || Oskari/Bergie || % || Beta to be made public for testing
|- style="background:Tomato"
| 2008-06-10 || User profile improvements defined and started || Oskari/Bergie || 70% || Revamped, [https://bugs.maemo.org/show_bug.cgi?id=2224 some bugs left]
|- style="background:LightBlue"
| 2008-06-10 || No pages remaining in [[:Category:Midgard wiki]] || Dave || 20% || Decided to discontinue this task
|- style="background:LightGreen"
| 2008-06-30 || [[Task:Maemo brand|Maemo brand]] || Quim || '''DONE''' || Considering this OK. Formal approval before the next sprint meeting unless someone finds a bug.
|- style="background:LightGreen"
| 2008-06-30 || [[Task:Sprint progress|Sprint progress]] || Quim || '''DONE''' || The process is setup, now it's up to everybody to do their part.
|- style="background:LightGreen"
| 2008-06-30 || [[Task:Components and packages|Components and packages]] || Soumya || '''DONE''' || Table ready, problems uploading
|- style="background:Tomato"
| 2008-06-30 || [[Maemo.org_logo_contest]] selection process || Dave || % || Agreed that needs to be selection and not voting
|- style="background:LightGreen"
| 2008-06-30 || [[Maemo Summit 2008/Organization|Maemo Summit 2008 organization]] || Quim || '''DONE''' || In sync with c-base and all tasks listed - objectives of the sprint completed
|- style="background:LightGreen"
| 2008-06-30 || All components of product Website in good hands || Andre || '''DONE''' || All bugs triaged, missing only component owners list in this wiki
|}

==Bugs==
{| class="wikitable sortable"
|-
! Created
! Bug
! Component
! Assigned
! %
! Highlights
|- style="background:LightGreen"
| 2005-09-18 || [https://bugs.maemo.org/show_bug.cgi?id=95 desktop-files documented poorly] || Documentation || Dave || '''DONE''' ||
|- style="background:LightGreen"
| 2005-10-10 || [https://bugs.maemo.org/show_bug.cgi?id=101 Use the wiki for developer documentation] || Documentation || Dave || '''DONE''' || Now in the hands of Maemo SW team.
|-
| 2006-06-26 || [https://bugs.maemo.org/show_bug.cgi?id=630 Increased Bugzilla transparency - get the developers involved!] || Bugzilla || Andre/Karsten || 10% || In (long-term) progress
|- style="background:LightGreen"
| 2007-06-26 || [https://bugs.maemo.org/show_bug.cgi?id=1587 Cleaning the community wiki from official docs] || Documentation || Dave || 100% || Not the same as ["No pages left in [[:Category:Midgard wiki]]
|-
| 2007-11-05 || [https://bugs.maemo.org/show_bug.cgi?id=2212 Karma system should allow more e-mail addresses] || Profile || Bergie || % ||
|- style="background:LightBlue"
| 2007-11-06 || [https://bugs.maemo.org/show_bug.cgi?id=2224 Maemo user profile public formatting isn't nice] || Profile || Bergie || 70% || Depedent bugs open
|-
| 2008-01-24 || [https://bugs.maemo.org/show_bug.cgi?id=2828 It took a week to announcement to appear in maemo.org front page] || General || Bergie || % || Depends on [[Task:Fast Server]]
|-
| 2008-06-05 || [https://bugs.maemo.org/show_bug.cgi?id=3220 Midgard access control for folders and pages does not work] || Documentation || Bergie || % || Demoted to Medium
|-
| 2008-06-18 || [https://bugs.maemo.org/show_bug.cgi?id=3262 Defining company and role in profiles] || Profile || Oskari || % || HIGH because of Summit registration and Who is Who
|- style="background:LightGreen"
| 2008-06-18 || [https://bugs.maemo.org/show_bug.cgi?id=3264 Garage is (re)sending a "maemo logo competition" mail every hour] || Garage || Ferenc || '''DONE''' ||
|-
|-style="background:Tomato"
| 2008-06-23 || [https://bugs.maemo.org/show_bug.cgi?id=3280 Wiki pages sometimes fail to load with "lost network connection"] || Wiki || Ferenc || 50% || need an apache expert to see why it is crashin during high load (perhaps related to Midgard as well)
|-
|- style="background:LightGreen"
| 2008-06-23 || [https://bugs.maemo.org/show_bug.cgi?id=3283 Install the citation extension for the wiki] || Wiki || Ferenc || '''DONE''' ||
|-
| 2008-06-29 || [https://bugs.maemo.org/show_bug.cgi?id=3339 MediaBox Media Center appears as developed by Nokia when it's not] || Downloads || Bergie || 50% || Bug seems to be in midcom/datamanager, reassigning to bergie
|-
|- style="background:LightGreen"
| 2008-06-29 || [https://bugs.maemo.org/show_bug.cgi?id=3341 Install the Category Tree extension for the wiki] || Wiki || Ferenc || '''DONE''' ||
|-
|- style="background:LightGreen"
| 2008-06-29 || [https://bugs.maemo.org/show_bug.cgi?id=3342 Install the Dynamic Page List extension for the wiki] || Wiki || Ferenc || '''DONE''' ||
|-
|-
|-style="background:Tomato"
| 2008-06-30 || [https://bugs.maemo.org/show_bug.cgi?id=3354 Publishing packages to garage.maemo.org often results in "lost connection" and "permission denied" from scp] || Garage || Ferenc || 0% || '''This bug is still there and is a major problem!'''--[[User:xfade|xfade]] 08:04, 21 July 2008 (UTC); I can not reproduce it [[User:feri|feri]] 18:02, 22 July 2008 (UTC) ||
|-
|- style="background:LightGreen"
| 2008-06-06 || [https://bugs.maemo.org/show_bug.cgi?id=3228 found = format_regex.match(data_string) : TypeError: expected string or buffer] || Garage || Ferenc || '''DONE''' ||
|}

The bugs assigned in the last sprint meeting are marked as [https://bugs.maemo.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Website&component=Bugzilla&component=Calendar&component=Documentation&component=Downloads&component=Garage&component=General&component=News&component=Profile&component=Repositories&component=Wiki&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=High&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= HIGH]. The bugs proposed for the next sprint are marked as [https://bugs.maemo.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Website&component=Bugzilla&component=Calendar&component=Documentation&component=Downloads&component=Garage&component=General&component=News&component=Profile&component=Repositories&component=Wiki&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=Medium&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= MEDIUM]. Only product/component maintainers can change this status. Comment on a bug if you want to push it up. Check also those marked as [https://bugs.maemo.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Website&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=easyfix&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= EASYFIX].

==Activity log==
Latest activity report goes on top.

; Tuesday 2008-07-22

* Dave
** Yesterday: Conference - wrote & gave GNOME Mobile presentation at OMX.
** Today: Sprint meeting & attending OSCON.

* Andre
** Yesterday: Triage new bugs, (bug)mail followup, published initial version of [https://wiki.maemo.org/Bugsquad Bugsquad Triage Guide]
** Today: Triage the few new bugs, start improving [https://maemo.org/bugzilla/page.cgi?id=bug-writing.html Bugwriting How-to], triage old bugs, prepare tonight's Sprint2 and Bugzilla Meeting

* Niels
** Yesterday: Fixed wiki ssl problem, worked on wiki problems, worked on application comments bugs/enhancements.
** Today: Check repository queue manager problems, application comments bugs, prepare for meeting.

* Marcell
** Yesterday: cleaned my inbox after the holidays
** Today: Contacted the ISP about [https://bugs.maemo.org/show_bug.cgi?id=3127 3127] and a RAM upgrade to garage.maemo.org, contacted Nokia FDP about [https://bugs.maemo.org/show_bug.cgi?id=2350 2350] and the missing extras dl statistics.

; Monday 2008-07-21

* Dave
** Yesterday: Attended FLOSS Foundations day 2. Called for volunteers for logo contest.
** Today: Attending Open Mobile Exchange at OSCON. Giving a presentation on GNOME Mobile. Will keep on contest judging today.
** Problems: Timezone issue - I don't know when the sprint meeting is on. ''[http://www.timeanddate.com/worldclock/fixedtime.html?month=7&day=22&year=2008&hour=19&min=0&sec=0&p1=0 timeanddate.com is your friend] --[[User:xfade|xfade]] 08:09, 22 July 2008 (UTC)''

* Andre
** Yesterday: Triage Website bugs, continue triage old bugs, work on [https://wiki.maemo.org/Bugsquad Bugsquad Triage Guide]
** Today: Triage new bugs, (bug)mail followup, trigae some old bugs, work on [https://wiki.maemo.org/Bugsquad Bugsquad Triage Guide]

* Niels
** Thursday: Bugzilla wiki plugin testing and some garage maintenance.
** Today: Triage and work on bugs that have been assigned to me over the weekend.

* Quim
** Yesterday: [http://lists.maemo.org/pipermail/maemo-community/2008-July/000480.html Summit budget situation explained]. [http://maemo.org/news/events/ maemo.org events updated]. Created [[How_to_push_a_maemo.org_task]], [[Task:Publishing_API_docs]] and [[Objective:Release_soon_and_often]]. Added new proposals to [[100Days/Sprint3]].
** Today: Nothing until the Sprint planning meeting.
** Problems: [http://lists.maemo.org/pipermail/maemo-community/2008-July/000479.html Unable to upload a file to the wiki]

; Sunday 2008-07-20

* Quim
** Yesterday: Asking sponsored participants to hurry up with bookings. Triage Website bugs. Pushing plan for a GNOME hackfest.
** Today: Will work instead of Tuesday. Explaining the Summit budget situation. Update maemo.org events. Prepare Sprint3 meeting.

* Dave
** Yesterday: Attended FLOSS Foundations meeting. Made first draft of [[companies in Maemo development]]
** Today: Attending [http://flossfoundations.org FLOSS Foundations meeting] day 2. Start looking for a jury for the logo contest.

; Saturday 2008-07-19

* Quim
** Yesterday: Sponsorship requests up to date. [[Maemo_Summit_2008/Accommodation|Accommodation]] recommendations made. Pushing plan for a GNOME hackfest.
** Today: Will work instead of Monday. Asking sponsored participants to hurry up with bookings. Triage Website bugs.
** Problems: Can't decide on all sponsorship requests while having big items undefined in the budget. High season in Berlin in September, many hotels/Hostels quite booked those days, this increases average price of accommodation.

* Dave
** Yesterday: Travelling to Portland
** Today: Attending [http://flossfoundations.org FLOSS Foundations meeting]. Will work on list of companies & recruiting/identifying logo competition judges too.

; Friday 2008-07-18

* Dave
** Yesterday: As expected, not much time for Maemo stuff.
** Today: Travelling to OSCon all day.

* Andre
** Yesterday: Triaged some older bugs
** Today: Triage Website bugs, continue triage old bugs, work on [https://wiki.maemo.org/Bugsquad Bugsquad Triage Guide]

* Quim
** Yesterday: Visited c-base: cool people, great space! We started discussing about the details. They agreed to send a modular budget by the end of next week.
** Today: Clean queue of sponsorship requests. Have a look to accommodation in Berlin Mitte and surroundings (although it's raining...)
** Problems: imo we are starting to get many sponsorship requests not very reasonable, perhaps a "device discount" fever is starting. Hopefully not since I have better things to do than triaging requests from unknown people trying out. In any case this is a better problem than the lack of awareness we had just 3 days ago. :)

; Thursday 2008-07-17

* Dave
** Yesterday: Wrote a presentation for OSCon 2008 (next week), spent all afternoon on administrative stuff (bank, accountant, post office, phone calls), spent quite a while answering email.
** Today: Some phone calls, wrapping up GUADEC/GNOME stuff, will not make much progress on maemo stuff. Plan to kick-start the selection team for logo contest.
** Problems: July is the month of conferences. I'm only back & I'm leaving again. Need to learn how to get work done on the road.

* Niels
** Yesterday: MySQL upgrade preparation for Bugzilla, installed fixes for profiles. Requested new certificate for wiki. Worked on garage performance issues and monitored the massmailer.
** Today: Fix some bugs related to mediawiki Bugzilla plugin, work on Extras changes.
** Problems: Can't seem to find anybody whom can handle my SSL renewal request due to holidays.

* Ferenc
** Yesterday: fixed twice :) [https://bugs.maemo.org/show_bug.cgi?id=3264 mail bug on garage]
** Today: nothing
** Problems: none

* Quim
** Yesterday: Help Soumya getting a first draft of [[Task:Components_and_packages]] out. Complete 1st (and last?) wave of Summit promotion with a mass mailing that is working quite well. GNOME Hackfest could be based on GStreamer. OSiM registration, agreed to wait until August 1st to define the group package.
** Today: Fly to Berlin and agree the basics with the c-base guys. If time permits, have a look to hostels in the area.
** Problems: Couldn't upload Soumya's table. Wiki won't allow uploading OOo docs. Sent to maemo-community but retained because of 40kb limit (the mail had 46kb). In Ferenc's hands now.

; Wednesday 2008-07-16

* Ferenc
** Yesterday: viewvc install started on garage
** Today: complete viewvc install on garage, fix [https://bugs.maemo.org/show_bug.cgi?id=3264 mail bug on garage]
** Problems: garage is slow and overloaded. from time to time the svn commit hook script makes the server very busy. the qt4 team is using the garage web space to maintain their Debian repo there. they should move to extras-devel.

* Quim
** Yesterday: Split [[Maemo_Summit_2008/Organization|tasks and roles]] of the Summit + instructions for travel sent. Agreed with Soumya first draft of components and packages. More Summit promo in [http://www.internettablettalk.com/forums/showthread.php?p=203493 ITt] and got some good names (yay!). Details on possible GNOME Hackfest in Berlin.
** Today: Help Soumya getting a first draft of [[Task:Components_and_packages]] out, even if it's still a bit messy and not very nice-looking (Markitechture is a complex art!). OSiM developer session plan.
** Problems: Not a big one but OSiM discount is on their side now. Waiting.

* Niels
** Yesterday: Worked on performance issues on garage (Added php caching, smarter reindexing of repositories), setup non-free distribution for extras-devel and testing with etrunko, fixed some repository reindexing issues.
** Today: Fix wiki ssl certificate, fix non-free cron issues, get garage performance issues sorted out.
** Problems: Wiki ssl certificate expired.

* Dave
** Yesterday: Cleared email backlog (yay!). No-one on #maemo bit for the [[Integrate Bluetooth networks into Connection Manager | wiki page of the day]] - looks like I'll be cleaning it up myself. Talked to Quim about "Who's who" (see, reporting Problems does work) - looks like I'm blocking on [https://bugs.maemo.org/show_bug.cgi?id=3262 bug #3262], and will be bumping to [[100Days/Sprint3]]. Didn't get round to creating the wiki page with companies & logos - will do it today.
** Today: Create wiki page with list of companies working on maemo, plus logos. Presentation to finish for OSCon next week, and some outstanding GUADEC/GNOME stuff, must see accountant too, rest of the day in the wiki - goal: 3 pages.
** Problems: Not enough hours in the day. Quim: Can you put in a request with management for days to be extended to 28 hours, please?

; Tuesday 2008-07-15
* Andre
** Yesterday: Catch up with incoming bugs of the last week and follow-up mail and bugmail; sync statuses with Nokia's internal Tracker
** Today: Clean up more old bugs; work on Bugsquad proposal and wiki pages
** Problems: only non-technical (flu) ;-)

* Dave
** Yesterday: French bank holiday. Fixed up "Wiki page of the Day", and caught up with part of my mail backlog. Also did some GNOME stuff.
** Today: Finish catching up with email backlog. List companies involved in maemo development and send list to maemo-community. Fix up 2 wiki pages, and push people on #maemo to fix up the Wiki page of the Day.
** Problems: I don't know what to do with the list of companies working on maemo when it's done. We should put logos somewhere, figure out what a company needs to do to get on the list, and link this into someplace sensible. Not sure if this is best as a new Midgard page or a living Wiki page.

* Ferenc
** Today: [https://bugs.maemo.org/show_bug.cgi?id=3264 mail bug on garage], viewvc install on garage to reduce the load
** Problems: none

* Niels
** Yesterday: Debugged repository problems, tuned repository tools to lower load on garage, tested registration, installed bugzilla plugin for mediawiki (Doesn't work yet because of firewall issues)
** Today: Try to get new things done instead of trying to fix random things breaking.
** Problems: Insane server load on multiple machines, lack of access to machines, lack of response from ISP and people on vacation, but apart from that everything is OK.

* Quim
** Yesterday: [http://flors.wordpress.com/2008/07/15/that-gnome-week-in-istanbul/ Blog notes about GUADEC]. More Summit promotion (#maemo & GNOME Foundation) + [[Maemo_Summit_2008/Accommodation|instructions for accommodation]]. Assist Soumya on [[Task:Components_and_packages]].
** Today: Split tasks and roles of the Summit + instructions for travel + OSiM discount. Agree with Soumya first draft of components and packages?
** Problems: Reaching the right audience for sponsorship requests is harder than I thought e.g. penguinbait knew just yesterday about all this and now it's too late for him. I wonder if there are more cases like him. I want to have the sponsored guys decided asap for efficiency and to avoid last minute stress.

; Monday 2008-07-14

* Karsten
** Last week: GUADEC (Discussions, meetings, socializing, some talks. No mail, VPN was blocked.)
** Today: Triaging last weeks bug reports.

* Niels
** Friday, Weekend: Garage work and extras support, registration debugging/testing.
** Today: Investigate registration problem, look into repository problems and work on open bugs.
** Problems: High server load on garage.

* Andre
** Last week: GUADEC (talks, GNOME meetings, socializing. had problems to access my mail and irc)
** Today: Catch up with incoming bugs of the last week and follow-up mail and bugmail; sync statuses with Nokia's internal Tracker

* Quim
** Last week: Promoting the Maemo Summit in GUADEC and ITt. Testing the buggy registration/sponsorship.
** Today: Blog notes about GUADEC. Split tasks and roles of the Summit + more promotion + instructions to book flights. Assist Soumya on [[Task:Components_and_packages]].
** Problems: Unsure whether Dave is waiting for me to push "Who's who in Maemo - Discussion on implementation details pending".

; Sunday 2008-07-13

* Dave
** Since Wednesday: Attended GUADEC, patchy internet access, updated WPotD, but a little disappointed in community response (with the exception of GeneralAntilles)
** Tomorrow: Update [[modifying the root image]] and [[using Valgrind and gdb in Scratchbox]]

; Friday 2008-07-11
* Niels
** Yesterday: Worked on [[Providing_changes_since_last_version_of_a_package]], created a [http://wiki.maemo.org/index.php?title=Main_Page&useskin=monobookmaemo Maemo skin] for the wiki, helped some Extras users.
** Today: Work on .install files for Diablo Extras, look into registration problems.

; Thursday 2008-07-10
* Niels
** Yesterday: Added a non-free queue for diablo extras, so we can test adding packages there. Fixed garage svn stats and a chinook repository corruption.
** Today: Look into how to easily record changes for packages and work on [[Task:Consolidation_of_Extras]]

; Wednesday 2008-07-09
* Niels
** Yesterday: [https://bugs.maemo.org/show_bug.cgi?id=3225 Fixed] screenshots in /downloads, some wiki work and extras user help.

; Tuesday 2008-07-08
* Dave
** Yesterday: Finished migrating new Intro. Cleaned up [[partitioning a flash card]]. Finished a GNOME press release. Travelled to Istanbul.
** Today: Ran GNOME Mobile BOF. Will play in FreeFA World Cup this afternoon.

* Quim
** Yesterday: Had the ''Maemo & Nokia BOF'' at [http://guadec.org GUADEC]. Met Andre & Karsten + many others. Socializing.
** Today: Upload audio file of the session and blog about it. Review Summit registrations. Invite upstream maintainers to the Maemo Summit.
** Problems: None

* Niels
** Yesterday: Assisted extras users, [http://communitizer.blogspot.com/2008/07/maemoorgdownloads-automatic-updates.html blogged] about downloads auto updating, installed and tested the new profile pages, fixed [https://bugs.maemo.org/show_bug.cgi?id=3412 bug #3412]: permalink for downloads broken, installed and tested patch for memcached related issues on maemo.org.
** Today: Work on Extras related documentation and plans. Add link on /downloads to Extras upload documentation.
** Problems: None

; Monday 2008-07-07
* Niels
** Friday: Worked on some repository dependency problems for extras and DP team. Added automatic version updating to /downloads with data from the extras repositories. Worked on some bugs and did some user support for extras.
** Today: Blog automatic version update, Work on [[Task:Consolidation_of_Extras]]
** Problems: None

* Dave
** Yesterday: Cleaned up [[USB networking]], set [[booting from a flash card]] as Wiki page of the day, and when that got fixed, set [[partitioning a flash card]] as WPotD.
** Today: Migrate the rest of [[User:Peterschneider| the new Intro page]], clean up [[partitioning a flash card]], revisit GUADEC presentation, travel to Istanbul.
** Problems: None

; Friday 2008-07-04
* Andre
** Yesterday: follow-up mail and bugmail; ITT and mailing list postings
** Today: follow-up mail and bugmail; triaging incoming bug reports and reproducing/forwarding issues
** Problems: None

* Dave
** Today: Caught up on 2 days email. Sick baby. Not much progress.
** Problems: No babysitter :(

* Niels
** Yesterday: Worked on extras dependency problem and tried to get more info about the SSU dependencies. Tested registration interface and did some fixes. Test automatic version update script for downloads on the internal test machine.
** Today: Work on open bugs and downloads version updates.
** Problems: None

* Quim
** Yesterday: Launched the Maemo Summit + feedback on registration related bugs + promotion in [http://flors.wordpress.com/2008/07/03/maemo-summit-registration-open-free/ planets] and [http://www.internettablettalk.com/forums/showthread.php?t=21569 ITt].
** Today: Clarify OSiM registration for Summit participants and little else since I'm [http://live.gnome.org/GUADEC/2008/Travel flying to Istanbul].
** Problems: [https://bugs.maemo.org/show_bug.cgi?id=3264 Bug 3264] impedes better Summit promotion in maemo.org. I can't find the way in Midgard to approve sponsorship requests.

; Thursday 2008-07-03
* Dave
** Yesterday and Today: Attended a conference (RMLL 2008) yesterday and today, and prepared presentations most of the day Tuesday. Renewed usb_networking as Wiki page of the Day - unfortunately, no improvements to the page so far. I plan to work on it tomorrow to kick-start the effort.
** Problems: None of note.
* Niels
** Yesterday: Tested garage svn commit mail problems, worked on repository dependency issues, worked on .install files and library problems for extras, [http://communitizer.blogspot.com/2008/07/application-in-extras-devel-ok-promote.html blogged about promotion interface] and checked some autobuilder problems.
** Today: A bit more dependency problems, make sure registration interface works today. Add more documentation to the wiki about Extras.
** Problems: Reporting system for download stats lags, so I can't update the stats in /downloads

* Quim
** Yesterday: [[Task:Sprint_progress]] ready to go. Talked with Soumya about [[Task:Components_and_packages]] + Development Platform team participation in [[Maemo_Summit_2008]].
** Today: Whatever is needed to launch the Summit registration. Define tasks around [[Maemo_Summit_2008]].
** Problems: Impatient about the Summit registration. [http://www.tllts.org/ Got interviewed] till early morning and DP team celebrates 4.1 release, so not much work expected.

; Wednesday 2008-07-02

* Ferenc
** Yesterday: Accepting bugs for this sprint
** Today: Working on the bugs shown with light blue. Expected fix for those are early tomorrow.
** Problems: None

* Quim
** Yesterday: Feedback to Summit registration. Kicked off the [[Task:Sprint_progress]]. [http://flors.wordpress.com/2008/07/02/maemo-x-10/ Blogged] about [[Task:Maemo_brand]] review and misc stuff about maemo.org.
** Today: Fine tune [[Task:Sprint_progress]] and define tasks around [[Maemo_Summit_2008]].--[[User:qgil|qgil]] 09:43, 2 July 2008 (UTC)
** Problems: I stayed at home and couldn't test registration in internal server.

* Niels
** Activities: Yesterday I added IRC log of sprint meeting, extras support, committed promotion interface changes, checked connection problems builder, tried to fix libglade2 dependency problems in extras-devel for diablo, user support for autobuilder (mostly build-depends problems), autobuilder bug hunting, #maemo contact change requested, fixed problem in maemo profile, notified about .install files missing for diablo.
** Problems: Autobuilder connection problem with proxy (need others to fix this issue), .install files not available for diablo. (Need changes in promoter for that) [Plan for today:] Fix and check libglade dependency problems in diablo extras-devel, find a solution for .install files --[[User:xfade|xfade]] 08:42, 2 July 2008 (UTC)

Talk:Task:Brainstorming new features

2008-07-28T11:41:24Z

24.164.22.34: /* uservoice.com */

== IdeaStorm ==
''Moved from [[2010 Agenda]]''
* As suggested [http://geekpenguin.blogspot.com/2008/04/bright-idea.html here] and [http://www.internettablettalk.com/forums/showthread.php?t=19556 here], we could 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?--[[User:qgil|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 -- [[User:felipec|FelipeC]] 12:43, 2 June 2008 (UTC)''

This objective is now listed in the [https://garage.maemo.org/plugins/wiki/index.php?June2008Sprint&id=106&type=g maemo.org development backlog]. Oskari from Nemein pushes but you can help out already today.

== uservoice.com ==

Krisse suggests to have a look at http://uservoice.com - which looks like a commercial service based in something like IdeaStorm.--[[User:qgil|qgil]] 19:30, 25 July 2008 (UTC)
:Okay, I've got to admit here that I hadn't come across Ideastorm before when I suggested Uservoice. From the looks of things they're rather similar, and personally I'd be okay with either, as long as there is some easier-to-understand alternative to Bugzilla, and as long as Nokia does actually respond to suggestions. BTW Uservoice is commercial but it doesn't have ads, its business model is based around offering extra features to the companies using their service.--[[User:krisse|krisse]] 10:13, 28 July 2008 (UTC)
::Having said that, does Ideastorm have the same limited number of votes as Uservoice? That's quite an important feature to discourage people from suggesting things thoughtlessly.--[[User:krisse|krisse]] 10:21, 28 July 2008 (UTC)
:::The main difference is that Uservoice is a hosted service defined by a company you pay for, while IdeaStorm is an open source application you can install or port to your servers and configure in the way you want, free of charge.--[[User:qgil|qgil]] 11:05, 28 July 2008 (UTC)
::::This one's a no brainer. ;) Open source > *. —[[Special:Contributions/24.164.22.34|24.164.22.34]] 11:41, 28 July 2008 (UTC)

Talk:Drivers justification

2008-07-21T09:04:37Z

24.164.22.34: /* The GPL violation issue */

List hardware here which is underutilised/undocumented

==PowerVR==

3d rendering (hopefully onto 5mbit on omap2420 SARAM buffer

==IVA==

Conversion from RGB to YUV, decoding video frames, scaling and blitting bitmaps

==5mbit SRAM==
Possible use as an RGB framebuffer for powervr/flat x11 surface.
Would require the IVA to convert and push this RGB data onto SDRAM "standard" surface for the Epson LCD to display on screen quickly.

== SRAM notes/discussion ==

:irc question:
::<jott> lcuk: have you actually tried to investigate accessing the sram?
::<lcuk> where is it... ?
::<lcuk> this is what documentation is all about
::<jott> lcuk: drivers/video/omap/dispc.c atleast reads "#define OMAP2_SRAM_START 0x40200000"
::<overflo>
144 #define OMAP2_SRAM_START 0x40200000
145 /* Maximum size, in reality this is smaller if SRAM is partially locked. */
146 #define OMAP2_SRAM_SIZE 0xa0000 /* 640k */
:: these locations are used as ram by ARM7 (IVA Processor)

::http://mxr.maemo.org/diablo/source/kernel-source-diablo-2.6.21/kernel-source/drivers/video/omap/dispc.c

:::AFAIK it is already used. 5mbits is VGA resolution. It is currently used as 'video plane' i.e. some sort of overlay. omapfb driver support more (3) planes and this 640x480 video plane in SRAM is used for media playback by stock media player. [[User:fanoush|fanoush]]

:::fanoush, can you shed some light on how its used by the mediaplayer? We realise its vga resolution but it would be a start.
:::also, what is the point in 3 planes when it can barely send 1 plane fast enough. as a base enabler for 3d and faster graphics it would be an ideal start. --[[User:lcuk|lcuk]] 21:24, 16 July 2008 (UTC)

:::the reason for more planes is simplicity and speed, each plane can be enabled/disabled separately and framebuffer update (sending data to epson chip) merges those planes and gives priority to the video one (i.e. sends data only from the topmost one) so it works like overlay on desktop (and is used in same way by Xv ?). The reason for using SRAM is speed and maybe dispc can also do some operations only in SRAM, it was briefly explained by dstone on mailing list at the time second OS2007 update came with significant video speedup. Also maybe some/same plane is used by camera for similar reasons. BTW this is maybe not best place to go into details :-) [[User:fanoush|fanoush]] 08:16, 17 July 2008 (UTC)

:::As for the media player, more correct is perhaps to say that that VGA plane in SRAM is used for implementing Xv support in xserver so anything using Xv should use it too. I'm not 100% sure about SRAM being really allocated and used but whole multiple plane support with possibility of different per-plane memory type (quite complicated code) was added to kernel with that OS update so it would be insane to write so much code and complicate stuff in a big way and then not to use it. I also believe (but can be wrong) I've seen the code with plane definitions in kernel but can't find it now. [[User:fanoush|fanoush]] 09:49, 17 July 2008 (UTC)

:::Agreed on the multi plane support, it can be used to help double/triple buffering.
:::As for actually making use of the SRAM I am not so sure. The dispc.c omap display driver below does make use of it: its expected to, it is the driver for the direct omap2420 display. however from what we can gather this is not loaded for the n8x0, we use the omapfb/blizzard chain which uses regular DDR.
:::If mediaplayer can allocate/use memory for its own private purposes, we should be able to as well. --[[User:lcuk|lcuk]] 10:51, 17 July 2008 (UTC)

:::as for double buffering - perhaps yes, planes are not equally fast and big but one could enable/disable one of them and draw into the other and force region update. As for dispc I believe it is _is_ used. It has remote mode and can send data over rfbi (not so much different than feeding LCD directly). So there are two similar ways - draw to sdram and push it to epson chip or draw to sram and let dispc to do it too. I believe this is used because dispc can do scaling on the fly too so for larger frames you can cheat and actually send less data and overcame slow rfbi interface this way (downscaling done by epson is useless here, you want to minimize size of source data sent, not destination). It is all pretty crazy, never seen before drawing to screen scattered over so many different drivers used in combination. As for verifying plane location it should be quite easy to add some debug code when iterating over planes and print plane memory type. Maybe it is even printed to kernel log at boot time. [[User:fanoush|fanoush]] 12:15, 17 July 2008 (UTC)

:::i was under the impression the dispc framebuffer driver was used on ti development boards within monte-vista and not touched or initialized at all by maemo at present. we initialize omapfb and talk to the blizzard low level interface without mention of any on OMAP memory (technically the blizzard doesn't even know or care that it is sitting on an OMAP motherboard).
:::With the omapfb, there are multiple planes and from what I understand all are allocated in standard SDRAM.
:::The way I am thinking of utilizing the SRAM would be to allocate a buffer similar to the dispc SRAM based frambuffer, then after rendering, update a frame by pushing the data out to the already allocated blizzard SDRAM buffer (using the IVA to perform RGB->YUV conversion if required per the display mode) and then tell blizzard to update.
:::Sure, its a longer path but right now (because of lack of information) I am not sure we can tell the powervr to render directly to SDRAM. If it is possible it may also give applications a fast RGB pixelbuffer to do non 3d fancy things which are limited at present by SDRAM access speeds. --[[Special:Contributions/80.0.224.233|80.0.224.233]] 13:31, 17 July 2008 (UTC)
:::I believe the ompafb we do use was originally created to support the omap1 processor family which had to use an external lcd because it did not have a SRAM framebuffer or direct video out from the chip (it didnt have its own graphics card). --[[Special:Contributions/80.0.224.233|80.0.224.233]] 13:52, 17 July 2008 (UTC)

:::Now that's interesting, it is not in SRAM indeed. At least in Diablo/N810. Will check OS2007/N800 but most probably it will be similar.
::: omapfb: s1d13745 LCD controller rev 1 initialized (CNF pins 3)
::: omapfb: region0 phys 80600000 virt ffa01000 size=770048 type=0
::: omapfb: region1 phys 80700000 virt ffabd000 size=786432 type=0
::: omapfb: region2 phys 87c00000 virt ffb7d000 size=1572864 type=0
::: omapfb: Framebuffer initialized. Total vram 3129344 planes 3
:::So why they added plane support in SRAM is beyond me 8-0 [[User:fanoush|fanoush]] 14:35, 17 July 2008 (UTC)

:::Huh, I was right after all. This is OS2007/N800
::: omapfb: region0 phys 87e00000 virt ffa01000 size=770048 type=0
::: omapfb: region1 phys 4022f000 virt d002f000 size=462848 type=1
::: omapfb: region2 phys 87f00000 virt ffabd000 size=770048 type=0
::: omapfb: Framebuffer initialized. Total vram 2002944 planes 3
:::I wonder why they disabled it in OS2008 (or maybe Diablo?) --[[User:fanoush|fanoush]] 15:51, 17 July 2008 (UTC)

:::fanoush, very interesting indeed and would appear to confirm the need for clear documentation. --[[User:lcuk|lcuk]] 21:10, 17 July 2008 (UTC)

:::The 2.6.18 kernel has it defined in arch/arm/mach-omap2/board-n800.c, second plane is defined in SRAM with size 640x480x12bpp. This is no longer true since first 2.6.21 kernel used in OS2008 (defined in same source). True that planes are defined to be much larger so they would no longer fit into SRAM. The third plane now has space for two full 800x480 frames. --[[User:fanoush|fanoush]] 06:33, 18 July 2008 (UTC)

== justification point ==

Word "justification" in the title implies that we are supposed to justify it to Nokia (or other IP holder) why we need this information. For good justification, we have to show what value IP holder gets from disclosing information, not what value the community gets. Here is the justification I suggest:

* Among Maemo community there are many people who are willing to perform for free work that companies would have to hire embedded software engineers to do.
* Some of these people have already proven that they have enough qualification to do the job.
* An embedded software engineer costs company at least $75,000 on the average. Thus, if somebody does the same work for free, this leads to direct cost savings to IP holders.
* Even if a project is of no direct interest to the IP holder at this moment, there is no cost to the IP holder, so there is no risk.
* Just about any popular system functionality extension to the Maemo platform (A2DP, rotated display, etc.) greatly increases value of the platform to end users (not necessarily developers). Therefore, even if the company sees no direct use for the feature, it still helps the company to sell more products.

What do we expect from Nokia and other IP holders:

* Give certain qualified people from the Maemo community access to documentation after signing all proper NDAs.
* Give these people some qualified advice from engineers inside the company.
* Accept work from these people and integrate it into official software releases as necessary.

== example fast cpu rendering ==

selfless link to liqbase, whether it needs to be seen on the frontpage to show the differences to normal rendering?
http://www.youtube.com/watch?v=PUPp_mE7rwI

== The GPL violation issue ==

I have started circulating the draft and I got already some interesting feedback.

So we have a driver used strictly internally and strictly for R&D purposes. This driver was done for the 2.4 kernel. When moved to 2.6 we have problems with GPL license violations, which we could ''solve'' in three ways:

# <irony>Keep the driver as it is and leave the driver installation to you. This way we do not distribute GPL violating drivers, but this way you are using GPL violating drivers.</irony>
# <irony>We hack the GPL checking from the kernel we will ship, so no GPL violation (but loads of upset kernel developers?)</irony>
# We spend a lot of time and money rewriting the driver to be shippable without any kernel changes or violations (not very feasible on our side, I tell you)

Note that in the points above we are not even mentioning TI, who needs to agree in the game since at the end they are the ones licensing the driver.

This is not last word. I will be posting here feedback as I get it.--[[User:qgil|qgil]] 10:12, 17 July 2008 (UTC)
:IANAL, but I don't think (1) is viable: the driver is still a derived work, even if you don't bundle it yourself. (2) would cause so much negative press as to be unbelievable and would cause serious harm to the platform (and so the community). One possible option would be to contract an external community member (or members) under NDA to receive the driver and its source with the understanding that it is not for distribution. For all intents and purposes this is therefore still Nokia internal use. That developer can then do option (3). --[[User:jaffa|Jaffa]] 11:06, 17 July 2008 (UTC)
::Good to see that we are in the same page. The first two options are listed as mathematical possibilities but in real terms are No-Go. About the third option, in principle I see a problem combining "community member" and "NDA" since normally NDAs are signed with individuals in companies or other types or organizations (e.g. universities, research centers...). In any case the organization that helps external developers getting contracts signed is Forum Nokia. Kate Alhola is the Maemo contact there and in fact she is interested and working in finding a way to get this puzzle sorted out in some way. I have sent her a link to this page. You know her as well. looks like a way to see if it's possible to move forward. In any case I keep the feedback channel open in my side and I will report here anything new.--[[User:qgil|qgil]] 18:06, 17 July 2008 (UTC)
:Note: The 2. alternative, just disabling the GPL check is really not on option that Nokia can do at all, it was just mentioned indicating there is no good and acceptable way that Nokia can do for shipping the driver. [[User:kate|kate]] 08:52, 21 July 2008 (UTC)

Talk:Drivers justification

2008-07-21T09:04:09Z

24.164.22.34: /* The GPL violation issue */ Reformatting for proper threading

List hardware here which is underutilised/undocumented

==PowerVR==

3d rendering (hopefully onto 5mbit on omap2420 SARAM buffer

==IVA==

Conversion from RGB to YUV, decoding video frames, scaling and blitting bitmaps

==5mbit SRAM==
Possible use as an RGB framebuffer for powervr/flat x11 surface.
Would require the IVA to convert and push this RGB data onto SDRAM "standard" surface for the Epson LCD to display on screen quickly.

== SRAM notes/discussion ==

:irc question:
::<jott> lcuk: have you actually tried to investigate accessing the sram?
::<lcuk> where is it... ?
::<lcuk> this is what documentation is all about
::<jott> lcuk: drivers/video/omap/dispc.c atleast reads "#define OMAP2_SRAM_START 0x40200000"
::<overflo>
144 #define OMAP2_SRAM_START 0x40200000
145 /* Maximum size, in reality this is smaller if SRAM is partially locked. */
146 #define OMAP2_SRAM_SIZE 0xa0000 /* 640k */
:: these locations are used as ram by ARM7 (IVA Processor)

::http://mxr.maemo.org/diablo/source/kernel-source-diablo-2.6.21/kernel-source/drivers/video/omap/dispc.c

:::AFAIK it is already used. 5mbits is VGA resolution. It is currently used as 'video plane' i.e. some sort of overlay. omapfb driver support more (3) planes and this 640x480 video plane in SRAM is used for media playback by stock media player. [[User:fanoush|fanoush]]

:::fanoush, can you shed some light on how its used by the mediaplayer? We realise its vga resolution but it would be a start.
:::also, what is the point in 3 planes when it can barely send 1 plane fast enough. as a base enabler for 3d and faster graphics it would be an ideal start. --[[User:lcuk|lcuk]] 21:24, 16 July 2008 (UTC)

:::the reason for more planes is simplicity and speed, each plane can be enabled/disabled separately and framebuffer update (sending data to epson chip) merges those planes and gives priority to the video one (i.e. sends data only from the topmost one) so it works like overlay on desktop (and is used in same way by Xv ?). The reason for using SRAM is speed and maybe dispc can also do some operations only in SRAM, it was briefly explained by dstone on mailing list at the time second OS2007 update came with significant video speedup. Also maybe some/same plane is used by camera for similar reasons. BTW this is maybe not best place to go into details :-) [[User:fanoush|fanoush]] 08:16, 17 July 2008 (UTC)

:::As for the media player, more correct is perhaps to say that that VGA plane in SRAM is used for implementing Xv support in xserver so anything using Xv should use it too. I'm not 100% sure about SRAM being really allocated and used but whole multiple plane support with possibility of different per-plane memory type (quite complicated code) was added to kernel with that OS update so it would be insane to write so much code and complicate stuff in a big way and then not to use it. I also believe (but can be wrong) I've seen the code with plane definitions in kernel but can't find it now. [[User:fanoush|fanoush]] 09:49, 17 July 2008 (UTC)

:::Agreed on the multi plane support, it can be used to help double/triple buffering.
:::As for actually making use of the SRAM I am not so sure. The dispc.c omap display driver below does make use of it: its expected to, it is the driver for the direct omap2420 display. however from what we can gather this is not loaded for the n8x0, we use the omapfb/blizzard chain which uses regular DDR.
:::If mediaplayer can allocate/use memory for its own private purposes, we should be able to as well. --[[User:lcuk|lcuk]] 10:51, 17 July 2008 (UTC)

:::as for double buffering - perhaps yes, planes are not equally fast and big but one could enable/disable one of them and draw into the other and force region update. As for dispc I believe it is _is_ used. It has remote mode and can send data over rfbi (not so much different than feeding LCD directly). So there are two similar ways - draw to sdram and push it to epson chip or draw to sram and let dispc to do it too. I believe this is used because dispc can do scaling on the fly too so for larger frames you can cheat and actually send less data and overcame slow rfbi interface this way (downscaling done by epson is useless here, you want to minimize size of source data sent, not destination). It is all pretty crazy, never seen before drawing to screen scattered over so many different drivers used in combination. As for verifying plane location it should be quite easy to add some debug code when iterating over planes and print plane memory type. Maybe it is even printed to kernel log at boot time. [[User:fanoush|fanoush]] 12:15, 17 July 2008 (UTC)

:::i was under the impression the dispc framebuffer driver was used on ti development boards within monte-vista and not touched or initialized at all by maemo at present. we initialize omapfb and talk to the blizzard low level interface without mention of any on OMAP memory (technically the blizzard doesn't even know or care that it is sitting on an OMAP motherboard).
:::With the omapfb, there are multiple planes and from what I understand all are allocated in standard SDRAM.
:::The way I am thinking of utilizing the SRAM would be to allocate a buffer similar to the dispc SRAM based frambuffer, then after rendering, update a frame by pushing the data out to the already allocated blizzard SDRAM buffer (using the IVA to perform RGB->YUV conversion if required per the display mode) and then tell blizzard to update.
:::Sure, its a longer path but right now (because of lack of information) I am not sure we can tell the powervr to render directly to SDRAM. If it is possible it may also give applications a fast RGB pixelbuffer to do non 3d fancy things which are limited at present by SDRAM access speeds. --[[Special:Contributions/80.0.224.233|80.0.224.233]] 13:31, 17 July 2008 (UTC)
:::I believe the ompafb we do use was originally created to support the omap1 processor family which had to use an external lcd because it did not have a SRAM framebuffer or direct video out from the chip (it didnt have its own graphics card). --[[Special:Contributions/80.0.224.233|80.0.224.233]] 13:52, 17 July 2008 (UTC)

:::Now that's interesting, it is not in SRAM indeed. At least in Diablo/N810. Will check OS2007/N800 but most probably it will be similar.
::: omapfb: s1d13745 LCD controller rev 1 initialized (CNF pins 3)
::: omapfb: region0 phys 80600000 virt ffa01000 size=770048 type=0
::: omapfb: region1 phys 80700000 virt ffabd000 size=786432 type=0
::: omapfb: region2 phys 87c00000 virt ffb7d000 size=1572864 type=0
::: omapfb: Framebuffer initialized. Total vram 3129344 planes 3
:::So why they added plane support in SRAM is beyond me 8-0 [[User:fanoush|fanoush]] 14:35, 17 July 2008 (UTC)

:::Huh, I was right after all. This is OS2007/N800
::: omapfb: region0 phys 87e00000 virt ffa01000 size=770048 type=0
::: omapfb: region1 phys 4022f000 virt d002f000 size=462848 type=1
::: omapfb: region2 phys 87f00000 virt ffabd000 size=770048 type=0
::: omapfb: Framebuffer initialized. Total vram 2002944 planes 3
:::I wonder why they disabled it in OS2008 (or maybe Diablo?) --[[User:fanoush|fanoush]] 15:51, 17 July 2008 (UTC)

:::fanoush, very interesting indeed and would appear to confirm the need for clear documentation. --[[User:lcuk|lcuk]] 21:10, 17 July 2008 (UTC)

:::The 2.6.18 kernel has it defined in arch/arm/mach-omap2/board-n800.c, second plane is defined in SRAM with size 640x480x12bpp. This is no longer true since first 2.6.21 kernel used in OS2008 (defined in same source). True that planes are defined to be much larger so they would no longer fit into SRAM. The third plane now has space for two full 800x480 frames. --[[User:fanoush|fanoush]] 06:33, 18 July 2008 (UTC)

== justification point ==

Word "justification" in the title implies that we are supposed to justify it to Nokia (or other IP holder) why we need this information. For good justification, we have to show what value IP holder gets from disclosing information, not what value the community gets. Here is the justification I suggest:

* Among Maemo community there are many people who are willing to perform for free work that companies would have to hire embedded software engineers to do.
* Some of these people have already proven that they have enough qualification to do the job.
* An embedded software engineer costs company at least $75,000 on the average. Thus, if somebody does the same work for free, this leads to direct cost savings to IP holders.
* Even if a project is of no direct interest to the IP holder at this moment, there is no cost to the IP holder, so there is no risk.
* Just about any popular system functionality extension to the Maemo platform (A2DP, rotated display, etc.) greatly increases value of the platform to end users (not necessarily developers). Therefore, even if the company sees no direct use for the feature, it still helps the company to sell more products.

What do we expect from Nokia and other IP holders:

* Give certain qualified people from the Maemo community access to documentation after signing all proper NDAs.
* Give these people some qualified advice from engineers inside the company.
* Accept work from these people and integrate it into official software releases as necessary.

== example fast cpu rendering ==

selfless link to liqbase, whether it needs to be seen on the frontpage to show the differences to normal rendering?
http://www.youtube.com/watch?v=PUPp_mE7rwI

== The GPL violation issue ==

I have started circulating the draft and I got already some interesting feedback.

So we have a driver used strictly internally and strictly for R&D purposes. This driver was done for the 2.4 kernel. When moved to 2.6 we have problems with GPL license violations, which we could ''solve'' in three ways:

# <irony>Keep the driver as it is and leave the driver installation to you. This way we do not distribute GPL violating drivers, but this way you are using GPL violating drivers.</irony>
# <irony>We hack the GPL checking from the kernel we will ship, so no GPL violation (but loads of upset kernel developers?)</irony>
# We spend a lot of time and money rewriting the driver to be shippable without any kernel changes or violations (not very feasible on our side, I tell you)

Note that in the points above we are not even mentioning TI, who needs to agree in the game since at the end they are the ones licensing the driver.

This is not last word. I will be posting here feedback as I get it.--[[User:qgil|qgil]] 10:12, 17 July 2008 (UTC)
:IANAL, but I don't think (1) is viable: the driver is still a derived work, even if you don't bundle it yourself. (2) would cause so much negative press as to be unbelievable and would cause serious harm to the platform (and so the community). One possible option would be to contract an external community member (or members) under NDA to receive the driver and its source with the understanding that it is not for distribution. For all intents and purposes this is therefore still Nokia internal use. That developer can then do option (3). --[[User:jaffa|Jaffa]] 11:06, 17 July 2008 (UTC)
::Good to see that we are in the same page. The first two options are listed as mathematical possibilities but in real terms are No-Go. About the third option, in principle I see a problem combining "community member" and "NDA" since normally NDAs are signed with individuals in companies or other types or organizations (e.g. universities, research centers...). In any case the organization that helps external developers getting contracts signed is Forum Nokia. Kate Alhola is the Maemo contact there and in fact she is interested and working in finding a way to get this puzzle sorted out in some way. I have sent her a link to this page. You know her as well. looks like a way to see if it's possible to move forward. In any case I keep the feedback channel open in my side and I will report here anything new.--[[User:qgil|qgil]] 18:06, 17 July 2008 (UTC)
Note: The 2. alternative, just disabling the GPL check is really not on option that Nokia can do at all, it was just mentioned indicating there is no good and acceptable way that Nokia can do for shipping the driver. [[User:kate|kate]] 08:52, 21 July 2008 (UTC)

Talk:Task:100Days

2008-06-01T20:10:38Z

24.164.22.34: /* How can I help? */

== Scope of the 100 Days ==

Hi, just a comment: anything inside maemo.org-the-webiste fits inside the range of things that the community, the maemo.org team and myself as Nokia contact can push forward without much discussion and interference if we all agree on the appropriatness and feasibility.

Anything related to software in the platform itself (as opposed to the server infrastructure), has many other stakeholders and dependencies and therefore fall out of the scope of the maemo.org planning exercise. If you want to compile these ideas and proposals fine, but it would be really useful to keep in this page the scope on purely maemo.org, its content, processes, servers, tools... and the people collaborating around it.

More or less the same principle applies to the [[2010 Agenda]] but in that case the discussion is more strategy and some software platform related topics might be more on topic.--[[User:qgil|qgil]] 13:29, 30 May 2008 (UTC)

== A few suggestions for developers ==
A few more suggestions for developers - the bottom rungs of the ladder.

1. Validate and verify the tools installation for the current shipping version, particularly the HOWTO. I follow the instructions but nothing builds. At least until I do an apt-get dist-upgrade, update, upgrade or something similar, then apt-get the -dev versions of a half dozen things, none of which is mentioned. Which brings me to:

2. Insure the hello-world will actually build on a system cleanly installed following the exact instructions from step 1. (I had to edit things in mine) and form a deb which will work on a tablet - both install and remove. Also split out stand-alone versions to use as templates (I can't get a statusbar only version to come up as everything seems to be interdependent). Maemopad is a great write template, but a paint template (slightly more than trivial graphic demo) would be nice.

Hildon is not something I've dealt with, and has its own quirks along with GTK. They aren't bad, but I could spend a week just learning the ins and outs. But there aren't very many examples I can just change the icons and add in a chunk of code to do a simple task as a starting point, at least not without doing a lot of searching (e.g. some statusbar clocks are stand-alone).

3. Simplify the autogen/automake/autoconf stuff. Most of this will only be run under fixed releases, so the checking for some specific version of 20 libraries is redundant, and makes the build horribly complicated. Either in scratchbox things are there or not (and see #1 above if they are not! I also have to keep doing apt-gets since I need -dev of everything and often don't have them). Do I really need libtool for a trivial statusbar app?

:Autoconf is actually quite important for code portability, not only across maemo releases (1.0, 1.1, mistral, scirocco, bora, chinook, diablo and so on) but also (and more importantly) across platforms. There is a lot of cross-pollination happening right now, and that's a very good thing IMHO. It will make your life much easier when you decide to port your application to (for example) Ubuntu Mobile, Openmoko or "desktop" GNOME, and it also makes porting stuff from other platforms to maemo simpler.
: Having said that, it is a bit of a learning curve, but perhaps what's needed is more entry-level documentation/tutorials (chapter 5 is a very good start at that) and tools to simplify bootstrapping (like the anjuta plugin).

The goal is that anyone should be able to do a working deb for a trivial off-the-cuff application or status bar, home, or control panel applet in 5 minutes by doing a global substitute (or perhaps changing a few lines of the form: #define APPNAME HILDON_HELLO_WORLD, #define AppName HildonHelloWorld, #define appname hildon_hello_world, etc.) and adding a few lines of code and scaled icons.

And for "garage", there should be one centralized repository, so there would be a "garage" parallel to "extras" with all betas and releases not higher up in the chain. Right now I've got dozens of archives and sources, so when I do a restore it becomes a nightmare getting all the applications back and it makes application manager slower having to go through dozens of archives. It doesn't help having a "garage page" if it is not much better than hosting offsite. But then for all these add-ons I could just do apt-get source and/or apt-get install. Maybe this is what "extras" is for, but it seems to never work or have anything. —Preceding unsigned comment added by [[User:70.209.165.167|70.209.165.167]] 19:32, 29 May 2008 (UTC)

== Mostly Technical Suggestions ==

=== Development ===

1. Place references / howtos / tutorials onto one page so that developer does not need to click through several menus.

2. Move outdated documentation away, but move older documentation that has not been updated for 4.x up, with a note "not fully applicable for 4.x".

3. Make it possible for logged-in developers to annotate any place in the documentation. Link to annotations from documentation.

4. Switch to SB2. SB1 is difficult to install and stays insulated from the rest of developer's system, making development complicated.

5. Provide an example of simple build environment *not* relying on AutoConf and its friends. A single includable makefile should suffice, when used with SB2.

6. Clearly *say* in the SB readme that it is not possible to debug every application on the desktop, show how to test applications on the target device using SSH/SCP or some other means.

7. Maybe provide a few simple stylesheets and JavaScript libs for creating quick iPhone-like web apps running in MicroB. This should be very light, very easy to use, and targeted to casual users.

=== Discussion Forums ===

1. Fix iTT's style sheets so that they work well on MicroB! It is a joke that a site dedicated to internet tablets cannot be effectively viewed with an internet tablet.
: Just stylesheets may not be enough - the real problem lies elsewhere: run a Firebug Net test and look at the results - seems like right now the front page is 700k, delivered by 67 requests. Some things take seconds to load, some javascripts are with php extension, thus not using cache, taking precious bandwidth and seconds to load, I'm not sure I see the reason for that. Things that can be done to get it faster - javascript libraries can be compressed with YUI compressor for instance and not served with php so they can cache properly, replace youtube videos with handy links for mytube just for ITs, combine stylesheets and javascripts together, reducing requests, use fewer PNGs with alpha, if any - Cairo probably will have a good deal of trouble displaying them on an IT. [[User:bundyo|bundyo]] 20:44, 30 May 2008 (UTC)
:: Umgh... I did notice the stylesheet but did not know it was that bad. My suggestion would be to simplify the page rather than use compressor, etc. There is absolutely no reason for this page to be this complicated and take 700kB. It is not doing anything special, just presenting a few views to the reader. Really hope Reggie sees the light at some point and changes his setup. —Preceding unsigned comment added by [[User:fms|fms]] 17:19, 30 May 2008 (UTC)
:Though definitely something that needs doing, it's a bit out of scope for maemo.org. ;) Somebody want to run through the areas where Reggie could optimized and open a thread in the [http://www.internettablettalk.com/forums/forumdisplay.php?f=16 Comment/Suggest] forum over there? —[[User:generalantilles|generalantilles]] 21:22, 30 May 2008 (UTC)
2. Integrate iTT with Maemo.org karma system.
:See [https://bugs.maemo.org/show_bug.cgi?id=2303 bug #2303] and [https://bugs.maemo.org/show_bug.cgi?id=2304 bug #2304] —[[User:generalantilles|generalantilles]] 00:25, 1 June 2008 (UTC)

=== Software Distribution ===

1. Actively hunt on the Net for maemo apps not yet added to Maemo Extras, talk to developers, ask and help them to commit applications to Maemo Extras. This especially applies to app porters currently active at iTT.

2. Use gronmayer's scripts to create a web site that merges applications from all known repositories into a single list and lets you browse them with MicroB using HTML UI similar to N-Gage, Apple Store, etc. While it sounds ambitious, it is not difficult to do, as we always have app descriptions and icons (form .deb files) and we also have screenshots for apps hosted at Garage. Reformatting this data in a format that can be nicely presented in tablet browser is not difficult.

3. Effectively replace "iTT Software Section" with #2 from this list.

:: About 2 and 3 - I thought we all agreed on that here: http://www.internettablettalk.com/forums/showthread.php?t=20261, just compiling a single list won't solve the dependency hell. [[User:bundyo|bundyo]] 19:04, 30 May 2008 (UTC)

:: It will not but then it is not the goal of 2. The goal is to supplement the current half-baked Application Installer app with a quickly modifiable online interface for searching and selecting applications. This will help users to find more applications and in the same time it will help developers to figure out just how exactly application installer should work. Instead of waiting for the next OS release, it is really easy to modify the web interface and see which modification is better. Later, the real App Installer can be designed to have the same or similar interface.
::: I can see what your idea is, but i don't think the user will be happy when his/her NIT falls into a reboot loop due to some library replacement. Not good for official, but maybe will be good for the developers to see what is already ported and not doing it again. [[User:bundyo|bundyo]] 20:49, 30 May 2008 (UTC)
:::: Situation where a library used by some other application is being upgraded can be checked and reported to the user, as a warning. And no, of course I do not suggest that this system is associated with Nokia in any way: Nokia can't be held responsible for all the repositories out there.
::::: Well, then it should be discussed as kind of an upgrade to Gronmayer's site, maybe with him? [[User:bundyo|bundyo]] 21:35, 30 May 2008 (UTC)
:::::: Definitely: after all, he has all the code already. Replicating it is extra work. As to the UI, I have got a mock up already, if anybody is interested (http://fms.komkon.org/Maemo/). [[User:fms|fms]]

== 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" --[[User:peterschneider|peterschneider]] 10:02, 30 May 2008 (UTC)

== Smoothing the introduction of new users to maemo.org ==

* The development section should be organized in a simple, clear and centralized way to beginners. The following information is important and should be presented to the newcomers immediately they enter the development section.
# Simple steps of getting started should be presented in a clear and definite way ,on a conspicuous area with color. for example:
## Sign up a maemo account (link to register page)
## Download and set up development environment.(link to detailed method page)
## Create hello world application, Package and Test(link to several typical and simple examples,and useful links to advanced docs should be included)
## Collaboration on maemo.org and Launch app on the download section (link to pages including usage of project homepage)
# Key features of maemo platform should be presented on the section page explicitly.
## Free to develop and launch applications.
## Powerful enough to create advanced applications.
## Flexibility in programming (Gtk+/C,Python,Qt and etc)
## Easy to port existing application.
# Wiki on frequent technical problems in programming(the how-tos part),and entry to developer's disscusion board(link to ITT's or a new one) to help newcomers to find solutions to difficulty and ask for help.
# All docs in a catalog with good classification for look up.
# Maemo's roadmap and history, technical news and announcement about maemo.
# Maemo app gallery and entry to experienced and recently active developers' tech blogs.

== Style and accessibility of maemo.org ==

There are some consistency problems with the clarity of the maemo.org web sites. Although some are simply visual clutter, and not critical, some definitely obscure important links; a notable example is the complete list of applications. It appears to be simply a heading, as it matches the color and font of all the other headings.

garage.maemo.org does not seem to have this problem, all links are underlined, and the traditionally expected color for links.

References regarding link accessibility are easily found (a google search for "underlined link usability" brings back a great deal of useful links). Here are a handful.

* Excellent [http://www.useit.com/alertbox/20040510.html accessible link overview] by Jakob Nielsen
* Nice writeup regarding [http://www.uie.com/brainsparks/2006/07/05/do-links-need-underlines/ user expectations] when reading links
* A [http://www.usability.gov/pubs/052007news.html US Government site on accessibility]. Note that they suggest avoiding "non traditional colors for links" although this is never really strictly held to in most web sites. Colors should always mean the same things, however.
* Another [http://www.webcredible.co.uk/user-friendly-resources/web-usability/effective-link-text.shtml nice article] summarizing the best use of links. The article also references many other similar articles.

Hover effects can be useful and attractive, but with a stylus-oriented browser, you cannot practically hover the cursor at all.

We all want a pleasant, modern and attractive web site on both tablet and desktop. A nice solution is to make a light-colored underline that darkens as you hover. This is easily done, and supported across all modern browsers:

<code>
a,a:link,a:visited { text-decoration:none; border-bottom: 1px solid grey; color: red;}
a:hover,a:active { border-bottom: 1px solid red;}
</code>

Here visited links are not differentiated from unvisited links. It is recommended to do so, but uncommon; I suspect users wouldn't notice.
--[[User:boxofsnoo|boxofsnoo]] 02:42, 1 June 2008 (UTC)

== How can I help? ==

How can I help in this process, as one of the people responsible of the maemo.org planning at Nokia? I could help organizing the content, identifying what is out of scope or what more realistically falls in the Agenda 2010. Or I could just shut up and let you work. :) fyi, in the meantime I'm already working on the maemo.org short and mid term plans internally at Nokia. --[[User:qgil|qgil]] 19:05, 1 June 2008 (UTC)
::I don't think a little direction will repress things too much at this point, and I definitely thing it will help stimulate and focus the brainstorm. Not only because of the clearer definition of purpose, scope and direction, but also from the interest a more visible Nokia involvement would make. The end result, of course, being a much more productive session. --[[Special:Contributions/24.164.22.34|24.164.22.34]] 20:10, 1 June 2008 (UTC)

Task:100Days

2008-05-31T23:18:40Z

24.164.22.34: /* Style and format */

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'''.
* '''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.
* Don't put things which aren't feasible in '''3 months'''. For long term suggestions, consider adding them at [[2010_Agenda|maemo.org 2010]].
* Discussion of the 100 Days agenda should be held in the [[Talk:100Days|discussion page]].
|}

==Get the server and bandwidth infrastructure up to speed==
Although things have improved some (particularly after the OS2008 release), they don't seem to be keeping up well with the ever increasing numbers of tablet users, and downtime or slowness from the critical services offered by maemo.org is unacceptable.
* Mirror repository.maemo.org to ensure good uptime and fast response.
* Mirror tablets-dev.nokia.com to ensure good uptime and fast response.
* Improve the hardware and bandwidth availability behind *.maemo.org to ensure good uptime and fast response—maemo.org is too slow!

== Increase openness ==
Openness is a significant part of what makes maemo so strong, putting together a plan for addressing closed-source components (particularly those directly controlled by Nokia (e.g. low-level stuff like mce and dsme, and user-space stuff like tablet-browser and the task/statusbar applets).

=== The plan ===
* Identify all closed components in the OS at each layer:
** Initfs/direct hardware access
** Firmware used by kernel modules (Wifi, Bluetooth)
** Low-level system daemons (mce, dsme)
** User-space applications (tablet-browser, applets)
* For each package:
** Outline purpose in a dedicated wiki page.
** Describe the closed-source rationale.
*** ''Will need some form of mediawiki template for such pages --[[User:jaffa|jaffa]] 22:26, 29 May 2008 (UTC)''
* Document the process for working towards opening the component, or its specification.
* Ensuring any new closed packages get a wiki page containing their rationale.

== Software distribution ==
=== The website ===
* Implement some sort of automated single-click push-to-Downloads for Garage projects.

==== [http://www.internettablettalk.com Internet Tablet Talk] Syndication ====
* Provide an automatic way to syndicate applications to the Internet Tablet Talk Software Section (itTSS).
* Each application (version) that is syndicated on 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, hopefully, will help to 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.

==== maemo "Application Store" ====
* Actively hunt on the Net for maemo apps not yet added to Maemo Extras, talk to developers, ask and help them to commit applications to Maemo Extras. This especially applies to app porters currently active at iTT.
* Use gronmayer's scripts to create a web site that merges applications from all known repositories into a single list and lets you browse them with MicroB using HTML UI similar to N-Gage, Apple Store, etc. While it sounds ambitious, it is not difficult to do, as we always have app descriptions and icons (form .deb files) and we also have screenshots for apps hosted at Garage. Reformatting this data in a format that can be nicely presented in tablet browser is not difficult.
* Effectively replace "itTSS" with this website.

=== The repositories ===
* Again, because this can't be stressed enough, get the infrastructure behind the repositories up to speed—we need servers, we need bandwidth and we need mirrors.
* Streamline the acceptance system for Extras(-devel), (not necessarily easier or less stringent, but more straightforward and clear).
* Lay out the groundwork for a peer-review system for Extras acceptance (or devel to Extras promotion) to help ensure good quality assurance on its packages.

== Developer documentation ==
=== Clean out the cobwebs, remove the cruft ===
* Get what's still useful and mostly relevant completely up to speed for maemo 4.x.
* Archive the outdated information away from the maemo 4.x stuff.
* Mark the outdated stuff clearly.

=== Get organized ===
* Put together an easy-to-navigate, sensible index for the documentation content.
** Place references/howtos/tutorials onto one page so that developer does not need to click through several menus.
* Improve the search (google?).

=== Get focused ===
* Add porting FAQ wiki page detailing common problems developers will run into (i.e. application is killed 3 seconds after launch) and how to deal with them. Provide examples of typical GTK/Motif/etc. application changes needed to properly Hildonize the application. List ways to deal with porting of toolkit-specific functionality whether it be internationalization or mouse/keyboard input.
* Make it possible for logged-in developers to annotate any place in the documentation. Link to annotations from documentation.
* Provide an example of simple build environment *not* relying on AutoConf and its friends. A single includable makefile should suffice, when used with SB2.
* Clearly *say* in the SB readme that it is not possible to debug every application on the desktop, show how to test applications on the target device using SSH/SCP or some other means.
* Clearly define what changes is made by default on gtk : like GtkTreeView with hidden header columns by default, or image-button off ...

=== Look towards the future ===
* 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 usability.
* 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
* Maybe provide a few simple stylesheets and JavaScript libs for creating quick iPhone-like web apps running in MicroB. This should be very light, very easy to use, and targeted to casual users.

== maemo.org ==
* Re-write and expand Introduction to better serve as a useful introduction for newcomers to the platform.
** 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".
* Single sign on for maemo.org/garage.maemo.org/wiki/bugzilla -> would make community participation easier and the 'karma' calculation (if needed) too.

=== Style and format ===
* 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, a "new bugs" section with voting on the fly will boost bugzilla usage.
* Make links more standardized. New users often expect links would be underlined, even subtly, or appear to be a button of some kind. Don't rely on hover effects because the tablet can't practically use them. See [http://en.wikipedia.org/wiki/Mystery_Meat_Navigation Wikipedia on 'Mystery Meat Navigation']
** ''This is much less of an issue for a lot of people —[[User:generalantilles|generalantilles]] 19:49, 31 May 2008 (UTC)''
** ''Please stop expecting your advanced experience of new users. Read up on web accessibility, be inviting to the new users.''--[[User:boxofsnoo|boxofsnoo]] 23:08, 31 May 2008 (UTC)
*** ''I really don't see the issue (and never particularly have with this much-abused "Mystery Meat" nonsense), and I don't think it has anything to do with my experience, wikipedia (your source) uses the exact same system for link identification. . . . This should probably be taken to the talk page, anyway. —[[Special:Contributions/24.164.22.34|24.164.22.34]] 23:18, 31 May 2008 (UTC)
* 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' 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 offer 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.

== Communication ==
* 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 links them 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)''
*** ''I'm not convinced that two channels is too many, either. —[[User:generalantilles|generalantilles]] 20:04, 31 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.
* It's unclear where to report problems about packages found in the application catalog. A single bug tracker is needed, or at least a catalog that would redirect the user to the appropriate tracker from a common start page. Or we could set up a "maemo" distribution on launchpad.net, which would let us integrate with the bug trackers of individual packages.

== What the community needs to do ==
* Put together an plan of action for moving forward with a community-maintained Hacker Edition (based on what Quim said [http://www.archive.org/details/QuimGil-MaemoLinuxtag2008Update here])
* Put the pressure on developers:
** Encourage developers not using a repository to package their applications and push them to Extras(-devel), and get developers with 3rd-party repositories to close them down and push their stuff into Extras(-devel).
** Encourage developers to follow proper packaging guidelines (based on the draft [https://maemo.org/forrest-images/pdf/maemo-policy.pdf here]).
** Encourage developers launching applications on Downloads to include as much information about the application as possible (screenshots, good descriptions, good changelogs).

== 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)
* Update the vmware appliance with sb2 and python2.5 setted. And more publicity on the vmware appliance, as there is already one on garage, but many don't know it.

Task:2010 Agenda

2008-05-30T15:32:53Z

24.164.22.34: /* Maemo developer resources */

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,contact list, and tasks: A well integrated framework (with binding for many languages such python).
** Possibly related to and syncable between Nokia phone models - as well as online. PIM data should be available everywhere.
* 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 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

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.--[[User:peterschneider|peterschneider]] 10:03, 30 May 2008 (UTC)