<?xml version="1.0" encoding="iso-8859-1"?><!-- generator="b2evolution/1.9.2" -->
<rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"					xmlns:admin="http://webns.net/mvcb/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
		<channel rdf:about="http://www.maemopeople.org/index.php/jaffa">
			<title>Jaffa's Projects</title>
			<link>http://www.maemopeople.org/index.php/jaffa</link>
			<description></description>
			<dc:language>en-UK</dc:language>
			<admin:generatorAgent rdf:resource="http://b2evolution.net/?v=1.9.2"/>
			<sy:updatePeriod>hourly</sy:updatePeriod>
			<sy:updateFrequency>1</sy:updateFrequency>
			<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>
			<items>
				<rdf:Seq>
									<rdf:li rdf:resource="http://www.maemopeople.org/index.php/jaffa/2010/03/17/running_for_the_maemo_community_council_"/>
									<rdf:li rdf:resource="http://www.maemopeople.org/index.php/jaffa/2010/01/12/catorise_auto_organise_n900_applications"/>
									<rdf:li rdf:resource="http://www.maemopeople.org/index.php/jaffa/2009/11/21/maemo_weekly_news_a_proposal"/>
									<rdf:li rdf:resource="http://www.maemopeople.org/index.php/jaffa/2009/10/13/downloading_ovi_maps_without_a_network_c"/>
									<rdf:li rdf:resource="http://www.maemopeople.org/index.php/jaffa/2009/09/21/why_i_m_not_standing_for_the_council_but"/>
								</rdf:Seq>
			</items>
		</channel>
		
		<item rdf:about="http://www.maemopeople.org/index.php/jaffa/2010/03/17/running_for_the_maemo_community_council_">
			<title>Running for the Maemo Community Council... again</title>
			<link>http://www.maemopeople.org/index.php/jaffa/2010/03/17/running_for_the_maemo_community_council_</link>
			<dc:date>2010-03-17T13:44:23Z</dc:date>
			<dc:creator>Jaffa</dc:creator>
			<dc:subject>Maemo</dc:subject>
			<description>The election period has started for the next Maemo Community Council election and we have a number of excellent candidates, including - even if I do say so myself - me ;-)

Before I decided to run, I asked each candidate a series of questions - the answers we've given are linked to from the candidate summary page. I'd also encourage other community members to come up with questions for the candidates.

My full candidacy announcement is in the thread. The main point is that the last six months, having stepped back from the council, have given me a new perspective. The biggest issue I've seen is one of communication and clear facilitation. We need to reduce the overhead and streamline community action. Therefore, if elected, I will push for:


A clear cooperation with the growing MeeGo community through MeeGo's Community Working Group and develop a transition plan to ensure the level of collaboration the council has with Nokia isn't lost in the new world.
A Moblin/Maemo/MeeGo summit which looks to the present as well as to the future.
Appropriate support and resources for existing device owners as Nokia transition to MeeGo. Exactly what form this will take will depend on whether running MeeGo is a day-to-day reality for N8x0 and N900 users:

If MeeGo provides a comparable experience, without any loss of functionality, the resources around Maemo can be slowly redirected.
However, if MeeGo for existing devices is - at best - of developer interest only, the existing Maemo community must  continue, and must continue to provide support, help and resources to Maemo users.

Mer^2 should help with the final point, and I'm proud to have been on the council which approached Nokia requesting a distmaster role; and suggesting that Carsten (Stskeeps) was the right man for the job.
Increasing the visibility of the maemo.org sprint process and reducing the burden on volunteers. Niels Breet (X-Fade) being made the maemo.org team leader will help here. Having been involved in the running of an agile project for over 2 years, I believe:

Niels should chair the sprint meeting.
The meeting participants should be responsible for setting their priorities and what will be included.
Input should be provided by Nokia (Tero Kojo) and the community (the Council chair) on their issues and priorities before the meeting which should be taken into account within the prioritisation.

