Task:100Days

(Increase End-User Involvement)
m (Protected "Task:100Days" [edit=autoconfirmed:move=autoconfirmed])
 
(48 intermediate revisions not shown)
Line 1: Line 1:
-
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.
+
{{task|completed}}
-
{| style="background-color:#f4f09c; border: 1px silver solid; padding: 10px;"
+
The '''100 Days Action Plan''' brainstorm for maemo.org has covered its first objective and now the list of proposal is closed. Now the help is needed in the committed tasks listed below. The strategic brainstorm continues at [[2010_Agenda|maemo.org 2010]].
-
| [[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=
=Community-led action plan process=
-
The result of this brainstorm, once ideas start firming up in the sections below, should be:
+
Planned sprints:
-
* A set of [http://meta.wikimedia.org/wiki/Help:Template mediawiki templates] for creating consistency in...
+
* Sprint 1. Started on 2008/06/10. [https://garage.maemo.org/plugins/wiki/index.php?June2008Sprint&id=106&type=g Tasks committed]. IRC review meeting on 2008/06/30.
-
* A page for each of the sections below (e.g. [[Increasing transparency]]) containing:
+
* [[100Days/Sprint2|Sprint 2]]. IRC review meeting on 2008/07/22.
-
** a detailed step-by-step plan for what will be delivered within 100 days
+
* [[100Days/Sprint3|Sprint 3]]. IRC review meeting on 2008/08/12.
-
** a list of community members committed to providing it (say 2-6?)
+
* [[100Days/Sprint4|Sprint 4]]. IRC review meeting on 2008/09/02.
-
** a community member as notional leader, responsible for overall delivery of that stream
+
* [[100Days/Sprint5|Sprint 5]]. Life/IRC review meeting at [[Maemo Summit 2008|maemo summit]] on 2008/09/19.
-
** sign-off by [[User:qgil|qgil]] as community manager that he views it as constructive
+
-
Then, once the brainstorm has completed:
+
=Agreed tasks=
-
# 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 ==
== Defining maemo ==
{{main|Task:Defining maemo}}
{{main|Task:Defining maemo}}
Crystal-clear definitions of maemo, maemo.org, OS2008 and so on.
Crystal-clear definitions of maemo, maemo.org, OS2008 and so on.
 +
 +
[[User:Qgil|qgil]] coordinates this task. Not included in the Sprint 1 (June) but you can start helping out now.
==Fast server==
==Fast server==
Line 38: Line 23:
Browsing and downloading from maemo.org should be simply fast. No excuses.
Browsing and downloading from maemo.org should be simply fast. No excuses.
-
== Increasing transparency ==
+
Nemein will work on this task. More details to come.
-
{{main|Increasing transparency}}
+
 
 +
== Mapping openness ==
 +
{{main|Task:Mapping openness}}
* Identifying closed-source components and the reasons why, addressing the community's concerns over openness.
* Identifying closed-source components and the reasons why, addressing the community's concerns over openness.
 +
 +
[[User:Qgil|qgil]] coordinates this task. Not included in the Sprint 1 (June) but you can start helping out now.
== [http://www.internettablettalk.com Internet Tablet Talk] Collaboration ==
== [http://www.internettablettalk.com Internet Tablet Talk] Collaboration ==
{{main|Task:ITt 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.
+
maemo.org and ITt services should integrate much better i.e. maemo.org Downloads syndicated in ITt and ITt users getting maemo.org [[karma]].
 +
 
 +
Nemein will handle this task. Henri is the contact. More to come soon.
== Consolidation of extras ==
== Consolidation of extras ==
-
{{main|Task: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.
+
The Extras repository needs to become the single reference for developers willing to reach end users at large.
 +
 
 +
Niels to coordinate this. More details to come.
== Improving maemo.org ==
== Improving maemo.org ==
-
{{main|Improving maemo.org}}
+
{{main|Task:Improving maemo.org}}
maemo.org needs improvements in usability, content, format and style.
maemo.org needs improvements in usability, content, format and style.
 +
 +
Dave to coordinate this task. More details to come up later.
 +
 +
Nemein will help on this, but there needs to be a clear plan first to see who pushes what.
=== Content cleanup ===
=== Content cleanup ===
Line 58: Line 55:
Dress up the most important content, dump what is not relevant, handle the rest via the wiki.
Dress up the most important content, dump what is not relevant, handle the rest via the wiki.
-
== Roadmap for the maemo platform ==
+
== Roadmap for the Maemo platform ==
-
{{main|Task:maemo roadmap}}
+
{{main|Open development/Maemo roadmap}}
-
A maemo roadmap for developers, disclosing information about open source component and developer libraries.
+
A Maemo roadmap for developers, disclosing information about open source components and developer libraries.
 +
 
 +
[[User:Qgil|qgil]] coordinates this task. Planned for the Sprint 5 (September) but you can start helping out now.
== Community Council ==
== Community Council ==
-
{{main|Task:Community Council}}
+
{{main|Community Council}}
A process for electing a small "Community Council" should be created and elections held.
A process for electing a small "Community Council" should be created and elections held.
 +
 +
This task needs a coordinator.
 +
:''Jaffa, lardman, or myself are probably the ones to push this. Jaffa's currently on vacation, so I'll get together with lardman tomorrow to start getting the ball rolling on this. —[[User:generalantilles|GeneralAntilles]] 01:01, 12 June 2008 (UTC)''
== More pre-agreed tasks ==
== More pre-agreed tasks ==
Help planning them further and moving them to an own page.
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.
+
* [[Task:Using garage.maemo.org]] - Ferenc
-
* Close misnamed (and now misused) maemo2midgard-discuss mailing list and create maemo-web alongside existing mailing lists for overall discussions about maemo.org sites.
+
* Close misnamed (and now misused) maemo2midgard-discuss mailing list and create maemo-community alongside existing mailing lists for overall discussions about maemo.org sites and community topics in general. Ferenc . '''[http://lists.maemo.org/mailman//listinfo/maemo-community DONE]'''.
-
:''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)''
+
-
 
+
-
== Increase End-User Involvement ==
+
-
* Allowances need to be made to elicit and encourage feedback from non-technical users.  User complaints and ideas need an outlet if maemo is to stay relevant as anything other than an obscure hacker's project. Quality Assurance needs to center on the users' needs, not the developers'.  This type of QA is vital, but thankless.  It should be determined what resources Nokia is willing to contribute to such an effort, given the difficulty in getting developers to voluntarily see such an effort as a high priority.
+
-
 
+
-
-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)
+
[[Category:Community]]
 +
[[Category:maemo.org]]

Latest revision as of 11:00, 28 August 2012

Image:Ambox_notice.png
This task is completed and this page stays here for documentation purposes only. Please file bugs or propose a new, related task if you want to push this forward.
Please see the talk page for discussion.

The 100 Days Action Plan brainstorm for maemo.org has covered its first objective and now the list of proposal is closed. Now the help is needed in the committed tasks listed below. The strategic brainstorm continues at maemo.org 2010.

Contents

Community-led action plan process

Planned sprints:

Agreed tasks

Defining maemo

Main article: Task:Defining maemo

Crystal-clear definitions of maemo, maemo.org, OS2008 and so on.

qgil coordinates this task. Not included in the Sprint 1 (June) but you can start helping out now.

Fast server

Main article: Task:Fast Server

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

Nemein will work on this task. More details to come.

Mapping openness

Main article: Task:Mapping openness

  • Identifying closed-source components and the reasons why, addressing the community's concerns over openness.

qgil coordinates this task. Not included in the Sprint 1 (June) but you can start helping out now.

Internet Tablet Talk Collaboration

Main article: 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.

Nemein will handle this task. Henri is the contact. More to come soon.

Consolidation of extras

Main article: Task:Consolidation of Extras

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

Niels to coordinate this. More details to come.

Improving maemo.org

Main article: Task:Improving maemo.org

maemo.org needs improvements in usability, content, format and style.

Dave to coordinate this task. More details to come up later.

Nemein will help on this, but there needs to be a clear plan first to see who pushes what.

Content cleanup

Main article: Task:Content Cleanup

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

Roadmap for the Maemo platform

Main article: Open development/Maemo roadmap

A Maemo roadmap for developers, disclosing information about open source components and developer libraries.

qgil coordinates this task. Planned for the Sprint 5 (September) but you can start helping out now.

Community Council

Main article: Community Council

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

This task needs a coordinator.

Jaffa, lardman, or myself are probably the ones to push this. Jaffa's currently on vacation, so I'll get together with lardman tomorrow to start getting the ball rolling on this. —GeneralAntilles 01:01, 12 June 2008 (UTC)

More pre-agreed tasks

Help planning them further and moving them to an own page.

  • Task:Using garage.maemo.org - Ferenc
  • Close misnamed (and now misused) maemo2midgard-discuss mailing list and create maemo-community alongside existing mailing lists for overall discussions about maemo.org sites and community topics in general. Ferenc . DONE.