+<P>I think that the only real argument that school managers "hear" is
+cost reduction. They don't give too much weight on quality, stability,
+just because they are normally not open to change.</p>
+
+<p>Students adapts very quickly to GNU/Linux (and for them being able
+to switch between different OS is a plus value); teachers and managers
+don't.</p>
+
+<p>We decided to move to Linux because students at our school have own
+laptop and we have the responsibility to keep the laptop ready to use;
+we were really unsatisfied with Microsoft since every Monday we had 20
+machine to fix for viral infections... With Linux this has been
+reduced to zero, since people installs almost only from official
+repositories. I think that our special needs brought us to Linux.
+Those who don't have such needs will hardly move to Linux.</p>
+</description>
+ </item>
+
+ <item>
+ <title>Naturvernforbundet i Oslo bruker OpenStreetmap i sin kalender</title>
+ <link>http://people.skolelinux.org/pere/blog/Naturvernforbundet_i_Oslo_bruker_OpenStreetmap_i_sin_kalender.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Naturvernforbundet_i_Oslo_bruker_OpenStreetmap_i_sin_kalender.html</guid>
+ <pubDate>Sun, 16 Sep 2012 12:00:00 +0200</pubDate>
+ <description><p>Veldig morsomt å se at
+<a href="http://naturvernforbundet.no/noa/">Naturvernforbundet Oslo og
+Akershus</a> bruker kart fra
+<a href="http://www.openstreetmap.no/">OpenStreetmap.org<a/> i
+<a href="http://naturvernforbundet.no/noa/bestill-markakalenderen-2013-article24039-1939.html">sine
+kalendere</a>. Vidar Gundersen i kartgruppa
+<a href="http://lists.nuug.no/pipermail/kart/2012-September/003696.html">forteller
+på den norske epostlisten</a> til prosjektet at hvert blad i
+kalenderen har et turforslag på baksiden, med kart fra OpenStreetmap.
+Tidligere kjøpte de visst kart fra kartverket, men nå slipper de
+det.</p>
+
+<p>Denne nyheten synes jeg er fantastisk bra, og jeg håper de får
+følge av flere, slik at det potensielle og fryktede inntektstapet for
+kartverket ved frigjøring av kartdata blir mindre, og forhåpentligvis
+til slutt så lite at frykten for å frigjøre data overvinnes.</p>
+</description>
+ </item>
+
+ <item>
+ <title>IETF activity to standardise video codec</title>
+ <link>http://people.skolelinux.org/pere/blog/IETF_activity_to_standardise_video_codec.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IETF_activity_to_standardise_video_codec.html</guid>
+ <pubDate>Sat, 15 Sep 2012 20:00:00 +0200</pubDate>
+ <description><p>After the
+<a href="http://people.skolelinux.org/pere/blog/IETF_standardize_its_first_multimedia_codec__Opus.html">Opus
+codec made</a> it into <a href="http://www.ietf.org/">IETF</a> as
+<a href="http://tools.ietf.org/html/rfc6716">RFC 6716</a>, I had a look
+to see if there is any activity in IETF to standardise a video codec
+too, and I was happy to discover that there is some activity in this
+area. A non-"working group" mailing list
+<a href="https://www.ietf.org/mailman/listinfo/video-codec">video-codec</a>
+was
+<a href="http://ietf.10.n7.nabble.com/New-Non-WG-Mailing-List-video-codec-Video-codec-BoF-discussion-list-td119548.html">created 2012-08-20</a>. It is intended to discuss the topic and if a
+formal working group should be formed.</p>
+
+<p>I look forward to see how this plays out. There is already
+<a href="http://www.ietf.org/mail-archive/web/video-codec/current/msg00003.html">an
+email from someone</a> in the MPEG group at ISO asking people to
+participate in the ISO group. Given how ISO failed with OOXML and given
+that it so far (as far as I can remember) only have produced
+multimedia formats requiring royalty payments, I suspect
+joining the ISO group would be a complete waste of time, but I am not
+involved in any codec work and my opinion will not matter much.</p>
+
+<p>If one of my readers is involved with codec work, I hope she will
+join this work to standardise a royalty free video codec within
+IETF.</p>
+</description>
+ </item>
+
+ <item>
+ <title>IETF standardize its first multimedia codec: Opus</title>
+ <link>http://people.skolelinux.org/pere/blog/IETF_standardize_its_first_multimedia_codec__Opus.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IETF_standardize_its_first_multimedia_codec__Opus.html</guid>
+ <pubDate>Wed, 12 Sep 2012 13:50:00 +0200</pubDate>
+ <description><p>Yesterday, <a href="http://www.ietf.org/">IETF</a> announced the
+publication of of
+<a href="http://tools.ietf.org/html/rfc6716">RFC 6716, the Definition
+of the Opus Audio Codec</a>, a low latency, variable bandwidth, codec
+intended for both VoIP, film and music. This is the first time, as
+far as I know, that IETF have standardized a multimedia codec. In
+<a href="http://tools.ietf.org/html/rfc3533">RFC 3533</a>, IETF
+standardized the OGG container format, and it has proven to be a great
+royalty free container for audio, video and movies. I hope IETF will
+continue to standardize more royalty free codeces, after ISO and MPEG
+have proven incapable of securing everyone equal rights to publish
+multimedia content on the Internet.</p>
+
+<p>IETF require two interoperating independent implementations to
+ratify a standard, and have so far ensured to only standardize royalty
+free specifications. Both are key factors to allow everyone (rich and
+poor), to compete on equal terms on the Internet.</p>
+
+<p>Visit the <a href="http://opus-codec.org/">Opus project page</a> if
+you want to learn more about the solution.</p>