This will reduce the workload for the volunteers on the council, increase the ownership of the tasks and provide greater accountability of the paid contributors.
A summary table listing the high-level issues facing the community and who on the council will act as a point of contact for them. An example for the current council could be:

       Extras QA process         VDVsx
       Optification              gcobb
       Community outreach        Texrat

Support for Randall Arnold's community outreach programme, which is trying to grow the Maemo community rather than just the Maemo platform. With the launch of the Ovi store for Maemo, much focus is given to that rather than the community provisions such as Extras.
Empowering of community members to lead initiatives such as Google Summer of Code, conference attendance etc.
A monetisation/donation framework for community-provided downloads.


Whether you vote for me, or someone else, I'd encourage you to vote! The transition from Maemo to MeeGo means the community's representatives to Nokia are more important than ever. Voting is open to anyone with a maemo.org account which is older than 3 months, and has accrued more than 10 karma points.</description>
			<content:encoded><![CDATA[<p>The election period has started for the next <a href="http://wiki.maemo.org/Community_Council/Council_election_Q1_2010">Maemo Community Council election</a> and we have a number of <a href="http://wiki.maemo.org/Community_Council/Candidate_declarations_for_March_2010">excellent candidates</a>, including - even if I do say so myself - me ;-)</p>

<p>Before I decided to run, I asked each candidate a series of questions - the answers we've given are linked to from the candidate summary page. I'd also encourage other community members to come up with questions for the candidates.</p>

<p>My <a href="http://lists.maemo.org/pipermail/maemo-community/2010-March/004118.html">full candidacy announcement</a> is in the thread. The main point is that the last six months, having stepped back from the council, have given me a new perspective. The biggest issue I've seen is one of communication and clear facilitation. We need to reduce the overhead and streamline community action. Therefore, if elected, I will push for:</p>

<ul>
<li>A clear cooperation with the growing MeeGo community through MeeGo's <a href="http://lists.meego.com/pipermail/meego-community/2010-March/000320.html">Community Working Group</a> and develop a transition plan to ensure the level of collaboration the council has with Nokia isn't lost in the new world.</li>
<li>A Moblin/Maemo/MeeGo summit which looks to the present as well as to the future.</li>
<li><p>Appropriate support and resources for existing device owners as Nokia transition to MeeGo. Exactly what form this will take will depend on whether running MeeGo is a day-to-day reality for N8x0 and N900 users:</p>
<ol>
<li><p>If MeeGo provides a comparable experience, without any loss of functionality, the resources around Maemo can be slowly redirected.</p>
<li>However, if MeeGo for existing devices is - at best - of developer interest only, the existing Maemo community <strong>must</strong>  continue, and must continue to provide support, help and resources to Maemo users.
</li></li></ol>
<p>Mer^2 should help with the final point, and I'm proud to have been on the council which approached Nokia requesting a distmaster role; and suggesting that Carsten (Stskeeps) was the right man for the job.</p></li>
<li><p>Increasing the visibility of the maemo.org sprint process and reducing the burden on volunteers. Niels Breet (X-Fade) being made the <a href="http://maemoteam.wordpress.com/2010/01/06/a-role-change-for-niels-x-fade-in-the-maemo-org-team/">maemo.org team leader</a> will help here. Having been involved in the running of an agile project for over 2 years, I believe:</p>
<ul>
<li>Niels should chair the sprint meeting.</li>
<li>The meeting participants should be responsible for setting their priorities and what will be included.</li>
<li>Input should be provided by Nokia (Tero Kojo) and the community (the Council chair) on their issues and priorities before the meeting which should be taken into account within the prioritisation.</li>
</ul>
<p>This will reduce the workload for the volunteers on the council, increase the ownership of the tasks and provide greater accountability of the paid contributors.</p></li>
<li><p>A summary table listing the high-level issues facing the community and who on the council will act as a point of contact for them. An example for the current council could be:</p>
<pre>
       Extras QA process         VDVsx
       Optification              gcobb
       Community outreach        Texrat
</pre></li>
<li>Support for Randall Arnold's community outreach programme, which is trying to grow the Maemo community rather than just the Maemo platform. With the launch of the Ovi store for Maemo, much focus is given to that rather than the community provisions such as Extras.</li>
<li>Empowering of community members to lead initiatives such as Google Summer of Code, conference attendance etc.</li>
<li>A <a href="http://lists.maemo.org/pipermail/maemo-developers/2010-January/023980.html">monetisation/donation framework</a> for community-provided downloads.</li>
</ul>

<p>Whether you vote for me, or someone else, I'd encourage you to vote! The transition from Maemo to MeeGo means the community's representatives to Nokia are more important than ever. Voting is open to anyone with a maemo.org account which is older than 3 months, and has accrued more than 10 <a href="http://wiki.maemo.org/Karma">karma</a> points.</p>]]></content:encoded>
		</item>

		
		<item rdf:about="http://www.maemopeople.org/index.php/jaffa/2010/01/12/catorise_auto_organise_n900_applications">
			<title>Catorise: auto-organise N900 applications </title>
			<link>http://www.maemopeople.org/index.php/jaffa/2010/01/12/catorise_auto_organise_n900_applications</link>
			<dc:date>2010-01-12T22:52:59Z</dc:date>
			<dc:creator>Jaffa</dc:creator>
			<dc:subject>Maemo</dc:subject>
			<description>In a brief break from Hermes-related Maemo work, I was inspired by Manfred Weiss' MyMenu to create an auto-organising menu application for the N900:



