<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="generator" content="Osso Notes">
<title></title></head>
<body>
<p>Thank you for this, Quim.</p>
<p></p>
<p>I personally wish there was some way to pull the many, many great tips and tricks out of Talk, like a prospector hunting for gold, and collect them somewhere central. Too much for one person, but a good organizer / delegator could send out teams to rove through the threads and return with the nuggets...</p>
<p></p>
<p>For instance, there are great tips for setting up an ssh socks5 proxy, trying out the Fremantle interface on your N810, using a bluetooth mouse on your tablet, encoding DVDs for best playback, printing from the tablet, connecting to passworded Windows shares, streaming video from the tablet with VLC, etc, etc... </p>
<p></p>
<p>There are just so many, many, um, not-so-useful posts to sift through... </p>
<p></p>
<p>----- Original message -----</p>
<p>Hi, does actually the docmaster have a clear assignment?</p>
<p></p>
<p><a href="http://wiki.maemo.org/Maemo.org_team">http://wiki.maemo.org/Maemo.org_team</a></p>
<p></p>
<p>Until now Dave has been involved in multiple and diverse tasks, but less</p>
<p>and less ties to documentation work.</p>
<p></p>
<p>Yet documentation is far from ideal in the Maemo project. Good</p>
<p>documentation for develope and contributors is an essential part of the</p>
<p>maturity and success of a project. Although there are many excellent</p>
<p>undocumented projects that defy this principle, the Maemo project</p>
<p>decided that it was idea to fund a community docmaster.</p>
<p></p>
<p>But... what does this mean in practice? Some ideas to consider:</p>
<p></p>
<p>- There are many bugs about the official documentation. The stable and</p>
<p>the unstable. What bugs are more important? What are more urgent? The</p>
<p>docmaster can chase Maemo SW on the things that need a fix before the rest.</p>
<p></p>
<p>- Are the official docs delivered what the community needs? Maybe there</p>
<p>is something important missing. Maybe there are some areas that should</p>
<p>be documented further. The docmaster could influence the planning for</p>
<p>future documentation work.</p>
<p></p>
<p>- What about the frequent questions from users and developers. Are they</p>
<p>being followed to detect what needs more/better documentation, or just a</p>
<p>prominent place somewhere so people can find it?</p>
<p></p>
<p>- Actually the docmaster could even give a try to the documentation</p>
<p>before is being released, preventing some of the bugs to even show up.</p>
<p></p>
<p>- And the documentation tools. We have discussed about using the wiki</p>
<p>for developer documentation, about publishing the APIs nicely à la</p>
<p>library.gnome.org... what is the status of these projects? Is the doc</p>
<p>master not only following them but active there?</p>
<p></p>
<p>- Specifically, 1 of the 6 2010 objectives (don't you think they are</p>
<p>forgotten) is about community documentation:</p>
<p><a href="http://wiki.maemo.org/2010_Agenda#Co-production_of_official_.26_community_documentation">http://wiki.maemo.org/2010_Agenda#Co-production_of_official_.26_community_documentation</a></p>
<p></p>
<p>Then there are problems of documentation in the community projects e.g.</p>
<p></p>
<p>- Plenty of tips and tricks lost in talk.maemo.org. Who will recover them?</p>
<p></p>
<p>- Actually there was the debate of the old ITt wiki and the diff with</p>
<p>still with the tmo wiki. The docmaster should drive the discussion there</p>
<p>and put time to fix what needs more urgent fixing.</p>
<p><a href="http://talk.maemo.org/showthread.php?t=26503">http://talk.maemo.org/showthread.php?t=26503</a></p>
<p></p>
<p>- Is our wiki well organized? Provides a nice entry for the people using</p>
<p>it? I don't even know since I find the 4 things I use frequently, but</p>
<p>what about others?</p>
<p></p>
<p>- Also in Downloads there are many popular projects that are missing</p>
<p>screenshots or a good description. The doc master could contact the</p>
<p>remarkable projects and ask them to be a bit more careful about their</p>
<p>releases.</p>
<p></p>
<p>... and I could go on since I don't code neither I design, but almost</p>
<p>everybody can type a letter or two. ;)</p>
<p></p>
<p>I'm not saying that Dave should all this all the time, but I think the</p>
<p>docmaster should have the initiative to see what is most needed first</p>
<p>and go for it. Some tasks are continuous and need to be made as part of</p>
<p>as routine. Some others need a frontal attack until completed.</p>
<p></p>
<p>What will be the Must, Should and Could tasks of the docmaster in the</p>
<p>following sprint?</p>
<p></p>
<p>--</p>
<p>Quim Gil</p>
<p>open source advocate</p>
<p>Maemo Software @ Nokia</p>
<p></p>
<p>_______________________________________________</p>
<p>maemo-community mailing list</p>
<p><a href="mailto:maemo-community@maemo.org">maemo-community@maemo.org</a></p>
<p><a href="https://lists.maemo.org/mailman/listinfo/maemo-community">https://lists.maemo.org/mailman/listinfo/maemo-community</a></p>
<p></p>
<p></p>
</body>
</html>