Generated.

[homepage.git] / blog / index.rss

diff --git a/blog/index.rss b/blog/index.rss
index f90c04cceb5b85d6fc584e89e603ce52129e69b8..f3d27fa43630ea22a2581bbb97f5539e6613d0bd 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -6,6 +6,60 @@
                 <link>http://people.skolelinux.org/pere/blog/</link>
                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
        
                 <link>http://people.skolelinux.org/pere/blog/</link>
                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
        

+       <item>
+               <title>Fiksgatami tar form - snart klar for test</title>
+               <link>http://people.skolelinux.org/pere/blog/Fiksgatami_tar_form___snart_klar_for_test.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fiksgatami_tar_form___snart_klar_for_test.html</guid>
+                <pubDate>Sun, 13 Feb 2011 21:10:00 +0100</pubDate>
+               <description>
+&lt;p&gt;NUUGs Fiksgatami-tjeneste tar sakte form, og den siste uka har vi
+betalt mySociety i England for å tilpasse kildekoden til deres
+tjeneste slik at den skal fungere for Norge.  I løpet av kommende uke
+regner jeg at vi skal i gang med testing.&lt;/p&gt;
+
+&lt;p&gt;For å forberede testing, har jeg tatt en titt på hva slags
+informasjon som samles inn av kommuner som har lignende tjeneste for
+sin kommune allerede på plass.  Jeg har tittet på tjenestene til
+&lt;a href=&quot;http://www.gatami.no/&quot;&gt;Tromsø&lt;/a&gt;,
+&lt;a href=&quot;http://www.porsgrunn.kommune.no/Hovedmeny/Selvbetjening/MinGate/&quot;&gt;Porsgrunn&lt;/a&gt;
+og &lt;a href=&quot;http://fiksgata.kongsvinger.no/&quot;&gt;Kongsvinger&lt;/a&gt;.  Jeg
+tittet også på
+&lt;a href=&quot;http://www.asker.kommune.no/Dialog/Kontakt-oss/AskerDialogen/&quot;&gt;Askers&lt;/a&gt;,
+som er litt på siden at det jeg skriver om her&lt;/p&gt;
+
+&lt;p&gt;Om problemet samles alle tjenestene inn plassering, enten som
+adresse eller som kartkoordinat.  De samler også inn en
+oppsummering/overskrift og en lengre beskrivelse, og noen av dem
+tillater bilde og vedlegg lagt ved.  Alle problemene tildeles en
+kategori, og det er stort overlapp i kategoriseringen:&lt;/p&gt;
+
+&lt;table&gt;
+&lt;tr&gt;&lt;th&gt;Tromsø&lt;/th&gt;        &lt;th&gt;Porsgrunn&lt;/th&gt;           &lt;th&gt;Kongsvinger&lt;/th&gt;&lt;/tr&gt;
+&lt;tr&gt;&lt;td&gt;Vei&lt;/td&gt;           &lt;td&gt;Hull i veg&lt;/td&gt;          &lt;td&gt;Veg/Vegvedlikehold&lt;/td&gt;&lt;/tr&gt;
+&lt;tr&gt;&lt;td&gt;&lt;/td&gt;              &lt;td&gt;&lt;/td&gt;                    &lt;td&gt;Skilt/Trafikksikkerhet&lt;/td&gt;&lt;/tr&gt;
+&lt;tr&gt;&lt;td&gt;Gatelys&lt;/td&gt;       &lt;td&gt;Gatelys virker ikke&lt;/td&gt; &lt;td&gt;Gatelys&lt;/td&gt;&lt;/tr&gt;
+&lt;tr&gt;&lt;td&gt;Vann og avløp&lt;/td&gt; &lt;td&gt;Vann og avløp&lt;/td&gt;       &lt;td&gt;Vann/Avløp&lt;/td&gt;&lt;/tr&gt;
+&lt;tr&gt;&lt;td&gt;Park&lt;/td&gt;          &lt;td&gt;Park&lt;/td&gt;                &lt;td&gt;Park/Grønt&lt;/td&gt;&lt;/tr&gt;
+&lt;tr&gt;&lt;td&gt;Friluftsliv&lt;/td&gt;   &lt;td&gt;Friluft&lt;/td&gt;&lt;/tr&gt;
+&lt;tr&gt;&lt;td&gt;Renovasjon&lt;/td&gt;    &lt;td&gt;Renovasjon&lt;/td&gt;          &lt;td&gt;Renovasjon/Avfall&lt;/td&gt;&lt;/tr&gt;
+&lt;tr&gt;&lt;td&gt;                   &lt;td&gt;Grafitti-Tagging&lt;/td&gt;    &lt;td&gt;Grafitti/Tagging&lt;/td&gt;&lt;/tr&gt;
+&lt;tr&gt;&lt;td&gt;&lt;/td&gt;              &lt;td&gt;&lt;/td&gt;                    &lt;td&gt;Forsøpling&lt;/td&gt;&lt;/tr&gt;
+&lt;tr&gt;&lt;td&gt;Annet&lt;/td&gt;         &lt;td&gt;Annet&lt;/td&gt;               &lt;td&gt;Annet&lt;/td&gt;&lt;/tr&gt;
+&lt;/table&gt;
+
+&lt;p&gt;Om de som rapporterer inn problemet, blir det samlet inn navn,
+epostadresse, et eller to telefonnummer og for Asker postadresse.
+Noen vil også vite hvordan tilbakemelding ønskes, dvs. epost, telefon
+eller via post.&lt;/p&gt;
+
+&lt;p&gt;Fiksgatami skulle kunne håndtere innsending til disse kommunene
+uten større problemer, tror jeg.  Kategorier defineres per område,
+slik at kommunene kan få meldinger inndelt i de kategoriene de
+trenger.  Fiksgatami samler i utgangspunktet kun inn navn og
+epostadresse for innsender, og det tror jeg vi skal fortsette med.&lt;/p&gt;
+</description>
+       </item>
+       

        <item>
                <title>Bedre kommunegrense for Oslo i OpenStreetmap.org</title>
                <link>http://people.skolelinux.org/pere/blog/Bedre_kommunegrense_for_Oslo_i_OpenStreetmap_org.html</link>
        <item>
                <title>Bedre kommunegrense for Oslo i OpenStreetmap.org</title>
                <link>http://people.skolelinux.org/pere/blog/Bedre_kommunegrense_for_Oslo_i_OpenStreetmap_org.html</link>