Catorise organises the application menu to have top-levels corresponding to the sections in Application Manager. Features:


Uses the section icons from the current theme, falling back to the default theme if none available.
Determines an application's section from the same information the packager used when uploading it to Extras.
Keeps track of application installs/uninstalls.
Entirely non-destructive: remove the package and everything goes back to how it was before.
"All" and "Other" sections, just as in the App Manager, to provide additional access routes.


So, with Catorise the section you find an application's icon is the same you used to install it!

It is currently in Extras-devel. This should, therefore, only be tested by people who are willing to suffer potential data loss, hair loss and the eating of babies.

It's largely feature complete, however there are some known problems/future developments:


Applications installed from Ovi will go into the "Other" section, due to the way Ovi on Maemo has been designed. I've some thoughts on how to work around this, though.
Changing the theme will only update the icons on the next application install/removal.
A quick GUI editor could be created to manipulate /opt/catorise/menu which is a simple text file cache to speed-up rebuilding. This would allow the user to shuffle the apps to best suit their use cases.
</description>
			<content:encoded><![CDATA[<p>In a brief break from <a href="http://hermes.garage.maemo.org/">Hermes</a>-related Maemo work, I was inspired by <a href="http://maemo.org/profile/view/manzn/">Manfred Weiss</a>' <a href="http://talk.maemo.org/showthread.php?t=39141">MyMenu</a> to create an <em>auto-</em>organising menu application for the N900:</p>

<div style="text-align:center; margin: 0.5em auto"><center><a href="http://www.flickr.com/photos/30863507@N02/4268177643/"><img src="http://farm3.static.flickr.com/2739/4268177643_45faf68bd8_m.jpg" alt="[New application menu: top-level]" /></a></center></div>

<p><em>Catorise</em> organises the application menu to have top-levels corresponding to the sections in Application Manager. Features:</p>

<ul>
<li>Uses the <a href="http://blogs.igalia.com/vjaquez/2009/12/14/shinning-new-ham/">section icons</a> from the current theme, falling back to the default theme if none available.</li>
<li>Determines an application's section from the same information the packager used when uploading it to Extras.</li>
<li>Keeps track of application installs/uninstalls.</li>
<li>Entirely non-destructive: remove the package and everything goes back to how it was before.</li>
<li>"All" and "Other" sections, just as in the App Manager, to provide additional access routes.</li>
</ul>

<p>So, with <em>Catorise</em> the section you find an application's icon is the same you used to install it!</p>

<p><strong>It is <a href="http://maemo.org/packages/view/catorise/">currently</a> in Extras-devel. This should, therefore, only be tested by people who are willing to suffer potential data loss, hair loss and the eating of babies.</strong></p>

<p>It's largely feature complete, however there are some known problems/future developments:</p>

<ul>
<li>Applications installed from Ovi will go into the "Other" section, due to the way Ovi on Maemo has been designed. I've some thoughts on how to work around this, though.</li>
<li>Changing the theme will only update the icons on the next application install/removal.</li>
<li>A quick GUI editor could be created to manipulate <code>/opt/catorise/menu</code> which is a simple text file cache to speed-up rebuilding. This would allow the user to shuffle the apps to best suit their use cases.</li>
</ul>]]></content:encoded>
		</item>

		
		<item rdf:about="http://www.maemopeople.org/index.php/jaffa/2009/11/21/maemo_weekly_news_a_proposal">
			<title>Maemo Weekly News: a proposal</title>
			<link>http://www.maemopeople.org/index.php/jaffa/2009/11/21/maemo_weekly_news_a_proposal</link>
			<dc:date>2009-11-21T20:34:34Z</dc:date>
			<dc:creator>Jaffa</dc:creator>
			<dc:subject>Maemo</dc:subject>
			<description>I've been discussing this idea with a few key contributors over the past few days to make sure it's realistic and feasible. We've polished it and would like to ask for volunteers for a new Maemo Weekly News digest.

