Task:Content Cleanup

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


 * Get what's still useful and mostly relevant completely up to speed for maemo 4.x.
 * Archive the outdated information away from the maemo 4.x stuff.
 * Mark the outdated stuff clearly.
 * Agreed. What about a new wiki page listing what is really essential and should be put upfront? One approach could be to have the essential bits well written and presented in static-ish CMS pages and stable PDFs and then move all the rest to this wiki ecosystem. As soon as new wiki content gets really good we could productize it and promote it.--qgil 07:34, 2 June 2008 (UTC)
 * Don't create new wiki pages. The more pages you create, the more difficult it becomes to find and navigate stuff. Delete unused wiki pages instead. For documentation, you only need to have 1 (one) wiki page with a list of all references, how-tos, and tutorials that apply to the current OS (4.x). If a document does not 100% apply but is still useful, mark it as "partly deprecated". Create the same kind of pages for older OSes and link to them from the top of 4.x page, but make links small because this stuff is outdated and less important. fms 16:16, 2 June 2008 (UTC)
 * ''I meant a new wiki page just for working purposes, like the other ones being created to work on the 100 days objectives". In this working-wiki-page we would propose and agree on the very essential pages and diocs that need to be promoted and stand alone, while all the rest would be moved wither to really secondary pages (i.e. "Disclaimers") or wiki pages easy to be edited and improved.--qgil 08:57, 4 June 2008 (UTC)

Get organized

 * 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?).
 * The plan is to have all the official HowTos and docs under a well structured Maemo Reference Guide. Deadline: Diablo release. This reference guide would sit between the Quickstart Guide and the Training Materials. There were some fixes in the search and should be working much better now.--qgil 07:34, 2 June 2008 (UTC)
 * The website search has already been improved, will add this wiki to the search too. --xfade 13:37, 2 June 2008 (UTC)

Get focused

 * 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.
 * Make it possible for logged-in developers to annotate any place in the documentation. Link to annotations from documentation.
 * 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 ...
 * The idea is to have the sources of the official documentation here in this wiki. Users could add comments in the discussion pages, perhaps some users could get edit rights too. To be decided. The Nokia teams would updated their part of the documentation here and then all would be revised and conveniently package in PDF when a new stable release comes. So yes, we can put this in the 100 Days and then let's see how far we go in this timeframe.--qgil 07:34, 2 June 2008 (UTC)

Look towards the future

 * 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.
 * Good ideas, they can be pushed by Nokia and the community. The point about Javascript libs is imho more of a 2010 Agenda thing, though. I don't mean we wouldn't have anything before 2010, but 100 Days is just too tight. Besides, the work to be done goes beyond maemo.org.--qgil 07:34, 2 June 2008 (UTC)