Task:100Days
(→Consolidation of extras) |
(→Roadmap for the maemo platform) |
||
| Line 67: | Line 67: | ||
{{main|Task:maemo roadmap}} | {{main|Task: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 component and developer libraries. | ||
| + | |||
| + | Quim to handle this. More details to come. | ||
== Community Council == | == Community Council == | ||
Revision as of 07:56, 10 June 2008
The 100 Days Action Plan brainstorm for maemo.org has covered it's 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
The result of this brainstorm, once ideas start firming up in the sections below, should be:
- A set of 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 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/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 article: Task:Defining maemo
Crystal-clear definitions of maemo, maemo.org, OS2008 and so on.
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.
Increasing transparency
Main article: Increasing transparency
- Identifying closed-source components and the reasons why, addressing the community's concerns over openness.
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: Improving maemo.org
maemo.org needs improvements in usability, content, format and style.
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: Task:maemo roadmap
A maemo roadmap for developers, disclosing information about open source component and developer libraries.
Quim to handle this. More details to come.
Community Council
Main article: 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.--qgil 07:45, 2 June 2008 (UTC)