Workload: little to some.
Benefits: glory.

Read on for more info...
Background
There are a lot of facets to the Maemo community, whether it's Bugzilla, maemo-developers, #maemo, Planet, Talk or Brainstorm. With the N900 and Maemo 5, there's been a noticeable increase in traffic in all these areas.
There have been suggestions of Maemo magazines before, but they've fallen over because:

The people involved haven't been integrated into the community.
They've been a lot of work to create.
They tried to move away from maemo.org/news/

Similarly, there are blogs (like Reggie's Maemo Talk) which highlight key important things; but some of them also suffer from the same problems above and none yet go into the level of detail I'd like to see.
With the increase in volume, and limits on my own time, I'm finding it harder to be aware of all the things going on. In particular, little asides and so on on talk which are key to the community, but buried in a thread. The old complaint of "too much happening outside of talk.maemo.org" is now reversed, IMHO, but the SNR is too low to follow "New Posts" religiously and develop software at the same time.
Idea
A weekly news digest of key useful/informative/interesting/insightful news from all Maemo news sources. Similar in style and approach to Linux Weekly News.
This is, in many ways, a continuation of Ryan's "Community Highlights" but doing less work, being more encompassing and more repeatable.
This is NOT an attempt to aggregate ALL Maemo-related news, but provide a selection of highlights during the week; of interest to those who are involved in the platform and the community, but without the time to follow enough of the conversations in all the places to find the ones interesting to them. By acting as a filter, more people will be able to be involved in the things which interest them, resulting in an increase of higher quality submissions for members of the community who might not be heard from as much.
Implementation
The key to its success is to produce something which is useful, integrated and deterministic; but without being a massive resource hog.
Produced weekly, every week, with a series of sections - probably similar to those on tmo. Something like:

Front page
Applications
Development
Community
Devices
Maemo in the Wild
...

To gather the news, a series of sub-editors/contributors would have access to a Twitter account (@maemoweeklynews, say). The posts to this feed would consist of the section, a few keywords and a link to the content (thread, post, email message, blog) which triggered it. For example, recently this may include:

Applications - wazd helping qwerty12 on Transmission: http://s56.radikal.ru/i152/0911/34/a388e13890a0.png
Devices - Release firmware available to download: http://flors.wordpress.com/2009/11/16/maemo-5-final-release-updated-sdk-and-firmware/

Suggestions on content could be directed at it from people's own Twitter accounts. The sub-editors would then be able to pick and choose from these if it's something they'd missed.
As each issue is being pulled together, one or more sub-editors would then review the posts to that Twitter feed for their sections and flesh it out with a longer paragraph/quote. Full-blown stories would also be possible, but I imagine that being a rarity (if ever). There would then be an overall editor(s) making sure there's no duplication and also including things from maemo.org/downloads/ (top 10 apps, and new apps this week) and the bug jars (top 10 activity, probably).
The completed digest would then be posted to a site and syndicated to Planet.
Hopefully this shouldn't be too much work; and sub-editors/contributors would be able to post to the feed during their daily review of their slice of the community.
To collect the sub-editors, I'd suggest a recruitment &#38; screening process of the form "what 3 would you have done for last week?" See more details below.
Getting Involved
I'm now looking for:

CONTRIBUTORS: long-standing members of the community to volunteer to highlight content they see during their Maemo day. This could be whilst sat on IRC, reading the mailing lists, watching maemo.org/news/, contributing on Brainstorm or reading Talk. The only extra work you'd have to do was use your favourite Twitter client to post links you thought should be in the digest.
Approx. number of positions: 20-30
SUB-EDITORS: contributors who are also willing to flesh out the links each week by selecting a representative quote. I will be ensuring we have the tools in place to make this as easy as possible.
Approx. number of positions: 5-10
EDITORS: the people with ultimately responsibility. The sub-editors who make sure the whole thing is consistent.
Approx. number of positions: 2-4

As I want to start it small (it can always grow once we work out the details a bit better and see how it goes), anyone who'd like to be involved can reply to this (it'll be on maemo-community, my blog and talk.maemo.org) with:

maemo.org username
Position wanted (contributor/sub-editor/editor)
Channels you follow
Preferred section(s) if sub-editor (feel free to make up a new one)
One/two sentence bio.
Two or three links you'd've posted in the last 2 weeks.

This is an opportunity to help collaborate and facilitate spreading Maemo news; if you're a long-time contributor to the platform, your insights will be invaluable. If you're a relative newcomer, looking for a way to contribute, this is your chance!
</description>
			<content:encoded><![CDATA[<p>I've been discussing this idea with a few key contributors over the past few days to make sure it's realistic and feasible. We've polished it and would like to ask for volunteers for a new Maemo Weekly News digest.</p>
<ul>
<em>Workload:</em> little to some.<br />
<em>Benefits:</em> glory.
</ul>
<p>Read on for more info...</p>
<h3>Background</h3>
<p>There are a lot of facets to the Maemo community, whether it's Bugzilla, maemo-developers, #maemo, Planet, Talk or Brainstorm. With the N900 and Maemo 5, there's been a noticeable increase in traffic in all these areas.</p>
<p>There have been suggestions of Maemo magazines before, but they've fallen over because:</p>
<ol>
<li>The people involved haven't been integrated into the community.</li><br />
<li>They've been a lot of work to create.</li><br />
<li>They tried to move away from <a href="http://maemo.org/news/">maemo.org/news/</a></li>
</ol>
<p>Similarly, there are blogs (like Reggie's Maemo Talk) which highlight key important things; but some of them also suffer from the same problems above and none yet go into the level of detail I'd like to see.</p>
<p>With the increase in volume, and limits on my own time, I'm finding it harder to be aware of all the things going on. In particular, little asides and so on on talk which are key to the community, but buried in a thread. The old complaint of "too much happening outside of talk.maemo.org" is now reversed, IMHO, but the SNR is too low to follow "New Posts" religiously <em>and</em> develop software at the same time.</p>
<h3>Idea</h3>
<p>A weekly news digest of key useful/informative/interesting/insightful news from all Maemo news sources. Similar in style and approach to <a href="http://lwn.net/Articles/360596/">Linux Weekly News</a>.</p>
<p>This is, in many ways, a continuation of Ryan's "<a href="http://maemo.org/community/council/community_highlights_for_december_2008-part_i-january_2009-part_ii/">Community</a> <a href="http://maemo.org/community/council/635a8ae4fd0f11dd90b3938ce0b5aa01aa01/">Highlights</a>" but doing less work, being more encompassing and more repeatable.</p>
<p>This is NOT an attempt to aggregate ALL Maemo-related news, but provide a selection of highlights during the week; of interest to those who are involved in the platform and the community, but without the time to follow enough of the conversations in all the places to find the ones interesting to them. By acting as a filter, more people will be able to be involved in the things which interest them, resulting in an increase of higher quality submissions for members of the community who might not be heard from as much.</p>
<h3>Implementation</h3>
<p>The key to its success is to produce something which is useful, integrated and deterministic; but without being a massive resource hog.</p>
<p>Produced weekly, every week, with a series of sections - probably similar to those on tmo. Something like:</p>
<ul>
<li>Front page</li>
<li>Applications</li>
<li>Development</li>
<li>Community</li>
<li>Devices</li>
<li>Maemo in the Wild</li>
<li>...</li>
</ul>
<p>To gather the news, a series of sub-editors/contributors would have access to a Twitter account (@maemoweeklynews, say). The posts to this feed would consist of the section, a few keywords and a link to the content (thread, post, email message, blog) which triggered it. For example, recently this may include:</p>
<ul>
<li><em>Applications</em> - wazd helping qwerty12 on Transmission: <a href="http://s56.radikal.ru/i152/0911/34/a388e13890a0.png">http://s56.radikal.ru/i152/0911/34/a388e13890a0.png</a></li>
<li><em>Devices</em> - Release firmware available to download: <a href="http://flors.wordpress.com/2009/11/16/maemo-5-final-release-updated-sdk-and-firmware/">http://flors.wordpress.com/2009/11/16/maemo-5-final-release-updated-sdk-and-firmware/</a></li>
</ul>
<p>Suggestions on content could be directed at it from people's own Twitter accounts. The sub-editors would then be able to pick and choose from these if it's something they'd missed.</p>
<p>As each issue is being pulled together, one or more sub-editors would then review the posts to that Twitter feed for their sections and flesh it out with a longer paragraph/quote. Full-blown stories would also be possible, but I imagine that being a rarity (if ever). There would then be an overall editor(s) making sure there's no duplication and also including things from maemo.org/downloads/ (top 10 apps, and new apps this week) and the bug jars (top 10 activity, probably).</p>
<p>The completed digest would then be posted to a site and syndicated to Planet.</p>
<p>Hopefully this shouldn't be too much work; and sub-editors/contributors would be able to post to the feed during their daily review of their slice of the community.</p>
<p>To collect the sub-editors, I'd suggest a recruitment &amp; screening process of the form "what 3 would you have done for last week?" See more details below.</p>
<h3>Getting Involved</h3>
<p>I'm now looking for:</p>
<ol>
<li><p><strong>CONTRIBUTORS:</strong> long-standing members of the community to volunteer to highlight content they see during their Maemo day. This could be whilst sat on IRC, reading the mailing lists, watching maemo.org/news/, contributing on Brainstorm or reading Talk. <em>The only extra work you'd have to do was use your favourite Twitter client to post links you thought should be in the digest.</em></p>
<p>Approx. number of positions: 20-30</p></li><br />
<li><p><strong>SUB-EDITORS:</strong> contributors who are also willing to flesh out the links each week by selecting a representative quote. I will be ensuring we have the tools in place to make this as easy as possible.</p>
<p>Approx. number of positions: 5-10</p></li><br />
<li><p><strong>EDITORS:</strong> the people with ultimately responsibility. The sub-editors who make sure the whole thing is consistent.</p>
<p>Approx. number of positions: 2-4</p></li>
</ol>
<p>As I want to start it small (it can always grow once we work out the details a bit better and see how it goes), anyone who'd like to be involved can reply to this (it'll be on maemo-community, my blog and talk.maemo.org) with:</p>
<ul>
<li>maemo.org username</li>
<li>Position wanted (contributor/sub-editor/editor)</li>
<li>Channels you follow</li>
<li>Preferred section(s) if sub-editor (feel free to make up a new one)</li>
<li>One/two sentence bio.</li>
<li>Two or three links you'd've posted in the last 2 weeks.</li>
</ul>
<p>This is an opportunity to help collaborate and facilitate spreading Maemo news; if you're a long-time contributor to the platform, your insights will be invaluable. If you're a relative newcomer, looking for a way to contribute, this is your chance!</p>
]]></content:encoded>
		</item>

		
		<item rdf:about="http://www.maemopeople.org/index.php/jaffa/2009/10/13/downloading_ovi_maps_without_a_network_c">
			<title>Downloading Ovi Maps without a network connection</title>
			<link>http://www.maemopeople.org/index.php/jaffa/2009/10/13/downloading_ovi_maps_without_a_network_c</link>
			<dc:date>2009-10-13T09:21:08Z</dc:date>
			<dc:creator>Jaffa</dc:creator>
			<dc:subject>Maemo</dc:subject>
			<description>Unlike Navicore/Wayfinder on previous Maemo devices, Ovi Maps on the N900 downloads maps on demand. This is obviously a problem if you're going somewhere abroad and don't want to pay extortionate data roaming charges.

