Task:2010 Agenda

(Eliminate porting and allow synchronisation with upstream distributions: moved to Unsure)
m (Reverted edits by 189.191.93.73 (Talk); changed back to last version by Timsamoff)
 
(16 intermediate revisions not shown)
Line 3: Line 3:
Help defining the '''maemo.org 2010 Agenda'''. This is taken to mean the vision the community has for the state of maemo in 2010.
Help defining the '''maemo.org 2010 Agenda'''. This is taken to mean the vision the community has for the state of maemo in 2010.
-
= Agreed objectives =
+
= Objectives =
 +
Each objective consists of a list of tasks. The list of objectives here is ready for community approval but the tasks in each page need surely more iterations.
-
Please create own pages for each.
+
== Best community for mobile Linux innovation  ==
 +
{{main|Objective:Best community for mobile Linux innovation}}
 +
The best open source projects target primarily the Maemo platform.
== Release soon & often ==
== Release soon & often ==
-
 
{{main|Objective:Release soon and often}}
{{main|Objective:Release soon and often}}
Public releases of Maemo while it's being developed.
Public releases of Maemo while it's being developed.
-
 
-
[[User:Qgil|qgil]] coordinates this objective.
 
== One place to track feedback ==
== One place to track feedback ==
-
 
{{main|Objective:One place to track feedback}}
{{main|Objective:One place to track feedback}}
bugs.maemo.org to get Nokia developers involved as well as the consolidated community projects.
bugs.maemo.org to get Nokia developers involved as well as the consolidated community projects.
-
== Documentation ==
+
== Co-production of official & community documentation ==
-
* See [http://times.usefulinc.com/2003/11/25-gnomedevel Edd Dumbill's appraisal of developer.gnome.org]:
+
{{main|Objective:Co-production of official & community documentation}}
-
** Audience - clearly separate documentation for tablet users, application developers and core platform hackers
+
Nokia and the Maemo community to collaborate in the production of the documentation developers and other contributors need.
-
** 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)
+
-
 
+
-
This objective is now listed in the [https://garage.maemo.org/plugins/wiki/index.php?June2008Sprint&id=106&type=g maemo.org development backlog]. Nemein pushes but you can help out already today.
+
-
 
+
-
* 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)''
+
== Community localization ==
== Community localization ==
-
* Better localization guidelines for new and existing Developers.
+
{{main|Objective:Community localization}}
-
** Keep focused on the core of the project
+
The Maemo experience in our own language, translated by ourselves.
-
** 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)''
+
-
 
+
-
== 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
+
-
''This is a great idea, I would love to download a "media player" or a "games machine", or a "productivity tablet", etc., without worrying about downloading each individual package.  The only problem I would see with this is in losing pre-existing settings and files and programs.  I guess this would be more for deployment on new machines than updating an old one --mee 05:44, 7 June 2008 (UTC)
+
-
''
+
-
 
+
-
===Examples===
+
-
-3 configs-
+
-
--hacker
+
-
--gamer
+
-
--communicator
+
-
 
+
-
make a device that fits those requirements exactly and you have a perfect tool.  The only problem is to reach that level of quality, you need intensive user feedback,  The best way to elicit such feedback, is to concentrate on a non-technical application.  Gamer is the best example.  If you can host a number of good applications, like tuxpaint or ''Wesnoth'', the application depth alone would make the device indispensable.  Make the best portable chess computer, with a deepfritz engine, and you've achieved an incredibly powerful tool.
+
-
 
+
-
timeframe - 12-24 weeks (adding timeframe, because ultimately decisions will be made based on man-hours available and men available.  Budgets are a necessary part of any successful project)
+
-
 
+
-
=== Maintenance of the 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)''
+
-
 
+
-
 
+
-
 
+
-
== 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)''
+
-
 
+
-
== Marketing analysis ==
+
-
=== 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, network specifics) => 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
+
-
* User
+
-
** Private person with no special interest (likely EMail, browser, calendar, adressbook, chat and some small games)
+
-
** Business User (Needs PIM inkl. Synchronisation (important!) and Office, MS compatibility is a must)
+
-
** Surfer (Uses the Device as primary or secondary browser, possibly also for EMail)
+
-
** Linux Advocat (needs ports of all the common Linux Tools)
+
-
 
+
-
=== Software group analysis ===
+
-
 
+
-
* Desktop ports
+
-
* Mobility specific software (GPS, Chat, Syncing)
+
-
* Games
+
-
* Multimedia
+
-
 
+
-
=== Future trends analysis ===
+
-
 
+
-
So where is the market going?
+
-
 
+
-
* Memory is cheap
+
-
* Ergonomics
+
-
* Mobility
+
-
* Synchronisation
+
-
* Convergence
+
-
* Education - http://wiki.sugarlabs.org, Tutorials and other educational tools built-in, such as complete man pages
+
-
 
+
-
== Marketing the community efforts to consumers ==
+
-
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)
+
-
== Garage improvements ==
+
== Maemo variants ==
-
* Implement some sort of automated single-click push-to-Downloads for Garage projects.
+
{{main|Objective:Maemo variants}}
-
:''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)''
+
Tools to bring platform innovation to adventurous users.
-
::''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)
+

Latest revision as of 13:34, 17 January 2012

Image:Ambox_notice.png
This is an ongoing task, planned to be completed during the current maemo.org development sprint. Any help is appreciated!
Please see the talk page for discussion.

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

Contents

[edit] Objectives

Each objective consists of a list of tasks. The list of objectives here is ready for community approval but the tasks in each page need surely more iterations.

[edit] Best community for mobile Linux innovation

Main article: Objective:Best community for mobile Linux innovation

The best open source projects target primarily the Maemo platform.

[edit] Release soon & often

Main article: Objective:Release soon and often

Public releases of Maemo while it's being developed.

[edit] One place to track feedback

Main article: Objective:One place to track feedback

bugs.maemo.org to get Nokia developers involved as well as the consolidated community projects.

[edit] Co-production of official & community documentation

Main article: Objective:Co-production of official & community documentation

Nokia and the Maemo community to collaborate in the production of the documentation developers and other contributors need.

[edit] Community localization

Main article: Objective:Community localization

The Maemo experience in our own language, translated by ourselves.

[edit] Maemo variants

Main article: Objective:Maemo variants

Tools to bring platform innovation to adventurous users.