|
m |
| (143 intermediate revisions not shown) |
| Line 1: |
Line 1: |
| - | The '''maemo.org 100 Days Action Plan'''
| + | {{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= |
| | + | Planned sprints: |
| | + | * 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. |
| | + | * [[100Days/Sprint2|Sprint 2]]. IRC review meeting on 2008/07/22. |
| | + | * [[100Days/Sprint3|Sprint 3]]. IRC review meeting on 2008/08/12. |
| | + | * [[100Days/Sprint4|Sprint 4]]. IRC review meeting on 2008/09/02. |
| | + | * [[100Days/Sprint5|Sprint 5]]. Life/IRC review meeting at [[Maemo Summit 2008|maemo summit]] on 2008/09/19. |
| | | | |
| - | ==Get the server and bandwidth infrastructure up to speed== | + | =Agreed tasks= |
| - | Although things have improved some (particularly after the OS2008 release), they don't seem to be keeping up well with the ever increasing numbers of tablet users, and downtime or slowness from the critical services offered by maemo.org is unacceptable.
| + | |
| - | * Mirror repository.maemo.org to ensure good uptime and fast response.
| + | |
| - | * Mirror tablets-dev.nokia.com to ensure good uptime and fast response.
| + | |
| - | * Improve the hardware and bandwidth availability behind *.maemo.org to ensure good uptime and fast response—maemo.org is too slow!
| + | |
| - | :This work is ongoing and the results should be noticed way before the end of the 100 Days.--[[User:qgil|qgil]] 06:24, 2 June 2008 (UTC)
| + | |
| | | | |
| - | == Increase openness == | + | == Defining maemo == |
| - | Openness is a significant part of what makes maemo so strong, putting together a plan for addressing closed-source components (particularly those directly controlled by Nokia (e.g. low-level stuff like mce and dsme, and user-space stuff like tablet-browser and the task/statusbar applets).
| + | {{main|Task:Defining maemo}} |
| - | :Perhaps ''Map openness'' would be a more accurate description, specially for the 100 Days. Nokia has not the goal of shipping a 100% open source platform. Open source is the recommended approach, but closed source is used when it offers a differentiator, an advantage over competitors. But it is good to get a common understanding on why Nokia is shipping component X as closed source, and answer when possible to requests about opensourcing something.--[[User:qgil|qgil]] 06:46, 2 June 2008 (UTC)
| + | Crystal-clear definitions of maemo, maemo.org, OS2008 and so on. |
| | | | |
| - | === The plan ===
| + | [[User:Qgil|qgil]] coordinates this task. Not included in the Sprint 1 (June) but you can start helping out now. |
| - | * Identify all components (a module name isn't enough). Be like GNOME's release set list.
| + | |
| - | * Identify all closed components in the OS at each layer:
| + | |
| - | ** Initfs/direct hardware access
| + | |
| - | ** Firmware used by kernel modules (Wifi, Bluetooth)
| + | |
| - | ** Low-level system daemons (mce, dsme)
| + | |
| - | ** User-space applications (tablet-browser, applets)
| + | |
| - | * For each package:
| + | |
| - | ** Outline purpose in a dedicated wiki page.
| + | |
| - | ** Describe the closed-source rationale.
| + | |
| - | *** ''Will need some form of mediawiki template for such pages --[[User:jaffa|jaffa]] 22:26, 29 May 2008 (UTC)''
| + | |
| - | * Document the process for working towards opening the component, or its specification.
| + | |
| - | * Ensuring any new closed packages get a wiki page containing their rationale.
| + | |
| - | :Yes, we can do or at least start something along these lines in the 100 Days. What about getting into details about this plan in a page apart, to keeop the main page clean? (same would apply to the rest of actions taken) Let's also see to the potential starting points i.e. [http://maemo.org/development/documentation/how-tos/4-x/maemo_architecture.html the maemo architecture] and the [http://tablets-dev.nokia.com/4.0.1/4.0_vs_4.0.1_content_comparison.html list of packages].--[[User:qgil|qgil]] 06:46, 2 June 2008 (UTC)
| + | |
| | | | |
| - | == Software distribution == | + | ==Fast server== |
| - | === The website ===
| + | {{main|Task:Fast Server}} |
| - | * Implement some sort of automated single-click push-to-Downloads for Garage projects.
| + | Browsing and downloading from maemo.org should be simply fast. No excuses. |
| - | :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)
| + | |
| | | | |
| - | ==== [http://www.internettablettalk.com Internet Tablet Talk] Syndication ====
| + | Nemein will work on this task. More details to come. |
| - | * Provide an automatic way to syndicate applications to the Internet Tablet Talk Software Section (itTSS).
| + | |
| - | * Each application (version) that is syndicated on Internet Tablet Talk, starts a new thread in the forums so end-users get notified of new apps as well as provide a way to give feedback to the developers. Developers themselves can also join in the discussion. This, hopefully, will help to better the quality of applications.
| + | |
| - | ** ''What would be the point of most the garage facilities then? I am not convinced that developers will all go looking at ITT for feedback (some projects work like that, but most rely on mailing lists and irc for example). If there was to a ITT thread for user feedback then maybe add to it a big fat 'report a bug on package x' or 'contact developers of package x'. '' --[[User:trickie|trickie]] 12:17, 1 June 2008 (UTC)
| + | |
| - | * Provide a way for developers to easily add a bug at the application's Garage page for confirmed bugs reported in the discussion thread.
| + | |
| - | :We have agreed with ITt on the general idea. It's something urgent and it would be definitely good to see it in the 100 Days. The specific plan to be discussed in an open page, either here or in ITt or both. In any case, it's clear that the feature is "syndication". Then ITt or whoever can benefit from that, and are the developers of each piece of software that decide if they want to direct the user feedback to ITt, their garage project, the project website, etc.--[[User:qgil|qgil]] 06:59, 2 June 2008 (UTC)
| + | |
| | | | |
| - | ==== maemo "Application Store" ==== | + | == Mapping openness == |
| - | * Actively hunt on the Net for maemo apps not yet added to Maemo Extras, talk to developers, ask and help them to commit applications to Maemo Extras. This especially applies to app porters currently active at iTT.
| + | {{main|Task:Mapping openness}} |
| - | * Use gronmayer's scripts to create a web site that merges applications from all known repositories into a single list and lets you browse them with MicroB using HTML UI similar to N-Gage, Apple Store, etc. While it sounds ambitious, it is not difficult to do, as we always have app descriptions and icons (form .deb files) and we also have screenshots for apps hosted at Garage. Reformatting this data in a format that can be nicely presented in tablet browser is not difficult. | + | * Identifying closed-source components and the reasons why, addressing the community's concerns over openness. |
| - | * Effectively replace "itTSS" with this website.
| + | |
| - | * Actively convince maintainers of other repositories to join the maemo extras repository. This would save some headache from offline and broken repositories.
| + | |
| - | * Make sure that all applications which are actually available in the repositories can be found in the Maemo.org downloads section.
| + | |
| - | :From a Nokia point of view the interest is to have a single repository for distributing third party applications. External repositories should be an exception targeting very specific needs and users. Nokia is not interested in blurring the boundaries between a community supported extras repository and the repo someone has setup somewhere.--[[User:qgil|qgil]] 06:59, 2 June 2008 (UTC)
| + | |
| | | | |
| - | === The repositories ===
| + | [[User:Qgil|qgil]] coordinates this task. Not included in the Sprint 1 (June) but you can start helping out now. |
| - | * Again, because this can't be stressed enough, get the infrastructure behind the repositories up to speed—we need servers, we need bandwidth and we need mirrors.
| + | |
| - | * Streamline the acceptance system for Extras(-devel), (not necessarily easier or less stringent, but more straightforward and clear).
| + | |
| - | * Lay out the groundwork for a peer-review system for Extras acceptance (or devel to Extras promotion) to help ensure good quality assurance on its packages.
| + | |
| | | | |
| - | == Developer documentation == | + | == [http://www.internettablettalk.com Internet Tablet Talk] Collaboration == |
| - | === Clean out the cobwebs, remove the cruft ===
| + | {{main|Task:ITt Collaboration}} |
| - | * Get what's still useful and mostly relevant completely up to speed for maemo 4.x.
| + | maemo.org and ITt services should integrate much better i.e. maemo.org Downloads syndicated in ITt and ITt users getting maemo.org [[karma]]. |
| - | * Archive the outdated information away from the maemo 4.x stuff.
| + | |
| - | * Mark the outdated stuff clearly.
| + | |
| | | | |
| - | === Get organized ===
| + | Nemein will handle this task. Henri is the contact. More to come soon. |
| - | * Put together an easy-to-navigate, sensible index for the documentation content.
| + | |
| - | ** Place references/howtos/tutorials onto one page so that developer does not need to click through several menus.
| + | |
| - | * Improve the search (google?).
| + | |
| | | | |
| - | === Get focused === | + | == Consolidation of extras == |
| - | * Add porting FAQ wiki page detailing common problems developers will run into (i.e. application is killed 3 seconds after launch) and how to deal with them. Provide examples of typical GTK/Motif/etc. application changes needed to properly Hildonize the application. List ways to deal with porting of toolkit-specific functionality whether it be internationalization or mouse/keyboard input.
| + | {{main|Task:Consolidation of Extras}} |
| - | * Make it possible for logged-in developers to annotate any place in the documentation. Link to annotations from documentation.
| + | The Extras repository needs to become the single reference for developers willing to reach end users at large. |
| - | * Provide an example of simple build environment *not* relying on AutoConf and its friends. A single includable makefile should suffice, when used with SB2.
| + | |
| - | * Clearly *say* in the SB readme that it is not possible to debug every application on the desktop, show how to test applications on the target device using SSH/SCP or some other means.
| + | |
| - | * Clearly define what changes is made by default on gtk : like GtkTreeView with hidden header columns by default, or image-button off ...
| + | |
| | | | |
| - | === Look towards the future ===
| + | Niels to coordinate this. More details to come. |
| - | * Define types of applications that will be useful on the Internet Tablet
| + | |
| - | * Stress the fact that the Internet Tablet is not a PC and apps should be created/ported with the tablet form in mind. Don't just do a direct port of an existing app. Aim for quality and Internet Tablet usability.
| + | |
| - | * Focused discussion/guide on User Interface so apps will have a consistent look as well as provide a similar way to interface with the user
| + | |
| - | * Maybe provide a few simple stylesheets and JavaScript libs for creating quick iPhone-like web apps running in MicroB. This should be very light, very easy to use, and targeted to casual users.
| + | |
| | | | |
| - | == maemo.org == | + | == Improving maemo.org == |
| - | * Re-write and expand Introduction to better serve as a useful introduction for newcomers to the platform.
| + | {{main|Task:Improving maemo.org}} |
| - | ** Intro section should include "Who is the maemo community?, What is the maemo platform? The maemo software architecture, How does maemo.org work? Quick start guide to develop on maemo software, and presentations".
| + | maemo.org needs improvements in usability, content, format and style. |
| - | * Single sign on for maemo.org/garage.maemo.org/wiki/bugzilla -> would make community participation easier and the 'karma' calculation (if needed) too.
| + | |
| - | * Website information does not suit the needs of newcomers: How to install or do xy on the IT? Where is recent information about OS2008? Is this page, which I am looking at, an outdated or a recent page on maemo.org? What resources are available for me (alias I am confused by unconnected information sources: gronmayer, internettablettalk, planet.maemo, official Nokia site, internettabletschool, maemo ...) Where is a detailed roadmap for Maemo? Is there an application wishlist for OS2008? Where can I give input/ideas as end-user?
| + | |
| | | | |
| - | === Style and format ===
| + | Dave to coordinate this task. More details to come up later. |
| - | * Maemo.org can benefit from some face lifting - right now on 1280x1024 (this resolution seems to be very common to developers) only half of the real screen estate is used. With some loose block positioning both 800x480 and bigger resolutions can be supported. Maybe even specialized tablet finger-friendly look for those preferring it.
| + | |
| - | ** ''Resolution seems fine to me at the moment, and it works fine on the tablet without requiring the extra effort of maintaining a separate tablet style. Perhaps reducing the min-width to not require horizontal scrolling with the tablet browser windowed would be useful, though. [[User:generalantilles|generalantilles]] 21:02, 29 May 2008 (UTC)''
| + | |
| - | *** ''There won't be any extra effort on the resolution maintainment - this can be done with minor CSS modifications. As for the separate tablet style - this really requires extra effort and if done should be entirely optional. [[User:bundyo|bundyo]] 21:26, 29 May 2008 (UTC)''
| + | |
| - | * More relevant information displayed on front page, preferably customizable blocks like Netvibes and iGoogle. Since the content is gzipped, that won't be too harming to the traffic. Blocks can be optionally auto updated for those that like to keep their browser pages open (and if Prizm is ported - even in the tray). For instance, a "new bugs" section with voting on the fly will boost bugzilla usage.
| + | |
| - | * Make links more standardized. New users often expect links would be underlined, even subtly, or appear to be a button of some kind. Don't rely on hover effects because the tablet can't practically use them. See [http://en.wikipedia.org/wiki/Mystery_Meat_Navigation Wikipedia on 'Mystery Meat Navigation']
| + | |
| - | ** ''This is much less of an issue for a lot of people —[[User:generalantilles|generalantilles]] 19:49, 31 May 2008 (UTC)''
| + | |
| - | ** ''Please stop expecting your advanced experience of new users. Read up on web accessibility, be inviting to the new users.''--[[User:boxofsnoo|boxofsnoo]] 23:08, 31 May 2008 (UTC)
| + | |
| - | *** ''I really don't see the issue (and never particularly have with this much-abused "Mystery Meat" nonsense), and I don't think it has anything to do with my experience, wikipedia (your source) uses the exact same system for link identification. . . . Some specific examples would probably help your case. Anyway, this should probably be taken to the talk page. —[[User:generalantilles|generalantilles]] 23:20, 31 May 2008 (UTC)''
| + | |
| - | * Format and style need to be unified across as much of the site as possible (excluding things like Garage and Bugzilla). Take, for instance [http://maemo.org/news/planet-maemo/ Planet] and [http://maemo.org/news/ News], two pages that should be very similar, if not the same. Perhaps take News' style and format and apply it to Planet (add the contributor's avatar to the upper right of each article? Much like [http://slashdot.org slashdot] does with their article category images.), as the News style seems to offer a cleaner look that better utilizes the available space.
| + | |
| - | * For the outliers like Garage and Bugzilla, at least the style should largely be unified with the main site—using the same fonts, same colors, etc.
| + | |
| | | | |
| - | == Communication ==
| + | Nemein will help on this, but there needs to be a clear plan first to see who pushes what. |
| - | * Today we have too many channels (ITT, maemo.org...). Maybe have some more focus like: maemo.org for developers and ITT for end users and something that links them so software releases can be announced automatically on ITT and users from ITT can easily post bugs on garage bugzilla for example.
| + | |
| - | ** ''Perhaps develop a plan, but this isn't specific enough to achieve in 3 months, IMHO --[[User:jaffa|jaffa]] 22:10, 29 May 2008 (UTC)''
| + | |
| - | *** ''I'm not convinced that two channels is too many, either. —[[User:generalantilles|generalantilles]] 20:04, 31 May 2008 (UTC)
| + | |
| - | * Develop a recommended usage policy for garage.maemo projects, taking into account turning off GForge modules not needed (perhaps defaulting in a subset rather than all, for new projects). Further discussions on whether non-core bugs should be in central Bugzilla and garage trackers merged/closed.
| + | |
| - | * Close misnamed (and now misused) maemo2midgard-discuss mailing list and create maemo-web alongside existing mailing lists for overall discussions about maemo.org sites.
| + | |
| - | * It's unclear where to report problems about packages found in the application catalog. A single bug tracker is needed, or at least a catalog that would redirect the user to the appropriate tracker from a common start page. Or we could set up a "maemo" distribution on launchpad.net, which would let us integrate with the bug trackers of individual packages.
| + | |
| | | | |
| - | == What the community needs to do == | + | === Content cleanup === |
| - | * Put together an plan of action for moving forward with a community-maintained Hacker Edition (based on what Quim said [http://www.archive.org/details/QuimGil-MaemoLinuxtag2008Update here])
| + | {{main|Task:Content Cleanup}} |
| - | * Put the pressure on developers:
| + | Dress up the most important content, dump what is not relevant, handle the rest via the wiki. |
| - | ** Encourage developers not using a repository to package their applications and push them to Extras(-devel), and get developers with 3rd-party repositories to close them down and push their stuff into Extras(-devel).
| + | |
| - | ** Encourage developers to follow proper packaging guidelines (based on the draft [https://maemo.org/forrest-images/pdf/maemo-policy.pdf here]).
| + | |
| - | ** Encourage developers launching applications on Downloads to include as much information about the application as possible (screenshots, good descriptions, good changelogs).
| + | |
| | | | |
| - | == Update developer libraries == | + | == Roadmap for the Maemo platform == |
| - | * gcc-4.x, glib, powervr, it's important to give developers much more time to play with newer tools than short before a major upgrade takes place (of course with disclaimer that nothing is guaranteed to be shipped in a certain way)
| + | {{main|Open development/Maemo roadmap}} |
| - | * Update the vmware appliance with sb2 and python2.5 setted. And more publicity on the vmware appliance, as there is already one on garage, but many don't know it. | + | 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 == |
| | + | {{main|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. —[[User:generalantilles|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 . '''[http://lists.maemo.org/mailman//listinfo/maemo-community DONE]'''. |
| | + | |
| | + | |
| | + | [[Category:Community]] |
| | + | [[Category:maemo.org]] |
Browsing and downloading from maemo.org should be simply fast. No excuses.
Nemein will work on this task. More details to come.
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.
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.
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.
Dress up the most important content, dump what is not relevant, handle the rest via the wiki.
A Maemo roadmap for developers, disclosing information about open source components and developer libraries.
A process for electing a small "Community Council" should be created and elections held.