Fortunately, S60 Ovi Maps users also have the same problem, and the solution is straightforward:


Scroll down the above URL and download the maps for the countries you are interested in. Obviously skip the instructions about downloading Ovi Maps - the N900 has Ovi Maps already installed!
Unzip the maps into cities/diskcache on the big VFAT partition (mounted under MyDocs) on your N900.
That's it!


Some of the files you may already have, I've chosen to overwrite them; YMMV.

However, as far as I can tell, searching for locations still requires a network connection :-(

</description>
			<content:encoded><![CDATA[<p>Unlike Navicore/Wayfinder on previous Maemo devices, Ovi Maps on the N900 downloads maps on demand. This is obviously a problem if you're going somewhere abroad and don't want to pay extortionate data roaming charges.</p>

<p>Fortunately, S60 Ovi Maps users also have the same problem, and the solution is straightforward:</p>

<ol>
<li>Scroll down the above URL and <a href="http://handphone-solution.blogspot.com/2009/07/direct-download-for-ovi-maps-30-without.html">download</a> the maps for the countries you are interested in. <strong>Obviously skip the instructions about downloading Ovi Maps - the N900 has Ovi Maps already installed!</strong></li><br />
<li><p>Unzip the maps into <code>cities/diskcache</code> on the big VFAT partition (mounted under <code>MyDocs</code>) on your N900.</p>
<li>That's it!</li>
</li></ol>

<p>Some of the files you may already have, I've chosen to <em>overwrite them; YMMV.</em></p>

<p>However, as far as I can tell, searching for locations still requires a network connection :-(</p>

]]></content:encoded>
		</item>

		
		<item rdf:about="http://www.maemopeople.org/index.php/jaffa/2009/09/21/why_i_m_not_standing_for_the_council_but">
			<title>Why I'm not standing for the council... but you should still vote!</title>
			<link>http://www.maemopeople.org/index.php/jaffa/2009/09/21/why_i_m_not_standing_for_the_council_but</link>
			<dc:date>2009-09-21T09:43:32Z</dc:date>
			<dc:creator>Jaffa</dc:creator>
			<dc:subject>Maemo</dc:subject>
			<description>As those of you who read maemo-community might know, I've decided not to run for the council this time.

I'm really proud of being a part of the first two councils, and the level of trust Nokia placed in us with the recruitment of the debmaster; chairing the sprint meetings for the gang-of-four; the decisions over the summit and inviting us to the launch of the N900 at Nokia World.

My enthusiasm for Maemo is not diminished; indeed, with the launch of the N900, I'm as excited now as I was waiting for the launch of the 770 back in November 2005. However, after a year on the council, I'm now looking forward to six months as "just" a normal community member. I've not come to this decision easily, and I'm very happy to have had such warm words of encouragement. My reasons are two-fold:


There are many other members of the community who should have a chance to represent us. In particular, I'm very happy that Stephen (sjgadsby), Val&#233;rio (VDVsx) and Graham (gcobb) have chosen to accept my nomination of them. The fact they're joined by the likes of Alan Bruce (qole), Gary Birkett (lcuk) and Jay Carter (zerojay) - and others - is even better.
The vitriol and nastiness spewed by a very vocal, but tiny, minority of people on talk.maemo.org - especially regarding the transition of internettablettalk.com to talk.maemo.org - took a lot of the fun away. Given the massive investment of time my role as chair required, taking the fun away removed one of the main motivations for me.


I still plan on being an active (and vocal) community member both as a developer, a community evangelist and as a user. I hope that if you would have voted for me, you consider voting for one of the excellent candidates we have standing (and we have many). In particular, Stephen, Val&#233;rio and Graham have all been long term contributors in many different ways and are tolerant, helpful people. I will struggle to cast my single transferable vote for them, Gary, Alan and Jay.

However whomever you vote for, please do vote (once you receive your voting tokens)! I think that the Community Council has been far more effective than I ever imagined it could be when I suggested it back in 2008 and I look forward to seeing where this community will go in the next six months
</description>
			<content:encoded><![CDATA[<p>As those of you who read <a href="http://lists.maemo.org/mailman/listinfo/maemo-community">maemo-community</a> might <a href="http://lists.maemo.org/pipermail/maemo-community/2009-September/002833.html">know</a>, I've decided <em>not</em> to run for the <a href="http://wiki.maemo.org/Community_Council">council</a> this time.</p>

<p>I'm really proud of being a part of the first two councils, and the level of trust Nokia placed in us with the recruitment of the <var>debmaster</var>; chairing the sprint meetings for the gang-of-four; the decisions over the summit and inviting us to the launch of the N900 at Nokia World.</p>

<p>My enthusiasm for Maemo is not diminished; indeed, with the launch of the N900, I'm as excited now as I was waiting for the launch of the 770 back in November 2005. However, after a year on the council, I'm now looking forward to six months as "just" a normal community member. I've not come to this decision easily, and I'm very happy to have had such warm words of encouragement. My reasons are two-fold:</p>

<ol>
<li>There are many other members of the community who should have a chance to represent us. In particular, I'm very happy that Stephen (<a href="http://maemo.org/profile/view/sjgadsby/">sjgadsby</a>), Val&#233;rio (<a href="http://maemo.org/profile/view/vdvax/">VDVsx</a>) and Graham (<a href="http://maemo.org/profile/view/gcobb/">gcobb</a>) have chosen to accept my nomination of them. The fact they're joined by the likes of Alan Bruce (<a href="http://maemo.org/profile/view/qole/">qole</a>), Gary Birkett (<a href="http://maemo.org/profile/view/lcuk/">lcuk</a>) and Jay Carter (<a href="http://maemo.org/profile/view/zerojay/">zerojay</a>) - and <a href="http://wiki.maemo.org/Community_Council/Candidate_declarations_for_September_2009">others</a> - is even better.</li><br />
<li>The vitriol and nastiness spewed by a very vocal, but tiny, minority of people on <a href="http://talk.maemo.org/">talk.maemo.org</a> - especially regarding <a href="http://talk.maemo.org/showthread.php?t=28674">the transition of internettablettalk.com to talk.maemo.org</a> - took a lot of the fun away. Given the massive investment of time my role as chair required, taking the fun away removed one of the main motivations for me.</li>
</ol>

<p>I still plan on being an active (and vocal) community member both as a developer, a community evangelist and as a user. I hope that if you would have voted for me, you consider voting for one of the excellent candidates we have standing (and we have many). In particular, Stephen, Val&#233;rio and Graham have all been long term contributors in many different ways and are tolerant, helpful people. I will struggle to cast my single transferable vote for them, Gary, Alan and Jay.</p>

<p>However whomever you vote for, please do <a href="http://maemo.org/vote/vote.php?election_id=7">vote</a> (once you receive your voting tokens)! I think that the Community Council has been far more effective than I ever imagined it could be when I suggested it back in 2008 and I look forward to seeing where this community will go in the next six months</p>
]]></content:encoded>
		</item>

		</rdf:RDF>