@@ -716,88 +770,5 @@ provided by external plugins like the Flash plugins.&lt;/p&gt;
 </description>
        </item>
        
 </description>
        </item>
        

-       <item>
-               <title>Chrome plan to drop H.264 support for HTML5 &amp;lt;video&amp;gt;</title>
-               <link>http://people.skolelinux.org/pere/blog/Chrome_plan_to_drop_H_264_support_for_HTML5__lt_video_gt_.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Chrome_plan_to_drop_H_264_support_for_HTML5__lt_video_gt_.html</guid>
-                <pubDate>Wed, 12 Jan 2011 22:10:00 +0100</pubDate>
-               <description>
-&lt;p&gt;Today I discovered
-&lt;a href=&quot;http://www.digi.no/860070/google-dropper-h264-stotten-i-chrome&quot;&gt;via
-digi.no&lt;/a&gt; that the Chrome developers, in a surprising announcement,
-&lt;a href=&quot;http://blog.chromium.org/2011/01/html-video-codec-support-in-chrome.html&quot;&gt;yesterday
-announced&lt;/a&gt; plans to drop H.264 support for HTML5 &amp;lt;video&amp;gt; in
-the browser.  The argument used is that H.264 is not a &quot;completely
-open&quot; codec technology.  If you believe H.264 was free for everyone
-to use, I recommend having a look at the essay
-&quot;&lt;a href=&quot;http://webmink.com/essays/h-264/&quot;&gt;H.264 – Not The Kind Of
-Free That Matters&lt;/a&gt;&quot;.  It is not free of cost for creators of video
-tools, nor those of us that want to publish on the Internet, and the
-terms provided by MPEG-LA excludes free software projects from
-licensing the patents needed for H.264.  Some background information
-on the Google announcement is available from
-&lt;a href=&quot;http://www.osnews.com/story/24243/Google_To_Drop_H264_Support_from_Chrome&quot;&gt;OSnews&lt;/a&gt;.
-A good read. :)&lt;/p&gt;
-
-&lt;p&gt;Personally, I believe it is great that Google is taking a stand to
-promote equal terms for everyone when it comes to video publishing on
-the Internet.  This can only be done by publishing using free and open
-standards, which is only possible if the web browsers provide support
-for these free and open standards.  At the moment there seem to be two
-camps in the web browser world when it come to video support.  Some
-browsers support H.264, and others support
-&lt;a href=&quot;http://www.theora.org/&quot;&gt;Ogg Theora&lt;/a&gt; and
-&lt;a href=&quot;http://www.webmproject.org/&quot;&gt;WebM&lt;/a&gt;
-(&lt;a href=&quot;http://www.diracvideo.org/&quot;&gt;Dirac&lt;/a&gt; is not really an option
-yet), forcing those of us that want to publish video on the Internet
-and which can not accept the terms of use presented by MPEG-LA for
-H.264 to not reach all potential viewers.
-Wikipedia keep &lt;a href=&quot;http://en.wikipedia.org/wiki/HTML5_video&quot;&gt;an
-updated summary&lt;/a&gt; of the current browser support.&lt;/p&gt;
-
-&lt;p&gt;Not surprising, several people would prefer Google to keep
-promoting H.264, and John Gruber
-&lt;a href=&quot;http://daringfireball.net/2011/01/simple_questions&quot;&gt;presents
-the mind set&lt;/a&gt; of these people quite well.  His rhetorical questions
-provoked a reply from Thom Holwerda with another set of questions
-&lt;a href=&quot;http://www.osnews.com/story/24245/10_Questions_for_John_Gruber_Regarding_H_264_WebM&quot;&gt;presenting
-the issues with H.264&lt;/a&gt;. Both are worth a read.&lt;/p&gt;
-
-&lt;p&gt;Some argue that if Google is dropping H.264 because it isn&#39;t free,
-they should also drop support for the Adobe Flash plugin.  This
-argument was covered by Simon Phipps in
-&lt;a href=&quot;http://blogs.computerworlduk.com/simon-says/2011/01/google-and-h264---far-from-hypocritical/index.htm&quot;&gt;todays
-blog post&lt;/a&gt;, which I find to put the issue in context.  To me it
-make perfect sense to drop native H.264 support for HTML5 in the
-browser while still allowing plugins.&lt;/p&gt;
-
-&lt;p&gt;I suspect the reason this announcement make so many people protest,
-is that all the users and promoters of H.264 suddenly get an uneasy
-feeling that they might be backing the wrong horse.  A lot of TV
-broadcasters have been moving to H.264 the last few years, and a lot
-of money has been invested in hardware based on the belief that they
-could use the same video format for both broadcasting and web
-publishing.  Suddenly this belief is shaken.&lt;/p&gt;
-
-&lt;p&gt;An interesting question is why Google is doing this.  While the
-presented argument might be true enough, I believe Google would only
-present the argument if the change make sense from a business
-perspective.  One reason might be that they are currently negotiating
-with MPEG-LA over royalties or usage terms, and giving MPEG-LA the
-feeling that dropping H.264 completely from Chroome, Youtube and
-Google Video would improve the negotiation position of Google.
-Another reason might be that Google want to save money by not having
-to pay the video tax to MPEG-LA at all, and thus want to move to a
-video format not requiring royalties at all.  A third reason might be
-that the Chrome development team simply want to avoid the
-Chrome/Chromium split to get more help with the development of Chrome.
-I guess time will tell.&lt;/p&gt;
-
-&lt;p&gt;Update 2011-01-15: The Google Chrome team provided
-&lt;a href=&quot;http://blog.chromium.org/2011/01/more-about-chrome-html-video-codec.html&quot;&gt;more
-background and information on the move&lt;/a&gt; it a blog post yesterday.&lt;/p&gt;
-</description>
-       </item>
-       

         </channel>
 </rss>
         </channel>
 </rss>