« June 2006 | Main | August 2006 »

July 25, 2006

The special problems of Ukrainian open source

In Kiev today, and I spent an interesting hour with three of the leaders of UAFOSS (Ukrainian Free and Open Source Software). They're involved in the now-familiar struggle to acquaint people with open source software, to convince the government to adopt it (or at least consider it in what are widely thought to be corrupt tendering processes), to encourage use in schools, libraries, and businesses. What's slightly unusual, according to my companions this afternoon, is that there are still laws on the books in Ukraine, holdovers from the still-looming Soviet days, which render use and production of open source software illegal. Apparently, a software developer needs to be able to show that he has been paid for the production of software that he has developed, and a user needs to be able to display a license agreement from a vendor licensed by the state. This would mean that, technically speaking, downloading and installing Firefox or Open Office is a crime in Ukraine, and contributing to an international project would also be out of bounds. A note on accuracy: I've googled this up and down and can't come up with anything concrete because, I suspect, I don't read Ukrainian, but have been assured by numerous Ukrainian colleagues that this is indeed the case. UAFOSS dedicates a significant amount of effort to having this law changed, although the somewhat regular collapse of the Ukrainian government (and the fact that there has only been a caretaker government here since January) has slowed their lobbying efforts considerably.

So far as I can tell, this law is totally obscure and widely ignored. A Google search will turn up a lively open source community in Ukraine, and after narrating the above story today, the UAFOSS guys went on to talk about all the open source work they *are* doing in Kiev, including an exciting-sounding localization project that involves the Ukraine's national language office and an effort to set up a network of help-desk centers around the country. Still, I can certainly understand why UAFOSS are working to change the law. Unfortuantely, unenforced and outdated laws languishing on the books can come back to bite at a later date if they're not cleared off. Further, forcing a discussion on open source licensing could help to break open other discussions on intellectual property issues that still tie the hands of other industries in Ukraine.

July 24, 2006

Linux desktops and NGOs

A few weeks ago, my friend Ethan Zuckerman wrote a post on the difficulties of running a Linux desktop. Even the relative success of Ubuntu, the popular version of the Debian distribution professionalized into consumer-grade ware by Mark Shuttleworth's company Canonical hasn't got me convinced that a Linux desktop is for everyone, and Ethan outlined why very effectively.

Today, I flew to Kiev, Ukraine with a colleague of mine who is an unusual breed: a relative non-techie who is also a Linux desktop user (Suse) and a Linux enthusiast/defender. At least until, perhaps, this morning at 7:30 a.m., when we sat down next to each other at the airport in Budapest and simultaneously flipped open our matching IBM Thinkpads. Mine started up, caught the Ferihegy airport free wireless (Pannon, if you're looking) and downloaded my last dregs of email; his did something that, to me, looked like those bad command line moments in hacker movies where the untutored audience is supposed to easily get it that Something Has Gone Wrong. So, my colleague was without his computer all day as we sat through three hours in Munich and two plane rides. After a consultation with the Linux guru back at our office, the problem was potentially isolated (a problem with the encryption container that holds all his data); as we're visiting our colleagues here in Kiev tomorrow morning, we'll set up my colleague's computer with a static IP address tomorrow morning and Linux Guru from our office will tunnel in from Budapest and try to sort out the problem.

To my way of thinking, this is an interesting illustration of when, for non-techies, running a Linux desktop can work, and when it may not work so well. My colleague may be able to solve his problem because he:
1. Has a dedicated Linux guru in our office
2. Has a mobile phone on which he can call said guru when he's out of the office
3. Has an office to go to in a foreign country where he can set up a particular help desk situation on the fly
4. Has been patient enough and dedicated enough to his Linux experiment not to toss his laptop out the window and restart with a Windows machine when things go wrong.

This situation led to a dinner discussion tonight with an open source savvy Ukranian colleague: when is it appropriate to encourage non-profit organizations to use Linux machines? From one perspective, open source seems like a logical solution to the tech woes of many low-resource organizations struggling to survive, sometimes in very hostile political environments: an open source desktop means you're not using pirated software that could potentially give the authorities an excuse to close you down; if you're Tajik or Georgian or another non-Microsoft language, it might mean that you can use software in your own language, instead of in English or Russian; if you have some command-line confidence, you may be able to customize it in ways that make the software more useful to you than a Windows desktop would be. However, given the type of situation outlined above, I think it's difficult to suggest that for an individual organization without an easily accessible Linux-friendly tech support person, open source desktops would be the right choice (although I do think anyone can use the open source triple play of Open Office, Firefox, and Thunderbird with little trouble, if they are launched in the right direction).

What we concluded over a meal of Ukranian pickled vegetables, kvas, and stuffed cabbage was the utility of institutional structure in a Linux desktop deployment: universities, libraries, schools, and government offices all have the advantage of structure, usually some tech support, and better yet (at least in educational environments) a set of users who may also willingly become the techies needed to solve others problems. This is the kind of situation where I think it makes a lot of sense to deploy Linux desktops, and indeed, from Shuttleworth's TuxLabs to SchoolNet Namibia to the Deerleap Project in Georgia to the Armenian national library's experiments with open source, that model has started to bear real fruit; it's also started to acclimate real users to a new system without the same level of risk that they'll be alienated through frustration or poor support.

Update: we couldn't get a static IP address in our Kiev office, so Colleague is out of luck until we get back to Budapest on Friday.

July 08, 2006

Trust networks and squid-ink risotto

I'm about to leave for a week of vacation in Croatia's golden port city, Dubrovnik. Aside from admiring the beauty of the ancient walls and the blue, blue Adriatic, I also want to eat well -- squid ink risotto, fried calamari, clams in white wine and garlic...all of these top of the list of reasons to head down to seaside Croatia from landlocked Hungary. I've spent this morning scanning the web for restaurant recommendations in Dubrovnik, and I find myself stymied once again by the complications of sifting through online information.

Conventional wisdom tells me that I should be using my trusted online networks to find this information, and indeed, I have turned to the places I normally would for restaurant recommendations, that is, sites that I trust to give me some good reviews. I started with Saveur magazine's online archive, moved on to Chowhound, Gridskipper, and TimeOut. I checked Dubrovnik on Technorati to see if anyone had blogged about restaurants recently, and Dubrovnik/food/restaurants on Flickr to see if anyone had usefully tagged photos.

The result is not that great, an hour later, and has led me to consider (as I often do when I'm looking for travel information) what a hit or miss operation information searches and relying on trusted networks are when, in reality, you don't have a trusted network in place. Here's a quick run-down of what I found:

Saveur, my most exalted, trusted source, is not in any way a member of the read/write web. They publish a dead-tree magazine, and they put those articles online. That said, they are absolutely the best, and have never, every failed me in any of my travels from lobster pasta in Venice to mind-bendingly good tapas in Xerez, Andalusia. Unfortunately, they've never written on Dubrovnik. So cross that one off for this trip.

Chowhound, my next best source for recommendations, troubled me this time around. Chowhound is a site for people who consider themselves "foodies", and the "chowhounders" do their good work by sniffing out small, unknown restaurants. Their very useful discussion forum can sometimes yield epicurean gems. The problem with Chowhound is that it's largely a US-based site; their international discussions are not, in fact, very trustworthy. In a search for Dubrovnik, I found lots of discussion threads, but when I cross-referenced the recommendations on the discussion threads with a guidebook I have (the always-useful but not culinarily-minded Lonely Planet), I found almost 100 percent overlap. That is, the so-called chowhounds who were writing about Dubrovnik were not sniffing out new, unknown local joints, but were in fact commenting on the restaurants already in the guidebook that just about everyone who visits Crotia has in their backpack. There's certainly utility in that, but ... if the users on Chowhound are simply discussing what Lonely Planet has already recommended, I wouldn't rely on them as experts; it's not a trusted network after all. And indeed, there are no Croatians posting on Chowhound that I saw, which is really unfortunate. (The other kind of recommendation on Chowhound for Dubrovnik are the "I went to a great little restaurant down a back street near the port, but I can't remember the name" variety, which are just kind of irritating. Please, don't bother.)

On to Gridskipper, which does list Dubrovnik as one of its cities "on the grid"; however, the only restaurant recommended there is not qualified in any way -- the writer just says it's "one of the city's best". Well, maybe, but when I search online I don't find other information on it or recommendations for it. So that really wasn't so helpful, and I realize that when push comes to shove (am I going to get into a cab and cross the city to go to a specific restaurant) I don't really trust Gridskipper on restaurant issues -- or at least not on this one. Since there's no context for the recommendation, and I don't know who the writer is, I'm skeptical.

TimeOut is semi-useful, but they want us to buy the dead-tree copy so the information is light. I do trust TimeOut, but again -- not really the read/write web. I'm just going by their single writer's recommendations.

The noise on Technorati around Dubrovnik is too difficult to sift through -- lots of link factories or advertising come back, so I give up. Flickr yields, as usual, a wonderland of beautiful pictures of Croatian seafood when I do my search, but there's no associated information with any of the pictures (i.e., where did you eat that gorgeous shrimp?)

The moral of this story is that I've ended up a bit stymied. No online source that I really trust has led me to good restaurant options in Dubrovnik. I'm now planning to call up a friend who's a tour guide and was in Croatia with a group a few weeks back for her insights, and then go out and buy a copy of another friend's book on Croatia, Annabel Barber's Visible Cities Dubrovnik.

I think the reason I find this long tale interesting is because of, well, the theory of the internet's long tail that Wired's Chris Anderson and others have written extensively about over the past two years. The theory, which I largely agree with, is that web 2.0 allows for incredibly rich information geared to very niche markets or demographics (foodies traveling to Dubrovnik, i.e.); related thinking revolves around the idea that trusted communities will form around these niches, and that the read/write web allows everyone to join those communities as both a consumer and producer of information. That's great, again, I largely agree with that.

The problem I see is that some niches which are transitory, and some niches aren't. I am going to care for a long time about data security and human rights organizations, and it's worth it for me to build a community of trust around that issue. I only care this week about good restaurants in Dubrovnik, and it really not worth it for me to build or join a community of trust around that. Nevertheless, I want to be able to dip into online communities who do care about that issue when I need to know more about it -- and yet, I'm not really in a position to evaluate who is a trusted source in a specific network. How do I know that so-and-so poster on Chowhound is reliable? Why should I trust the person who recommended to Gridskipper that X restaurant in Dubrovnik is excellent? So, one of the downsides I see with the beauty of niche information is the inability of an individual to be involved in as many as they want to, or need to, be. I think that what comes out of this is more and more recommendation systems a la Slashdot or Digg that are geared in a very niche way. However, a lot of sites will need to be rebuilt to put those kinds of tools in place....so I still see a long haul ahead of us for making the read/write web truly useful. These kinds of experiences are a good reminder to me that, no matter how fast it seems like we're moving on communications technologies, we're still taking baby steps. And that's why I'm heading out now to buy Annabel's book to take with me this afternoon to Dubrovnik.

PS: If any of my five readers have a suggestion for where to eat in Dubrovnik, leave a comment!