blog/archive/2010/12/index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2           "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
   4   <head>
   5     <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
   6     <title>Petter Reinholdtsen: entries from December 2010</title>
   7     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/style.css" />
   8     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/vim.css" />
   9     <link rel="alternate" title="RSS Feed" href="12.rss" type="application/rss+xml" />
  10   </head>
  11   <body>
  12     <!-- XML FEED -->
  13     <div class="title">
  14  <h1>
  15      <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
  16
  17  </h1>
  18
  19 </div>
  20
  21
  22     <h3>Entries from December 2010.</h3>
  23
  24     <div class="entry">
  25       <div class="title">
  26         <a href="http://people.skolelinux.org/pere/blog/Student_group_continue_the_work_on_my_Reprap_3D_printer.html">Student group continue the work on my Reprap 3D printer</a>
  27       </div>
  28       <div class="date">
  29          9th December 2010
  30       </div>
  31       <div class="body">
  32         <p>A few days ago, I was introduces to some students in the robot
  33 student assosiation <a href="http://www.robotica.no/">Robotica
  34 Osloensis</a> at the University of Oslo where I work, who planned to
  35 get their own 3D printer.  They wanted to learn from me based on my
  36 work in the area.  After having a short lunch meeting with them, I
  37 offered them to borrow my reprap kit, as I never had time to complete
  38 the build and this seem unlike to change any time soon.  I look
  39 forward to see how this goes.  This monday their volunteer driver
  40 picked up my kit and drove it to their lab, and tomorrow I am told the
  41 last exam is over so they can start work on getting the 3D printer
  42 operational.</p>
  43
  44 <p>The robotic group have already build several robots on their own,
  45 and seem capable of getting the reprap operational.  I really look
  46 forward to being able to print all the cool 3D designs published on
  47 <a href="http://www.thingiverse.com/">Thingiverse</a>.  I even got
  48 some 3D scans I got made during Dagen@IFI when one of the groups at
  49 the computer science department at the university demonstrated their
  50 very cool 3D scanner.</p>
  51
  52       </div>
  53       <div class="tags">
  54
  55
  56         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap</a>.
  57
  58
  59       </div>
  60     </div>
  61     <div class="padding"></div>
  62
  63     <div class="entry">
  64       <div class="title">
  65         <a href="http://people.skolelinux.org/pere/blog/Martin_Bekkelund__En_stille_b_nn_om_Datalagringsdirektivet.html">Martin Bekkelund: En stille bønn om Datalagringsdirektivet</a>
  66       </div>
  67       <div class="date">
  68          9th December 2010
  69       </div>
  70       <div class="body">
  71         <p><a href="http://www.bekkelund.net/">Martin Bekkelund</a> ved
  72 <a href="http://www.friprog.no/">friprog-senteret</a> har skrevet
  73 følgende
  74 <a href="http://www.bekkelund.net/2010/12/09/en-stille-bonn/">korte
  75 oppsummering</a> rundt datalagringsdirektivet, som jeg videreformidler
  76 her.</p>
  77
  78 <p><blockquote><strong>Det pågår i disse dager en intens diskusjon om
  79 innføring av Datalagringsdirektivet (<acronym
  80 title="Datalagringsdirektivet">DLD</acronym>) i norsk rett. Kanskje
  81 har du gjort deg opp en mening, kanskje er du usikker. I begge
  82 tilfeller ber jeg deg lese videre.</strong></p>
  83
  84 <p>Samtlige fagmiljøer, både i Norge og EU, har konkludert med at
  85 <acronym title="Datalagringsdirektivet">DLD</acronym> ikke bør
  86 innføres på nåværende tidspunkt. Den tekniske kvaliteten på direktivet
  87 er dårlig, det griper uforholdsmessig inn i personvernet, det har
  88 store mangler og viktige spørsmål som hvem som skal ha tilgang og
  89 hvordan data skal lagres er fortsatt uavklart.</p>
  90
  91 <ul>
  92 <li><a href="http://ikt-norge.no/norge-kan-slippe-datalagringsdirektivet/">EU-ekspertene sier</a> at konsekvensene av å benytte vetoretten er minimale</li>
  93 <li><a href="http://www.regjeringen.no/pages/2281080/Deninternasjonalejuristkommisjon.pdf">Juristene påpeker</a> at direktivet er i strid med EMK</li>
  94 <li><a href="http://www.dagbladet.no/2010/12/06/kultur/debatt/kronikk/dld/personvern/14594699/">Datatilsynet sier</a> direktivet får store konsekvenser for personvernet og at direktivet er irreversibelt</li>
  95 <li><a href="http://www.bekkelund.net/?s=dld">Teknologene sier</a> at sikker lagring ikke er mulig, at det er svært enkelt å omgå og mulig å manipulere data og produsere falske beviser</li>
  96 <li><a href="http://www.regjeringen.no/pages/2281080/NJ_247460_1_P.pdf">Pressen sier</a> nei av hensyn til kildevernet</li>
  97 <li>Det er store <a href="http://tetzschner.blogspot.com/2010/03/den-tyske-forfatningsdomstol.html">interne</a> <a href="http://stoppdld.no/2010/03/02/datalagring-stoppet-av-tysk-forfatningsdomstol/">stridigheter</a> i EU. Blant annet har den tyske forfatningsdomstolen funnet at måten <acronym title="Datalagringsdirektivet">DLD</acronym> er innført på er i strid med tysk grunnlov</li>
  98 <li>Alle de store <a href="http://www.bekkelund.net/2010/12/08/lokasjonsdata-og-datalagringsdirektivet/">operatørene og tilbyderne sier nei</a>, av tekniske og personvernmessige årsaker</li>
  99 </ul>
 100
 101 <p>Jeg liker å tro at jeg er en hyggelig fyr. Jeg har et rent
 102 rulleblad, og med unntak av to fartsbøter har jeg aldri vært en byrde
 103 for samfunnet. Det akter jeg å fortsette med. Det er mange som meg,
 104 lovlydige, pliktoppfyllende borgere som aldri vil utgjøre en trussel
 105 mot noe som helst. Vi synes derfor det er trist og sårende at all vår
 106 atferd skal overvåkes døgnkontinuerlig.</p>
 107
 108 <p><strong>Understøttet av faglige vurderinger kan du trygt si nei til
 109 <acronym title="Datalagringsdirektivet">DLD</acronym>.</strong></p>
 110
 111 <p><a href="http://www.bekkelund.net/kontakt/">Ta kontakt med meg</a>
 112 hvis du har spørsmål om <acronym
 113 title="Datalagringsdirektivet">DLD</acronym>, uansett hva det måtte
 114 gjelde.</p>
 115
 116 <p class="info">Denne teksten er å anse som <a
 117 href="http://creativecommons.org/licenses/publicdomain/"><em>Public
 118 Domain</em></a>. Spre den videre til alle som kan ha nytte av
 119 den!</p>
 120 </blockquote></p>
 121
 122 <p>Siste <a href="http://www.nettavisen.no/it/article3043918.ece">melding
 123 fra Nettavisen</a> er at regjeringen planlegger å fremme sitt forslag
 124 til implementering av datalagringsdirektivet i morgen, i ly av
 125 fredprisutdelingen for å få minst mulig pressedekning om saken.  Vi
 126 får snart se om det stemmer.</p>
 127
 128       </div>
 129       <div class="tags">
 130
 131
 132         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>.
 133
 134
 135       </div>
 136     </div>
 137     <div class="padding"></div>
 138
 139     <div class="entry">
 140       <div class="title">
 141         <a href="http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html">Now accepting bitcoins - anonymous and distributed p2p crypto-money</a>
 142       </div>
 143       <div class="date">
 144         10th December 2010
 145       </div>
 146       <div class="body">
 147         <p>With this weeks lawless
 148 <a href="http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html">governmental
 149 attacks</a> on Wikileak and
 150 <a href="http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech">free
 151 speech</a>, it has become obvious that PayPal, visa and mastercard can
 152 not be trusted to handle money transactions.
 153 A blog post from
 154 <a href="http://webmink.com/2010/12/06/now-accepting-bitcoin/">Simon
 155 Phipps on bitcoin</a> reminded me about a project that a friend of
 156 mine mentioned earlier.  I decided to follow Simon's example, and get
 157 involved with <a href="http://www.bitcoin.org/">BitCoin</a>.  I got
 158 some help from my friend to get it all running, and he even handed me
 159 some bitcoins to get started.  I even donated a few bitcoins to Simon
 160 for helping me remember BitCoin.</p>
 161
 162 <p>So, what is bitcoins, you probably wonder?  It is a digital
 163 crypto-currency, decentralised and handled using peer-to-peer
 164 networks.  It allows anonymous transactions and prohibits central
 165 control over the transactions, making it impossible for governments
 166 and companies alike to block donations and other transactions.  The
 167 source is free software, and while the key dependency wxWidgets 2.9
 168 for the graphical user interface is missing in Debian, the command
 169 line client builds just fine.  Hopefully Jonas
 170 <a href="http://bugs.debian.org/578157">will get the package into
 171 Debian</a> soon.</p>
 172
 173 <p>Bitcoins can be converted to other currencies, like USD and EUR.
 174 There are <a href="http://www.bitcoin.org/trade">companies accepting
 175 bitcoins</a> when selling services and goods, and there are even
 176 currency "stock" markets where the exchange rate is decided.  There
 177 are not many users so far, but the concept seems promising.  If you
 178 want to get started and lack a friend with any bitcoins to spare,
 179 you can even get
 180 <a href="https://freebitcoins.appspot.com/">some for free</a> (0.05
 181 bitcoin at the time of writing).  Use
 182 <a href="http://www.bitcoinwatch.com/">BitcoinWatch</a> to keep an eye
 183 on the current exchange rates.</p>
 184
 185 <p>As an experiment, I have decided to set up bitcoind on one of my
 186 machines.  If you want to support my activity, please send Bitcoin
 187 donations to the address
 188 <b>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</b>.  Thank you!</p>
 189
 190       </div>
 191       <div class="tags">
 192
 193
 194         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>.
 195
 196
 197       </div>
 198     </div>
 199     <div class="padding"></div>
 200
 201     <div class="entry">
 202       <div class="title">
 203         <a href="http://people.skolelinux.org/pere/blog/Pornoskannerne_p__flyplassene_bedrer_visst_ikke_sikkerheten.html">Pornoskannerne på flyplassene bedrer visst ikke sikkerheten</a>
 204       </div>
 205       <div class="date">
 206         11th December 2010
 207       </div>
 208       <div class="body">
 209         <p>Via <a href="http://webmink.com/2010/12/10/links-for-2010-12-10/">en
 210 blogpost fra Simon Phipps i går</a>, fant jeg en referanse til
 211 <a href="http://www.washingtontimes.com/news/2010/dec/9/exposed-tsas-x-rated-scanner-fraud/">en
 212 artikkel i Washington Times</a> som igjen refererer til en artikkel i
 213 det fagfellevurderte tidsskriftet Journal of Transportation Security
 214 med tittelen
 215 "<a href="http://springerlink.com/content/g6620thk08679160/fulltext.html">An
 216 evaluation of airport x-ray backscatter units based on image
 217 characteristics</a>" som enkelt konstaterer at
 218 <a href="http://www.dailysquib.co.uk/?a=2389&c=124">pornoscannerne</a>
 219 som kler av reisende på flyplasser ikke er i stand til å avsløre det
 220 produsenten og amerikanske myndigheter sier de skal avsløre.  Kort
 221 sagt, de bedrer ikke sikkerheten.  Reisende må altså la ansatte på
 222 flyplasser <a href="http://www.thousandsstandingaround.org/">se dem
 223 nakne eller la seg beføle i skrittet</a> uten grunn.  Jeg vil
 224 fortsette å nekte å bruke disse pornoskannerne, unngå flyplasser der
 225 de er tatt i bruk, og reise med andre transportmidler enn fly hvis jeg
 226 kan.</p>
 227
 228       </div>
 229       <div class="tags">
 230
 231
 232         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>.
 233
 234
 235       </div>
 236     </div>
 237     <div class="padding"></div>
 238
 239     <div class="entry">
 240       <div class="title">
 241         <a href="http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html">Some thoughts on BitCoins</a>
 242       </div>
 243       <div class="date">
 244         11th December 2010
 245       </div>
 246       <div class="body">
 247         <p>As I continue to explore
 248 <a href="http://www.bitcoin.org/">BitCoin</a>, I've starting to wonder
 249 what properties the system have, and how it will be affected by laws
 250 and regulations here in Norway.  Here are some random notes.</p>
 251
 252 <p>One interesting thing to note is that since the transactions are
 253 verified using a peer to peer network, all details about a transaction
 254 is known to everyone.  This means that if a BitCoin address has been
 255 published like I did with mine in my initial post about BitCoin, it is
 256 possible for everyone to see how many BitCoins have been transfered to
 257 that address.  There is even a web service to look at the details for
 258 all transactions.  There I can see that my address
 259 <a href="http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a>
 260 have received 16.06 Bitcoin, the
 261 <a href="http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3">1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3</a>
 262 address of Simon Phipps have received 181.97 BitCoin and the address
 263 <a href="http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt</A>
 264 of EFF have received 2447.38 BitCoins so far.  Thank you to each and
 265 every one of you that donated bitcoins to support my activity. The
 266 fact that anyone can see how much money was transfered to a given
 267 address make it more obvious why the BitCoin community recommend to
 268 generate and hand out a new address for each transaction.  I'm told
 269 there is no way to track which addresses belong to a given person or
 270 organisation without the person or organisation revealing it
 271 themselves, as Simon, EFF and I have done.</p>
 272
 273 <p>In Norway, and in most other countries, there are laws and
 274 regulations limiting how much money one can transfer across the border
 275 without declaring it.  There are money laundering, tax and accounting
 276 laws and regulations I would expect to apply to the use of BitCoin.
 277 If the Skolelinux foundation
 278 (<a href="http://linuxiskolen.no/slxdebianlabs/donations.html">SLX
 279 Debian Labs</a>) were to accept donations in BitCoin in addition to
 280 normal bank transfers like EFF is doing, how should this be accounted?
 281 Given that it is impossible to know if money can across the border or
 282 not, should everything or nothing be declared?  What exchange rate
 283 should be used when calculating taxes?  Would receivers have to pay
 284 income tax if the foundation were to pay Skolelinux contributors in
 285 BitCoin?  I have no idea, but it would be interesting to know.</p>
 286
 287 <p>For a currency to be useful and successful, it must be trusted and
 288 accepted by a lot of users.  It must be possible to get easy access to
 289 the currency (as a wage or using currency exchanges), and it must be
 290 easy to spend it.  At the moment BitCoin seem fairly easy to get
 291 access to, but there are very few places to spend it.  I am not really
 292 a regular user of any of the vendor types currently accepting BitCoin,
 293 so I wonder when my kind of shop would start accepting BitCoins.  I
 294 would like to buy electronics, travels and subway tickets, not herbs
 295 and books. :) The currency is young, and this will improve over time
 296 if it become popular, but I suspect regular banks will start to lobby
 297 to get BitCoin declared illegal if it become popular.  I'm sure they
 298 will claim it is helping fund terrorism and money laundering (which
 299 probably would be true, as is any currency in existence), but I
 300 believe the problems should be solved elsewhere and not by blaming
 301 currencies.</p>
 302
 303 <p>The process of creating new BitCoins is called mining, and it is
 304 CPU intensive process that depend on a bit of luck as well (as one is
 305 competing against all the other miners currently spending CPU cycles
 306 to see which one get the next lump of cash).  The "winner" get 50
 307 BitCoin when this happen.  Yesterday I came across the obvious way to
 308 join forces to increase ones changes of getting at least some coins,
 309 by coordinating the work on mining BitCoins across several machines
 310 and people, and sharing the result if one is lucky and get the 50
 311 BitCoins.  Check out
 312 <a href="http://www.bluishcoder.co.nz/bitcoin-pool/">BitCoin Pool</a>
 313 if this sounds interesting.  I have not had time to try to set up a
 314 machine to participate there yet, but have seen that running on ones
 315 own for a few days have not yield any BitCoins througth mining
 316 yet.</p>
 317
 318 <p>Update 2010-12-15: Found an <a
 319 href="http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi">interesting
 320 criticism</a> of bitcoin.  Not quite sure how valid it is, but thought
 321 it was interesting to read.  The arguments presented seem to be
 322 equally valid for gold, which was used as a currency for many years.</p>
 323
 324       </div>
 325       <div class="tags">
 326
 327
 328         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>.
 329
 330
 331       </div>
 332     </div>
 333     <div class="padding"></div>
 334
 335     <div class="entry">
 336       <div class="title">
 337         <a href="http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html">How to test if a laptop is working with Linux</a>
 338       </div>
 339       <div class="date">
 340         22nd December 2010
 341       </div>
 342       <div class="body">
 343         <p>The last few days I have spent at work here at the <a
 344 href="http://www.uio.no/">University of Oslo</a> testing if the new
 345 batch of computers will work with Linux.  Every year for the last few
 346 years the university have organised shared bid of a few thousand
 347 computers, and this year HP won the bid.  Two different desktops and
 348 five different laptops are on the list this year.  We in the UNIX
 349 group want to know which one of these computers work well with RHEL
 350 and Ubuntu, the two Linux distributions we currently handle at the
 351 university.</p>
 352
 353 <p>My test method is simple, and I share it here to get feedback and
 354 perhaps inspire others to test hardware as well.  To test, I PXE
 355 install the OS version of choice, and log in as my normal user and run
 356 a few applications and plug in selected pieces of hardware.  When
 357 something fail, I make a note about this in the test matrix and move
 358 on.  If I have some spare time I try to report the bug to the OS
 359 vendor, but as I only have the machines for a short time, I rarely
 360 have the time to do this for all the problems I find.</p>
 361
 362 <p>Anyway, to get to the point of this post.  Here is the simple tests
 363 I perform on a new model.</p>
 364
 365 <ul>
 366
 367 <li>Is PXE installation working?  I'm testing with RHEL6, Ubuntu Lucid
 368 and Ubuntu Maverik at the moment.  If I feel like it, I also test with
 369 RHEL5 and Debian Edu/Squeeze.</li>
 370
 371 <li>Is X.org working?  If the graphical login screen show up after
 372 installation, X.org is working.</li>
 373
 374 <li>Is hardware accelerated OpenGL working?  Running glxgears (in
 375 package mesa-utils on Ubuntu) and writing down the frames per second
 376 reported by the program.</li>
 377
 378 <li>Is sound working?  With Gnome and KDE, a sound is played when
 379 logging in, and if I can hear this the test is successful.  If there
 380 are several audio exits on the machine, I try them all and check if
 381 the Gnome/KDE audio mixer can control where to send the sound.  I
 382 normally test this by playing
 383 <a href="http://www.nuug.no/aktiviteter/20101012-chef/ ">a HTML5
 384 video</a> in Firefox/Iceweasel.</li>
 385
 386 <li>Is the USB subsystem working?  I test this by plugging in a USB
 387 memory stick and see if Gnome/KDE notices this.</li>
 388
 389 <li>Is the CD/DVD player working?  I test this by inserting any CD/DVD
 390 I have lying around, and see if Gnome/KDE notices this.</li>
 391
 392 <li>Is any built in camera working?  Test using cheese, and see if a
 393 picture from the v4l device show up.</li>
 394
 395 <li>Is bluetooth working?  Use the Gnome/KDE browsing tool to see if
 396 any bluetooth devices are discovered.  In my office, I normally see a
 397 few.</li>
 398
 399 <li>For laptops, is the SD or Compaq Flash reader working.  I have
 400 memory modules lying around, and stick them in and see if Gnome/KDE
 401 notice this.</li>
 402
 403 <li>For laptops, is suspend/hibernate working?  I'm testing if the
 404 special button work, and if the laptop continue to work after
 405 resume.</li>
 406
 407 <li>For laptops, is the extra buttons working, like audio level,
 408 adjusting background light, switching on/off external video output,
 409 switching on/off wifi, bluetooth, etc?  The set of buttons differ from
 410 laptop to laptop, so I just write down which are working and which are
 411 not.</li>
 412
 413 <li>Some laptops have smart card readers, finger print readers,
 414 acceleration sensors etc.  I rarely test these, as I do not know how
 415 to quickly test if they are working or not, so I only document their
 416 existence.</li>
 417
 418 </ul>
 419
 420 <p>By now I suspect you are really curious what the test results are
 421 for the HP machines I am testing.  I'm not done yet, so I will report
 422 the test results later.  For now I can report that HP 8100 Elite work
 423 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
 424 and audio fail on RHEL6.  Ubuntu Maverik worked with 8440p.  As you
 425 can see, I have most machines left to test.  One interesting
 426 observation is that Ubuntu Lucid has almost twice the frame rate than
 427 RHEL6 with glxgears.  No idea why.</p>
 428
 429       </div>
 430       <div class="tags">
 431
 432
 433         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
 434
 435
 436       </div>
 437     </div>
 438     <div class="padding"></div>
 439
 440     <div class="entry">
 441       <div class="title">
 442         <a href="http://people.skolelinux.org/pere/blog/165_norske_overv_kningskamera_registert_s__langt_i_OpenStreetmap_org.html">165 norske overvåkningskamera registert så langt i OpenStreetmap.org</a>
 443       </div>
 444       <div class="date">
 445         24th December 2010
 446       </div>
 447       <div class="body">
 448         <p>Jeg flikket litt på OpenStreetmap.org i går, og oppdaget ved en
 449 tilfeldighet at det er en rekke noder som representerer
 450 overvåkningskamera som ikke blir med på kartet med overvåkningskamera
 451 i Norge som
 452 <a href="http://people.skolelinux.org/pere/blog/Kart_over_overv__kningskamera_i_Norge.html">jeg
 453 laget</a> for snart to år siden.  Fra før tok jeg med noder merket med
 454 man_made=surveillance, mens det er en rekke noder som kun er merket
 455 med highway=speed_camera.  Endret på koden som henter ut kameralisten
 456 fra OSM, og vips er antall kamera økt til 165.</p>
 457
 458 <a href="http://people.skolelinux.no/pere/surveillance-norway/">Kartet</a>
 459 er fortsatt ikke komplett, så hvis du ser noen kamera som mangler,
 460 legg inn ved å følge instruksene fra
 461 <a href="http://personvern.no/wiki/index.php/Kameraovervåkning">prosjektsiden</a>.
 462 Hvis du vet om noen flere måter å merke overvåkningskamera i OSM, ta
 463 kontakt slik at jeg kan få med også disse.</p>
 464
 465       </div>
 466       <div class="tags">
 467
 468
 469         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
 470
 471
 472       </div>
 473     </div>
 474     <div class="padding"></div>
 475
 476     <div class="entry">
 477       <div class="title">
 478         <a href="http://people.skolelinux.org/pere/blog/Officeshots_still_going_strong.html">Officeshots still going strong</a>
 479       </div>
 480       <div class="date">
 481         25th December 2010
 482       </div>
 483       <div class="body">
 484         <p>Half a year ago I
 485 <a href="http://people.skolelinux.org/pere/blog/Officeshots_taking_shape.html">wrote
 486 a bit</a> about <a href="http://www.officeshots.org/">OfficeShots</a>,
 487 a web service to allow anyone to test how ODF documents are handled by
 488 the different programs reading and writing the ODF format.</p>
 489
 490 <p>I just had a look at the service, and it seem to be going strong.
 491 Very interesting to see the results reported in the gallery, how
 492 different Office implementations handle different ODF features.  Sad
 493 to see that KOffice was not doing it very well, and happy to see that
 494 LibreOffice has been tested already (but sadly not listed as a option
 495 for OfficeShots users yet).  I am glad to see that the ODF community
 496 got such a great test tool available.</p>
 497
 498       </div>
 499       <div class="tags">
 500
 501
 502         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 503
 504
 505       </div>
 506     </div>
 507     <div class="padding"></div>
 508
 509     <div class="entry">
 510       <div class="title">
 511         <a href="http://people.skolelinux.org/pere/blog/The_reply_from_Edgar_Villanueva_to_Microsoft_in_Peru.html">The reply from Edgar Villanueva to Microsoft in Peru</a>
 512       </div>
 513       <div class="date">
 514         25th December 2010
 515       </div>
 516       <div class="body">
 517         <p>A few days ago
 518 <a href="http://www.idg.no/computerworld/article189879.ece">an
 519 article</a> in the Norwegian Computerworld magazine about how version
 520 2.0 of
 521 <a href="http://en.wikipedia.org/wiki/European_Interoperability_Framework">European
 522 Interoperability Framework</a> has been successfully lobbied by the
 523 proprietary software industry to remove the focus on free software.
 524 Nothing very surprising there, given
 525 <a href="http://news.slashdot.org/story/10/03/29/2115235/Open-Source-Open-Standards-Under-Attack-In-Europe">earlier
 526 reports</a> on how Microsoft and others have stacked the committees in
 527 this work.  But I find this very sad.   The definition of
 528 <a href="http://www.nuug.no/dokumenter/standard-presse-def-200506.txt">an
 529 open standard from version 1</a> was very good, and something I
 530 believe should be used also in the future, alongside
 531 <a href="http://www.digistan.org/open-standard:definition">the
 532 definition from Digistan</A>.  Version 2 have removed the open
 533 standard definition from its content.</p>
 534
 535 <p>Anyway, the news reminded me of the great reply sent by Dr. Edgar
 536 Villanueva, congressman in Peru at the time, to Microsoft as a reply
 537 to Microsofts attack on his proposal regarding the use of free software
 538 in the public sector in Peru.  As the text was not available from a
 539 few of the URLs where it used to be available, I copy it here from
 540 <a href="http://gnuwin.epfl.ch/articles/en/reponseperou/villanueva_to_ms.html">my
 541 source</a> to ensure it is available also in the future.  Some
 542 background information about that story is available in
 543 <a href="http://www.linuxjournal.com/article/6099">an article</a> from
 544 Linux Journal in 2002.</p>
 545
 546 <blockquote>
 547 <p>Lima, 8th of April, 2002<br>
 548 To: Señor JUAN ALBERTO GONZÁLEZ<br>
 549 General Manager of Microsoft Perú</p>
 550
 551 <p>Dear Sir:</p>
 552
 553 <p>First of all, I thank you for your letter of March 25, 2002 in which you state the official position of Microsoft relative to Bill Number 1609, Free Software in Public Administration, which is indubitably inspired by the desire for Peru to find a suitable place in the global technological context. In the same spirit, and convinced that we will find the best solutions through an exchange of clear and open ideas, I will take this opportunity to reply to the commentaries included in your letter.</p>
 554
 555 <p>While acknowledging that opinions such as yours constitute a significant contribution, it would have been even more worthwhile for me if, rather than formulating objections of a general nature (which we will analyze in detail later) you had gathered solid arguments for the advantages that proprietary software could bring to the Peruvian State, and to its citizens in general, since this would have allowed a more enlightening exchange in respect of each of our positions.</p>
 556
 557 <p>With the aim of creating an orderly debate, we will assume that what you call "open source software" is what the Bill defines as "free software", since there exists software for which the source code is distributed together with the program, but which does not fall within the definition established by the Bill; and that what you call "commercial software" is what the Bill defines as "proprietary" or "unfree", given that there exists free software which is sold in the market for a price like any other good or service.</p>
 558
 559 <p>It is also necessary to make it clear that the aim of the Bill we are discussing is not directly related to the amount of direct savings that can by made by using free software in state institutions. That is in any case a marginal aggregate value, but in no way is it the chief focus of the Bill. The basic principles which inspire the Bill are linked to the basic guarantees of a state of law, such as:</p>
 560
 561 <p>
 562 <ul>
 563 <li>Free access to public information by the citizen. </li>
 564 <li>Permanence of public data. </li>
 565 <li>Security of the State and citizens.</li>
 566 </ul>
 567 </p>
 568
 569 <p>To guarantee the free access of citizens to public information, it is indispensable that the encoding of data is not tied to a single provider. The use of standard and open formats gives a guarantee of this free access, if necessary through the creation of compatible free software.</p>
 570
 571 <p>To guarantee the permanence of public data, it is necessary that the usability and maintenance of the software does not depend on the goodwill of the suppliers, or on the monopoly conditions imposed by them. For this reason the State needs systems the development of which can be guaranteed due to the availability of the source code.</p>
 572
 573 <p>To guarantee national security or the security of the State, it is indispensable to be able to rely on systems without elements which allow control from a distance or the undesired transmission of information to third parties. Systems with source code freely accessible to the public are required to allow their inspection by the State itself, by the citizens, and by a large number of independent experts throughout the world. Our proposal brings further security, since the knowledge of the source code will eliminate the growing number of programs with *spy code*. </p>
 574
 575 <p>In the same way, our proposal strengthens the security of the citizens, both in their role as legitimate owners of information managed by the state, and in their role as consumers. In this second case, by allowing the growth of a widespread availability of free software not containing *spy code* able to put at risk privacy and individual freedoms.</p>
 576
 577 <p>In this sense, the Bill is limited to establishing the conditions under which the state bodies will obtain software in the future, that is, in a way compatible with these basic principles.</p>
 578
 579
 580 <p>From reading the Bill it will be clear that once passed:<br>
 581 <li>the law does not forbid the production of proprietary software</li>
 582 <li>the law does not forbid the sale of proprietary software</li>
 583 <li>the law does not specify which concrete software to use</li>
 584 <li>the law does not dictate the supplier from whom software will be bought</li>
 585 <li>the law does not limit the terms under which a software product can be licensed.</li>
 586
 587 </p>
 588
 589 <p>What the Bill does express clearly, is that, for software to be acceptable for the state it is not enough that it is technically capable of fulfilling a task, but that further the contractual conditions must satisfy a series of requirements regarding the license, without which the State cannot guarantee the citizen adequate processing of his data, watching over its integrity, confidentiality, and accessibility throughout time, as these are very critical aspects for its normal functioning.</p>
 590
 591 <p>We agree, Mr. Gonzalez, that information and communication technology have a significant impact on the quality of life of the citizens (whether it be positive or negative). We surely also agree that the basic values I have pointed out above are fundamental in a democratic state like Peru. So we are very interested to know of any other way of guaranteeing these principles, other than through the use of free software in the terms defined by the Bill.</p>
 592
 593 <p>As for the observations you have made, we will now go on to analyze them in detail:</p>
 594
 595 <p>Firstly, you point out that: "1. The bill makes it compulsory for all public bodies to use only free software, that is to say open source software, which breaches the principles of equality before the law, that of non-discrimination and the right of free private enterprise, freedom of industry and of contract, protected by the constitution."</p>
 596
 597 <p>This understanding is in error. The Bill in no way affects the rights you list; it limits itself entirely to establishing conditions for the use of software on the part of state institutions, without in any way meddling in private sector transactions. It is a well established principle that the State does not enjoy the wide spectrum of contractual freedom of the private sector, as it is limited in its actions precisely by the requirement for transparency of public acts; and in this sense, the preservation of the greater common interest must prevail when legislating on the matter.</p>
 598
 599 <p>The Bill protects equality under the law, since no natural or legal person is excluded from the right of offering these goods to the State under the conditions defined in the Bill and without more limitations than those established by the Law of State Contracts and Purchasing (T.U.O. by Supreme Decree No. 012-2001-PCM).</p>
 600
 601 <p>The Bill does not introduce any discrimination whatever, since it only establishes *how* the goods have to be provided (which is a state power) and not *who* has to provide them (which would effectively be discriminatory, if restrictions based on national origin, race religion, ideology, sexual preference etc. were imposed). On the contrary, the Bill is decidedly antidiscriminatory. This is so because by defining with no room for doubt the conditions for the provision of software, it prevents state bodies from using software which has a license including discriminatory conditions.</p>
 602
 603 <p>It should be obvious from the preceding two paragraphs that the Bill does not harm free private enterprise, since the latter can always choose under what conditions it will produce software; some of these will be acceptable to the State, and others will not be since they contradict the guarantee of the basic principles listed above. This free initiative is of course compatible with the freedom of industry and freedom of contract (in the limited form in which the State can exercise the latter). Any private subject can produce software under the conditions which the State requires, or can refrain from doing so. Nobody is forced to adopt a model of production, but if they wish to provide software to the State, they must provide the mechanisms which guarantee the basic principles, and which are those described in the Bill.</p>
 604
 605 <p>By way of an example: nothing in the text of the Bill would prevent your company offering the State bodies an office "suite", under the conditions defined in the Bill and setting the price that you consider satisfactory. If you did not, it would not be due to restrictions imposed by the law, but to business decisions relative to the method of commercializing your products, decisions with which the State is not involved.</p>
 606
 607 <p>To continue; you note that:" 2. The bill, by making the use of open source software compulsory, would establish discriminatory and non competitive practices in the contracting and purchasing by public bodies..."</p>
 608
 609 <p>This statement is just a reiteration of the previous one, and so the response can be found above. However, let us concern ourselves for a moment with your comment regarding "non-competitive ... practices."</p>
 610
 611 <p>Of course, in defining any kind of purchase, the buyer sets conditions which relate to the proposed use of the good or service. From the start, this excludes certain manufacturers from the possibility of competing, but does not exclude them "a priori", but rather based on a series of principles determined by the autonomous will of the purchaser, and so the process takes place in conformance with the law. And in the Bill it is established that *no one* is excluded from competing as far as he guarantees the fulfillment of the basic principles.</p>
 612
 613 <p>Furthermore, the Bill *stimulates* competition, since it tends to generate a supply of software with better conditions of usability, and to better existing work, in a model of continuous improvement.</p>
 614
 615 <p>On the other hand, the central aspect of competivity is the chance to provide better choices to the consumer. Now, it is impossible to ignore the fact that marketing does not play a neutral role when the product is offered on the market (since accepting the opposite would lead one to suppose that firms' expenses in marketing lack any sense), and that therefore a significant expense under this heading can influence the decisions of the purchaser. This influence of marketing is in large measure reduced by the bill that we are backing, since the choice within the framework proposed is based on the *technical merits* of the product and not on the effort put into commercialization by the producer; in this sense, competitiveness is increased, since the smallest software producer can compete on equal terms with the most powerful corporations.</p>
 616
 617 <p>It is necessary to stress that there is no position more anti-competitive than that of the big software producers, which frequently abuse their dominant position, since in innumerable cases they propose as a solution to problems raised by users: "update your software to the new version" (at the user's expense, naturally); furthermore, it is common to find arbitrary cessation of technical help for products, which, in the provider's judgment alone, are "old"; and so, to receive any kind of technical assistance, the user finds himself forced to migrate to new versions (with non-trivial costs, especially as changes in hardware platform are often involved). And as the whole infrastructure is based on proprietary data formats, the user stays "trapped" in the need to continue using products from the same supplier, or to make the huge effort to change to another environment (probably also proprietary).</p>
 618
 619 <p>You add: "3. So, by compelling the State to favor a business model based entirely on open source, the bill would only discourage the local and international manufacturing companies, which are the ones which really undertake important expenditures, create a significant number of direct and indirect jobs, as well as contributing to the GNP, as opposed to a model of open source software which tends to have an ever weaker economic impact, since it mainly creates jobs in the service sector."</p>
 620
 621 <p>I do not agree with your statement. Partly because of what you yourself point out in paragraph 6 of your letter, regarding the relative weight of services in the context of software use. This contradiction alone would invalidate your position. The service model, adopted by a large number of companies in the software industry, is much larger in economic terms, and with a tendency to increase, than the licensing of programs.</p>
 622
 623 <p>On the other hand, the private sector of the economy has the widest possible freedom to choose the economic model which best suits its interests, even if this freedom of choice is often obscured subliminally by the disproportionate expenditure on marketing by the producers of proprietary software.</p>
 624
 625 <p>In addition, a reading of your opinion would lead to the conclusion that the State market is crucial and essential for the proprietary software industry, to such a point that the choice made by the State in this bill would completely eliminate the market for these firms. If that is true, we can deduce that the State must be subsidizing the proprietary software industry. In the unlikely event that this were true, the State would have the right to apply the subsidies in the area it considered of greatest social value; it is undeniable, in this improbable hypothesis, that if the State decided to subsidize software, it would have to do so choosing the free over the proprietary, considering its social effect and the rational use of taxpayers money.</p>
 626
 627 <p>In respect of the jobs generated by proprietary software in countries like ours, these mainly concern technical tasks of little aggregate value; at the local level, the technicians who provide support for proprietary software produced by transnational companies do not have the possibility of fixing bugs, not necessarily for lack of technical capability or of talent, but because they do not have access to the source code to fix it. With free software one creates more technically qualified employment and a framework of free competence where success is only tied to the ability to offer good technical support and quality of service, one stimulates the market, and one increases the shared fund of knowledge, opening up alternatives to generate services of greater total value and a higher quality level, to the benefit of all involved: producers, service organizations, and consumers.</p>
 628
 629 <p>It is a common phenomenon in developing countries that local software industries obtain the majority of their takings in the service sector, or in the creation of "ad hoc" software. Therefore, any negative impact that the application of the Bill might have in this sector will be more than compensated by a growth in demand for services (as long as these are carried out to high quality standards). If the transnational software companies decide not to compete under these new rules of the game, it is likely that they will undergo some decrease in takings in terms of payment for licenses; however, considering that these firms continue to allege that much of the software used by the State has been illegally copied, one can see that the impact will not be very serious. Certainly, in any case their fortune will be determined by market laws, changes in which cannot be avoided; many firms traditionally associated with proprietary software have already set out on the road (supported by copious expense) of providing services associated with free software, which shows that the models are not mutually exclusive.</p>
 630
 631 <p>With this bill the State is deciding that it needs to preserve certain fundamental values. And it is deciding this based on its sovereign power, without affecting any of the constitutional guarantees. If these values could be guaranteed without having to choose a particular economic model, the effects of the law would be even more beneficial. In any case, it should be clear that the State does not choose an economic model; if it happens that there only exists one economic model capable of providing software which provides the basic guarantee of these principles, this is because of historical circumstances, not because of an arbitrary choice of a given model.</p>
 632
 633 <p>Your letter continues: "4. The bill imposes the use of open source software without considering the dangers that this can bring from the point of view of security, guarantee, and possible violation of the intellectual property rights of third parties."</p>
 634
 635 <p>Alluding in an abstract way to "the dangers this can bring", without specifically mentioning a single one of these supposed dangers, shows at the least some lack of knowledge of the topic. So, allow me to enlighten you on these points.</p>
 636
 637 <p>On security:</p>
 638
 639 <p>National security has already been mentioned in general terms in the initial discussion of the basic principles of the bill. In more specific terms, relative to the security of the software itself, it is well known that all software (whether proprietary or free) contains errors or "bugs" (in programmers' slang). But it is also well known that the bugs in free software are fewer, and are fixed much more quickly, than in proprietary software. It is not in vain that numerous public bodies responsible for the IT security of state systems in developed countries require the use of free software for the same conditions of security and efficiency.</p>
 640
 641 <p>What is impossible to prove is that proprietary software is more secure than free, without the public and open inspection of the scientific community and users in general. This demonstration is impossible because the model of proprietary software itself prevents this analysis, so that any guarantee of security is based only on promises of good intentions (biased, by any reckoning) made by the producer itself, or its contractors.</p>
 642
 643 <p>It should be remembered that in many cases, the licensing conditions include Non-Disclosure clauses which prevent the user from publicly revealing security flaws found in the licensed proprietary product.</p>
 644
 645 <p>In respect of the guarantee:</p>
 646
 647 <p>As you know perfectly well, or could find out by reading the "End User License Agreement" of the products you license, in the great majority of cases the guarantees are limited to replacement of the storage medium in case of defects, but in no case is compensation given for direct or indirect damages, loss of profits, etc... If as a result of a security bug in one of your products, not fixed in time by yourselves, an attacker managed to compromise crucial State systems, what guarantees, reparations and compensation would your company make in accordance with your licensing conditions? The guarantees of proprietary software, inasmuch as programs are delivered ``AS IS'', that is, in the state in which they are, with no additional responsibility of the provider in respect of function, in no way differ from those normal with free software.</p>
 648
 649 <p>On Intellectual Property:</p>
 650
 651 <p>Questions of intellectual property fall outside the scope of this bill, since they are covered by specific other laws. The model of free software in no way implies ignorance of these laws, and in fact the great majority of free software is covered by copyright. In reality, the inclusion of this question in your observations shows your confusion in respect of the legal framework in which free software is developed. The inclusion of the intellectual property of others in works claimed as one's own is not a practice that has been noted in the free software community; whereas, unfortunately, it has been in the area of proprietary software. As an example, the condemnation by the Commercial Court of Nanterre, France, on 27th September 2001 of Microsoft Corp. to a penalty of 3 million francs in damages and interest, for violation of intellectual property (piracy, to use the unfortunate term that your firm commonly uses in its publicity).</p>
 652
 653 <p>You go on to say that: "The bill uses the concept of open source software incorrectly, since it does not necessarily imply that the software is free or of zero cost, and so arrives at mistaken conclusions regarding State savings, with no cost-benefit analysis to validate its position."</p>
 654
 655 <p>This observation is wrong; in principle, freedom and lack of cost are orthogonal concepts: there is software which is proprietary and charged for (for example, MS Office), software which is proprietary and free of charge (MS Internet Explorer), software which is free and charged for (Red Hat, SuSE etc GNU/Linux distributions), software which is free and not charged for (Apache, Open Office, Mozilla), and even software which can be licensed in a range of combinations (MySQL).</p>
 656
 657 <p>Certainly free software is not necessarily free of charge. And the text of the bill does not state that it has to be so, as you will have noted after reading it. The definitions included in the Bill state clearly *what* should be considered free software, at no point referring to freedom from charges. Although the possibility of savings in payments for proprietary software licenses are mentioned, the foundations of the bill clearly refer to the fundamental guarantees to be preserved and to the stimulus to local technological development. Given that a democratic State must support these principles, it has no other choice than to use software with publicly available source code, and to exchange information only in standard formats.</p>
 658
 659 <p>If the State does not use software with these characteristics, it will be weakening basic republican principles. Luckily, free software also implies lower total costs; however, even given the hypothesis (easily disproved) that it was more expensive than proprietary software, the simple existence of an effective free software tool for a particular IT function would oblige the State to use it; not by command of this Bill, but because of the basic principles we enumerated at the start, and which arise from the very essence of the lawful democratic State.</p>
 660
 661 <p>You continue: "6. It is wrong to think that Open Source Software is free of charge. Research by the Gartner Group (an important investigator of the technological market recognized at world level) has shown that the cost of purchase of software (operating system and applications) is only 8% of the total cost which firms and institutions take on for a rational and truly beneficial use of the technology. The other 92% consists of: installation costs, enabling, support, maintenance, administration, and down-time."</p>
 662
 663 <p>This argument repeats that already given in paragraph 5 and partly contradicts paragraph 3. For the sake of brevity we refer to the comments on those paragraphs. However, allow me to point out that your conclusion is logically false: even if according to Gartner Group the cost of software is on average only 8% of the total cost of use, this does not in any way deny the existence of software which is free of charge, that is, with a licensing cost of zero.</p>
 664
 665 <p>In addition, in this paragraph you correctly point out that the service components and losses due to down-time make up the largest part of the total cost of software use, which, as you will note, contradicts your statement regarding the small value of services suggested in paragraph 3. Now the use of free software contributes significantly to reduce the remaining life-cycle costs. This reduction in the costs of installation, support etc. can be noted in several areas: in the first place, the competitive service model of free software, support and maintenance for which can be freely contracted out to a range of suppliers competing on the grounds of quality and low cost. This is true for installation, enabling, and support, and in large part for maintenance. In the second place, due to the reproductive characteristics of the model, maintenance carried out for an application is easily replicable, without incurring large costs (that is, without paying more than once for the same thing) since modifications, if one wishes, can be incorporated in the common fund of knowledge. Thirdly, the huge costs caused by non-functioning software ("blue screens of death", malicious code such as virus, worms, and trojans, exceptions, general protection faults and other well-known problems) are reduced considerably by using more stable software; and it is well known that one of the most notable virtues of free software is its stability.</p>
 666
 667 <p>You further state that: "7. One of the arguments behind the bill is the supposed freedom from costs of open-source software, compared with the costs of commercial software, without taking into account the fact that there exist types of volume licensing which can be highly advantageous for the State, as has happened in other countries."</p>
 668
 669 <p>I have already pointed out that what is in question is not the cost of the software but the principles of freedom of information, accessibility, and security. These arguments have been covered extensively in the preceding paragraphs to which I would refer you.</p>
 670
 671 <p>On the other hand, there certainly exist types of volume licensing (although unfortunately proprietary software does not satisfy the basic principles). But as you correctly pointed out in the immediately preceding paragraph of your letter, they only manage to reduce the impact of a component which makes up no more than 8% of the total.</p>
 672
 673 <p>You continue: "8. In addition, the alternative adopted by the bill (I) is clearly more expensive, due to the high costs of software migration, and (II) puts at risk compatibility and interoperability of the IT platforms within the State, and between the State and the private sector, given the hundreds of versions of open source software on the market."</p>
 674
 675 <p>Let us analyze your statement in two parts. Your first argument, that migration implies high costs, is in reality an argument in favor of the Bill. Because the more time goes by, the more difficult migration to another technology will become; and at the same time, the security risks associated with proprietary software will continue to increase. In this way, the use of proprietary systems and formats will make the State ever more dependent on specific suppliers. Once a policy of using free software has been established (which certainly, does imply some cost) then on the contrary migration from one system to another becomes very simple, since all data is stored in open formats. On the other hand, migration to an open software context implies no more costs than migration between two different proprietary software contexts, which invalidates your argument completely.</p>
 676
 677 <p>The second argument refers to "problems in interoperability of the IT platforms within the State, and between the State and the private sector" This statement implies a certain lack of knowledge of the way in which free software is built, which does not maximize the dependence of the user on a particular platform, as normally happens in the realm of proprietary software. Even when there are multiple free software distributions, and numerous programs which can be used for the same function, interoperability is guaranteed as much by the use of standard formats, as required by the bill, as by the possibility of creating interoperable software given the availability of the source code.</p>
 678
 679 <p>You then say that: "9. The majority of open source code does not offer adequate levels of service nor the guarantee from recognized manufacturers of high productivity on the part of the users, which has led various public organizations to retract their decision to go with an open source software solution and to use commercial software in its place."</p>
 680
 681 <p>This observation is without foundation. In respect of the guarantee, your argument was rebutted in the response to paragraph 4. In respect of support services, it is possible to use free software without them (just as also happens with proprietary software), but anyone who does need them can obtain support separately, whether from local firms or from international corporations, again just as in the case of proprietary software.</p>
 682
 683 <p>On the other hand, it would contribute greatly to our analysis if you could inform us about free software projects *established* in public bodies which have already been abandoned in favor of proprietary software. We know of a good number of cases where the opposite has taken place, but not know of any where what you describe has taken place.</p>
 684
 685 <p>You continue by observing that: "10. The bill discourages the creativity of the Peruvian software industry, which invoices 40 million US$/year, exports 4 million US$ (10th in ranking among non-traditional exports, more than handicrafts) and is a source of highly qualified employment. With a law that encourages the use of open source, software programmers lose their intellectual property rights and their main source of payment."</p>
 686
 687 <p>It is clear enough that nobody is forced to commercialize their code as free software. The only thing to take into account is that if it is not free software, it cannot be sold to the public sector. This is not in any case the main market for the national software industry. We covered some questions referring to the influence of the Bill on the generation of employment which would be both highly technically qualified and in better conditions for competition above, so it seems unnecessary to insist on this point.</p>
 688
 689 <p>What follows in your statement is incorrect. On the one hand, no author of free software loses his intellectual property rights, unless he expressly wishes to place his work in the public domain. The free software movement has always been very respectful of intellectual property, and has generated widespread public recognition of its authors. Names like those of Richard Stallman, Linus Torvalds, Guido van Rossum, Larry Wall, Miguel de Icaza, Andrew Tridgell, Theo de Raadt, Andrea Arcangeli, Bruce Perens, Darren Reed, Alan Cox, Eric Raymond, and many others, are recognized world-wide for their contributions to the development of software that is used today by millions of people throughout the world. On the other hand, to say that the rewards for authors rights make up the main source of payment of Peruvian programmers is in any case a guess, in particular since there is no proof to this effect, nor a demonstration of how the use of free software by the State would influence these payments.</p>
 690
 691 <p>You go on to say that: "11. Open source software, since it can be distributed without charge, does not allow the generation of income for its developers through exports. In this way, the multiplier effect of the sale of software to other countries is weakened, and so in turn is the growth of the industry, while Government rules ought on the contrary to stimulate local industry."</p>
 692
 693 <p>This statement shows once again complete ignorance of the mechanisms of and market for free software. It tries to claim that the market of sale of non- exclusive rights for use (sale of licenses) is the only possible one for the software industry, when you yourself pointed out several paragraphs above that it is not even the most important one. The incentives that the bill offers for the growth of a supply of better qualified professionals, together with the increase in experience that working on a large scale with free software within the State will bring for Peruvian technicians, will place them in a highly competitive position to offer their services abroad.</p>
 694
 695 <p>You then state that: "12. In the Forum, the use of open source software in education was discussed, without mentioning the complete collapse of this initiative in a country like Mexico, where precisely the State employees who founded the project now state that open source software did not make it possible to offer a learning experience to pupils in the schools, did not take into account the capability at a national level to give adequate support to the platform, and that the software did not and does not allow for the levels of platform integration that now exist in schools."</p>
 696
 697 <p>In fact Mexico has gone into reverse with the Red Escolar (Schools Network) project. This is due precisely to the fact that the driving forces behind the Mexican project used license costs as their main argument, instead of the other reasons specified in our project, which are far more essential. Because of this conceptual mistake, and as a result of the lack of effective support from the SEP (Secretary of State for Public Education), the assumption was made that to implant free software in schools it would be enough to drop their software budget and send them a CD ROM with Gnu/Linux instead. Of course this failed, and it couldn't have been otherwise, just as school laboratories fail when they use proprietary software and have no budget for implementation and maintenance. That's exactly why our bill is not limited to making the use of free software mandatory, but recognizes the need to create a viable migration plan, in which the State undertakes the technical transition in an orderly way in order to then enjoy the advantages of free software.</p>
 698
 699 <p>You end with a rhetorical question: "13. If open source software satisfies all the requirements of State bodies, why do you need a law to adopt it? Shouldn't it be the market which decides freely which products give most benefits or value?"</p>
 700
 701 <p>We agree that in the private sector of the economy, it must be the market that decides which products to use, and no state interference is permissible there. However, in the case of the public sector, the reasoning is not the same: as we have already established, the state archives, handles, and transmits information which does not belong to it, but which is entrusted to it by citizens, who have no alternative under the rule of law. As a counterpart to this legal requirement, the State must take extreme measures to safeguard the integrity, confidentiality, and accessibility of this information. The use of proprietary software raises serious doubts as to whether these requirements can be fulfilled, lacks conclusive evidence in this respect, and so is not suitable for use in the public sector.</p>
 702
 703 <p>The need for a law is based, firstly, on the realization of the fundamental principles listed above in the specific area of software; secondly, on the fact that the State is not an ideal homogeneous entity, but made up of multiple bodies with varying degrees of autonomy in decision making. Given that it is inappropriate to use proprietary software, the fact of establishing these rules in law will prevent the personal discretion of any state employee from putting at risk the information which belongs to citizens. And above all, because it constitutes an up-to-date reaffirmation in relation to the means of management and communication of information used today, it is based on the republican principle of openness to the public.</p>
 704
 705 <p>In conformance with this universally accepted principle, the citizen has the right to know all information held by the State and not covered by well- founded declarations of secrecy based on law. Now, software deals with information and is itself information. Information in a special form, capable of being interpreted by a machine in order to execute actions, but crucial information all the same because the citizen has a legitimate right to know, for example, how his vote is computed or his taxes calculated. And for that he must have free access to the source code and be able to prove to his satisfaction the programs used for electoral computations or calculation of his taxes.</p>
 706
 707 <p>I wish you the greatest respect, and would like to repeat that my office will always be open for you to expound your point of view to whatever level of detail you consider suitable.</p>
 708
 709 <p>Cordially,<br>
 710 DR. EDGAR DAVID VILLANUEVA NUÑEZ<br>
 711 Congressman of the Republic of Perú.</p>
 712 </blockquote>
 713
 714       </div>
 715       <div class="tags">
 716
 717
 718         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 719
 720
 721       </div>
 722     </div>
 723     <div class="padding"></div>
 724
 725     <div class="entry">
 726       <div class="title">
 727         <a href="http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html">Is Ogg Theora a free and open standard?</a>
 728       </div>
 729       <div class="date">
 730         25th December 2010
 731       </div>
 732       <div class="body">
 733         <p><a href="http://www.digistan.org/open-standard:definition">The
 734 Digistan definition</a> of a free and open standard reads like this:</p>
 735
 736 <blockquote>
 737
 738 <p>The Digital Standards Organization defines free and open standard
 739 as follows:</p>
 740
 741 <ol>
 742
 743 <li>A free and open standard is immune to vendor capture at all stages
 744 in its life-cycle. Immunity from vendor capture makes it possible to
 745 freely use, improve upon, trust, and extend a standard over time.</li>
 746
 747 <li>The standard is adopted and will be maintained by a not-for-profit
 748 organisation, and its ongoing development occurs on the basis of an
 749 open decision-making procedure available to all interested
 750 parties.</li>
 751
 752 <li>The standard has been published and the standard specification
 753 document is available freely. It must be permissible to all to copy,
 754 distribute, and use it freely.</li>
 755
 756 <li>The patents possibly present on (parts of) the standard are made
 757 irrevocably available on a royalty-free basis.</li>
 758
 759 <li>There are no constraints on the re-use of the standard.</li>
 760
 761 </ol>
 762
 763 <p>The economic outcome of a free and open standard, which can be
 764 measured, is that it enables perfect competition between suppliers of
 765 products based on the standard.</p>
 766 </blockquote>
 767
 768 <p>For a while now I have tried to figure out of Ogg Theora is a free
 769 and open standard according to this definition.  Here is a short
 770 writeup of what I have been able to gather so far.  I brought up the
 771 topic on the Xiph advocacy mailing list
 772 <a href="http://lists.xiph.org/pipermail/advocacy/2009-July/001632.html">in
 773 July 2009</a>, for those that want to see some background information.
 774 According to Ivo Emanuel Gonçalves and Monty Montgomery on that list
 775 the Ogg Theora specification fulfils the Digistan definition.</p>
 776
 777 <p><strong>Free from vendor capture?</strong></p>
 778
 779 <p>As far as I can see, there is no single vendor that can control the
 780 Ogg Theora specification.  It can be argued that the
 781 <a href="http://www.xiph.org/">Xiph foundation</A> is such vendor, but
 782 given that it is a non-profit foundation with the expressed goal
 783 making free and open protocols and standards available, it is not
 784 obvious that this is a real risk.  One issue with the Xiph
 785 foundation is that its inner working (as in board member list, or who
 786 control the foundation) are not easily available on the web.  I've
 787 been unable to find out who is in the foundation board, and have not
 788 seen any accounting information documenting how money is handled nor
 789 where is is spent in the foundation.  It is thus not obvious for an
 790 external observer who control The Xiph foundation, and for all I know
 791 it is possible for a single vendor to take control over the
 792 specification.  But it seem unlikely.</p>
 793
 794 <p><strong>Maintained by open not-for-profit organisation?</strong></p>
 795
 796 <p>Assuming that the Xiph foundation is the organisation its web pages
 797 claim it to be, this point is fulfilled.  If Xiph foundation is
 798 controlled by a single vendor, it isn't, but I have not found any
 799 documentation indicating this.</p>
 800
 801 <p>According to
 802 <a href="http://media.hiof.no/diverse/fad/rapport_4.pdf">a report</a>
 803 prepared by Audun Vaaler og Børre Ludvigsen for the Norwegian
 804 government, the Xiph foundation is a non-commercial organisation and
 805 the development process is open, transparent and non-Discrimatory.
 806 Until proven otherwise, I believe it make most sense to believe the
 807 report is correct.</p>
 808
 809 <p><strong>Specification freely available?</strong></p>
 810
 811 <p>The specification for the <a href="http://www.xiph.org/ogg/doc/">Ogg
 812 container format</a> and both the
 813 <a href="http://www.xiph.org/vorbis/doc/">Vorbis</a> and
 814 <a href="http://theora.org/doc/">Theora</a> codeces are available on
 815 the web.  This are the terms in the Vorbis and Theora specification:
 816
 817 <blockquote>
 818
 819 Anyone may freely use and distribute the Ogg and [Vorbis/Theora]
 820 specifications, whether in private, public, or corporate
 821 capacity. However, the Xiph.Org Foundation and the Ogg project reserve
 822 the right to set the Ogg [Vorbis/Theora] specification and certify
 823 specification compliance.
 824
 825 </blockquote>
 826
 827 <p>The Ogg container format is specified in IETF
 828 <a href="http://www.xiph.org/ogg/doc/rfc3533.txt">RFC 3533</a>, and
 829 this is the term:<p>
 830
 831 <blockquote>
 832
 833 <p>This document and translations of it may be copied and furnished to
 834 others, and derivative works that comment on or otherwise explain it
 835 or assist in its implementation may be prepared, copied, published and
 836 distributed, in whole or in part, without restriction of any kind,
 837 provided that the above copyright notice and this paragraph are
 838 included on all such copies and derivative works.  However, this
 839 document itself may not be modified in any way, such as by removing
 840 the copyright notice or references to the Internet Society or other
 841 Internet organizations, except as needed for the purpose of developing
 842 Internet standards in which case the procedures for copyrights defined
 843 in the Internet Standards process must be followed, or as required to
 844 translate it into languages other than English.</p>
 845
 846 <p>The limited permissions granted above are perpetual and will not be
 847 revoked by the Internet Society or its successors or assigns.</p>
 848 </blockquote>
 849
 850 <p>All these terms seem to allow unlimited distribution and use, an
 851 this term seem to be fulfilled.  There might be a problem with the
 852 missing permission to distribute modified versions of the text, and
 853 thus reuse it in other specifications.  Not quite sure if that is a
 854 requirement for the Digistan definition.</p>
 855
 856 <p><strong>Royalty-free?</strong></p>
 857
 858 <p>There are no known patent claims requiring royalties for the Ogg
 859 Theora format.
 860 <a href="http://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=65782">MPEG-LA</a>
 861 and
 862 <a href="http://yro.slashdot.org/story/10/04/30/237238/Steve-Jobs-Hints-At-Theora-Lawsuit">Steve
 863 Jobs</a> in Apple claim to know about some patent claims (submarine
 864 patents) against the Theora format, but no-one else seem to believe
 865 them.  Both Opera Software and the Mozilla Foundation have looked into
 866 this and decided to implement Ogg Theora support in their browsers
 867 without paying any royalties.  For now the claims from MPEG-LA and
 868 Steve Jobs seem more like FUD to scare people to use the H.264 codec
 869 than any real problem with Ogg Theora.</p>
 870
 871 <p><strong>No constraints on re-use?</strong></p>
 872
 873 <p>I am not aware of any constraints on re-use.</p>
 874
 875 <p><strong>Conclusion</strong></p>
 876
 877 <p>3 of 5 requirements seem obviously fulfilled, and the remaining 2
 878 depend on the governing structure of the Xiph foundation.  Given the
 879 background report used by the Norwegian government, I believe it is
 880 safe to assume the last two requirements are fulfilled too, but it
 881 would be nice if the Xiph foundation web site made it easier to verify
 882 this.</p>
 883
 884 <p>It would be nice to see other analysis of other specifications to
 885 see if they are free and open standards.</p>
 886
 887       </div>
 888       <div class="tags">
 889
 890
 891         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
 892
 893
 894       </div>
 895     </div>
 896     <div class="padding"></div>
 897
 898     <div class="entry">
 899       <div class="title">
 900         <a href="http://people.skolelinux.org/pere/blog/The_many_definitions_of_a_open_standard.html">The many definitions of a open standard</a>
 901       </div>
 902       <div class="date">
 903         27th December 2010
 904       </div>
 905       <div class="body">
 906         <p>One of the reasons I like the Digistan definition of
 907 "<a href="http://www.digistan.org/open-standard:definition">Free and
 908 Open Standard</a>" is that this is a new term, and thus the meaning of
 909 the term has been decided by Digistan.  The term "Open Standard" has
 910 become so misunderstood that it is no longer very useful when talking
 911 about standards.  One end up discussing which definition is the best
 912 one and with such frame the only one gaining are the proponents of
 913 de-facto standards and proprietary solutions.</p>
 914
 915 <p>But to give us an idea about the diversity of definitions of open
 916 standards, here are a few that I know about.  This list is not
 917 complete, but can be a starting point for those that want to do a
 918 complete survey.  More definitions are available on the
 919 <a href="http://en.wikipedia.org/wiki/Open_standard">wikipedia
 920 page</a>.</p>
 921
 922 <p>First off is my favourite, the definition from the European
 923 Interoperability Framework version 1.0.  Really sad to notice that BSA
 924 and others has succeeded in getting it removed from version 2.0 of the
 925 framework by stacking the committee drafting the new version with
 926 their own people.  Anyway, the definition is still available and it
 927 include the key properties needed to make sure everyone can use a
 928 specification on equal terms.</p>
 929
 930 <blockquote>
 931
 932 <p>The following are the minimal characteristics that a specification
 933 and its attendant documents must have in order to be considered an
 934 open standard:</p>
 935
 936 <ul>
 937
 938 <li>The standard is adopted and will be maintained by a not-for-profit
 939 organisation, and its ongoing development occurs on the basis of an
 940 open decision-making procedure available to all interested parties
 941 (consensus or majority decision etc.).</li>
 942
 943 <li>The standard has been published and the standard specification
 944 document is available either freely or at a nominal charge. It must be
 945 permissible to all to copy, distribute and use it for no fee or at a
 946 nominal fee.</li>
 947
 948 <li>The intellectual property - i.e. patents possibly present - of
 949 (parts of) the standard is made irrevocably available on a royalty-
 950 free basis.</li>
 951
 952 <li>There are no constraints on the re-use of the standard.</li>
 953
 954 </ul>
 955 </blockquote>
 956
 957 <p>Another one originates from my friends over at
 958 <a href="http://www.dkuug.dk/">DKUUG</a>, who coined and gathered
 959 support for <a href="http://www.aaben-standard.dk/">this
 960 definition</a> in 2004.  It even made it into the Danish parlament as
 961 <a href="http://www.ft.dk/dokumenter/tingdok.aspx?/samling/20051/beslutningsforslag/B103/som_fremsat.htm">their
 962 definition of a open standard</a>.  Another from a different part of
 963 the Danish government is available from the wikipedia page.</p>
 964
 965 <blockquote>
 966
 967 <p>En åben standard opfylder følgende krav:</p>
 968
 969 <ol>
 970
 971 <li>Veldokumenteret med den fuldstændige specifikation offentligt
 972 tilgængelig.</li>
 973
 974 <li>Frit implementerbar uden økonomiske, politiske eller juridiske
 975 begrænsninger på implementation og anvendelse.</li>
 976
 977 <li>Standardiseret og vedligeholdt i et åbent forum (en såkaldt
 978 "standardiseringsorganisation") via en åben proces.</li>
 979
 980 </ol>
 981
 982 </blockquote>
 983
 984 <p>Then there is <a href="http://www.fsfe.org/projects/os/def.html">the
 985 definition</a> from Free Software Foundation Europe.</p>
 986
 987 <blockquote>
 988
 989 <p>An Open Standard refers to a format or protocol that is</p>
 990
 991 <ol>
 992
 993 <li>subject to full public assessment and use without constraints in a
 994 manner equally available to all parties;</li>
 995
 996 <li>without any components or extensions that have dependencies on
 997 formats or protocols that do not meet the definition of an Open
 998 Standard themselves;</li>
 999
1000 <li>free from legal or technical clauses that limit its utilisation by
1001 any party or in any business model;</li>
1002
1003 <li>managed and further developed independently of any single vendor
1004 in a process open to the equal participation of competitors and third
1005 parties;</li>
1006
1007 <li>available in multiple complete implementations by competing
1008 vendors, or as a complete implementation equally available to all
1009 parties.</li>
1010
1011 </ol>
1012
1013 </blockquote>
1014
1015 <p>A long time ago, SUN Microsystems, now bought by Oracle, created
1016 its
1017 <a href="http://blogs.sun.com/dennisding/resource/Open%20Standard%20Definition.pdf">Open
1018 Standards Checklist</a> with a fairly detailed description.</p>
1019
1020 <blockquote>
1021 <p>Creation and Management of an Open Standard
1022
1023 <ul>
1024
1025 <li>Its development and management process must be collaborative and
1026   democratic:
1027
1028          <ul>
1029
1030          <li>Participation must be accessible to all those who wish to
1031             participate and can meet fair and reasonable criteria
1032             imposed by the organization under which it is developed
1033             and managed.</li>
1034
1035          <li>The processes must be documented and, through a known
1036             method, can be changed through input from all
1037             participants.</li>
1038
1039          <li>The process must be based on formal and binding commitments for
1040             the disclosure and licensing of intellectual property rights.</li>
1041
1042          <li>Development and management should strive for consensus,
1043             and an appeals process must be clearly outlined.</li>
1044
1045          <li>The standard specification must be open to extensive
1046             public review at least once in its life-cycle, with
1047             comments duly discussed and acted upon, if required.</li>
1048
1049          </ul>
1050
1051 </li>
1052
1053 </ul>
1054
1055 <p>Use and Licensing of an Open Standard</p>
1056 <ul>
1057
1058 <li>The standard must describe an interface, not an implementation,
1059   and the industry must be capable of creating multiple, competing
1060   implementations to the interface described in the standard without
1061   undue or restrictive constraints.  Interfaces include APIs,
1062   protocols, schemas, data formats and their encoding.</li>
1063
1064 <li> The standard must not contain any proprietary "hooks" that create
1065   a technical or economic barriers</li>
1066
1067 <li>Faithful implementations of the standard must
1068   interoperate. Interoperability means the ability of a computer
1069   program to communicate and exchange information with other computer
1070   programs and mutually to use the information which has been
1071   exchanged. This includes the ability to use, convert, or exchange
1072   file formats, protocols, schemas, interface information or
1073   conventions, so as to permit the computer program to work with other
1074   computer programs and users in all the ways in which they are
1075   intended to function.</li>
1076
1077 <li>It must be permissible for anyone to copy, distribute and read the
1078   standard for a nominal fee, or even no fee. If there is a fee, it
1079   must be low enough to not preclude widespread use.</li>
1080
1081 <li>It must be possible for anyone to obtain free (no royalties or
1082   fees; also known as "royalty free"), worldwide, non-exclusive and
1083   perpetual licenses to all essential patent claims to make, use and
1084   sell products based on the standard.  The only exceptions are
1085   terminations per the reciprocity and defensive suspension terms
1086   outlined below. Essential patent claims include pending, unpublished
1087   patents, published patents, and patent applications. The license is
1088   only for the exact scope of the standard in question.
1089
1090       <ul>
1091
1092       <li> May be conditioned only on reciprocal licenses to any of
1093         licensees' patent claims essential to practice that standard
1094         (also known as a reciprocity clause)</li>
1095
1096       <li> May be terminated as to any licensee who sues the licensor
1097         or any other licensee for infringement of patent claims
1098         essential to practice that standard (also known as a
1099         "defensive suspension" clause)</li>
1100
1101       <li> The same licensing terms are available to every potential
1102         licensor</li>
1103
1104       </ul>
1105 </li>
1106
1107 <li>The licensing terms of an open standards must not preclude
1108   implementations of that standard under open source licensing terms
1109   or restricted licensing terms</li>
1110
1111 </ul>
1112
1113 </blockquote>
1114
1115 <p>It is said that one of the nice things about standards is that
1116 there are so many of them.  As you can see, the same holds true for
1117 open standard definitions.  Most of the definitions have a lot in
1118 common, and it is not really controversial what properties a open
1119 standard should have, but the diversity of definitions have made it
1120 possible for those that want to avoid a level marked field and real
1121 competition to downplay the significance of open standards.  I hope we
1122 can turn this tide by focusing on the advantages of Free and Open
1123 Standards.</p>
1124
1125       </div>
1126       <div class="tags">
1127
1128
1129         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
1130
1131
1132       </div>
1133     </div>
1134     <div class="padding"></div>
1135
1136     <div class="entry">
1137       <div class="title">
1138         <a href="http://people.skolelinux.org/pere/blog/What_standards_are_Free_and_Open_as_defined_by_Digistan_.html">What standards are Free and Open as defined by Digistan?</a>
1139       </div>
1140       <div class="date">
1141         30th December 2010
1142       </div>
1143       <div class="body">
1144         <p>After trying to
1145 <a href="http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html">compare
1146 Ogg Theora</a> to
1147 <a href="http://www.digistan.org/open-standard:definition">the Digistan
1148 definition</a> of a free and open standard, I concluded that this need
1149 to be done for more standards and started on a framework for doing
1150 this.  As a start, I want to get the status for all the standards in
1151 the Norwegian reference directory, which include UTF-8, HTML, PDF, ODF,
1152 JPEG, PNG, SVG and others.  But to be able to complete this in a
1153 reasonable time frame, I will need help.</p>
1154
1155 <p>If you want to help out with this work, please visit
1156 <a href="http://wiki.nuug.no/grupper/standard/digistan-analyse">the
1157 wiki pages I have set up for this</a>, and let me know that you want
1158 to help out.  The IRC channel #nuug on irc.freenode.net is a good
1159 place to coordinate this for now, as it is the IRC channel for the
1160 NUUG association where I have created the framework (I am the leader
1161 of the Norwegian Unix User Group).</p>
1162
1163 <p>The framework is still forming, and a lot is left to do.  Do not be
1164 scared by the sketchy form of the current pages. :)</p>
1165
1166       </div>
1167       <div class="tags">
1168
1169
1170         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
1171
1172
1173       </div>
1174     </div>
1175     <div class="padding"></div>
1176
1177     <p style="text-align: right;"><a href="12.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS Feed" width="36" height="14" /></a></p>
1178     <div id="sidebar">
1179
1180
1181
1182 <h2>Archive</h2>
1183 <ul>
1184
1185 <li>2012
1186 <ul>
1187
1188 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
1189
1190 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
1191
1192 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
1193
1194 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
1195
1196 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
1197
1198 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
1199
1200 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (12)</a></li>
1201
1202 </ul></li>
1203
1204 <li>2011
1205 <ul>
1206
1207 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
1208
1209 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
1210
1211 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
1212
1213 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
1214
1215 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
1216
1217 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
1218
1219 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
1220
1221 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
1222
1223 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
1224
1225 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
1226
1227 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
1228
1229 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
1230
1231 </ul></li>
1232
1233 <li>2010
1234 <ul>
1235
1236 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
1237
1238 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
1239
1240 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
1241
1242 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
1243
1244 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
1245
1246 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
1247
1248 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
1249
1250 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
1251
1252 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
1253
1254 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
1255
1256 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
1257
1258 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
1259
1260 </ul></li>
1261
1262 <li>2009
1263 <ul>
1264
1265 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
1266
1267 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
1268
1269 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
1270
1271 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
1272
1273 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
1274
1275 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
1276
1277 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
1278
1279 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
1280
1281 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
1282
1283 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
1284
1285 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
1286
1287 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
1288
1289 </ul></li>
1290
1291 <li>2008
1292 <ul>
1293
1294 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
1295
1296 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1297
1298 </ul></li>
1299
1300 </ul>
1301
1302
1303
1304 <h2>Tags</h2>
1305 <ul>
1306
1307  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
1308
1309  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1310
1311  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1312
1313  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (2)</a></li>
1314
1315  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (12)</a></li>
1316
1317  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1318
1319  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (55)</a></li>
1320
1321  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (109)</a></li>
1322
1323  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (9)</a></li>
1324
1325  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1326
1327  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (141)</a></li>
1328
1329  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (17)</a></li>
1330
1331  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
1332
1333  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (6)</a></li>
1334
1335  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (30)</a></li>
1336
1337  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (16)</a></li>
1338
1339  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (8)</a></li>
1340
1341  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (4)</a></li>
1342
1343  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1344
1345  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (22)</a></li>
1346
1347  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (188)</a></li>
1348
1349  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (139)</a></li>
1350
1351  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (4)</a></li>
1352
1353  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1354
1355  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (32)</a></li>
1356
1357  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (48)</a></li>
1358
1359  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1360
1361  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1362
1363  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
1364
1365  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (4)</a></li>
1366
1367  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1368
1369  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
1370
1371  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1372
1373  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (23)</a></li>
1374
1375  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1376
1377  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (1)</a></li>
1378
1379  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (35)</a></li>
1380
1381  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (1)</a></li>
1382
1383  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (4)</a></li>
1384
1385  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (10)</a></li>
1386
1387  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (6)</a></li>
1388
1389  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (32)</a></li>
1390
1391  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (1)</a></li>
1392
1393  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (25)</a></li>
1394
1395 </ul>
1396
1397
1398     </div>
1399     <p style="text-align: right">
1400  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.4</a>
1401 </p>
1402
1403   </body>
1404 </html>