Congratulations!
This is a valid RSS feed.
Recommendations
This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.
line 242, column 0: (2 occurrences) [help]
<content:encoded><![CDATA[<p>Announcing another maemo.org Bugday: </p>
Source: http://blogs.gnome.org/aklapper/category/computer/maemo/feed/rss/
<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"xmlns:content="http://purl.org/rss/1.0/modules/content/"xmlns:wfw="http://wellformedweb.org/CommentAPI/"xmlns:dc="http://purl.org/dc/elements/1.1/"xmlns:atom="http://www.w3.org/2005/Atom"xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"xmlns:slash="http://purl.org/rss/1.0/modules/slash/"xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"><channel><title>maemo – andré klapper's blog.</title><atom:link href="https://blogs.gnome.org/aklapper/category/computer/maemo/feed/" rel="self" type="application/rss+xml" /><link>https://blogs.gnome.org/aklapper</link><description>i'm not dead yet, but i'm working on it.</description><lastBuildDate>Tue, 03 Jan 2012 17:05:16 +0000</lastBuildDate><language>en-US</language><sy:updatePeriod>hourly </sy:updatePeriod><sy:updateFrequency>1 </sy:updateFrequency><generator>https://wordpress.org/?v=6.2.2</generator><item><title>Maemo, MeeGo, Mer, Tizen: Short statūs</title><link>https://blogs.gnome.org/aklapper/2012/01/03/maemo-meego-tizen-mer/</link><comments>https://blogs.gnome.org/aklapper/2012/01/03/maemo-meego-tizen-mer/#comments</comments><dc:creator><![CDATA[aklapper]]></dc:creator><pubDate>Tue, 03 Jan 2012 17:05:16 +0000</pubDate><category><![CDATA[computer]]></category><category><![CDATA[lang-en]]></category><category><![CDATA[maemo]]></category><category><![CDATA[meego]]></category><guid isPermaLink="false">http://blogs.gnome.org/aklapper/?p=1041</guid><description><![CDATA[While the official Maemo platform (led by Nokia) is not actively developed anymore, some 3rd party Extras and the Maemo Community Updates project (which welcomes helping hands) are quite alive. MeeGo never managed to fulfil its own expectations with regard … <a href="https://blogs.gnome.org/aklapper/2012/01/03/maemo-meego-tizen-mer/">Continue reading <span class="meta-nav">→</span></a>]]></description><content:encoded><![CDATA[<p>While the official <a href="http://maemo.org/">Maemo</a> platform (led by Nokia) is not actively developed anymore, some 3rd party Extras and the <a href="http://wiki.maemo.org/Community_SSU">Maemo Community Updates</a> project (which welcomes helping hands) are quite alive. <br /><a href="https://meego.com/">MeeGo</a> <a href="http://lwn.net/Articles/444567/">never managed</a> to fulfil its own expectations with regard to <a href="http://blogs.gnome.org/aklapper/2011/06/21/meego-qa-and-re-questions/">openness and transparency</a> and is also more or less dead. <br /><a href="https://www.tizen.org/">Tizen</a> (MeeGo’s successor) is still <a href="https://en.wikipedia.org/wiki/Vaporware">vaporware</a> plus <a href="https://www.tizen.org/community">membership is mostly invite-only</a> while I prefer transparency. </p><p><a href="http://merproject.org/"><img decoding="async" loading="lazy" src="http://blogs.gnome.org/aklapper/files/2012/01/Mer_Logo.png" alt="Mer Logo" width="128" height="140" class="alignright size-full wp-image-1044" /></a>What is left and to recommend in this area is <a href="http://merproject.org/">Mer</a>, a community-driven project based on MeeGo with real open governance and trustworthy maintainers that know how to communicate.</p><p>Consequently I have removed my admin flag for MeeGo’s bugtracker (it <a href="https://bugs.meego.com/show_bug.cgi?id=24590">feels unmaintained</a> anyway) and unsubscribed from nearly all MeeGo and Tizen mailing lists. <br />I will continue to stick around in the Maemo and Mer communities (mailing lists, IRC, bugtrackers) as they currently feel like the places to be. Cheers!</p>]]></content:encoded><wfw:commentRss>https://blogs.gnome.org/aklapper/2012/01/03/maemo-meego-tizen-mer/feed/</wfw:commentRss><slash:comments>6</slash:comments></item><item><title>MeeGo conference San Francisco</title><link>https://blogs.gnome.org/aklapper/2011/05/26/meego-conf-sf/</link><comments>https://blogs.gnome.org/aklapper/2011/05/26/meego-conf-sf/#comments</comments><dc:creator><![CDATA[aklapper]]></dc:creator><pubDate>Thu, 26 May 2011 06:36:35 +0000</pubDate><category><![CDATA[computer]]></category><category><![CDATA[lang-en]]></category><category><![CDATA[maemo]]></category><category><![CDATA[meego]]></category><guid isPermaLink="false">http://blogs.gnome.org/aklapper/?p=911</guid><description><![CDATA[I went to San Francisco (US&A) to play Ping-Pong with Chris (I also recommend him as a tour guide – he knows the city). At the same time a conference took place. At the weekend’s preconference I discussed MeeGo L10N … <a href="https://blogs.gnome.org/aklapper/2011/05/26/meego-conf-sf/">Continue reading <span class="meta-nav">→</span></a>]]></description><content:encoded><![CDATA[<p>I went to San Francisco (US&A) to play Ping-Pong with <a href="http://blixtra.org/blog/">Chris</a> (I also recommend him as a tour guide – he knows the city). At the same time <a href="http://sf2011.meego.com/">a conference</a> took place.</p><p>At the weekend’s preconference I discussed MeeGo L10N with <a href="https://meego.com/users/margie">Margie</a>. I <a href="http://lists.meego.com/pipermail/meego-il10n/2011-May/000454.html">cleaned</a> up <a href="http://wiki.meego.com/Localization_team">the wiki</a> before, but still there is enough to still sort out:</p><ul><li><a href="http://wiki.meego.com/How_to_run_a_translation_team">no rules for starting a translation team or conflict management</a></li><li>No deadlines / <a href="http://wiki.meego.com/String_Freeze_Policy">String freezes</a> / decision processes for break approvals</li><li>For GTK based modules, developers often forget to add an entry to the LINGUAS file when adding .po files</li><li>no <a href="http://wiki.meego.com/Localization_team#Information_for_software_developers">instructions for Gtk Internationalization</a> for Developers (the <a href="https://live.gnome.org/TranslationProject/DevGuidelines/">GNOME documentation</a> might be helpful here)</li><li>The GLS prefix in bug summaries is confusing (it stands for “Global Languages Solutions”) – <a href="http://lists.meego.com/pipermail/meego-il10n/2011-May/000498.html">some plans to change this</a>.</li></ul><p>The most important talk from my point of view was <a href="https://meego.com/users/stskeeps">Carsten</a>‘s “<a href="http://sf2011.meego.com/program/sessions/transparency-inclusion-and-meritocracy-meego-theory-and-practice">Transparency, inclusion and meritocracy in MeeGo: Theory and practice</a>” showing some of the transparency problems that MeeGo has not only after one of the two bigger companies involved <a href="http://conversations.nokia.com/2011/02/11/open-letter-from-ceo-stephen-elop-nokia-and-ceo-steve-ballmer-microsoft/">announced a change in direction</a>.</p><p>There was also a <a href="http://sf2011.meego.com/program/sessions/bof-meego-release-engineering">Release Engineering BoF</a>. A great opportunity as so far <a href="http://lists.meego.com/pipermail/meego-pm/2011-May/000071.html">I had been totally unsuccessful</a> in understanding how this works in MeeGo. This has not improved yet though. It looks like decisions are made completely in private in the offices of one company (Intel) instead of the public (internet). Other issues: The Submit Request account process is not documented – how to contribute from a new company? You’d expect something other than dead silence here. But it was agreed on that the <a href="http://wiki.meego.com/Core_OS_Program/changecontrol#Approvers">CCB</a> (Change Control Board) process for MeeGo 1.2 was completely invisible and “crap”. (<a href="https://meego.com/users/dawnfoster">Dawn</a> might now complain about my use of language, but this was the wording used by those running the session.)</p><p>But the original reason to come here was MeeGo’s Error Management (EM) and Quality Assurance (QA). I outlined <a href="http://lists.meego.com/pipermail/meego-qa/2011-May/001604.html">some EM and QA issues to discuss</a> on the meego-qa mailing list before the conference took place. See the <a href="http://lists.meego.com/pipermail/meego-qa/2011-May/001673.html">summary of this BoF</a>. Hoping to see further discussions of issues in the public, as agreed upon. <br /><a href="https://meego.com/users/iekku">Iekku</a> and I gave <a href="http://sf2011.meego.com/program/sessions/bug%E2%80%99s-life-presentation-bug%E2%80%99s-life-cycle">a talk on the basics of bug handling</a>. Plus <a href="https://meego.com/users/ericlr">Eric</a> and <a href="https://meego.com/users/sdjayna">Stephen</a> presented <a href="http://sf2011.meego.com/program/sessions/bam-bud-and-bugzilla-extension-mechanism-revealed">some cute Bugzilla extensions</a> but I leave it to them to blog and email about it (a good task as they have been too silent and invisible so far).</p>]]></content:encoded><wfw:commentRss>https://blogs.gnome.org/aklapper/2011/05/26/meego-conf-sf/feed/</wfw:commentRss><slash:comments>3</slash:comments></item><item><title>Naoko</title><link>https://blogs.gnome.org/aklapper/2011/05/18/naoko/</link><comments>https://blogs.gnome.org/aklapper/2011/05/18/naoko/#comments</comments><dc:creator><![CDATA[aklapper]]></dc:creator><pubDate>Wed, 18 May 2011 09:44:48 +0000</pubDate><category><![CDATA[computer]]></category><category><![CDATA[gnome]]></category><category><![CDATA[lang-en]]></category><category><![CDATA[maemo]]></category><category><![CDATA[misc]]></category><category><![CDATA[non-technical]]></category><category><![CDATA[prague]]></category><guid isPermaLink="false">http://blogs.gnome.org/aklapper/?p=904</guid><description><![CDATA[In case Miguel makes it popular to take the name of a previous company and change the order of the letters a bit to find a name for a new company, this is my proposal for Nokia (as I pass … <a href="https://blogs.gnome.org/aklapper/2011/05/18/naoko/">Continue reading <span class="meta-nav">→</span></a>]]></description><content:encoded><![CDATA[<p>In case <a href="http://tirania.org/blog/archive/2011/May-16.html">Miguel</a> makes it popular to take the <a href="https://secure.wikimedia.org/wikipedia/en/wiki/Ximian">name of a previous company</a> and change the order of the letters a bit to find a name for a <a href="http://www.xamarin.com/">new company</a>, this is my proposal for Nokia (as I pass that shop quite often at night when going home and have to smile everytime):</p><p><img decoding="async" loading="lazy" src="http://blogs.gnome.org/aklapper/files/2011/05/20110515_naoko.jpg" alt="Naoko" width="460" height="259" class="aligncenter size-full wp-image-905" /></p>]]></content:encoded><wfw:commentRss>https://blogs.gnome.org/aklapper/2011/05/18/naoko/feed/</wfw:commentRss><slash:comments>2</slash:comments></item><item><title>My MeeGo bugtriaging experience so far</title><link>https://blogs.gnome.org/aklapper/2010/12/08/my-meego-bugtriaging-experience-so-far/</link><comments>https://blogs.gnome.org/aklapper/2010/12/08/my-meego-bugtriaging-experience-so-far/#comments</comments><dc:creator><![CDATA[aklapper]]></dc:creator><pubDate>Wed, 08 Dec 2010 00:39:02 +0000</pubDate><category><![CDATA[computer]]></category><category><![CDATA[lang-en]]></category><category><![CDATA[maemo]]></category><category><![CDATA[meego]]></category><guid isPermaLink="false">http://blogs.gnome.org/aklapper/?p=754</guid><description><![CDATA[But it happened that it was early October and that I felt like diving into MeeGo bugtriaging. After some public whining, Carsten (who’s always a huge help) and Dawn were kind enough to point out the existence of the meego-qa … <a href="https://blogs.gnome.org/aklapper/2010/12/08/my-meego-bugtriaging-experience-so-far/">Continue reading <span class="meta-nav">→</span></a>]]></description><content:encoded><![CDATA[<p>But it happened that it was early October and that I felt like diving into <a href="http://meego.com/">MeeGo</a> bugtriaging. After some public whining, <a href="http://meego.com/users/stskeeps">Carsten</a> (who’s always a huge help) and <a href="http://meego.com/users/dawnfoster">Dawn</a> were kind enough to point out the existence of the <a href="http://lists.meego.com/listinfo/meego-qa">meego-qa mailing list</a>. I subscribed.</p><p>At that time there also was a <a href="http://wiki.meego.com/Quality/Bugtriage#MeeGo_Bug_Triage_Team">wikipage</a> with a list of names (“Contact the first person in the team” without any hints how to) and an IRC channel (#meego-bugs on Freenode) with one or two people but not much feedback.</p><p>Being in a <a href="http://www.urbandictionary.com/define.php?term=JFDI">JFDI</a> mood I moved some wikipages (related information was split under wiki.meego.com/Quality and wiki.meego.com/Bugzilla) and asked some questions on the mailing list. Some have been answered, others haven’t. <br />I sometimes wondered if either QA engineers don’t know answers or if QA management prefers to remain silent to avoid making decisions, or if a few people just consider documenting their workflows and communicating what they are working on in public a waste of time.</p><p>What has changed: <br />I set up a <a href="http://wiki.meego.com/Quality/Bugtriage_Guide">triage guide</a>. <br />The <a href="http://wiki.meego.com/Quality/Bugtriage#MeeGo_Bug_Triage_Meetings">bugtriage meetings</a> are now on IRC, in public. <br />The wikipage looks way better, things have become more transparent in general, and the IRC channel constantly has some people lurking around. <br />On a related note, the <a href="http://video.linuxfoundation.org/video/1902">QA talk at MeeGo conference</a> was particularly helpful to get the broader picture of all the MeeGo QA tasks and to realize that bugtriaging is just a small part of the picture.</p><p>Next on my list is to start collecting stock answers (<a href="http://wiki.maemo.org/Bugs:Stock_answers">like in Maemo</a>) which requires help from triagers having specific knowledge. However, as I like to sort them by Bugzilla products, I am a bit reluctant as <a href="http://meego.com/users/ericlr">Eric</a> said that the classification and product structure in MeeGo Bugzilla will probably change a bit after deploying Bugzilla 3.6.</p><p>Still there is enough to do and I am not happy with the current “openness” state. Remaining unanswered questions that I cannot “solve” myself as I miss information:</p><ul><li>Who “defined” who became/is a triage team lead (=first person in each of the <a href="http://wiki.meego.com/Quality/Bugtriage#MeeGo_Bug_Triage_Team">triager lists</a>)? Were there elections, was it a decision of the companies involved, or was it meritocratic?</li><li>Why should I add my name to the <a href="http://wiki.meego.com/Quality/Bugtriage#MeeGo_Bug_Triage_Team">triager lists</a> as I could also triage without adding my name to a wikipage? What obligations are connected to adding my name?</li><li>What is concretely the job of “triage team leads” in contrast to “normal” team members? Why was a hierarchy considered as needed and introduced?</li><li>Documented permission requirements are missing. For example feature requests in bugs.meego.com cannot be fully edited without permissions (e.g. “Summary” line is non-editable). I don’t want to discuss the usefulness that I cannot fix typos in summaries because of that, but I’d like to see this documented in the wiki at least as I might not be the only person who was initially confused by it. I can’t document it myself as I don’t know the exact reasons behind this.</li><li>What does “Error Manager rights on MeeGo Bugzilla” actually mean? Filed a <a href="http://bugs.meego.com/show_bug.cgi?id=8848">bug report</a>, no progress yet. Feel free to vote.</li><li>Missing policy when to completely block access to a report and when to just mark specific comments as private – See <a href="http://www.mail-archive.com/meego-qa@lists.meego.com/msg00042.html">my posting</a>.</li><li>Difference and handling of “enhancement” severity vs. “MeeGo Features” classification and documenting the explanation <a href="http://wiki.meego.com/Quality/Bugtriage_Guide#What_severity.2Fpriority_should_be_set.3F">in the wiki</a>.</li><li>There is a list of <a href="http://wiki.meego.com/MeeGoBugzilla_Customization">code customizations</a> for MeeGo Bugzilla. Are the source code patches somewhere available? Have they been upstreamed or submitted as patches in bugzilla.mozilla.org (in case that it makes sense)? If not, why not, and is it planned to do so?</li><li>Where to handle MeeGo Extras/Surrounds apps bug reports? – See <a href="http://www.mail-archive.com/meego-qa@lists.meego.com/msg00107.html">posting here</a>.</li></ul>]]></content:encoded><wfw:commentRss>https://blogs.gnome.org/aklapper/2010/12/08/my-meego-bugtriaging-experience-so-far/feed/</wfw:commentRss><slash:comments>1</slash:comments></item><item><title>bugs.maemo.org updated to 3.4</title><link>https://blogs.gnome.org/aklapper/2010/12/01/bugs-maemo-org-updated-to-3-4/</link><comments>https://blogs.gnome.org/aklapper/2010/12/01/bugs-maemo-org-updated-to-3-4/#comments</comments><dc:creator><![CDATA[aklapper]]></dc:creator><pubDate>Wed, 01 Dec 2010 04:47:50 +0000</pubDate><category><![CDATA[computer]]></category><category><![CDATA[lang-en]]></category><category><![CDATA[maemo]]></category><category><![CDATA[meego]]></category><guid isPermaLink="false">http://blogs.gnome.org/aklapper/?p=744</guid><description><![CDATA[As some might have noticed, bugs.maemo.org was upgraded from ancient version 2.22 to 3.4 last week. This means we now have a version running that is maintained upstream, a design that fits to the rest of maemo.org, less noisy comments, … <a href="https://blogs.gnome.org/aklapper/2010/12/01/bugs-maemo-org-updated-to-3-4/">Continue reading <span class="meta-nav">→</span></a>]]></description><content:encoded><![CDATA[<p>As some might have noticed, <a href="https://bugs.maemo.org">bugs.maemo.org</a> was upgraded from ancient version 2.22 to 3.4 last week. This means we now have a version running that is maintained upstream, a design that fits to the rest of <a href="http://maemo.org">maemo.org</a>, <a href="https://bugs.maemo.org/show_bug.cgi?id=8551">less noisy comments</a>, a <a href="https://bugs.maemo.org">frontpage</a> that now states “This is a community issue tracker, sponsored by Nokia, not a Nokia communication channel”, and <a href="https://bugs.maemo.org/show_bug.cgi?id=6272">less complexity</a> by e.g. hiding fields that normal users don’t ever need when filing a report. Plus we are not at the bottom of LPSolit’s <a href="https://lpsolit.wordpress.com/bugzilla-usage-worldwide/">list of Bugzilla installations</a> anymore. ;-)</p><p>All kudos goes to <a href="http://blogs.gnome.org/kbrae/2010/09/23/bugzilla-3-4-for-maemo-org/">Karsten Bräckelmann</a> for lots of work (like applying the maemo.org wide theme, turning some image files into pure CSS, and tracking down ugly database transition issues), <a href="http://amigadave.blogspot.com/2010/09/maemoorg-bugzilla-update.html">David King</a> for continuing with finetuning and fixing missing pieces, and <a href="http://maemo.org/profile/view/feri/">Ferenc Szekely</a> for testing and deploying!</p><p>Today I finished updating my little <a href="http://home.arcor.de/ak-47/pub/bugsmaemoorg_triage_help.user.js">Greasemonkey triage helper script for maemo.org Bugzilla</a> so it should be functional again.</p><p>I also wrote an initial <a href="http://home.arcor.de/ak-47/pub/bugsmeegocom_triage_help.user.js">Greasemonkey triage helper script for meego.com Bugzilla</a> that provides some common one-click stock answers and will display the email addresses of commenters and reporters by default (I like to spot immediately if a commenter has a corporate background).</p><p>(On a side note, yes, <a href="https://mozillalabs.com/jetpack/">Mozilla Jetpack extensions</a> are of course the future and to supersede Greasemonkey, like Matěj’s <a href="https://fedorahosted.org/bugzilla-triage-scripts/">bugzilla-triage-scripts</a>. That’s on the ever-growing to-do list.)</p>]]></content:encoded><wfw:commentRss>https://blogs.gnome.org/aklapper/2010/12/01/bugs-maemo-org-updated-to-3-4/feed/</wfw:commentRss><slash:comments>6</slash:comments></item><item><title>MeeGo Conference 2010</title><link>https://blogs.gnome.org/aklapper/2010/11/21/meego-conference-2010/</link><comments>https://blogs.gnome.org/aklapper/2010/11/21/meego-conference-2010/#comments</comments><dc:creator><![CDATA[aklapper]]></dc:creator><pubDate>Sun, 21 Nov 2010 19:25:15 +0000</pubDate><category><![CDATA[computer]]></category><category><![CDATA[lang-en]]></category><category><![CDATA[maemo]]></category><category><![CDATA[meego]]></category><guid isPermaLink="false">http://blogs.gnome.org/aklapper/?p=713</guid><description><![CDATA[The enthusiasm at this conference was pretty impressive. It was probably the right boost for the MeeGo project at the right time as engineers of involved companies could get to know each other and hopefully now also understand a bit … <a href="https://blogs.gnome.org/aklapper/2010/11/21/meego-conference-2010/">Continue reading <span class="meta-nav">→</span></a>]]></description><content:encoded><![CDATA[<p>The enthusiasm at this conference was pretty impressive. It was probably the right boost for the <a href="http://meego.com/">MeeGo project</a> at the right time as engineers of involved companies could get to know each other and hopefully now also understand a bit better the needs and expectations of the community with regard to openness. At least some of them. ;-) </p><p><img decoding="async" loading="lazy" src="http://blogs.gnome.org/aklapper/files/2010/11/MeeGo_logo.png" alt="MeeGo" title="MeeGo" width="309" height="102" class="alignright size-full wp-image-716" srcset="https://blogs.gnome.org/aklapper/files/2010/11/MeeGo_logo.png 309w, https://blogs.gnome.org/aklapper/files/2010/11/MeeGo_logo-150x49.png 150w, https://blogs.gnome.org/aklapper/files/2010/11/MeeGo_logo-300x99.png 300w" sizes="(max-width: 309px) 100vw, 309px" /></p><p>(Compared to other conferences) I went to a lot of talks in order to get a better understanding of MeeGo. </p><p>After the initial keynotes and Dawn Foster’s <a href="http://conference2010.meego.com/session/state-community">“State of the community”</a> talk I went to Eric & Stephen’s <a href="http://video.linuxfoundation.org/video/1830">“Error management Tools and Processes”</a> talk which helped realizing what we are after in the field of error management. </p><p>My second day started with Quim’s <a href="http://conference2010.meego.com/session/meego-marketing-brief">Marketing session</a> and Dave Neary’s enjoyable <a href="http://conference2010.meego.com/session/community-anti-patterns">“Community Anti-Patterns”</a> (many of them already well known from Maemo). Didn’t manage to attend Stskeeps’ <a href="http://conference2010.meego.com/session/meego-n900-past-present-and-future">“MeeGo on N900”</a> talk because of some chats in front of the venue and in the entrance hall. Continued with the insightful <a href="http://conference2010.meego.com/session/pushing-meego-internationalization-upstream">“MeeGo L10N/I18N upstream”</a>, <a href="http://conference2010.meego.com/session/inside-look-meego-community-metrics">“Community Metrics”</a> and <a href="http://conference2010.meego.com/session/meego-community-application-support-end-end-story">“Community Application support”</a>. </p><p>The <a href="http://conference2010.meego.com/session/meego-quality-approach">“MeeGo Quality Approach”</a> talk by Veli-Pekka Valula and May Xie was helpful to understand the complexity of <abbr title="Quality Assurance">QA</abbr> and why help in improving the bug management is welcome. Also a nice opportunity to meet the Intel QA folks from the <a href="http://lists.meego.com/listinfo/meego-qa">mailing list</a> in person! </p><p>My own <a href="http://conference2010.meego.com/session/handling-bug-reports-bugsmeegocom"><abbr title="Birds of a Feather">BoF</abbr> session</a> “Handling bug reports in bugs.meego.com” was on Wednesday morning right after the great Guinness party the evening before. Hence I incorrectly expected not to see many people around (and me being sleepy and tired) but according to feedback it went well and I think we had fun (well, <a href="http://www.flickr.com/photos/ju-key/5183778955/">I</a> had!). <br />When I created <a href="http://people.gnome.org/~aklapper/meego-conference2010/slides-bugmanaging.pdf">my slides</a> I had Josh Berkus’ <a href="http://video.linuxfoundation.org/video/1715">“How to Prevent Community: Making Sure Your Pond Stays Small”</a> in mind but I kept sticking to issues specific to bug management that could be done better in Maemo and MeeGo. Right now there are mostly bug reports by people with a technical background in the <a href="http://bugs.meego.com/">bugtracker</a> but once MeeGo becomes more popular we will have to deal with user reports with different qualities and points of view. <br />I hope the video will soon be available <a href="http://video.linuxfoundation.org/">somewhere here</a>. </p><p>All in all I had a good time in Dublin that left me in a positive mood regarding the future of MeeGo.</p>]]></content:encoded><wfw:commentRss>https://blogs.gnome.org/aklapper/2010/11/21/meego-conference-2010/feed/</wfw:commentRss><slash:comments>1</slash:comments></item><item><title>Three interesting Maemo5 bits</title><link>https://blogs.gnome.org/aklapper/2010/08/16/three-interesting-maemo5-bits/</link><comments>https://blogs.gnome.org/aklapper/2010/08/16/three-interesting-maemo5-bits/#comments</comments><dc:creator><![CDATA[aklapper]]></dc:creator><pubDate>Mon, 16 Aug 2010 12:23:19 +0000</pubDate><category><![CDATA[computer]]></category><category><![CDATA[lang-en]]></category><category><![CDATA[maemo]]></category><guid isPermaLink="false">http://blogs.gnome.org/aklapper/?p=600</guid><description><![CDATA[End of Life for Maemo5 hildon-desktop & friends. Being honest and communicating that something is dead: New, and good. On the wishlist for next time: Announce it on the developer mailing list (though that implies interaction with people outside of … <a href="https://blogs.gnome.org/aklapper/2010/08/16/three-interesting-maemo5-bits/">Continue reading <span class="meta-nav">→</span></a>]]></description><content:encoded><![CDATA[<ul><li><a href="http://maemo.gitorious.org/fremantle-hildon-desktop/hildon-desktop/commit/624231109e727e7b4c21c9f1a526ff191c309e5a">End of Life for Maemo5 hildon-desktop & friends</a>. <br />Being honest and communicating that something is dead: New, and good. <br />On the wishlist for next time: Announce it on the <a href="http://wiki.maemo.org/Community_mailing_lists#maemo-devel">developer mailing list</a> (though that implies interaction with people outside of Nokia, scary!) in case somebody wants to pick up maintainership. <br />Unlikely, but still.</li><li>If you want to file bug reports about user interface and platform component issues in Maemo5: It’s <a href="https://bugs.maemo.org/">welcome</a> in case of <i>major</i> issues. Otherwise save your time and efforts as <i>unstable</i> development happens in MeeGo Handset which has its own <a href="https://bugs.meego.com">bugtracker</a> awaiting your bug reports. MeeGo Handset <a href="http://flors.wordpress.com/2010/08/10/running-meego-1-1-unstable-in-your-n900/">can be run on an N900</a> if you love to live on the edge.</li><li><a href="http://talk.maemo.org/showpost.php?p=784443&postcount=32">Quim Gil on Maemo5 Licensing Change Requests</a>.</li></ul>]]></content:encoded><wfw:commentRss>https://blogs.gnome.org/aklapper/2010/08/16/three-interesting-maemo5-bits/feed/</wfw:commentRss><slash:comments>18</slash:comments></item><item><title>Next maemo.org Bugday: Wed, June 30th, 16:00-00:00 UTC</title><link>https://blogs.gnome.org/aklapper/2010/06/23/next-maemo-org-bugday-wed-june-30th-1600-0000-utc/</link><comments>https://blogs.gnome.org/aklapper/2010/06/23/next-maemo-org-bugday-wed-june-30th-1600-0000-utc/#comments</comments><dc:creator><![CDATA[aklapper]]></dc:creator><pubDate>Wed, 23 Jun 2010 04:47:59 +0000</pubDate><category><![CDATA[computer]]></category><category><![CDATA[lang-en]]></category><category><![CDATA[maemo]]></category><guid isPermaLink="false">http://blogs.gnome.org/aklapper/?p=577</guid><description><![CDATA[Announcing another maemo.org Bugday: Wednesday, June 30th, 16:00-00:00 UTC in #maemo-bugs on Freenode IRC No specific topic set – take a look at our wiki for some ideas. Bugdays are about hanging out together on IRC, triaging/discussing some reports in … <a href="https://blogs.gnome.org/aklapper/2010/06/23/next-maemo-org-bugday-wed-june-30th-1600-0000-utc/">Continue reading <span class="meta-nav">→</span></a>]]></description><content:encoded><![CDATA[<p>Announcing another maemo.org Bugday: </p><p><center><b>Wednesday, June 30th, 16:00-00:00 <a href="http://www.timeanddate.com/worldclock/converter.html">UTC</a><br /> in #maemo-bugs on Freenode IRC </b></center></p><p>No specific topic set – take a look at <a href="http://wiki.maemo.org/Bugs:Tasks">our wiki</a> for some ideas. </p><p>Bugdays are about hanging out together on IRC, triaging/discussing some reports in maemo.org Bugzilla, and introducing new people into triaging. No technical knowledge needed, no obligations. Step by and say hello to the <a href="http://wiki.maemo.org/Bugsquad">Bugsquad</a> or become part of it.</p>]]></content:encoded><wfw:commentRss>https://blogs.gnome.org/aklapper/2010/06/23/next-maemo-org-bugday-wed-june-30th-1600-0000-utc/feed/</wfw:commentRss><slash:comments>1</slash:comments></item><item><title>MyNokia in Maemo’s PR1.2 release</title><link>https://blogs.gnome.org/aklapper/2010/06/15/mynokia-in-maemos-pr1-2-release/</link><comments>https://blogs.gnome.org/aklapper/2010/06/15/mynokia-in-maemos-pr1-2-release/#comments</comments><dc:creator><![CDATA[aklapper]]></dc:creator><pubDate>Tue, 15 Jun 2010 13:32:17 +0000</pubDate><category><![CDATA[computer]]></category><category><![CDATA[lang-en]]></category><category><![CDATA[maemo]]></category><guid isPermaLink="false">http://blogs.gnome.org/aklapper/?p=564</guid><description><![CDATA[(I’m not the first person to cover this topic, anyway.) After upgrading my Nokia N900 to the latest software version (PR1.2) I got a “MyNokia” screen after rebooting. Nokia was kind enough to offer me both subscribing to their MyNokia … <a href="https://blogs.gnome.org/aklapper/2010/06/15/mynokia-in-maemos-pr1-2-release/">Continue reading <span class="meta-nav">→</span></a>]]></description><content:encoded><![CDATA[<p>(I’m <a href="http://tabulacrypticum.wordpress.com/2010/06/10/maemo-missteps-for-2010/">not the first person to cover this topic</a>, anyway.) </p><p>After upgrading my Nokia N900 to the latest software version (PR1.2) I got a “MyNokia” screen after rebooting.<br />Nokia was kind enough to offer me both subscribing to their MyNokia service by sending Nokia an SMS message and to read the Terms and Conditions of their service (Terms and Conditions that <a href="https://bugs.maemo.org/show_bug.cgi?id=10261">some people consider either incorrect or even illegal</a>). <br />I assume that in the hurry of getting the PR1.2 release out in time Nokia probably simply forgot to add a “Do not subscribe me” option. But who needs that anyway? It’s hard to imagine why people would not want to use it. You just give Nokia some of your private data and in return you get some cool and totally useful tricks and tips for your N900 that… you had known before already? Nah, come on! </p><p>Sending SMS to Nokia costs money as per <a href="https://bugs.maemo.org/attachment.cgi?id=2875&action=view">Terms and Conditions</a> (“Use of the Service may involve transmission of data through your service provider’s network. Your network service provider may charge for such data transmission.”) Also it’s not clear if the message will be sent to an international number or not (different costs).<br />So I removed the battery to switch off the device. But booting brought up the dialog again. So the available options are “Subscribe” and “Do not use your device”. By subscribing I send them data such as… hmm, what exactly? I cannot find a <i>clear</i> list in the Terms and Conditions. Does Nokia care about my privacy? </p><p>After <i>successfully</i> subscribing you receive an SMS welcoming message from Nokia which does not tell you from which exact phone number but there are <a href="http://talk.maemo.org/showpost.php?p=685145&postcount=62">users that extracted a list</a>. </p><p>To unsubscribe I had to send an SMS again to Nokia that I pay for again. So I went to the Settings section and tried to unsubscribe. And failed with a generic error: “Nokia: Attempt to unsubscribe has failed. Go to ‘My Nokia” in Settings to try again. Visit www.nokia.com/mynokia for more information.” <br />The second sentence told me to try again. So I tried again. And paid again. And failed again. And realized that <a href="https://bugs.maemo.org/show_bug.cgi?id=10261#c7">the UI does not give any indication whether you are currently subscribed or not</a>. <br />The frustrating user interface could be easily fixed by anybody if the code was open source.<br />It is not. </p><p><a href="http://amigadave.blogspot.com/">Dave</a> pointed out that there is a <a href="http://wiki.maemo.org/PR1.2_compulsory_My_Nokia_subscription">workaround for this registration</a>. And there <a href="https://bugs.maemo.org/show_bug.cgi?id=10366">are</a> <a href="https://bugs.maemo.org/show_bug.cgi?id=10261">dozens</a> <a href="http://discussions.nokia.co.uk/t5/Messaging-Email-and-Browsing/Nokia-You-owe-me-more-than-5-for-your-automatic-messages-to-a/td-p/645429">of</a> <a href="http://talk.maemo.org/showthread.php?t=53565">complaints</a>, also from other series than Maemo, which makes me wonder if Nokia Marketing is actually aware of this. </p><p>It was easy to get an answer to my previous question “Does Nokia care about my privacy?”: I simply went to <a href="http://www.nokia.com/privacy-policy">Nokia’s website</a> which states “WE CARE ABOUT YOUR PRIVACY” at the top. <br />Unfortunately they only offer me a postal address in Finland to find out what that exactly means as I have some open questions left – for example which exact data is stored. In accordance to <a href="http://dejure.org/gesetze/BDSG/" lang="de">German law</a> I must be told (§ 6 Abs. 2, § 28 Abs. 4, § 34 Abs. 1-3 BDSG, § 34 Abs. 1, § 43 Abs. 3 BDSG). </p><p>As written in the <a href="https://bugs.maemo.org/attachment.cgi?id=2875&action=view">Terms and Conditions</a>, “Except as set forth in Privacy Policy, Nokia shall not be responsible for any removal of the information or content you have submitted (“Material”) from the Service when your registration is terminated.” <br /><abbr title="I am not a lawyer">IANAL</abbr>, but that does not sound legal to me. </p><p>So if a Nokia Legal person can explain to me how their service and its terms are in accordance to German law (esp. §4 Abs. 3 BDSG) feel encouraged to leave a comment on this blog or send me an email. If this will not happen there are ways to force you to, as already listed here. </p><p>PS: Those who find irony in this posting are free to keep it.</p>]]></content:encoded><wfw:commentRss>https://blogs.gnome.org/aklapper/2010/06/15/mynokia-in-maemos-pr1-2-release/feed/</wfw:commentRss><slash:comments>22</slash:comments></item><item><title>maemo.org Bugday: Tue, May 4th, 17:00-02:00</title><link>https://blogs.gnome.org/aklapper/2010/04/27/maemo-org-bugday-tue-may-4th-1700-0200/</link><dc:creator><![CDATA[aklapper]]></dc:creator><pubDate>Tue, 27 Apr 2010 21:07:28 +0000</pubDate><category><![CDATA[computer]]></category><category><![CDATA[lang-en]]></category><category><![CDATA[maemo]]></category><guid isPermaLink="false">http://blogs.gnome.org/aklapper/?p=532</guid><description><![CDATA[Last time was big fun, hence time for another maemo.org Bugday: Tuesday, May 4th, 17:00-02:00 UTC in #maemo-bugs on Freenode IRC Bugdays are about hanging out together on IRC, triaging/discussing some reports in maemo.org Bugzilla, and introducing new people into … <a href="https://blogs.gnome.org/aklapper/2010/04/27/maemo-org-bugday-tue-may-4th-1700-0200/">Continue reading <span class="meta-nav">→</span></a>]]></description><content:encoded><![CDATA[<p>Last time was big fun, hence time for another maemo.org Bugday: </p><p><b><center>Tuesday, May 4th, 17:00-02:00 <a href="http://www.timeanddate.com/worldclock/converter.html">UTC</a><br />in #maemo-bugs on Freenode IRC </center></b></p><p>Bugdays are about hanging out together on IRC, triaging/discussing some reports in maemo.org Bugzilla, and introducing new people into triaging. </p><p>No technical knowledge needed, no obligations. </p><p>No specific topic – take a look <a href="http://wiki.maemo.org/Bugs:Tasks">here</a> for some ideas. </p><p>Step by and say hello to the <a href="http://wiki.maemo.org/Bugsquad">Bugsquad</a> or become part of it. :-) </p>]]></content:encoded></item></channel></rss>
If you would like to create a banner that links to this page (i.e. this validation result), do the following:
Download the "valid RSS" banner.
Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)
Add this HTML to your page (change the image
srcattribute if necessary):
If you would like to create a text link instead, here is the URL you can use: