Maemo Wiki Mirror - User contributions [en]

User:Smancke

2008-08-07T12:07:47Z

212.79.178.249: New page: Image:SebastianMancke.jpg [http://maemo.org/profile/view/smancke.html]

[[Image:SebastianMancke.jpg]]

[http://maemo.org/profile/view/smancke.html]

Maemo Summit 2008

2008-08-07T12:05:23Z

212.79.178.249: /* Saturday 20 */

[[image:C-logo_claim_blue.png‎|right]]

'''Join the first Maemo Summit'''

'''Berlin, September 19-20''' @ [http://c-base.org/ c-base] - right after http://www.osimworld.com

'''[https://maemo.org/news/events/registrations/register/2f91448248e711dd8bcbb7b26102ad49ad49.html Free registration]''' - '''[http://maemo.org/news/events/maemo_summit-001/ Who is attending]'''

Know more about Nokia's Linux platform and its evolution. Meet the core team, 3rd party professional developers and key community contributors. Showcase and discuss your work. Learn, share, hack. And have fun!

The [http://www.osimworld.com Open Source in Mobile World] conference is an interesting venue to know more about the business and technical context of the Maemo platform. Nokia is active in this event and invites the Maemo community to join it. After the conference we propose the first Maemo Summit calling to all contributors.

== Schedule ==

The program is still open. You can propose improvements in the [[Talk:Maemo summit 2008|discussion]] page.

'''The sessions and names are confirmed but the day/time they are scheduled might still change.'''

{| width="100%" border="1" cellpadding="5" cellspacing="0" bordercolor="#000000"
|+
=== Friday 19 ===
|-
| width="112" | '''9:00'''
| colspan="3" | '''Opening doors'''
|-
| '''9:30'''
| colspan="3" | '''Welcome!''', by [http://maemo.org/profile/view/jaaksi/ Ari Jaaksi] (VP - Maemo Software @ Nokia)
|-
| '''10:00'''
| colspan="3" | '''The outside view''', by [http://dailythemes.wordpress.com/ Jay Sullivan] ([http://www.mozilla.com/ Mozilla Corp.])
|-
| '''10:30'''
| colspan="3" | '''Hildon UI Vision''', by Harri Kiljander (Director, User Experience - Maemo Software @ Nokia)
|-
| '''11:00'''
| colspan="3" | '''What Maemo users want''', by [http://tabletblog.com/2008/05/3rd-anniversary-community-spotlight.html Reggie Suplido] ([http://www.internettablettalk.com/ Internet Tablet Talk]) and [http://www.neoncherry.com/ Krisse] ([http://tabletschool.blogspot.com/ Internet Tablet School])
|-
| '''11:30'''
| colspan="3" | '''What value can developers get out of Maemo''', by [http://maemo.org/profile/view/peterschneider.html Peter Schneider] (Head of Product Marketing, Maemo Software @ Nokia)
|-
| '''12:00'''
| colspan="3" | '''Break.'''
|-
| '''12:15'''
| colspan="3" | <p>'''Lightning sessions''', 5 min each + up to 1 extra min of grace. No more, no less. '''More slots left'''. [[Talk:Maemo_Summit_2008#Lightning_.2Aidea.2A_sessions|Lightning ideas]] are welcome too. List your proposal below keeping the format. Don't worry about how many sessions fit in this time slot, we will have an additional lightning session at 18h if there are more sessions proposed.
# Reserved for Yannick Pellet (5 min)
# [http://liquid.googlepages.com/lcuk liqbase], by Gary Birkett ([http://maemo.org/profile/view/lcuk.html lcuk])
# Converting videos on Linux using [http://mediautils.garage.maemo.org/tablet-encode.html tablet-encode], by Andrew Flegg ([http://maemo.org/profile/view/jaffa/ Jaffa])
# [http://www.internettablettalk.com/forums/showthread.php?t=21629 Debian in a chroot on the tablet], demo by Alan Bruce (qole).
# Maemo Bug Jar: Origins, Results, and Future Plans, by Stephen Gadsby ([http://maemo.org/profile/view/sjgadsby/ sjgadsby]).
# Reality or Vision? - The Nokia tablets for mobile and desktop use. LiveDemo/Presentation with [http://xsisusb.garage.maemo.org/ USB2VGA Adapter], bluetooth [http://anyremote.sourceforge.net/ anyremote] control by [http://www.linuxvision.de/ Uwe Koch]. ([http://maemo.org/profile/view/asys3/ asys3]).
# [http://samoff.com/maemoui/ An Unofficial Guide to Creating a Most Excellent maemo User Interface], by [[User:Timsamoff |Tim Samoff]].
# [http://esbox.garage.maemo.org/ ESBox] and [http://pluthon.garage.maemo.org/ Pluthon] '''Eclipse''' plugins: how to use Eclipse to develop Maemo applications, bye [[User:andy80|Andrea Grandi]].
# Teaser: maemo development using [http://illumination.sf.net Illumination] by [[User:framstag|Tim Teulings]].
# Cloud storage: Improve you app by syncing with internet services like Google Docs or Picasaweb by [[User:brontide|Eric Warnke]]
# Podcasts on NITs with [http://maemo.gpodder.org/ gPodder] and [http://thpinfo.com/2008/panucci/ Panucci] by Thomas Perl ([http://maemo.org/profile/view/thp.html thp])
# Mobile Medical Speech Translator (MedSLT): Multilingual Multimodal Speech Translator tailored for the medical domain by [[User:ntsourak|Nikos Tsourakis]]

|-
| '''14:00'''
| colspan="3" | '''Lunch!'''
|-
| rowspan="2" | '''15:00'''
| colspan="3" | '''Meet the Maemo SW developers''' (a representation of the main platform and OSS teams developing Maemo @ Nokia + special guests)
|-
| width="33%" | '''Desktop''' by Rodrigo Novo + Matthew Allum (OpenedHand)
| width="33%" | '''Connectivity''' by [http://maemo.org/profile/view/kvalo.html Kalle Valo]
| width="33%" | '''Development Platform''' by [http://maemo.org/profile/view/bijjal/ Soumya Bijjal], [http://maemo.org/profile/view/kaltsi/ Juha Kallioinen] (tbc), [http://maemo.org/profile/view/marcell/ Marcell Lengyel], [http://maemo.org/profile/view/qgil.html Quim Gil]
|-
| '''16:00'''
| width="33%" | '''Browser''' by [http://maemo.org/profile/view/andreypetrov.html Andrey Petrov], [http://maemo.org/profile/view/timeless.html timeless]
| width="33%" | '''Real-Time Communication''' by [http://maemo.org/profile/view/kh_naba/ Naba Kumar] (tbc), [http://maemo.org/profile/view/mzabaluev/ Mikhail Zabaluev] (tbc)
| width="33%" | '''Technology & Architecture''' by [http://maemo.org/profile/view/jtukkine/ Juha Tukkinen], [http://maemo.org/profile/view/bittinen/ Mika Leppinen]
|-
| '''17:00'''
| width="33%" | '''Core System''' by Kai Svahn (tbc), [http://maemo.org/profile/view/nakkebar/ Eero Tamminen], [http://maemo.org/profile/view/igor_stoppa.html Igor Stoppa], [http://maemo.org/profile/view/poussa.html Sakari Poussa]
| width="33%" | '''Multimedia''' by [http://maemo.org/profile/view/ensonic.html Stefan Kost], [http://maemo.org/profile/view/luc/ Luc Pionchon]
| width="33%" | '''[[Desktop_Search_Hackfest|Desktop Search Hackfest]]''' link, by [http://maemo.org/profile/view/konttori/ Urho Konttori], [http://maemo.org/profile/view/ifrade/ Iván Frade] + Jamie McCracken (Tracker)
|-
| '''18:00'''
| colspan="3" | '''Chill out.'''
* Dinner, music, drinks tbd.
* Dress code recommended: t-shirt with the maemo.org logo of [[Maemo.org_logo_contest_submissions|your choice]]. DISCLAIMER: can't be the winner logo. ;)
: Now that the new logo has been chosen, what exactly does this mean? --[[User:timsamoff|timsamoff]] 12:24, 5 August 2008 (UTC)
:: Wear a t-shirt with a maemo.org logo that you like from the competition. The official one isn't allowed ;) --[[User:xfade|xfade]] 14:47, 5 August 2008 (UTC)
::: what if you liked the official one? --[[User:dneary|Dave Neary]] 22:14, 6 August 2008 (UTC)
|}

{| width="100%" border="1" cellpadding="5" cellspacing="0" bordercolor="#000000"
|+

===Saturday 20===

I'm still working on a better way of scheduling this. Please feel free to email [[User:brontide|me]] or post on the discussion page if you have input. This is a work in progress, if you have good topic for community day I will find a way to schedule you in.

|-
| width="53" | '''9:00'''
| colspan="3" | '''Opening doors''' and wlan.
|-
| '''9:30'''
| colspan="3" | '''maemo.org after [[100Days|100 Days]]''', by [http://flors.wordpress.com/ Quim Gil] (marketing manager, open source - Maemo Software @ Nokia)
|-
| '''10:00'''
| colspan="3" | '''Introducing the [[Task:Community Council|Maemo Community Council]]''' (assuming there is one), by the members.
|-
| '''10:30'''
| colspan="3" | '''"We are not the Users": The hate and love behind the custom User experiences on Maemo.''' My goal is to talk about why be so different, why we ran from GTK, what are the motivations to do things in a so different way, the drawbacks and benefits of custom user experiences and the most important law for us on interaction designer: We are not the users, and why we must look at the problem with their eyes, even when we think it's not as smart as we would do it (or we think we could do it). Also a little bit of how to combine designers and developers on a same team as we did with Canola, Carman and the future maemo projects coming from INDT. By [[User:handful|Marcelo eduardo]]
|-
| width="53" | '''11:00'''
| colspan="3" | '''BoF: Future of maemo.org extras''', by Niels (and Ed?)
|-
| '''11:30'''
| colspan="3" | '''Lightning sessions''', 5 min each + up to 1 extra min of grace. No more, no less.
# '''mCalendar and mContact''': advanced syncing with google services [[User:khertan|Benoît HERVIER]]
# '''Screencasing''': x11vnc and pyvnc2swf bring visual documentation to users by [[User:brontide|Eric Warnke]]
# '''py2deb''': packaging your app onboard using py2deb and extras autobuilder [[User:khertan|Benoît HERVIER]]
# '''STIX''': Maemo Open Source test framework for Unit/Integration testing by Antti Heimola (Nokia)
# '''Maemo in police cars''': presentation of an embedded project based on N800's [[User:smancke|Sebastian Mancke]]
# Placeholder for Saturday sessions
|-
| '''12:00'''
| colspan="3" | '''Break'''
|-
| '''TRACKS'''
| width="33%" | '''Community/Discussion'''
| width="33%" | '''Development'''
| width="33%" | '''Core Platform'''
|-
| '''12:30'''
| width="33%" | '''Nokia & Productivity Tools''', by Miika Kuha
| width="33%" | '''Packaging and publishing software'''
| width="33%" | '''[http://blog.haerwu.biz/2008/08/01/nokia-n8x0-emulation-part-ii/ Maemo in QEMU N8x0 emulation:]''' what it is, how to use, what for can it be used. [[User:hrw|Marcin 'hrw' Juszkiewicz]]
|-
| '''13:30'''
| width="33%" | '''[http://dev.openbossa.org/trac/mamona Mamona] & Maemo: 2 way contribution (How to learn and grow up together)''', by Mamona developers from INdT.
| width="33%" | Rountable on porting application to and exploiting the advantages of the maemo platform. lead by [[User:anidel|anidel]]
| width="33%" | '''maemo.org extras Package Cleanup Sprint'''
|-
| '''13:30'''
| width="33%" | '''Building a Business on Maemo:''' At [http://frogmetrics.com Frogmetrics] we're building a real time customer feedback system on the Maemo platform. Come participate in a discussion about using tablets and the Maemo platform to build sustainable products and profitable businesses. [[User:dob|Doug Petkanics]]
| width="33%" | '''Using [http://mud-builder.garage.maemo.org/ mud-builder] to build packages''', by [[User:Jaffa|Jaffa]].
| width="33%" | '''[http://clutter-project.org/ Clutter]''', by [http://butterfeet.org/ Matthew Allum] ([http://o-hand.com/ OpenedHand])
|-
| '''14:00'''
| colspan="3" | '''Lunch!'''
|-
| '''15:00'''
| width="33%" | -
| width="33%" | '''Embedded Webapps''' Using webpy framework for on tablet web services by [[user:fpp]]
| width="33%" | DSP Programming: Introduction to DSP programming with examples of where and how, problems that might be met, how to use the DSP Gateway, data transfer, etc. [[User:lardman|Simon Pickering]]
|-
| '''15:30'''
| width="33%" | '''"[http://samoff.com/maemoui/ An Unofficial Guide to Creating a Most Excellent maemo User Interface]": Help make it ''official!''''' I'd like to open the doc up for community input and editing. Let's come together to create some truly "excellent" standards for dealing with user-centered UI design within the Maemo development community, by, [[User:Timsamoff |Tim Samoff]].
| width="33%" | '''Introduction To Telepathy:''' Components and use on the maemo platform. by Marco Barisione
| width="33%" | BoF session an idea for software that provides vector-based map data to maemo Mapper without compromising the existing raster-based design of Maemo Mapper. Soliciting feedback and developers for the project. by [[user:gnuite]]
|-
| '''16:00'''
| width="33%" | '''[[Bugsquad]] meeting'''
| width="33%" | '''Qt Maemo-Hildon Port & How to Develop Qt Application for the Maemo Platform''', by [[User:kate |Kate Alhola]] & [[User:gnuton |Antonio Aloisio]].
| width="33%" | '''Introduction to WebKit''' Come see WebKit's internals, 2 of its ports (Gtk and Qt) and why it is cool to hack. by Pierre-Luc Beaudoin (Collabora)
|-
| '''16:30'''
| width="33%" | -
| width="33%" | '''Introduction to Google Data API's''': An introduction to Python gdata bindings that can allow for easy interaction between you app and Google services. by [[User:Brontide|Eric Warnke]]
| width="33%" | '''maemo.org website redesign meeting''': A meeting to specify the design requirements for restyling the maemo.org website (reference: [[Task:Improving_maemo.org#maemo.org_homepage_refresh|Homepage Refresh]] & [[Task:Maemo.org_facelift|maemo.org Facelift]]). by [[User:xfade|Niels Breet]]
|-
| '''17:00'''
| colspan="3" | [[2010 Agenda|'''Maemo 2010''']]: Brainstorming session discussing current status / future desires for the Maemo platform. Where do we want to go in the next 24 months? What can we learn and share from other mobile platforms? Bring the whole community together to get input.
|-
| '''18:00'''
| colspan="3" | '''End.'''
|}

== Venue ==

The Maemo Summit is held in the headquarter of '''[http://www.c-base.org c-base]''' and the contiguous [http://www.eti-berlin.de/ eti Schauspielschule Berlin].

c-base is a non-profit association which has about 300 members. The purpose of this association is to increase knowledge and know-how regarding computer software, hardware and data networks ([http://en.wikipedia.org/wiki/C-base more]). eti Berlin is a school of actors based in a building with several rooms and a total surface available of 1.200m<sup>2</sup>. The perfect mix, full of creativity!

See [http://share.ovi.com/channel/qgil.public the videos].

c-base is in the very Mitte of Berlin. [http://maps.google.co.uk/maps?ie=UTF-8&oe=utf-8&rls=com.ubuntu:en-GB:unofficial&client=firefox-a&um=1&q=c-base&near=Berlin,+Germany&fb=1&cid=0,0,5828762841994571845&sa=X&oi=local_result&resnum=1&ct=image Map]

== Participants ==
'''[https://maemo.org/news/events/registrations/register/2f91448248e711dd8bcbb7b26102ad49ad49.html REGISTER]'''

It's the first Maemo Summit and it is good to know in advance who plans to attend, to fine tune practicalities and have enough space, connection, drinks, food.

Yes, the entrance is free. Registration is still requested for planning purposes.

== Travel ==
See [[Maemo_Summit_2008/Travel|when people are arriving in and leaving Berlin]].

[[Talk:Maemo_Summit_2008#Travel|Apparently]] there are options as affordable as 20€ including taxes from Stansted! [[Talk:Maemo_Summit_2008#Travel|Share your travel tips]] from different locations.

== Accommodation ==
See [[Maemo Summit 2008/Accommodation]].

== Sponsoring community contributors ==

See [[Maemo Summit 2008/Sponsorship]].

== Maemo in the OSiM program ==
See [[Maemo in OSiM World 2008]].

== Organization ==
See [[Maemo_Summit_2008/Organization]]. Volunteers needed!

== Links ==

Feel free to share/spread/forward/email...

* [http://upcoming.yahoo.com/event/839617/ Maemo summit on Upcoming!]
* [http://www.facebook.com/event.php?eid=16582874206 Maemo summit on Facebook - requires FB registration]
* [http://www.internettablettalk.com/forums/showthread.php?t=21569 Maemo summit discussion at Internet Tablet Talk]
* [http://lwn.net/Calendar/Monthly/2008-09/ LWN Calendar]

[[Events]]

Task:100Days

2008-06-06T09:00:39Z

212.79.178.249: /* Increasing transparency */

This page is meant to brainstorm the '''100 Days Action Plan''' for maemo.org. Please remember that it's about the maemo.org community, not the Nokia Internet Tablets.

{| 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]].
|}

=Community-led action plan process=
The result of this brainstorm, once ideas start firming up in the sections below, should be:
* A set of [http://meta.wikimedia.org/wiki/Help:Template mediawiki templates] for creating consistency in...
* A page for each of the sections below (e.g. [[Increasing transparency]]) containing:
** a detailed step-by-step plan for what will be delivered within 100 days
** a list of community members committed to providing it (say 2-6?)
** a community member as notional leader, responsible for overall delivery of that stream
** sign-off by [[User:qgil|qgil]] as community manager that he views it as constructive

Then, once the brainstorm has completed:
# Every 20 days, there should be:
## a status report wiki document coalescing all the streams' progress
## an IRC meeting of the stream leaders/[[User:qgil|qgil]]/anyone else to co-ordinate overall progress.

It would then be up to each mini-team to communicate and flesh-out their commitment within the first period, and then deliver it over the remaining period.

=Pre-agreed tasks=

== Defining maemo ==
{{main|Task:Defining maemo}}

Cristal clear definitions of maemo, maemo.org, OS2008 and so on.

==Fast server==
{{main|Task:Fast Server}}

Browsing and downloading from maemo.org should be simply fast. No excuses.

== Increasing transparency & openess ==
{{main|Increasing transparency}}
* Identifying closed-source components and the reasons why, addressing the community's concerns over openness.
* Formulating a clear statement by the comunity, that we expect Nokia to release more and more of the closed components as free software and this is our premise to enhance the comunity activity

== [http://www.internettablettalk.com Internet Tablet Talk] Collaboration ==
{{main|Task:ITt Collaboration}}

maemo.org and ITt services should integrate much better i.e. maemo.org Downloads syndicated in ITt and ITt users getting maemo.org karma.

== Consolidation of extras ==
{{main|Task:Consolidation of extras}}

The extras repository needs to become the single reference for developers willing to reach end users at large.

== Improving maemo.org ==
{{main|Improving maemo.org}}
maemo.org needs improvements in usability, content, format and style.

=== Content cleanup ===
{{main|Task:Content Cleanup}}

Dress up the most important content, dump what is not relevant, handle via wiki the rest.

== Roadmap for the maemo platform ==
{{main|Task:maemo roadmap}}

A maemo roadmap for developers, disclosing information about open source component and developer libraries.

== Community Council ==
{{main|Task:Community Council}}

A process for electing a small "Community Council" should be created and elections held.

== More pre-agreed tasks ==
Help planning them further and moving them to an own page.

* 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.
:''Both points agreed.--[[User:qgil|qgil]] 07:45, 2 June 2008 (UTC)''

= Still under discussion =
Please help defining, approving, discarding, postposing, etc these proposals. Their current status is Not Agreed, and they are likely to be out of the 100 Days unless they are actively pushed now.

== Garage improvements ==
* Implement some sort of automated single-click push-to-Downloads for Garage projects.
:''Interesting idea. What about the feasibility? Niels? Ferenc? In any case integrating Garage with Downloads make a lot of sense, and the question is whether this would fit in the 100 Days or later.--[[User:qgil|qgil]] 06:59, 2 June 2008 (UTC)''
::''I think we need to prevent (the need for) single file download as much as possible, but rather provide a way of uploading those packages into the extras repository directly from garage. This way people can also download the applications from the Application Manager. --[[User:xfade|xfade]] 13:20, 2 June 2008 (UTC)''
:::''More generally speaking, maybe something like single-click (or two, or three, or a dozen, but you get the picture) project management from Garage for everything? —[[User:generalantilles|generalantilles]] 16:09, 2 June 2008 (UTC)"
::''What I had understood (without reading and thinking much, I reckon) was a single click thingy for developers to upload updated packages in Garage and in a single click get the packages in extras and the update reflected in the Downloads section. Now I see that the request is probably about something different and what I'm thinking of is perhaps a bit too much for the next 100 Days. Should we move this then to 2010 Agenda under a generic "Garage-extras-Downloads integration"?''--[[User:qgil|qgil]] 20:11, 4 June 2008 (UTC)

== Bug tracking future plan ==

* 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.
:''Nokia is open to discuss any possibility of integration of maemo.org with third parties i.e. ITt and also using any external service i.e. launchpad.net. We can commit to overall plans for the 100 Days exercise but not on execution. Having a better and common understabnding of how this steps would fall in the 2010 Agenda would definitely help to see what are the right first steps.--[[User:qgil|qgil]] 07:45, 2 June 2008 (UTC)''

== Proposal to maintain legacy ==
* Put together a 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])
:''Having a specific proposal agreed by the community would definitely help.--[[User:qgil|qgil]] 07:50, 2 June 2008 (UTC)''

Task:100Days

2008-06-06T08:51:55Z

212.79.178.249: /* Increasing transparency */

This page is meant to brainstorm the '''100 Days Action Plan''' for maemo.org. Please remember that it's about the maemo.org community, not the Nokia Internet Tablets.

{| 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]].
|}

=Community-led action plan process=
The result of this brainstorm, once ideas start firming up in the sections below, should be:
* A set of [http://meta.wikimedia.org/wiki/Help:Template mediawiki templates] for creating consistency in...
* A page for each of the sections below (e.g. [[Increasing transparency]]) containing:
** a detailed step-by-step plan for what will be delivered within 100 days
** a list of community members committed to providing it (say 2-6?)
** a community member as notional leader, responsible for overall delivery of that stream
** sign-off by [[User:qgil|qgil]] as community manager that he views it as constructive

Then, once the brainstorm has completed:
# Every 20 days, there should be:
## a status report wiki document coalescing all the streams' progress
## an IRC meeting of the stream leaders/[[User:qgil|qgil]]/anyone else to co-ordinate overall progress.

It would then be up to each mini-team to communicate and flesh-out their commitment within the first period, and then deliver it over the remaining period.

=Pre-agreed tasks=

== Defining maemo ==
{{main|Task:Defining maemo}}

Cristal clear definitions of maemo, maemo.org, OS2008 and so on.

==Fast server==
{{main|Task:Fast Server}}

Browsing and downloading from maemo.org should be simply fast. No excuses.

== Increasing transparency ==
{{main|Increasing transparency}}
* Identifying closed-source components and the reasons why, addressing the community's concerns over openness.
* Formulating a clear statement by the comunity, that we expect Nokia to release more and more of the closed components as free software.

== [http://www.internettablettalk.com Internet Tablet Talk] Collaboration ==
{{main|Task:ITt Collaboration}}

maemo.org and ITt services should integrate much better i.e. maemo.org Downloads syndicated in ITt and ITt users getting maemo.org karma.

== Consolidation of extras ==
{{main|Task:Consolidation of extras}}

The extras repository needs to become the single reference for developers willing to reach end users at large.

== Improving maemo.org ==
{{main|Improving maemo.org}}
maemo.org needs improvements in usability, content, format and style.

=== Content cleanup ===
{{main|Task:Content Cleanup}}

Dress up the most important content, dump what is not relevant, handle via wiki the rest.

== Roadmap for the maemo platform ==
{{main|Task:maemo roadmap}}

A maemo roadmap for developers, disclosing information about open source component and developer libraries.

== Community Council ==
{{main|Task:Community Council}}

A process for electing a small "Community Council" should be created and elections held.

== More pre-agreed tasks ==
Help planning them further and moving them to an own page.

* 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.
:''Both points agreed.--[[User:qgil|qgil]] 07:45, 2 June 2008 (UTC)''

= Still under discussion =
Please help defining, approving, discarding, postposing, etc these proposals. Their current status is Not Agreed, and they are likely to be out of the 100 Days unless they are actively pushed now.

== Garage improvements ==
* Implement some sort of automated single-click push-to-Downloads for Garage projects.
:''Interesting idea. What about the feasibility? Niels? Ferenc? In any case integrating Garage with Downloads make a lot of sense, and the question is whether this would fit in the 100 Days or later.--[[User:qgil|qgil]] 06:59, 2 June 2008 (UTC)''
::''I think we need to prevent (the need for) single file download as much as possible, but rather provide a way of uploading those packages into the extras repository directly from garage. This way people can also download the applications from the Application Manager. --[[User:xfade|xfade]] 13:20, 2 June 2008 (UTC)''
:::''More generally speaking, maybe something like single-click (or two, or three, or a dozen, but you get the picture) project management from Garage for everything? —[[User:generalantilles|generalantilles]] 16:09, 2 June 2008 (UTC)"
::''What I had understood (without reading and thinking much, I reckon) was a single click thingy for developers to upload updated packages in Garage and in a single click get the packages in extras and the update reflected in the Downloads section. Now I see that the request is probably about something different and what I'm thinking of is perhaps a bit too much for the next 100 Days. Should we move this then to 2010 Agenda under a generic "Garage-extras-Downloads integration"?''--[[User:qgil|qgil]] 20:11, 4 June 2008 (UTC)

== Bug tracking future plan ==

* 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.
:''Nokia is open to discuss any possibility of integration of maemo.org with third parties i.e. ITt and also using any external service i.e. launchpad.net. We can commit to overall plans for the 100 Days exercise but not on execution. Having a better and common understabnding of how this steps would fall in the 2010 Agenda would definitely help to see what are the right first steps.--[[User:qgil|qgil]] 07:45, 2 June 2008 (UTC)''

== Proposal to maintain legacy ==
* Put together a 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])
:''Having a specific proposal agreed by the community would definitely help.--[[User:qgil|qgil]] 07:50, 2 June 2008 (UTC)''

Task:100Days

2008-06-06T08:51:32Z

212.79.178.249: /* Increasing transparency */

This page is meant to brainstorm the '''100 Days Action Plan''' for maemo.org. Please remember that it's about the maemo.org community, not the Nokia Internet Tablets.

{| 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]].
|}

=Community-led action plan process=
The result of this brainstorm, once ideas start firming up in the sections below, should be:
* A set of [http://meta.wikimedia.org/wiki/Help:Template mediawiki templates] for creating consistency in...
* A page for each of the sections below (e.g. [[Increasing transparency]]) containing:
** a detailed step-by-step plan for what will be delivered within 100 days
** a list of community members committed to providing it (say 2-6?)
** a community member as notional leader, responsible for overall delivery of that stream
** sign-off by [[User:qgil|qgil]] as community manager that he views it as constructive

Then, once the brainstorm has completed:
# Every 20 days, there should be:
## a status report wiki document coalescing all the streams' progress
## an IRC meeting of the stream leaders/[[User:qgil|qgil]]/anyone else to co-ordinate overall progress.

It would then be up to each mini-team to communicate and flesh-out their commitment within the first period, and then deliver it over the remaining period.

=Pre-agreed tasks=

== Defining maemo ==
{{main|Task:Defining maemo}}

Cristal clear definitions of maemo, maemo.org, OS2008 and so on.

==Fast server==
{{main|Task:Fast Server}}

Browsing and downloading from maemo.org should be simply fast. No excuses.

== Increasing transparency ==
{{main|Increasing transparency}}

* Identifying closed-source components and the reasons why, addressing the community's concerns over openness.
* Formulating a clear statement by the comunity, that we expect Nokia to release more and more of the closed components as free software.

== [http://www.internettablettalk.com Internet Tablet Talk] Collaboration ==
{{main|Task:ITt Collaboration}}

maemo.org and ITt services should integrate much better i.e. maemo.org Downloads syndicated in ITt and ITt users getting maemo.org karma.

== Consolidation of extras ==
{{main|Task:Consolidation of extras}}

The extras repository needs to become the single reference for developers willing to reach end users at large.

== Improving maemo.org ==
{{main|Improving maemo.org}}
maemo.org needs improvements in usability, content, format and style.

=== Content cleanup ===
{{main|Task:Content Cleanup}}

Dress up the most important content, dump what is not relevant, handle via wiki the rest.

== Roadmap for the maemo platform ==
{{main|Task:maemo roadmap}}

A maemo roadmap for developers, disclosing information about open source component and developer libraries.

== Community Council ==
{{main|Task:Community Council}}

A process for electing a small "Community Council" should be created and elections held.

== More pre-agreed tasks ==
Help planning them further and moving them to an own page.

* 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.
:''Both points agreed.--[[User:qgil|qgil]] 07:45, 2 June 2008 (UTC)''

= Still under discussion =
Please help defining, approving, discarding, postposing, etc these proposals. Their current status is Not Agreed, and they are likely to be out of the 100 Days unless they are actively pushed now.

== Garage improvements ==
* Implement some sort of automated single-click push-to-Downloads for Garage projects.
:''Interesting idea. What about the feasibility? Niels? Ferenc? In any case integrating Garage with Downloads make a lot of sense, and the question is whether this would fit in the 100 Days or later.--[[User:qgil|qgil]] 06:59, 2 June 2008 (UTC)''
::''I think we need to prevent (the need for) single file download as much as possible, but rather provide a way of uploading those packages into the extras repository directly from garage. This way people can also download the applications from the Application Manager. --[[User:xfade|xfade]] 13:20, 2 June 2008 (UTC)''
:::''More generally speaking, maybe something like single-click (or two, or three, or a dozen, but you get the picture) project management from Garage for everything? —[[User:generalantilles|generalantilles]] 16:09, 2 June 2008 (UTC)"
::''What I had understood (without reading and thinking much, I reckon) was a single click thingy for developers to upload updated packages in Garage and in a single click get the packages in extras and the update reflected in the Downloads section. Now I see that the request is probably about something different and what I'm thinking of is perhaps a bit too much for the next 100 Days. Should we move this then to 2010 Agenda under a generic "Garage-extras-Downloads integration"?''--[[User:qgil|qgil]] 20:11, 4 June 2008 (UTC)

== Bug tracking future plan ==

* 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.
:''Nokia is open to discuss any possibility of integration of maemo.org with third parties i.e. ITt and also using any external service i.e. launchpad.net. We can commit to overall plans for the 100 Days exercise but not on execution. Having a better and common understabnding of how this steps would fall in the 2010 Agenda would definitely help to see what are the right first steps.--[[User:qgil|qgil]] 07:45, 2 June 2008 (UTC)''

== Proposal to maintain legacy ==
* Put together a 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])
:''Having a specific proposal agreed by the community would definitely help.--[[User:qgil|qgil]] 07:50, 2 June 2008 (UTC)''

Task:2010 Agenda

2008-06-06T08:41:35Z

212.79.178.249: /* Standards */

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'''.
* Please keep things '''on-topic'''.
* '''Hardware requests''' are entirely ''out-of-scope'' and will be removed by community members trying to keep this page focused and on-topic.
* '''Software requests''' which would be trivial for a third party to provide—or are already on the roadmap—are ''out-of-scope'' and will be removed by community members trying to keep this page focused and on-topic.
* Discussion of the 2010 Agenda should be held in the [[Talk:2010 Agenda|discussion page]].
* If you think your suggestion should be done in the '''next 100 days''', please post it in the [[100Days|Maemo.org 100 Days Action Plan]].
|}

== maemo development process ==
=== Openness, openness, openness ===
* Developing maemo towards an operating system, not depending on proprietary components to be usable
* Core libraries developed in the open by Nokia employees and maemo.org community contributors.
* Non-Nokia specification writing and approval, worked on by Nokia employees and maemo.org community contributors; discussed on public mailing lists.
* The ability to build a complete, flashable image by maemo.org community for beta testing of open components in development. (May be less necessary in an SSU-based world: TBC)
* The ability to strip a maemo-based OS down to its base and build it up again differently (for example, KDE and no Hildon).
** By 2010, installing completely different UIs should be achievable through the Application Manager.
:''There are different big topics here, worth spliting them to further discuss: open development by Nokia teams, collaboration between Nokia and community developers, ability to build and distribute maemo OS variants.--[[User:qgil|qgil]] 08:53, 2 June 2008 (UTC)''

=== IdeaStorm ===
* As suggested [http://geekpenguin.blogspot.com/2008/04/bright-idea.html here] and [http://www.internettablettalk.com/forums/showthread.php?t=19556 here], set up an IdeaStorm for maemo to cover:
** Software ideas larger in scale than Bugzilla enhancement requests, in particular, acting as a focusing agent for Bugzilla enhancement requests (e.g. IdeaStorm brainstorming session -> multiple Bugzilla enhancement requests).
** Hardware requests outside the scope of Bugzilla.
:''Isn't this more of a 100 Days action?--[[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)''

=== Standards ===
The development for mobile devices forces the developers today, to focus on one target platform with one existing device. To give maemo a future, it will be essential to apply to existing standards, as well as work with other mobile projects to create new standards, wherever possible. Beyond the principal commitment to the GNOME Mobile stack and freedesktop.org standards, we have to formulate and support APIs and services for accessing and controlling the system functionality. Maybe a standardized DBus API currently rising at [http://www.freesmartphone.org FreeSmartphone.org] would the the right way.

=== Documentation ===
* See [http://times.usefulinc.com/2003/11/25-gnomedevel Edd Dumbill's appraisal of developer.gnome.org]:
** Audience - clearly separate documentation for tablet users, application developers and core platform hackers
** Provide tutorials and quizzes for core API components
** API documents and tutorials should be dated to make it clear whether they are current
** Editor - ensure that the content is maintained, coherent, correct
** Content - identify resources which are necessary and have them written
** Evangelism - we need to have more ISDs creating software for maemo, and an outreach program is needed
--[[User:dneary|dneary]] 15:57, 4 June 2008 (UTC)

== maemo developer resources ==
* Better localization guidelines for new and existing Developers.
** Keep focused on the core of the project
** Stay unified and work out the details later
** Focus every module in a step by step instead of a free for all
** Delegate. Newcomers need the experience.
:''It is sensible to introduce a point about community Localization in the 2010 Agenda: what is expected, what would be ideal. The discussion and specific planning would be better in a specific page, though.--[[User:qgil|qgil]] 09:05, 2 June 2008 (UTC)''

* Documentation System. (Help system???)
** getting started is way to difficult and will detour many great minds
** outsource to the blogger types in the group
*** voice record "dictate to the typers"
*** video and slide w/audio help for many
** cut out the opinions where are the real facts (make an easy to find location)
** Clearer UI guidelines for 3rd party developers.
:''Introducing newcomers to the platform is definitely a core case, since we expect lots of them coming. And not with a Linux and open source background necessarely. Again, what is expected and ideal, then the details to be worked out in separate pages.--[[User:qgil|qgil]] 09:05, 2 June 2008 (UTC)''

* Development Framework. ???
* Better GPS resources. (GeoClue???)
* Development Tools and Utilities for Linux, OS X and Windows.
** GUI development package (reduce learning curve)
** Better feedback on testing of packages
** make simple system for ideas to be tried
** Better emulator on PC. Comes with most default applications of NIT and is based on a newer QEmu (at least one that supports Virtualization Extensions).
* Better modern native languages support - like Vala and D. && how to build a hello world app in C++/Vala in 10 minute (no more!)
:''Let's take what is relevant of these points for the maemo.org community and online infrastructure. For instance "Better feedback on testing of packages" and "make simple system for ideas to be tried".--[[User:qgil|qgil]] 09:05, 2 June 2008 (UTC)''

=== Ship high level building blocks ===
* Think of media server, VoIP, contact lists, camera, GPS localization. Currently developers only have the low level API's, while mostly they just want a widget that displays the mentioned data and listen to user interaction signal or device signals. This also makes these functionalities look the same in all applications using them
:''This is out of scope in the 2010 Agenda call. API and developer offering in general will improve and we might organize similar a similar brainstorming for that.--[[User:qgil|qgil]] 09:05, 2 June 2008 (UTC)''

=== Create a repository for user-created images ===

* Make the process of creating and distributing custom images for tablets easy
* Provide infrastructure for users to upload their own hacked-together images
* Provide documentation on creating flashable images to users
* Make it as easy as possible to flash removable drives, and boot from removable drives

=== Eliminate porting and allow synchronisation with upstream distributions ===

A massive challenge and limiting factor for maemo is the lack of software that has been ported. A great goal for 2010 would be to work out how to allow direct use of repositories from an upstream distribution (e.g. Debian testing armel) so packages do not have to be ported at all. Initially this might only be for command line utilities, developer utilities, libraries, etc -- leaving GUI applications for a later phase. There would still be a need for some ported packages, and some maemo-specific repositories to contain them, but the "long tail" of less frequently used packages would be made available.

Once this has been achieved, and a large number of packages are available, maemo should be able to be updated from the repositories chosen by the user: some users may choose to keep in sync with Debian stable, others with testing and some even with unstable. This means that all packages (including system core packages like libc) need to be able to be updated (possibly with disclaimers). Nokia could choose to create Nokia-specific versions of some core libraries if they want to avoid risk of library changes.

A further stage (probably beyond 2010) would be to work out how to allow kernel upgrades, without necessarily having to sacrifice the closed-source drivers for key hardware! This could, for example, involve having a (limited) set of kernels available, with key closed source components rebuilt for them by Nokia, but not tied to ITOS release schedules.

The goal is to make the platform as useful as Debian is today, at least for those who do not insist on 100% openness.

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

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

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

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

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

== Target groups analysis ==

Nice summary by Peter. Here are some analysis tables to try which might to help identify concrete tasks to get the best of people, relationships and networks (of course the tables are likely not complete) --[[User:Framstag|Framstag]].

So who are the people were are interested in to join the group? Who are the people that might be interested in the device?

* Developer
** Wants to reuse existing infrastructure => Try to better integrate with portals like www.sf.net and similar. Perhaps in the end www.mameo.org is just an anaggregator for other sides?
** Documentation, Examples, Development enviroment
** Looking for co-developers, loking for porters => resource market
** Subgroup "Gtk/Gnome developer"
*** Wants to reduce porting => Identical APIs
** Subgroup "Foreign toolkit developer"
*** Wants to better integrate their application into the platform => Have two layer APIs, one that does not depend on Gtk libraries (or at least Gtk Event loop) and one that builds on top of that layer using Gtk/Gnome primitives.
** Subgroup "Game developer"
*** Wants more GUI power
*** Wants distribution channels
*** Wants (hardware) basics for new ideas and alternative games ideas
** Subgroup "Open Source activists"
*** Have everything open
** Subgroup "Commercial developers"
*** Require comerical support
* Software Porters
** Wants to reuse existing aproaches and solutions for the big distributions
** Would like to reduce changes to application, because developers is already prepared (screen resolution, networkspecifics) => push extended APIs upstream. Make thinks easier.
* Customizer (people reselling a hardware/software variant of the device, OS, GUI)
** Wants the distribution modifyable from ground up => Make things available, more open, document more processes and tools
* Add-on Hardware suppliers
** Wants hardward documentation
** Wants more interfaces

== Software group analysis ==

* Desktop ports
* Mobility specific software (GPS, Chat, Syncing)
* Games
* Multimedia

== Future trends analysis ==

So where is the market going?

* Mobility
* Synchronisation
* Convergence

== End-user software wishlist ==
{{main|Software wish-list}}
Software requests are really '''out-of-scope''' and ''not relevant'' to this brainstorming session. Please see the main article.

== Sell community efforts to consumers to bring consumers to the community ==
The maemo community is challenged by Nokia's need to succeed on the market. Not a unique position, but somehow strange for an open project. Right now IMHO, the output is by far not visible enough to average end users, which in turn means few users are likely to become active community members in the future. "Selling" the achievements of the community is crucial: End users need to know the potential of their devices and need to become a little curious so that some of them end up being active community members.
Existing problems are known: software distribution, localisation of maemo.org, communication, …
=== The one site for end users ===
To address those problems, I suggest to basically leave things as they at maemo.org but use a totally different site to showcase to first time users what the community achieves. This could well be [http://tableteer.nokia.com Tableteer] (which would have to be improved drastically, though!), meaning that Nokia would have to play an active role and there's little room for community input. It could also be (preferred) a Nokia funded community page or a sub-project of maemo.org, provided that Nokia really directs users there.
The point is to have it
* localised (the way we treat non English-speaking customers is incredibly bad ATM)
* feature selected downloads with whole articles
* offer short and superficial "How-To"- and "Did You Know?"-style articles and tablet-optimised videos, always including "Where to find more software"
* syndicate everything from the high-quality extras-repository in a list with screenshots, localised descriptions etc.
* link to further community resources, preferably those in the language currently requested by the user agent if available
In short: It should be friendly, understandable, deliberately incomplete, offer only the very best the community can give at any time. Above all, it should make users want more and make users want to know more.
This should help take the strain from maemo.org about localisation, how to present software etc. - maemo.org can then safely focus on developers and very advanced users.
:''Yes, all true. As you say this is homework for Nokia and it should be out of maemo.org in order to guarantee community independence and freedom to do things (even wrong or broken things) in this context. There have been some steps in the consumer marketing directions i.e. Tableteer or http://nokia.com/os2008 . More needs to be done and the community aspect of maemo is one of the things that should be stressed as a unique offer for end users beyond the device they bought and the software that came with it. This task is already in our plans, thank you for your input on that.--[[User:qgil|qgil]] 09:11, 4 June 2008 (UTC)
::''Good to hear it is on the agenda! Pls. just reconsider the matter-of-factly "this is homework for Nokia"-part. It can be, yes, but so far, they didn't come up with very useful solutions. After 3 years (or five, talking about 2010) it could be time for the community to step forward and present itself better. -- [[User:ossi|ossi]] 11:20, 4 June 2008 (UTC)

Task:2010 Agenda

2008-06-06T08:36:52Z

212.79.178.249:

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'''.
* Please keep things '''on-topic'''.
* '''Hardware requests''' are entirely ''out-of-scope'' and will be removed by community members trying to keep this page focused and on-topic.
* '''Software requests''' which would be trivial for a third party to provide—or are already on the roadmap—are ''out-of-scope'' and will be removed by community members trying to keep this page focused and on-topic.
* Discussion of the 2010 Agenda should be held in the [[Talk:2010 Agenda|discussion page]].
* If you think your suggestion should be done in the '''next 100 days''', please post it in the [[100Days|Maemo.org 100 Days Action Plan]].
|}

== maemo development process ==
=== Openness, openness, openness ===
* Developing maemo towards an operating system, not depending on proprietary components to be usable
* Core libraries developed in the open by Nokia employees and maemo.org community contributors.
* Non-Nokia specification writing and approval, worked on by Nokia employees and maemo.org community contributors; discussed on public mailing lists.
* The ability to build a complete, flashable image by maemo.org community for beta testing of open components in development. (May be less necessary in an SSU-based world: TBC)
* The ability to strip a maemo-based OS down to its base and build it up again differently (for example, KDE and no Hildon).
** By 2010, installing completely different UIs should be achievable through the Application Manager.
:''There are different big topics here, worth spliting them to further discuss: open development by Nokia teams, collaboration between Nokia and community developers, ability to build and distribute maemo OS variants.--[[User:qgil|qgil]] 08:53, 2 June 2008 (UTC)''

=== IdeaStorm ===
* As suggested [http://geekpenguin.blogspot.com/2008/04/bright-idea.html here] and [http://www.internettablettalk.com/forums/showthread.php?t=19556 here], set up an IdeaStorm for maemo to cover:
** Software ideas larger in scale than Bugzilla enhancement requests, in particular, acting as a focusing agent for Bugzilla enhancement requests (e.g. IdeaStorm brainstorming session -> multiple Bugzilla enhancement requests).
** Hardware requests outside the scope of Bugzilla.
:''Isn't this more of a 100 Days action?--[[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)''

=== Standards ===
The development for mobile devices forces the developers today to focus on one target platform with one existing device. To give maemo a future, it will be essential to apply to existing standards, as well as work with other mobile projects to create new standards, wherever possible. Beyond the principal commitment to the GNOME Mobile stack and freedesktop.org standards APIs and services for accessing and controlling the system functionality is needed.

=== Documentation ===
* See [http://times.usefulinc.com/2003/11/25-gnomedevel Edd Dumbill's appraisal of developer.gnome.org]:
** Audience - clearly separate documentation for tablet users, application developers and core platform hackers
** Provide tutorials and quizzes for core API components
** API documents and tutorials should be dated to make it clear whether they are current
** Editor - ensure that the content is maintained, coherent, correct
** Content - identify resources which are necessary and have them written
** Evangelism - we need to have more ISDs creating software for maemo, and an outreach program is needed
--[[User:dneary|dneary]] 15:57, 4 June 2008 (UTC)

== maemo developer resources ==
* Better localization guidelines for new and existing Developers.
** Keep focused on the core of the project
** Stay unified and work out the details later
** Focus every module in a step by step instead of a free for all
** Delegate. Newcomers need the experience.
:''It is sensible to introduce a point about community Localization in the 2010 Agenda: what is expected, what would be ideal. The discussion and specific planning would be better in a specific page, though.--[[User:qgil|qgil]] 09:05, 2 June 2008 (UTC)''

* Documentation System. (Help system???)
** getting started is way to difficult and will detour many great minds
** outsource to the blogger types in the group
*** voice record "dictate to the typers"
*** video and slide w/audio help for many
** cut out the opinions where are the real facts (make an easy to find location)
** Clearer UI guidelines for 3rd party developers.
:''Introducing newcomers to the platform is definitely a core case, since we expect lots of them coming. And not with a Linux and open source background necessarely. Again, what is expected and ideal, then the details to be worked out in separate pages.--[[User:qgil|qgil]] 09:05, 2 June 2008 (UTC)''

* Development Framework. ???
* Better GPS resources. (GeoClue???)
* Development Tools and Utilities for Linux, OS X and Windows.
** GUI development package (reduce learning curve)
** Better feedback on testing of packages
** make simple system for ideas to be tried
** Better emulator on PC. Comes with most default applications of NIT and is based on a newer QEmu (at least one that supports Virtualization Extensions).
* Better modern native languages support - like Vala and D. && how to build a hello world app in C++/Vala in 10 minute (no more!)
:''Let's take what is relevant of these points for the maemo.org community and online infrastructure. For instance "Better feedback on testing of packages" and "make simple system for ideas to be tried".--[[User:qgil|qgil]] 09:05, 2 June 2008 (UTC)''

=== Ship high level building blocks ===
* Think of media server, VoIP, contact lists, camera, GPS localization. Currently developers only have the low level API's, while mostly they just want a widget that displays the mentioned data and listen to user interaction signal or device signals. This also makes these functionalities look the same in all applications using them
:''This is out of scope in the 2010 Agenda call. API and developer offering in general will improve and we might organize similar a similar brainstorming for that.--[[User:qgil|qgil]] 09:05, 2 June 2008 (UTC)''

=== Create a repository for user-created images ===

* Make the process of creating and distributing custom images for tablets easy
* Provide infrastructure for users to upload their own hacked-together images
* Provide documentation on creating flashable images to users
* Make it as easy as possible to flash removable drives, and boot from removable drives

=== Eliminate porting and allow synchronisation with upstream distributions ===

A massive challenge and limiting factor for maemo is the lack of software that has been ported. A great goal for 2010 would be to work out how to allow direct use of repositories from an upstream distribution (e.g. Debian testing armel) so packages do not have to be ported at all. Initially this might only be for command line utilities, developer utilities, libraries, etc -- leaving GUI applications for a later phase. There would still be a need for some ported packages, and some maemo-specific repositories to contain them, but the "long tail" of less frequently used packages would be made available.

Once this has been achieved, and a large number of packages are available, maemo should be able to be updated from the repositories chosen by the user: some users may choose to keep in sync with Debian stable, others with testing and some even with unstable. This means that all packages (including system core packages like libc) need to be able to be updated (possibly with disclaimers). Nokia could choose to create Nokia-specific versions of some core libraries if they want to avoid risk of library changes.

A further stage (probably beyond 2010) would be to work out how to allow kernel upgrades, without necessarily having to sacrifice the closed-source drivers for key hardware! This could, for example, involve having a (limited) set of kernels available, with key closed source components rebuilt for them by Nokia, but not tied to ITOS release schedules.

The goal is to make the platform as useful as Debian is today, at least for those who do not insist on 100% openness.

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

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

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

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

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

== Target groups analysis ==

Nice summary by Peter. Here are some analysis tables to try which might to help identify concrete tasks to get the best of people, relationships and networks (of course the tables are likely not complete) --[[User:Framstag|Framstag]].

So who are the people were are interested in to join the group? Who are the people that might be interested in the device?

* Developer
** Wants to reuse existing infrastructure => Try to better integrate with portals like www.sf.net and similar. Perhaps in the end www.mameo.org is just an anaggregator for other sides?
** Documentation, Examples, Development enviroment
** Looking for co-developers, loking for porters => resource market
** Subgroup "Gtk/Gnome developer"
*** Wants to reduce porting => Identical APIs
** Subgroup "Foreign toolkit developer"
*** Wants to better integrate their application into the platform => Have two layer APIs, one that does not depend on Gtk libraries (or at least Gtk Event loop) and one that builds on top of that layer using Gtk/Gnome primitives.
** Subgroup "Game developer"
*** Wants more GUI power
*** Wants distribution channels
*** Wants (hardware) basics for new ideas and alternative games ideas
** Subgroup "Open Source activists"
*** Have everything open
** Subgroup "Commercial developers"
*** Require comerical support
* Software Porters
** Wants to reuse existing aproaches and solutions for the big distributions
** Would like to reduce changes to application, because developers is already prepared (screen resolution, networkspecifics) => push extended APIs upstream. Make thinks easier.
* Customizer (people reselling a hardware/software variant of the device, OS, GUI)
** Wants the distribution modifyable from ground up => Make things available, more open, document more processes and tools
* Add-on Hardware suppliers
** Wants hardward documentation
** Wants more interfaces

== Software group analysis ==

* Desktop ports
* Mobility specific software (GPS, Chat, Syncing)
* Games
* Multimedia

== Future trends analysis ==

So where is the market going?

* Mobility
* Synchronisation
* Convergence

== End-user software wishlist ==
{{main|Software wish-list}}
Software requests are really '''out-of-scope''' and ''not relevant'' to this brainstorming session. Please see the main article.

== Sell community efforts to consumers to bring consumers to the community ==
The maemo community is challenged by Nokia's need to succeed on the market. Not a unique position, but somehow strange for an open project. Right now IMHO, the output is by far not visible enough to average end users, which in turn means few users are likely to become active community members in the future. "Selling" the achievements of the community is crucial: End users need to know the potential of their devices and need to become a little curious so that some of them end up being active community members.
Existing problems are known: software distribution, localisation of maemo.org, communication, …
=== The one site for end users ===
To address those problems, I suggest to basically leave things as they at maemo.org but use a totally different site to showcase to first time users what the community achieves. This could well be [http://tableteer.nokia.com Tableteer] (which would have to be improved drastically, though!), meaning that Nokia would have to play an active role and there's little room for community input. It could also be (preferred) a Nokia funded community page or a sub-project of maemo.org, provided that Nokia really directs users there.
The point is to have it
* localised (the way we treat non English-speaking customers is incredibly bad ATM)
* feature selected downloads with whole articles
* offer short and superficial "How-To"- and "Did You Know?"-style articles and tablet-optimised videos, always including "Where to find more software"
* syndicate everything from the high-quality extras-repository in a list with screenshots, localised descriptions etc.
* link to further community resources, preferably those in the language currently requested by the user agent if available
In short: It should be friendly, understandable, deliberately incomplete, offer only the very best the community can give at any time. Above all, it should make users want more and make users want to know more.
This should help take the strain from maemo.org about localisation, how to present software etc. - maemo.org can then safely focus on developers and very advanced users.
:''Yes, all true. As you say this is homework for Nokia and it should be out of maemo.org in order to guarantee community independence and freedom to do things (even wrong or broken things) in this context. There have been some steps in the consumer marketing directions i.e. Tableteer or http://nokia.com/os2008 . More needs to be done and the community aspect of maemo is one of the things that should be stressed as a unique offer for end users beyond the device they bought and the software that came with it. This task is already in our plans, thank you for your input on that.--[[User:qgil|qgil]] 09:11, 4 June 2008 (UTC)
::''Good to hear it is on the agenda! Pls. just reconsider the matter-of-factly "this is homework for Nokia"-part. It can be, yes, but so far, they didn't come up with very useful solutions. After 3 years (or five, talking about 2010) it could be time for the community to step forward and present itself better. -- [[User:ossi|ossi]] 11:20, 4 June 2008 (UTC)

Task:2010 Agenda

2008-06-06T08:26:10Z

212.79.178.249: /* Openness, openness, openness */

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'''.
* Please keep things '''on-topic'''.
* '''Hardware requests''' are entirely ''out-of-scope'' and will be removed by community members trying to keep this page focused and on-topic.
* '''Software requests''' which would be trivial for a third party to provide—or are already on the roadmap—are ''out-of-scope'' and will be removed by community members trying to keep this page focused and on-topic.
* Discussion of the 2010 Agenda should be held in the [[Talk:2010 Agenda|discussion page]].
* If you think your suggestion should be done in the '''next 100 days''', please post it in the [[100Days|Maemo.org 100 Days Action Plan]].
|}

== maemo development process ==
=== Openness, openness, openness ===
* Developing maemo towards an operating system, not depending on proprietary components to be usable
* Core libraries developed in the open by Nokia employees and maemo.org community contributors.
* Non-Nokia specification writing and approval, worked on by Nokia employees and maemo.org community contributors; discussed on public mailing lists.
* The ability to build a complete, flashable image by maemo.org community for beta testing of open components in development. (May be less necessary in an SSU-based world: TBC)
* The ability to strip a maemo-based OS down to its base and build it up again differently (for example, KDE and no Hildon).
** By 2010, installing completely different UIs should be achievable through the Application Manager.
:''There are different big topics here, worth spliting them to further discuss: open development by Nokia teams, collaboration between Nokia and community developers, ability to build and distribute maemo OS variants.--[[User:qgil|qgil]] 08:53, 2 June 2008 (UTC)''

=== IdeaStorm ===
* As suggested [http://geekpenguin.blogspot.com/2008/04/bright-idea.html here] and [http://www.internettablettalk.com/forums/showthread.php?t=19556 here], set up an IdeaStorm for maemo to cover:
** Software ideas larger in scale than Bugzilla enhancement requests, in particular, acting as a focusing agent for Bugzilla enhancement requests (e.g. IdeaStorm brainstorming session -> multiple Bugzilla enhancement requests).
** Hardware requests outside the scope of Bugzilla.
:''Isn't this more of a 100 Days action?--[[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)''

=== Documentation ===
* See [http://times.usefulinc.com/2003/11/25-gnomedevel Edd Dumbill's appraisal of developer.gnome.org]:
** Audience - clearly separate documentation for tablet users, application developers and core platform hackers
** Provide tutorials and quizzes for core API components
** API documents and tutorials should be dated to make it clear whether they are current
** Editor - ensure that the content is maintained, coherent, correct
** Content - identify resources which are necessary and have them written
** Evangelism - we need to have more ISDs creating software for maemo, and an outreach program is needed
--[[User:dneary|dneary]] 15:57, 4 June 2008 (UTC)

== maemo developer resources ==
* Better localization guidelines for new and existing Developers.
** Keep focused on the core of the project
** Stay unified and work out the details later
** Focus every module in a step by step instead of a free for all
** Delegate. Newcomers need the experience.
:''It is sensible to introduce a point about community Localization in the 2010 Agenda: what is expected, what would be ideal. The discussion and specific planning would be better in a specific page, though.--[[User:qgil|qgil]] 09:05, 2 June 2008 (UTC)''

* Documentation System. (Help system???)
** getting started is way to difficult and will detour many great minds
** outsource to the blogger types in the group
*** voice record "dictate to the typers"
*** video and slide w/audio help for many
** cut out the opinions where are the real facts (make an easy to find location)
** Clearer UI guidelines for 3rd party developers.
:''Introducing newcomers to the platform is definitely a core case, since we expect lots of them coming. And not with a Linux and open source background necessarely. Again, what is expected and ideal, then the details to be worked out in separate pages.--[[User:qgil|qgil]] 09:05, 2 June 2008 (UTC)''

* Development Framework. ???
* Better GPS resources. (GeoClue???)
* Development Tools and Utilities for Linux, OS X and Windows.
** GUI development package (reduce learning curve)
** Better feedback on testing of packages
** make simple system for ideas to be tried
** Better emulator on PC. Comes with most default applications of NIT and is based on a newer QEmu (at least one that supports Virtualization Extensions).
* Better modern native languages support - like Vala and D. && how to build a hello world app in C++/Vala in 10 minute (no more!)
:''Let's take what is relevant of these points for the maemo.org community and online infrastructure. For instance "Better feedback on testing of packages" and "make simple system for ideas to be tried".--[[User:qgil|qgil]] 09:05, 2 June 2008 (UTC)''

=== Ship high level building blocks ===
* Think of media server, VoIP, contact lists, camera, GPS localization. Currently developers only have the low level API's, while mostly they just want a widget that displays the mentioned data and listen to user interaction signal or device signals. This also makes these functionalities look the same in all applications using them
:''This is out of scope in the 2010 Agenda call. API and developer offering in general will improve and we might organize similar a similar brainstorming for that.--[[User:qgil|qgil]] 09:05, 2 June 2008 (UTC)''

=== Create a repository for user-created images ===

* Make the process of creating and distributing custom images for tablets easy
* Provide infrastructure for users to upload their own hacked-together images
* Provide documentation on creating flashable images to users
* Make it as easy as possible to flash removable drives, and boot from removable drives

=== Eliminate porting and allow synchronisation with upstream distributions ===

A massive challenge and limiting factor for maemo is the lack of software that has been ported. A great goal for 2010 would be to work out how to allow direct use of repositories from an upstream distribution (e.g. Debian testing armel) so packages do not have to be ported at all. Initially this might only be for command line utilities, developer utilities, libraries, etc -- leaving GUI applications for a later phase. There would still be a need for some ported packages, and some maemo-specific repositories to contain them, but the "long tail" of less frequently used packages would be made available.

Once this has been achieved, and a large number of packages are available, maemo should be able to be updated from the repositories chosen by the user: some users may choose to keep in sync with Debian stable, others with testing and some even with unstable. This means that all packages (including system core packages like libc) need to be able to be updated (possibly with disclaimers). Nokia could choose to create Nokia-specific versions of some core libraries if they want to avoid risk of library changes.

A further stage (probably beyond 2010) would be to work out how to allow kernel upgrades, without necessarily having to sacrifice the closed-source drivers for key hardware! This could, for example, involve having a (limited) set of kernels available, with key closed source components rebuilt for them by Nokia, but not tied to ITOS release schedules.

The goal is to make the platform as useful as Debian is today, at least for those who do not insist on 100% openness.

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

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

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

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

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

== Target groups analysis ==

Nice summary by Peter. Here are some analysis tables to try which might to help identify concrete tasks to get the best of people, relationships and networks (of course the tables are likely not complete) --[[User:Framstag|Framstag]].

So who are the people were are interested in to join the group? Who are the people that might be interested in the device?

* Developer
** Wants to reuse existing infrastructure => Try to better integrate with portals like www.sf.net and similar. Perhaps in the end www.mameo.org is just an anaggregator for other sides?
** Documentation, Examples, Development enviroment
** Looking for co-developers, loking for porters => resource market
** Subgroup "Gtk/Gnome developer"
*** Wants to reduce porting => Identical APIs
** Subgroup "Foreign toolkit developer"
*** Wants to better integrate their application into the platform => Have two layer APIs, one that does not depend on Gtk libraries (or at least Gtk Event loop) and one that builds on top of that layer using Gtk/Gnome primitives.
** Subgroup "Game developer"
*** Wants more GUI power
*** Wants distribution channels
*** Wants (hardware) basics for new ideas and alternative games ideas
** Subgroup "Open Source activists"
*** Have everything open
** Subgroup "Commercial developers"
*** Require comerical support
* Software Porters
** Wants to reuse existing aproaches and solutions for the big distributions
** Would like to reduce changes to application, because developers is already prepared (screen resolution, networkspecifics) => push extended APIs upstream. Make thinks easier.
* Customizer (people reselling a hardware/software variant of the device, OS, GUI)
** Wants the distribution modifyable from ground up => Make things available, more open, document more processes and tools
* Add-on Hardware suppliers
** Wants hardward documentation
** Wants more interfaces

== Software group analysis ==

* Desktop ports
* Mobility specific software (GPS, Chat, Syncing)
* Games
* Multimedia

== Future trends analysis ==

So where is the market going?

* Mobility
* Synchronisation
* Convergence

== End-user software wishlist ==
{{main|Software wish-list}}
Software requests are really '''out-of-scope''' and ''not relevant'' to this brainstorming session. Please see the main article.

== Sell community efforts to consumers to bring consumers to the community ==
The maemo community is challenged by Nokia's need to succeed on the market. Not a unique position, but somehow strange for an open project. Right now IMHO, the output is by far not visible enough to average end users, which in turn means few users are likely to become active community members in the future. "Selling" the achievements of the community is crucial: End users need to know the potential of their devices and need to become a little curious so that some of them end up being active community members.
Existing problems are known: software distribution, localisation of maemo.org, communication, …
=== The one site for end users ===
To address those problems, I suggest to basically leave things as they at maemo.org but use a totally different site to showcase to first time users what the community achieves. This could well be [http://tableteer.nokia.com Tableteer] (which would have to be improved drastically, though!), meaning that Nokia would have to play an active role and there's little room for community input. It could also be (preferred) a Nokia funded community page or a sub-project of maemo.org, provided that Nokia really directs users there.
The point is to have it
* localised (the way we treat non English-speaking customers is incredibly bad ATM)
* feature selected downloads with whole articles
* offer short and superficial "How-To"- and "Did You Know?"-style articles and tablet-optimised videos, always including "Where to find more software"
* syndicate everything from the high-quality extras-repository in a list with screenshots, localised descriptions etc.
* link to further community resources, preferably those in the language currently requested by the user agent if available
In short: It should be friendly, understandable, deliberately incomplete, offer only the very best the community can give at any time. Above all, it should make users want more and make users want to know more.
This should help take the strain from maemo.org about localisation, how to present software etc. - maemo.org can then safely focus on developers and very advanced users.
:''Yes, all true. As you say this is homework for Nokia and it should be out of maemo.org in order to guarantee community independence and freedom to do things (even wrong or broken things) in this context. There have been some steps in the consumer marketing directions i.e. Tableteer or http://nokia.com/os2008 . More needs to be done and the community aspect of maemo is one of the things that should be stressed as a unique offer for end users beyond the device they bought and the software that came with it. This task is already in our plans, thank you for your input on that.--[[User:qgil|qgil]] 09:11, 4 June 2008 (UTC)
::''Good to hear it is on the agenda! Pls. just reconsider the matter-of-factly "this is homework for Nokia"-part. It can be, yes, but so far, they didn't come up with very useful solutions. After 3 years (or five, talking about 2010) it could be time for the community to step forward and present itself better. -- [[User:ossi|ossi]] 11:20, 4 June 2008 (UTC)