{"id":1347,"date":"2005-12-10T17:49:36","date_gmt":"2005-12-10T15:49:36","guid":{"rendered":"http:\/\/vizZzion.org\/blog\/2005\/12\/ososs-symposium-and-spiffier-photomanagement\/"},"modified":"2005-12-10T17:49:36","modified_gmt":"2005-12-10T15:49:36","slug":"ososs-symposium-and-spiffier-photomanagement","status":"publish","type":"post","link":"https:\/\/vizZzion.org\/blog\/2005\/12\/ososs-symposium-and-spiffier-photomanagement\/","title":{"rendered":"OSOSS symposium and spiffier photomanagement."},"content":{"rendered":"

\n\t\tOn Thursday, I visited the OSOSS
\nsymposium Open Doen<\/em><\/a> in Nieuwegein in the Netherlands. It was targeted at
\n(semi-)governmental organisation, informing about deployment of Open Source and open standards. A
\ncouple of migration pilots were discussed, amongst others. What really stroke me was the way they
\nhandled those. Let’s say you have a Windows environment, servers running NT4 still, maybe already
\nWin2k, desktops mainly win2000, that means mail is done with Exchange, authentication via Active
\nDirectory. You want to use more Open Source software in your organisation. One of the approaches to
\nmigrating to an “Open Source desktop” had as a requirements “No changes to the backend, we’re doing
\nonly desktops”. This requirement is quite a strange one. The first thing you should do is migrating
\nyour email to Open Source technology, then deploying LDAP and switching all those funny backend
\nsolutions. Your users won’t really notice, and the switching of those services will have little
\naffect on the productivity of your organisation. In fact, it will probably be quite easy.
But
\nno, let’s try to use Open Source software but authenticate with AD, connect your email client to
\nExchange – causes you headache for sure. I was under the impression that those migration pilots are
\nnot quite whole-hearted, which is a pity, since evaluating the Open Source desktop is not something
\nyou will do every year. Once you get a bad impression (which is actually caused by protocols not
\nbeing open) OSS won’t get another chance for some years. If you do it, do it right at first.First convert your communication protocols to something open to create equal chances, then have a
\nlook at what does perform well and what doesn’t, then choose the best solution.\n\t<\/p>\n

\n\t\tHarvard’s Jeffrey A. Kaplan presented the “Roadmap for Open ICT ecosystems”<\/a> which
\nput the whole thing in a much broader context. A good read for decisionmakers.\n\t<\/p>\n

\n\t\tThird interesting thing is that Maturity Models seem to be gaining more supporters, the term
\ncould’ve been heard in about half of the presentations I attended. I’m interested in those maturity
\nmodels since I’m doing research on quality metrics for Open Source software (solutions).\n\t<\/p>\n

\n\t\tYesterday night, I found the time to finally fix a usability bug on my website, a far too
\nlong “photo” menu which just dropped out of the bottom of everybody’s browser window. Hint: Do not
\ncreate menu entries automatically. Well, now I have categories<\/a> of<\/a> photo galleries<\/a>, which should be reasonably easy to
\nhandle for the next time. Also my wallpaper section<\/a>
\nhas gotten a major cleanup, now listing wallpapers in a nicer way than just Apache’s standard
\ndirectory listing.\n\t<\/p>\n","protected":false},"excerpt":{"rendered":"

On Thursday, I visited the OSOSS symposium Open Doen in Nieuwegein in the Netherlands. It was targeted at (semi-)governmental organisation, informing about deployment of Open Source and open standards. A couple of migration pilots were discussed, amongst others. What really stroke me was the way they handled those. Let’s say you have a Windows environment,… Continue reading OSOSS symposium and spiffier photomanagement.<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-1347","post","type-post","status-publish","format-standard","hentry","category-kde"],"_links":{"self":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/1347","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/comments?post=1347"}],"version-history":[{"count":0,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/1347\/revisions"}],"wp:attachment":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/media?parent=1347"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/categories?post=1347"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/tags?post=1347"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}