]> pere.pagekite.me Git - homepage.git/blob - blog/index.rss
Generated.
[homepage.git] / blog / index.rss
1 <?xml version="1.0" encoding="utf-8"?>
2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:atom="http://www.w3.org/2005/Atom">
3 <channel>
4 <title>Petter Reinholdtsen</title>
5 <description></description>
6 <link>http://people.skolelinux.org/pere/blog/</link>
7 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
8
9 <item>
10 <title>Debian Edu - some ideas for the future versions</title>
11 <link>http://people.skolelinux.org/pere/blog/Debian_Edu___some_ideas_for_the_future_versions.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Edu___some_ideas_for_the_future_versions.html</guid>
13 <pubDate>Mon, 11 Jun 2012 14:30:00 +0200</pubDate>
14 <description>&lt;p&gt;During my work on Debian Edu based on Squeeze, I came across some
15 issues that should be addressed in the Wheezy release. I finally
16 found time to wrap up my notes and provide quick summary of what I
17 found, with a bit explanation.&lt;/p&gt;
18
19 &lt;p&gt;&lt;ul&gt;
20
21 &lt;li&gt;We need to rewrite our package installation framework, as tasksel
22 changed from using tasksel tasks to using meta packages (aka packages
23 with dependencies like our education-* packages), and our installation
24 system depend on tasksel tasks in
25 /usr/share/tasksel/debian-edu-tasks.desc for package
26 installation.&lt;/li&gt;
27
28 &lt;li&gt;Enable Kerberos login for more services. Now with the Kerberos
29 foundation in place, we should use it to get single sign on with more
30 services, and avoiding unneeded password / login questions. We should
31 at least try to enable it for these services:
32 &lt;ul&gt;
33
34 &lt;li&gt;CUPS for admins to add/configure printers and users when using
35 quotas.&lt;/li&gt;
36 &lt;li&gt;Nagios for admins checking the system status.&lt;/li&gt;
37 &lt;li&gt;GOsa for admins updating LDAP and users changing their passwords.&lt;/li&gt;
38 &lt;li&gt;LDAP for admins updating LDAP.&lt;/li&gt;
39 &lt;li&gt;Squid for users when exam mode / filtering is active.&lt;/li&gt;
40 &lt;li&gt;ssh for admins and users to save a password prompt.&lt;/li&gt;
41
42 &lt;/ul&gt;&lt;/li&gt;
43
44 &lt;li&gt;When we move GOsa to use Kerberos instead of LDAP bind to
45 authenticate users, we should try to block or at least limit access to
46 use LDAP bind for authentication, to ensure Kerberos is used when it
47 is intended, and nothing fall back to using the less safe LDAP bind&lt;/li&gt;
48
49 &lt;li&gt;Merge debian-edu-config and debian-edu-install. The split made
50 sense when d-e-install did a lot more, but these days it is just an
51 inconvenience when we update the debconf preseeding values.&lt;/li&gt;
52
53 &lt;li&gt;Fix partman-auto to allow us to abort the installation before
54 touching the disk if the disk is too small. This is
55 &lt;a href=&quot;http://bugs.debian.org/653305&quot;&gt;BTS report #653305&lt;/a&gt; and the
56 d-i developers are fine with the patch and someone just need to apply
57 it and upload.&lt;/li&gt;
58
59 &lt;li&gt;Adjust to new LTSP framework (boot time config instead of install
60 time config). LTSP changed its design, and our hooks to install
61 packages and update the configuration is most likely not going to work
62 in Wheezy.
63
64 &lt;li&gt;Consider switching to NBD instead of NFS for LTSP root, to allow
65 the Kernel to cache files in its normal file cache, possibly speeding
66 up KDE login on slow networks.&lt;/li&gt;
67
68 &lt;li&gt;Make it possible to create expired user passwords that need to
69 change on first login. This is useful when handing out password on
70 paper, to make sure only the user know the password. This require
71 fixes to the PAM handling of kdm and gdm.&lt;/li&gt;
72
73 &lt;li&gt;Make GUI for adding new machines automatically from sitesummary.
74 The current command line script is not very friendly to people most
75 familiar with GUIs. This should probably be integrated into GOsa to
76 have it available where the admin will be looking for it..&lt;/li&gt;
77
78 &lt;li&gt;We should find way for Nagios to check that the DHCP service
79 actually is working (as in handling out IP addresses). None of the
80 Nagios checks I have found so far have been working for me.&lt;/li&gt;
81
82 &lt;li&gt;We should switch from libpam-nss-ldapd to sssd for all profiles
83 using LDAP, and not only on for roaming workstations, to have less
84 packages to configure and consistent setup across all profiles.&lt;/li&gt;
85
86 &lt;li&gt;We should configure Kerberos to update LDAP and Samba password
87 when changing password using the Kerberos protocol. The hook was
88 requested in &lt;a href=&quot;http://bugs.debian.org/588968&quot;&gt;BTS report
89 #588968&lt;/a&gt; and is now available in Wheezy. We might need to write a
90 MIT Kerberos plugin in C to get this.&lt;/li&gt;
91
92 &lt;li&gt;We should clean up the set of applications installed by default.
93 &lt;ul&gt;
94
95 &lt;li&gt;reduce the number of chemistry visualisers&lt;/li&gt;
96 &lt;li&gt;consider dropping xpaint&lt;/li&gt;
97 &lt;li&gt;and probably more?&lt;/li&gt;
98 &lt;/ul&gt;&lt;/li&gt;
99
100 &lt;li&gt;Some hardware need external firmware to work properly. This is
101 mostly the case for WiFi network cards, but there are some other
102 examples too. For popular laptops to work out of the box, such
103 firmware need to be installed from non-free, and we should provide
104 some GUI to do this. Ubuntu already have this implemented, and we
105 could consider using their packages. At the moment we have some
106 command line script to do this (one for the running system, another
107 for the LTSP chroot).&lt;/li&gt;
108
109
110 &lt;li&gt;In Squeeze, we provide KDE, Gnome and LXDE as desktop options. We
111 should extend the list to Xfce and Sugar, and preferably find a way to
112 install several and allow the admin or the user to select which one to
113 use.&lt;/li&gt;
114
115 &lt;li&gt;The golearn tool from the goplay package make it easy to check out
116 interesting educational packages. We should work on the package
117 tagging in Debian to ensure it represent all the useful educational
118 packages, and extend the tool to allow it to use packagekit to install
119 new applications with a simple mouse click.&lt;/li&gt;
120
121 &lt;li&gt;The Squeeze version got half a exam solution already in place,
122 with the introduction of iptable based network blocking, but for it to
123 be a complete exam solution the Squid proxy need to enable
124 filtering/blocking as well when the exam mode is enabled. We should
125 implement a way to easily enable this for the schools that want it,
126 instead of the &quot;it is documented&quot; method of today.&lt;/li&gt;
127
128 &lt;li&gt;A feature used in several schools is the ability for a teacher to
129 &quot;take over&quot; the desktop of individual or all computers in the room.
130 There are at least three implementations,
131 &lt;a href=&quot;italc.sourceforge.net/&quot;&gt;italc&lt;/a&gt;,
132 &lt;a href=&quot;http://www.itais.net/help/en/&quot;&gt;controlaula&lt;/a&gt; og
133 &lt;a href=&quot;http://www.epoptes.org/&quot;&gt;epoptes&lt;/a&gt; and we should pick one of
134 them and make it trivial to set it up in a school. The challenges is
135 how to distribute crypto keys and how to group computers in one room
136 and how to set up which machine/user can control the machines in a
137 given room.&lt;/li&gt;
138
139 &lt;li&gt;Tablets and surf boards are getting more and more popular, and we
140 should look into providing a good solution for integrating these into
141 the Debian Edu network. Not quite sure how. Perhaps we should
142 provide a installation profile with better touch screen support for
143 them, or add some sync services to allow them to exchange
144 configuration and data with the central server. This should be
145 investigated.&lt;/li&gt;
146
147 &lt;/ul&gt;&lt;/p&gt;
148
149 &lt;p&gt;I guess we will discover more as we continue to work on the Wheezy
150 version.&lt;/p&gt;
151 </description>
152 </item>
153
154 <item>
155 <title>Litt statistikk fra Offentlig Elektronisk postjournal</title>
156 <link>http://people.skolelinux.org/pere/blog/Litt_statistikk_fra_Offentlig_Elektronisk_postjournal.html</link>
157 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Litt_statistikk_fra_Offentlig_Elektronisk_postjournal.html</guid>
158 <pubDate>Sun, 10 Jun 2012 20:30:00 +0200</pubDate>
159 <description>&lt;p&gt;De siste månedene har jeg sammen med andre i NUUG jobbet med å
160 gjøre det enklere å få innsyn i offentlige dokumenter, og dette
161 inkluderer å gjøre postjournaler enklere tilgjengelig for maskinell
162 analyse og søk. I den forbindelse tok jeg i dag å tittet litt på
163 &lt;a href=&quot;http://www.oep.no/&quot;&gt;Offentlig Elektronisk Postjournal
164 (OEP)&lt;/a&gt;, FAD/DIFIs fellesløsning for departementer og statlige
165 etater.&lt;/p&gt;
166
167 &lt;p&gt;Her er antall oppføringer pr. måned det siste året,
168 &lt;a href=&quot;https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=htmltable&amp;name=postliste-oep&amp;query=select%20strftime(%22%25Y-%25m%22%2C%20%60recordpublishdate%60)%20as%20oeppubmonth%2C%20count(*)%20from%20%60swdata%60%20group%20by%20oeppubmonth%20order%20by%20oeppubmonth&quot;&gt;summert
169 opp&lt;/a&gt; ved hjelp av
170 &lt;a href=&quot;https://scraperwiki.com/scrapers/postliste-oep/&quot;&gt;en
171 Scraperwiki-database&lt;/a&gt;. Merk at denne Scraperwikien har
172 ytelsesproblemer pga. mengden data. &lt;/p&gt;
173
174 &lt;p&gt;&lt;table border=&quot;1&quot;&gt;
175 &lt;tr&gt;&lt;th&gt;Måned&lt;/th&gt;&lt;th&gt;Antall&lt;/th&gt;&lt;/tr&gt;
176 &lt;tr&gt;&lt;td&gt;2011-07&lt;/td&gt;&lt;td&gt;164355&lt;/td&gt;&lt;/tr&gt;
177 &lt;tr&gt;&lt;td&gt;2011-08&lt;/td&gt;&lt;td&gt;153662&lt;/td&gt;&lt;/tr&gt;
178 &lt;tr&gt;&lt;td&gt;2011-09&lt;/td&gt;&lt;td&gt;173134&lt;/td&gt;&lt;/tr&gt;
179 &lt;tr&gt;&lt;td&gt;2011-10&lt;/td&gt;&lt;td&gt;170665&lt;/td&gt;&lt;/tr&gt;
180 &lt;tr&gt;&lt;td&gt;2011-11&lt;/td&gt;&lt;td&gt;198409&lt;/td&gt;&lt;/tr&gt;
181 &lt;tr&gt;&lt;td&gt;2011-12&lt;/td&gt;&lt;td&gt;175908&lt;/td&gt;&lt;/tr&gt;
182 &lt;tr&gt;&lt;td&gt;2012-01&lt;/td&gt;&lt;td&gt;206875&lt;/td&gt;&lt;/tr&gt;
183 &lt;tr&gt;&lt;td&gt;2012-02&lt;/td&gt;&lt;td&gt;202862&lt;/td&gt;&lt;/tr&gt;
184 &lt;tr&gt;&lt;td&gt;2012-03&lt;/td&gt;&lt;td&gt;204225&lt;/td&gt;&lt;/tr&gt;
185 &lt;tr&gt;&lt;td&gt;2012-04&lt;/td&gt;&lt;td&gt;207931&lt;/td&gt;&lt;/tr&gt;
186 &lt;tr&gt;&lt;td&gt;2012-05&lt;/td&gt;&lt;td&gt;223754&lt;/td&gt;&lt;/tr&gt;
187 &lt;/table&gt;&lt;/p&gt;
188
189 &lt;p&gt;Det er også interessant å se hvor ofte ulike etater sender inn sine
190 journaloppføringer til OEP. OEP inneholder en liste med sist
191 innrapporteringsdato for alle som sender til OEP, og ved å se når og
192 hvor ofte det blir sendt inn fra etatene kan
193 &lt;a href=&quot;https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=htmltable&amp;name=postliste-oep-deliverydates&amp;query=select%20agency%2C%0A(julianday(datetime(&#39;now&#39;))%20-%20%0A%20julianday(min(%60deliverydate%60)))%2Fcount(*)%20as%20dayfreq%2C%0A%20count(*)%0Afrom%20%60swdata%60%20group%20by%20agency%20order%20by%20dayfreq%20desc&quot;&gt;frekvensen
194 beregnes&lt;/a&gt;. Her er bunnlista, dvs. de som leverer mer enn hver 10
195 dag beregnet fra
196 &lt;a href=&quot;https://scraperwiki.com/scrapers/postliste-oep-deliverydates/&quot;&gt;en
197 Scraperwiki-database&lt;/a&gt;:&lt;/p&gt;
198
199 &lt;p&gt;&lt;table border=&quot;1&quot;&gt;
200
201 &lt;tr&gt; &lt;th&gt;Etat&lt;/th&gt; &lt;th&gt;Frekvens&lt;/th&gt; &lt;th&gt;Leveringer&lt;/th&gt; &lt;/tr&gt;
202 &lt;tr&gt; &lt;td&gt;Norges geologiske undersøkelse&lt;/td&gt; &lt;td&gt;83.7527546296&lt;/td&gt; &lt;td&gt;1&lt;/td&gt; &lt;/tr&gt;
203 &lt;tr&gt; &lt;td&gt;Medietilsynet&lt;/td&gt; &lt;td&gt;33.7527546296&lt;/td&gt; &lt;td&gt;1&lt;/td&gt; &lt;/tr&gt;
204 &lt;tr&gt; &lt;td&gt;Departementenes servicesenter&lt;/td&gt; &lt;td&gt;23.8763773148&lt;/td&gt; &lt;td&gt;2&lt;/td&gt; &lt;/tr&gt;
205 &lt;tr&gt; &lt;td&gt;Kunnskapsdepartementet&lt;/td&gt; &lt;td&gt;15.8763773148&lt;/td&gt; &lt;td&gt;2&lt;/td&gt; &lt;/tr&gt;
206 &lt;tr&gt; &lt;td&gt;Kompetansesenter for distriktsutvikling&lt;/td&gt; &lt;td&gt;15.3763773148&lt;/td&gt; &lt;td&gt;2&lt;/td&gt; &lt;/tr&gt;
207 &lt;tr&gt; &lt;td&gt;Toll- og avgiftsdirektoratet&lt;/td&gt; &lt;td&gt;15.3763773148&lt;/td&gt; &lt;td&gt;2&lt;/td&gt; &lt;/tr&gt;
208 &lt;tr&gt; &lt;td&gt;Fredskorpset&lt;/td&gt; &lt;td&gt;12.5842515432&lt;/td&gt; &lt;td&gt;3&lt;/td&gt; &lt;/tr&gt;
209 &lt;tr&gt; &lt;td&gt;Statens legemiddelverk&lt;/td&gt; &lt;td&gt;12.1881886574&lt;/td&gt; &lt;td&gt;4&lt;/td&gt; &lt;/tr&gt;
210 &lt;tr&gt; &lt;td&gt;Utlendingsnemnda&lt;/td&gt; &lt;td&gt;11.5842515432&lt;/td&gt; &lt;td&gt;3&lt;/td&gt; &lt;/tr&gt;
211 &lt;tr&gt; &lt;td&gt;Politidirektoratet&lt;/td&gt; &lt;td&gt;10.9175848765&lt;/td&gt; &lt;td&gt;3&lt;/td&gt; &lt;/tr&gt;
212 &lt;tr&gt; &lt;td&gt;Skattedirektoratet&lt;/td&gt; &lt;td&gt;10.9175848765&lt;/td&gt; &lt;td&gt;3&lt;/td&gt; &lt;/tr&gt;
213 &lt;tr&gt; &lt;td&gt;Statens innkrevingssentral&lt;/td&gt; &lt;td&gt;10.5842515432&lt;/td&gt; &lt;td&gt;3&lt;/td&gt; &lt;/tr&gt;
214 &lt;tr&gt; &lt;td&gt;Barne-, ungdoms- og familiedirektoratet&lt;/td&gt; &lt;td&gt;10.2509182099&lt;/td&gt; &lt;td&gt;3&lt;/td&gt; &lt;/tr&gt;
215 &lt;tr&gt; &lt;td&gt;Kunst i offentlige rom&lt;/td&gt; &lt;td&gt;10.2509182099&lt;/td&gt; &lt;td&gt;3&lt;/td&gt; &lt;/tr&gt;
216
217 &lt;/table&gt;&lt;/p&gt;
218
219 &lt;p&gt;En kan beregne lignende frekvenser ved å sammenligne
220 journalføringsdato med publiseringsdato for hver enkelt oppføring i
221 OEP, men den lenken legger jeg ikke ved her for å unngå at
222 søkemotorroboter begynner å overbelaste Scraperwiki-databasen.&lt;/p&gt;
223
224 &lt;p&gt;Jeg har spurt Norges geologiske undersøkelse om hvorfor de leverer
225 så sjelden, og det kommer av at de har problemer etter oppgradering av
226 arkivsystemet sitt og jobber med å fikse det slik at de kan gå tilbake
227 til å levere hver uke. Har ikke undersøkt noen av de andre.&lt;/p&gt;
228 </description>
229 </item>
230
231 <item>
232 <title>TV with face recognition, for improved viewer experience</title>
233 <link>http://people.skolelinux.org/pere/blog/TV_with_face_recognition__for_improved_viewer_experience.html</link>
234 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/TV_with_face_recognition__for_improved_viewer_experience.html</guid>
235 <pubDate>Sat, 9 Jun 2012 22:00:00 +0200</pubDate>
236 <description>&lt;p&gt;Slashdot got a story about Intel planning a
237 &lt;a href=&quot;http://entertainment.slashdot.org/story/12/06/09/0012247/intel-to-launch-tv-service-with-facial-recognition-by-end-of-the-year&quot;&gt;TV
238 with face recognition&lt;/a&gt; to recognise the viewer, and it occurred to
239 me that it would be more interesting to turn it around, and do face
240 recognition on the TV image itself. It could let the viewer know who
241 is present on the screen, and perhaps look up their credibility,
242 company affiliation, previous appearances etc for the viewer to better
243 evaluate what is being said and done. That would be a feature I would
244 be willing to pay for.&lt;/p&gt;
245
246 &lt;p&gt;I would not be willing to pay for a TV that point a camera on my
247 household, like the big brother feature apparently proposed by Intel.
248 It is the telescreen idea fetched straight out of the book
249 &lt;a href=&quot;http://gutenberg.net.au/ebooks01/0100021.txt&quot;&gt;1984 by George
250 Orwell&lt;/a&gt;.&lt;/p&gt;
251 </description>
252 </item>
253
254 <item>
255 <title>Web service to look up HP and Dell computer hardware support status</title>
256 <link>http://people.skolelinux.org/pere/blog/Web_service_to_look_up_HP_and_Dell_computer_hardware_support_status.html</link>
257 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Web_service_to_look_up_HP_and_Dell_computer_hardware_support_status.html</guid>
258 <pubDate>Wed, 6 Jun 2012 23:15:00 +0200</pubDate>
259 <description>&lt;p&gt;A few days ago
260 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/SOAP_based_webservice_from_Dell_to_check_server_support_status.html&quot;&gt;I
261 reported how to get&lt;/a&gt; the support status out of Dell using an
262 unofficial and undocumented SOAP API, which I since have found out was
263 &lt;a href=&quot;http://lists.us.dell.com/pipermail/linux-poweredge/2012-February/045959.html&quot;&gt;discovered
264 by Daniel De Marco in february&lt;/a&gt;. Combined with my web scraping
265 code for HP, Dell and IBM
266 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Checking_server_hardware_support_status_for_Dell__HP_and_IBM_servers.html&quot;&gt;from
267 2009&lt;/a&gt;, I got inspired and wrote
268 &lt;a href=&quot;https://views.scraperwiki.com/run/computer-hardware-support-status/&quot;&gt;a
269 web service&lt;/a&gt; based on Scraperwiki to make it easy to look up the
270 support status and get a machine readable result back.&lt;/p&gt;
271
272 &lt;p&gt;This is what it look like at the moment when asking for the JSON
273 output:
274
275 &lt;blockquote&gt;&lt;pre&gt;
276 % GET &lt;a href=&quot;https://views.scraperwiki.com/run/computer-hardware-support-status/?format=json&amp;vendor=Dell&amp;servicetag=2v1xwn1&quot;&gt;https://views.scraperwiki.com/run/computer-hardware-support-status/?format=json&amp;vendor=Dell&amp;servicetag=2v1xwn1&lt;/a&gt;
277 supportstatus({&quot;servicetag&quot;: &quot;2v1xwn1&quot;, &quot;warrantyend&quot;: &quot;2013-11-24&quot;, &quot;shipped&quot;: &quot;2010-11-24&quot;, &quot;scrapestamputc&quot;: &quot;2012-06-06T20:26:56.965847&quot;, &quot;scrapedurl&quot;: &quot;http://143.166.84.118/services/assetservice.asmx?WSDL&quot;, &quot;vendor&quot;: &quot;Dell&quot;, &quot;productid&quot;: &quot;&quot;})
278 %
279 &lt;/pre&gt;&lt;/blockquote&gt;
280
281 &lt;p&gt;It currently support Dell and HP, and I am hoping for help to add
282 support for other vendors. The python source is available on
283 Scraperwiki and I welcome help with adding more features.&lt;/p&gt;
284 </description>
285 </item>
286
287 <item>
288 <title>Kommentar til artikkel i Adresseavisa som omtaler FiksGataMi</title>
289 <link>http://people.skolelinux.org/pere/blog/Kommentar_til_artikkel_i_Adresseavisa_som_omtaler_FiksGataMi.html</link>
290 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kommentar_til_artikkel_i_Adresseavisa_som_omtaler_FiksGataMi.html</guid>
291 <pubDate>Sat, 2 Jun 2012 19:30:00 +0200</pubDate>
292 <description>&lt;p&gt;Jeg oppdaget nylig en
293 &lt;a href=&quot;http://www.adressa.no/nyheter/trondheim/article1831198.ece&quot;&gt;artikkel
294 i Adresseavisa&lt;/a&gt; i Trondheim som nevner FiksGataMi, og der Trondheim
295 kommune ser ut til å fortelle at de ikke følger forvaltningslovens
296 krav ved mottak av meldinger sendt inn via FiksGataMi. La derfor
297 nettopp inn denne kommentaren til artikkelen:&lt;p&gt;
298
299 &lt;p&gt;&lt;blockquote&gt;
300
301 &lt;p&gt;Her er en liten faktaoppdatering om FiksGataMi-tjenesten, da noen
302 ser ut til å ha misforstått hvordan den fungerer.&lt;/p&gt;
303
304 &lt;p&gt;FiksGataMi er et privat initiativ opprettet og drevet av
305 medlemsforeningen NUUG. FiksGataMi tar imot meldinger om feil i
306 offentlig infrastruktur, og sender meldingen skriftlig videre på vegne
307 av innmelder til aktuell aktør i det offentlige, det være seg kommune,
308 fylke eller vegvesenregion. Offentlig etat blir valgt ut fra
309 geografisk plassering og kategori valgt av innsender. Offentlige
310 etater er i følge forvaltningsloven pliktig å følge opp og besvare
311 skriftlige henvendelser, og hvis noen av mottakerne ikke gjør dette
312 kan en klage på lovbrudd i det offentlige. FiksGataMi fungerer dermed
313 som en slags epostklient for innbyggerne der kopi av innsendte
314 meldinger gjøres tilgjengelig og knyttes til kartplassering for enkel
315 gjenfinning. Å sende inn nye problemrapporter via FiksGataMi er
316 dermed ikke avhengig av at kommunen aktivt må følge med på meldinger
317 hos FiksGataMi, da de får dem tilsendt på sine offisielle
318 epostmottakspunkter. Hvorvidt noe blir fikset og om innbyggerne er
319 opp til mottaker av meldingene. For Trondheim kommune er
320 mottaksadressen bydrift.vegdrift@trondheim.kommune.no, en adresse jeg
321 inntil jeg leste denne artikkelen trodde ble håndtert i henhold til
322 forvaltningslovens krav.&lt;/p&gt;
323
324 &lt;p&gt;Kan ellers fortelle at 57 kommuner lenker til FiksGataMi fra sine
325 nettsider, og at 37 % (4182 av 11266 ) av problemrapportene sendt inn
326 via FiksGataMi er markert som løst i løsningen. Trondheim kommune har
327 fått tilbud om å få rapportene levert på datamaskinlesbart format i
328 stedet for epost, men har ikke takket ja så langt.&lt;/p&gt;
329
330 &lt;p&gt;Vennlig hilsen Petter Reinholdtsen, en av NUUG-folkene bak FiksGataMi.no&lt;/p&gt;
331
332 &lt;/blockquote&gt;&lt;/p&gt;
333
334 &lt;p&gt;Det høres for meg ut som om innbyggerne i Trondheim burde klage på
335 kommunens potensielle lovbrudd.&lt;/p&gt;
336 </description>
337 </item>
338
339 <item>
340 <title>Debian Edu interview: Mike Gabriel</title>
341 <link>http://people.skolelinux.org/pere/blog/Debian_Edu_interview__Mike_Gabriel.html</link>
342 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Edu_interview__Mike_Gabriel.html</guid>
343 <pubDate>Sat, 2 Jun 2012 15:00:00 +0200</pubDate>
344 <description>&lt;p&gt;Back in 2010, Mike Gabriel showed up on the
345 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu and Skolelinux&lt;/a&gt;
346 mailing list. He quickly proved to be a valuable developer, and
347 thanks to his tireless effort we now have Kerberos integrated into the
348 &lt;a href=&quot;http://www.debian.org/News/2012/20120311.html&quot;&gt;Debian Edu
349 Squeeze&lt;/a&gt; version.&lt;/p&gt;
350
351 &lt;p&gt;&lt;strong&gt;Who are you, and how do you spend your days?&lt;/strong&gt;&lt;/p&gt;
352
353 &lt;p&gt;My name is Mike Gabriel, I am 38 years old and live near Kiel,
354 Schleswig-Holstein, Germany. I live together with a wonderful partner
355 (Angela Fuß) and two own children and two bonus children (contributed
356 by Angela).&lt;/p&gt;
357
358 &lt;p&gt;During the day I am part-time employed as a system administrator
359 and part-time working as an IT consultant. The consultancy work
360 touches free software topics wherever and whenever possible. During
361 the nights I am a free software developer. In the gaps I also train in
362 becoming an osteopath.&lt;/p&gt;
363
364 &lt;p&gt;Starting in 2010 we (Andreas Buchholz, Angela Fuß, Mike Gabriel)
365 have set up a free software project in the area of Kiel that aims at
366 introducing free software into schools. The project&#39;s name is
367 &quot;IT-Zukunft Schule&quot; (IT future for schools). The project links IT
368 skills with communication skills.&lt;/p&gt;
369
370 &lt;p&gt;&lt;strong&gt;How did you get in contact with the Skolelinux/Debian Edu
371 project?&lt;/strong&gt;&lt;/p&gt;
372
373 &lt;p&gt;While preparing our own customised Linux distribution for
374 &quot;IT-Zukunft Schule&quot; we were repeatedly asked if we really wanted to
375 reinvent the wheel. What schools really need is already available,
376 people said. From this impulse we started evaluating other Linux
377 distributions that target being used for school networks.&lt;/p&gt;
378
379 &lt;p&gt;At the end we short-listed two approaches and compared them: a
380 commercial Linux distribution developed by a company in Bremen,
381 Germany, and Skolelinux / Debian Edu. Between 12/2010 and 03/2011 we
382 went to several events and met people being responsible for marketing
383 and development of either of the distributions. Skolelinux / Debian
384 Edu was by far much more convincing compared to the other product that
385 got short-listed beforehand--across the full spectrum. What was most
386 attractive for me personally: the perspective of collaboration within
387 the developmental branch of the Debian Edu project itself.&lt;/p&gt;
388
389 &lt;p&gt;In parallel with this, we talked to many local and not-so-local
390 people. People teaching at schools, headmasters, politicians, data
391 protection experts, other IT professionals.&lt;/p&gt;
392
393 &lt;p&gt;We came to two conclusions:&lt;/p&gt;
394
395 &lt;p&gt;First, a technical conclusion: What schools need is available in
396 bits and pieces here and there, and none of the solutions really fit
397 by 100%. Any school we have seen has a very individual IT setup
398 whereas most of each school&#39;s requirements could mapped by a standard
399 IT solution. The requirement to this IT solution is flexibility and
400 customisability, so that individual adaptations here and there are
401 possible. In terms of re-distributing and rolling out such a
402 standardised IT system for schools (a system that is still to some
403 degree customisable) there is still a lot of work to do here
404 locally. Debian Edu / Skolelinux has been our choice as the starting
405 point.&lt;/p&gt;
406
407 &lt;p&gt;Second, a holistic conclusion: What schools need does not exist at
408 all (or we missed it so far). There are several technical solutions
409 for handling IT at schools that tend to make a good impression. What
410 has been missing completely here in Germany, though, is the enrolment
411 of people into using IT and teaching with IT. &quot;IT-Zukunft Schule&quot;
412 tries to provide an approach for this.&lt;/p&gt;
413
414 &lt;p&gt;Only some schools have some sort of a media concept which explains,
415 defines and gives guidance on how to use IT in class. Most schools in
416 Northern Germany do not have an IT service provider, the school&#39;s IT
417 equipment is managed by one or (if the school is lucky) two (admin)
418 teachers, most of the workload these admin teachers get done in there
419 spare time.&lt;/p&gt;
420
421 &lt;p&gt;We were surprised that only a very few admin teachers were
422 networked with colleagues from other schools. Basically, every school
423 here around has its individual approach of providing IT equipment to
424 teachers and students and the exchange of ideas has been quasi
425 non-existent until 2010/2011.&lt;/p&gt;
426
427 &lt;p&gt;Quite some (non-admin) teachers try to avoid using IT technology in
428 class as a learning medium completely. Several reasons for this
429 avoidance do exist.&lt;/p&gt;
430
431 &lt;p&gt;We discovered that no-one has ever taken a closer look at this
432 social part of IT management in schools, so far. On our quest journey
433 for a technical IT solution for schools, we discussed this issue with
434 several teachers, headmasters, politicians, other IT professionals and
435 they all confirmed: a holistic approach of considering IT management
436 at schools, an approach that includes the people in place, will be new
437 and probably a gain for all.&lt;/p&gt;
438
439 &lt;p&gt;&lt;strong&gt;What do you see as the advantages of Skolelinux/Debian
440 Edu?&lt;/strong&gt;&lt;/p&gt;
441
442 &lt;p&gt;There is a list of advantages: international context, openness to
443 any kind of contributions, do-ocracy policy, the closeness to Debian,
444 the different installation scenarios possible (from stand-alone
445 workstation to complex multi-server sites), the transparency within
446 project communication, honest communication within the group of
447 developers, etc.&lt;/p&gt;
448
449 &lt;p&gt;&lt;strong&gt;What do you see as the disadvantages of Skolelinux/Debian
450 Edu?&lt;/strong&gt;&lt;/p&gt;
451
452 &lt;p&gt;Every coin has two sides:&lt;/p&gt;
453
454 &lt;p&gt;Technically: &lt;a href=&quot;http://bugs.debian.org/311188&quot;&gt;BTS issue
455 #311188&lt;/a&gt;, tricky upgradability of a Debian Edu main server, network
456 client installations on top of a plain vanilla Debian installation
457 should become possible sometime in the near future, one could think
458 about splitting the very complex package debian-edu-config into
459 several portions (to make it easier for new developers to
460 contribute).&lt;/p&gt;
461
462 &lt;p&gt;Another issue I see is that we (as Debian Edu developers) should
463 find out more about the network of people who do the marketing for
464 Debian Edu / Skolelinux. There is a very active group in Germany
465 promoting Skolelinux on the bigger Linux Days within Germany. Are
466 there other groups like that in other countries? How can we bring
467 these marketing people together (marketing group A with group B and
468 all of them with the group of Debian Edu developers)? During the last
469 meeting of the German Skolelinux group, I got the impression of people
470 there being rather disconnected from the development department of
471 Debian Edu / Skolelinux.&lt;/p&gt;
472
473 &lt;p&gt;&lt;strong&gt;Which free software do you use daily?&lt;/strong&gt;&lt;/p&gt;
474
475 &lt;p&gt;For my daily business, I do not use commercial software at all.&lt;/p&gt;
476
477 &lt;p&gt;For normal stuff I use Iceweasel/Firefox, Libreoffice.org. For
478 serious text writing I prefer LaTeX. I use gimp, inkscape, scribus for
479 more artistic tasks. I run virtual machines in KVM and Virtualbox.&lt;/p&gt;
480
481 &lt;p&gt;I am one of the upstream developers of X2Go. In 2010 I started the
482 development of a Python based X2Go Client, called PyHoca-GUI.
483 PyHoca-GUI has brought forth a Python X2Go Client API that currently
484 is being integrated in Ubuntu&#39;s software center.&lt;/p&gt;
485
486 &lt;p&gt;For communications I have my own Kolab server running using Horde
487 as web-based groupware client. For IRC I love to use irssi, for Jabber
488 I have several clients that I use, mostly pidgin, though. I am also
489 the Debian maintainer of Coccinella, a Jabber-based interactive
490 whiteboard.&lt;/p&gt;
491
492 &lt;p&gt;My favourite terminal emulator is KDE&#39;s Yakuake.&lt;/p&gt;
493
494 &lt;p&gt;&lt;strong&gt;Which strategy do you believe is the right one to use to
495 get schools to use free software?&lt;/strong&gt;&lt;/p&gt;
496
497 &lt;p&gt;Communicate, communicate, communicate. Enrol people, enrol people,
498 enrol people.&lt;/p&gt;
499 </description>
500 </item>
501
502 <item>
503 <title>SOAP based webservice from Dell to check server support status</title>
504 <link>http://people.skolelinux.org/pere/blog/SOAP_based_webservice_from_Dell_to_check_server_support_status.html</link>
505 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/SOAP_based_webservice_from_Dell_to_check_server_support_status.html</guid>
506 <pubDate>Fri, 1 Jun 2012 15:20:00 +0200</pubDate>
507 <description>&lt;p&gt;A few years ago I wrote
508 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Checking_server_hardware_support_status_for_Dell__HP_and_IBM_servers.html&quot;&gt;how
509 to extract support status&lt;/a&gt; for your Dell and HP servers. Recently
510 I have learned from colleges here at the
511 &lt;a href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; that Dell have
512 made this even easier, by providing a SOAP based web service. Given
513 the service tag, one can now query the Dell servers and get machine
514 readable information about the support status. This perl code
515 demonstrate how to do it:&lt;/p&gt;
516
517 &lt;p&gt;&lt;pre&gt;
518 use strict;
519 use warnings;
520 use SOAP::Lite;
521 use Data::Dumper;
522 my $GUID = &#39;11111111-1111-1111-1111-111111111111&#39;;
523 my $App = &#39;test&#39;;
524 my $servicetag = $ARGV[0] or die &quot;Please supply a servicetag. $!\n&quot;;
525 my ($deal, $latest, @dates);
526 my $s = SOAP::Lite
527 -&gt; uri(&#39;http://support.dell.com/WebServices/&#39;)
528 -&gt; on_action( sub { join &#39;&#39;, @_ } )
529 -&gt; proxy(&#39;http://xserv.dell.com/services/assetservice.asmx&#39;)
530 ;
531 my $a = $s-&gt;GetAssetInformation(
532 SOAP::Data-&gt;name(&#39;guid&#39;)-&gt;value($GUID)-&gt;type(&#39;&#39;),
533 SOAP::Data-&gt;name(&#39;applicationName&#39;)-&gt;value($App)-&gt;type(&#39;&#39;),
534 SOAP::Data-&gt;name(&#39;serviceTags&#39;)-&gt;value($servicetag)-&gt;type(&#39;&#39;),
535 );
536 print Dumper($a -&gt; result) ;
537 &lt;/pre&gt;&lt;/p&gt;
538
539 &lt;p&gt;The output can look like this:&lt;/p&gt;
540
541 &lt;p&gt;&lt;pre&gt;
542 $VAR1 = {
543 &#39;Asset&#39; =&gt; {
544 &#39;Entitlements&#39; =&gt; {
545 &#39;EntitlementData&#39; =&gt; [
546 {
547 &#39;EntitlementType&#39; =&gt; &#39;Expired&#39;,
548 &#39;EndDate&#39; =&gt; &#39;2009-07-29T00:00:00&#39;,
549 &#39;Provider&#39; =&gt; &#39;&#39;,
550 &#39;StartDate&#39; =&gt; &#39;2006-07-29T00:00:00&#39;,
551 &#39;DaysLeft&#39; =&gt; &#39;0&#39;
552 },
553 {
554 &#39;EntitlementType&#39; =&gt; &#39;Expired&#39;,
555 &#39;EndDate&#39; =&gt; &#39;2009-07-29T00:00:00&#39;,
556 &#39;Provider&#39; =&gt; &#39;&#39;,
557 &#39;StartDate&#39; =&gt; &#39;2006-07-29T00:00:00&#39;,
558 &#39;DaysLeft&#39; =&gt; &#39;0&#39;
559 },
560 {
561 &#39;EntitlementType&#39; =&gt; &#39;Expired&#39;,
562 &#39;EndDate&#39; =&gt; &#39;2007-07-29T00:00:00&#39;,
563 &#39;Provider&#39; =&gt; &#39;&#39;,
564 &#39;StartDate&#39; =&gt; &#39;2006-07-29T00:00:00&#39;,
565 &#39;DaysLeft&#39; =&gt; &#39;0&#39;
566 }
567 ]
568 },
569 &#39;AssetHeaderData&#39; =&gt; {
570 &#39;SystemModel&#39; =&gt; &#39;GX620&#39;,
571 &#39;ServiceTag&#39; =&gt; &#39;8DSGD2J&#39;,
572 &#39;SystemShipDate&#39; =&gt; &#39;2006-07-29T19:00:00-05:00&#39;,
573 &#39;Buid&#39; =&gt; &#39;2323&#39;,
574 &#39;Region&#39; =&gt; &#39;Europe&#39;,
575 &#39;SystemID&#39; =&gt; &#39;PLX_GX620&#39;,
576 &#39;SystemType&#39; =&gt; &#39;OptiPlex&#39;
577 }
578 }
579 };
580 &lt;/pre&gt;&lt;/p&gt;
581
582 &lt;p&gt;I have not been able to find any documentation from Dell about this
583 service outside the
584 &lt;a href=&quot;http://xserv.dell.com/services/assetservice.asmx?op=GetAssetInformation&quot;&gt;inline
585 documentation&lt;/a&gt;, and according to
586 &lt;a href=&quot;http://iboyd.net/index.php/2012/02/14/updated-dell-warranty-information-script/&quot;&gt;one
587 comment&lt;/a&gt; it can have stability issues, but it is a lot better than
588 scraping HTML pages. :)&lt;/p&gt;
589
590 &lt;p&gt;Wonder if HP and other server vendors have a similar service. If
591 you know of one, drop me an email. :)&lt;/p&gt;
592 </description>
593 </item>
594
595 <item>
596 <title>Veileder fra DIFI om publisering av offentlige data</title>
597 <link>http://people.skolelinux.org/pere/blog/Veileder_fra_DIFI_om_publisering_av_offentlige_data.html</link>
598 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Veileder_fra_DIFI_om_publisering_av_offentlige_data.html</guid>
599 <pubDate>Fri, 1 Jun 2012 10:40:00 +0200</pubDate>
600 <description>&lt;p&gt;På onsdag rakk jeg såvidt innom
601 &lt;a href=&quot;http://www.meetup.com/osloopendata/&quot;&gt;Oslo Open Data Forums&lt;/a&gt;
602 møte, og fikk lagt hendene mine på DIFIs helt nye veileder
603 &quot;&lt;a href=&quot;http://veileder.data.norge.no/&quot;&gt;Åpne data. Del og skap
604 verdier. Veileder i tilgjengeliggjøring av offentlig data&lt;/a&gt;&quot; (også
605 &lt;a href=&quot;http://www.difi.no/filearchive/veileder-i-tilgjengeliggjoring-av-offentlig-data-web.pdf&quot;&gt;tilgjengelig
606 som PDF&lt;/a&gt; fra DIFI).&lt;/p&gt;
607
608 &lt;p&gt;Veilederen er veldig bra, og nevner viktige problemstillinger og
609 skisserer f.eks. både verdiskapningspotensialet og formatmulighetene
610 som en bør ha i bakhodet når en publiserer offentlig informasjon på
611 maskinlesbart format. Kildekoden til veilederen er
612 &lt;a href=&quot;https://github.com/difi/veileder-opnedata&quot;&gt;tilgjengelig via
613 github&lt;/a&gt;, og en kan rapportere tilbakemeldinger og forslag til
614 forbedringer der (eller via epost og twitter for de som ønsker
615 det).&lt;/p&gt;
616
617 &lt;p&gt;Det eneste jeg virkelig savnet i veilederen var omtale av
618 &lt;a href=&quot;http://www.w3.org/DesignIssues/LinkedData.html&quot;&gt;w3cs
619 stjerneklassifisering&lt;/a&gt; av åpne datakilder, som jeg tror ville være
620 nyttige mentale knagger for de som vurderer å publisere sin
621 informasjon på som åpne data. Jeg har
622 &lt;a href=&quot;https://github.com/difi/veileder-opnedata/issues/1&quot;&gt;rapportert
623 en github-bug&lt;/a&gt; om dette, så får vi se hvordan den blir behandlet.&lt;/p&gt;
624
625 &lt;p&gt;Det slo meg at det var veldig lite konkret i veilederen om valg av
626 bruksvilkår ved publisering (aka lisens), men jeg er ikke sikker på om
627 det hører hjemme der, da det er et vanskelig tema som kanskje heller
628 hører hjemme i sin egen veileder. Uansett, anbefaler alle å ta en
629 titt på veilederen og sikre at alle offentlige etater en har kontakt
630 med får en kopi.&lt;/p&gt;
631 </description>
632 </item>
633
634 <item>
635 <title>First monitor calibration using ColorHug</title>
636 <link>http://people.skolelinux.org/pere/blog/First_monitor_calibration_using_ColorHug.html</link>
637 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_monitor_calibration_using_ColorHug.html</guid>
638 <pubDate>Thu, 31 May 2012 22:10:00 +0200</pubDate>
639 <description>&lt;p&gt;A few days ago my color calibration gadget
640 &lt;a href=&quot;http://www.hughski.com/index.html&quot;&gt;ColorHug&lt;/a&gt; arrived in the
641 mail, and I&#39;ve had a few days to test it. As all my machines are
642 running Debian Squeeze, where
643 &lt;a href=&quot;http://packages.qa.debian.org/c/colorhug-client.html&quot;&gt;the
644 calibration software&lt;/a&gt; is missing (it is present in Wheezy and Sid),
645 I ran the calibration using the Fedora based live CD. This worked
646 just fine. So far I have only done the quick calibration. It was
647 slow enough for me, so I will leave the more extensive calibration for
648 another day.&lt;/p&gt;
649
650 &lt;p&gt;After calibration, I get a
651 &lt;a href=&quot;http://en.wikipedia.org/wiki/ICC_profile&quot;&gt;ICC color
652 profile&lt;/a&gt; file that can be passed to programs understanding such
653 tools. KDE do not seem to understand it out of the box, so I searched
654 for command line tools to use to load the color profile into X.
655 xcalib was the first one I found, and it seem to work fine for single
656 monitor setups. But for my video player, a laptop with a flat screen
657 attached, it was unable to load the color profile for the correct
658 monitor. After searching a bit, I
659 &lt;a href=&quot;http://ubuntuforums.org/showthread.php?t=1347896&quot;&gt;discovered&lt;/a&gt;
660 that the dispwin tool from the argyll package would do what I wanted,
661 and a simple&lt;/p&gt;
662
663 &lt;p&gt;&lt;pre&gt;
664 dispwin -d 1 profile.icc
665 &lt;/pre&gt;&lt;/p&gt;
666
667 &lt;p&gt;later I had the color profile loaded for the correct monitor. The
668 result was a bit more pink than I expected. I guess I picked the
669 wrong monitor type for the &quot;led&quot; monitor I got, but the result is good
670 enough for now.&lt;/p&gt;
671 </description>
672 </item>
673
674 <item>
675 <title>Hvor samles det inn bensinpriser for Norge?</title>
676 <link>http://people.skolelinux.org/pere/blog/Hvor_samles_det_inn_bensinpriser_for_Norge_.html</link>
677 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Hvor_samles_det_inn_bensinpriser_for_Norge_.html</guid>
678 <pubDate>Thu, 31 May 2012 13:30:00 +0200</pubDate>
679 <description>&lt;p&gt;Det finnes i følge de som har talt ca. 1600 bensinstasjoner i
680 Norge. Daglig innsamling av informasjon fra alle disse vil antagelig
681 kreve noen tusen frivillige. Dugnadsbasert innsamling av bensinpriser
682 for å gjøre det enklere å sammenligne priser og dermed bedre
683 konkurransen i bensinmarkedet er en idé som mange har gjennomført de
684 siste årene. Her er et forsøk på en oversikt over de som finnes i
685 dag.&lt;/p&gt;
686
687 &lt;dl&gt;
688
689 &lt;dt&gt;Dinside.no nettside&lt;/dt&gt;
690
691 &lt;dd&gt;Nettavisen dinside startet for noen år siden en dugnad for å
692 &lt;a href=&quot;http://www.dinside.no/1931/her-faar-du-billigst-bensin-diesel&quot;&gt;samle
693 inn drivstoffpriser&lt;/a&gt;. Tjenesten samler inn med et nettsideskjema
694 der en må registrere seg for å delta. En SMS-tjeneste har visst
695 eksistert tidligere, men er ute av drift 2012-05-31. Listen over
696 bensinstasjoner er kun tilgjengelig for registrerte brukere, og
697 mangler geografiske koordinater for fremvisning på kart. Listen over
698 innsamlede bensinpriser er tilgjengelig som nettside i litt over 24
699 timer etter registrering. Antall innsamlede priser pr. dag ligger i
700 området 10-35, og jeg har startet på
701 &lt;a href=&quot;https://scraperwiki.com/scrapers/dinside-bensinpriser/&quot;&gt;en
702 database over de publiserte prisene&lt;/a&gt; hos Scraperwiki.&lt;/dd&gt;
703
704 &lt;dt&gt;Bitfactorys mobilapp&lt;/dt&gt;
705
706 &lt;dd&gt;I fjor lanserte
707 &lt;a href=&quot;http://www.bitfactory.no/bensinpris.html&quot;&gt;selskapet Bitfactory
708 sin landsdekkende mobilapp&lt;/a&gt; (først for iphone, siden også for
709 Android) for å samle inn drivstoffpriser og gjøre det enkelt å finne
710 billigste stasjon i nærområdet ved hjelp av smarttelefon. Den
711 innsamlede informasjonen er ikke publisert på web, men dagens priser
712 kan hentes ut ved hjelp av et
713 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Litt_informasjon_om_Bitfactorys_Bensinpris_API.html&quot;&gt;web-API
714 som jeg har dokumentert med reversutvikling&lt;/a&gt;. Stasjonslisten
715 inneholder geografiske koordinater for fremvisning på kart. Antall
716 innsamlede priser pr. dag ser ut til å ligge rundt 200.&lt;/dd&gt;
717
718
719
720 &lt;dt&gt;NAF Bergens nettside og iphone-app&lt;/dt&gt;
721
722 &lt;dd&gt;I år lanserte NAF Bergen &lt;a href=&quot;http://www.drivstoffpriser.no/&quot;&gt;en
723 landsdekkende iphone-app&lt;/a&gt; koblet til NAF Bergens tjeneste for å
724 samle inn og varsle brukerne om bensinpriser. Nettstedet har
725 publisert listen over bensinstasjoner, men ikke en komplett oversikt
726 over innsamlede priser. De har interessant statistikk over
727 prisutviklingen som går tilbake til 2009.
728
729 &lt;dt&gt;bensinpris.net&lt;/dt&gt;
730
731 &lt;dd&gt;Nettside med prisinformasjon for Trondheimsområdet. Informasjonen
732 registreres via web og SMS, og krever ikke registrering. Nettsiden
733 viser de tre siste prisene registret for bensin og disel. Har liste
734 over kjente stasjoner tilgjengelig. Svært lite oppdatert for
735 tiden.&lt;/dd&gt;
736
737 &lt;/dl&gt;
738
739 &lt;p&gt;I tillegg er jeg kjent med drivstoffguiden.no som ser ut til å være
740 nedlagt, og at SSB som del av beregningen av konsumprisindeksen samler
741 inn driftstoffpriser hver måned og
742 &lt;a href=&quot;http://www.ssb.no/petroleumsalg/&quot;&gt;legger dem ut i
743 PDF-format&lt;/a&gt;.&lt;/p&gt;
744
745 &lt;p&gt;Det jeg ikke forstår er hvorfor det stadig opprettes nye nett- og
746 mobiltjenester for å samle inn bensinpriser, i stedet for å samarbeide
747 med de eksisterende løsninger for å gjøre de gode nok til nye
748 bruksområder. Jobben med å samle inn priser er formidabel, og hvis
749 målet er bedre konkurranse på bensinmarkedet ville jeg tro det beste
750 var om kundene samlet seg om _ett_ nettsted og samlet alle prisene
751 der, i stedet for å spre innsatsen på mange nettsteder. Jeg mistenker
752 årsaken ligger i at de aktørene som har satt opp tjenester så langt
753 ikke har lagt opp til deling og samarbeid på like vilkår med andre
754 aktører, og dermed gjort det vanskelig å legge til funksjonalitet som
755 presentasjon på kart, statistisk analyse eller kvalitetssikring av
756 bensinstasjonslisten og prisinformasjonen.&lt;/p&gt;
757
758 &lt;table&gt;
759
760 &lt;tr&gt;
761 &lt;th&gt;Tjeneste&lt;/th&gt;
762 &lt;th&gt;Offentlig stasjons-liste&lt;/th&gt;
763 &lt;th&gt;Publisert stasjons-geopunkt&lt;/th&gt;
764 &lt;th&gt;Publisert API for inn-legging&lt;/th&gt;
765 &lt;th&gt;Publisert API for ut-henting&lt;/th&gt;
766 &lt;th&gt;Publisert alle priser&lt;/th&gt;
767 &lt;th&gt;Publisert database&lt;/th&gt;
768 &lt;th&gt;Lands-dekkende&lt;/th&gt;
769 &lt;/tr&gt;
770
771 &lt;tr&gt;
772 &lt;td&gt;Dinside&lt;/td&gt;
773 &lt;td&gt;(ja)&lt;/td&gt;
774 &lt;td&gt;nei&lt;/td&gt;
775 &lt;td&gt;nei&lt;/td&gt;
776 &lt;td&gt;nei&lt;/td&gt;
777 &lt;td&gt;ja&lt;/td&gt;
778 &lt;td&gt;(ja)&lt;/td&gt;
779 &lt;td&gt;ja&lt;/td&gt;
780 &lt;/tr&gt;
781
782 &lt;tr&gt;
783 &lt;td&gt;Bitfactorys mobilapp&lt;/td&gt;
784 &lt;td&gt;nei&lt;/td&gt;
785 &lt;td&gt;ja&lt;/td&gt;
786 &lt;td&gt;(ja)&lt;/td&gt;
787 &lt;td&gt;(ja)&lt;/td&gt;
788 &lt;td&gt;nei&lt;/td&gt;
789 &lt;td&gt;nei&lt;/td&gt;
790 &lt;td&gt;ja&lt;/td&gt;
791 &lt;/tr&gt;
792
793 &lt;tr&gt;
794 &lt;td&gt;drivstoffpriser.no&lt;/td&gt;
795 &lt;td&gt;ja&lt;/td&gt;
796 &lt;td&gt;ja&lt;/td&gt;
797 &lt;td&gt;nei&lt;/td&gt;
798 &lt;td&gt;nei&lt;/td&gt;
799 &lt;td&gt;nei&lt;/td&gt;
800 &lt;td&gt;nei&lt;/td&gt;
801 &lt;td&gt;ja&lt;/td&gt;
802 &lt;/tr&gt;
803
804 &lt;tr&gt;
805 &lt;td&gt;bensinpris.net&lt;/td&gt;
806 &lt;td&gt;ja&lt;/td&gt;
807 &lt;td&gt;nei&lt;/td&gt;
808 &lt;td&gt;nei&lt;/td&gt;
809 &lt;td&gt;nei&lt;/td&gt;
810 &lt;td&gt;nei&lt;/td&gt;
811 &lt;td&gt;nei&lt;/td&gt;
812 &lt;td&gt;nei&lt;/td&gt;
813 &lt;/tr&gt;
814
815 &lt;/table&gt;
816
817 &lt;p&gt;Dinside mangler dugnadsbasert kvalitetssikring av stasjonslista,
818 georeferert informasjon og API for innlegging og uthenting av
819 informasjon. Bitfactory mangler publisering av all innsamlet
820 informasjon, dugnadsbasert kvalitetssikring av stasjonslista og
821 dokumentert API for innlegging og uthenting av informasjon. NAFs
822 løsning mangler publisering av all innsamlet informasjon og API for
823 innlegging og uthenting av informasjon.&lt;/p&gt;
824
825 &lt;p&gt;Jeg har nylig spurt folkene bak dinside.nos oversikt og
826 drivstoffpriser.no om de er villige til å gi ut sine innsamlede data
827 uten bruksbegresninger og tilby et dokumentert og publisert API for å
828 legge inn og hente ut informasjon. Så får vi se hva de sier.&lt;/p&gt;
829 </description>
830 </item>
831
832 </channel>
833 </rss>