I went to visit OggCamp10 venue The Black-e this afternoon with Dan and it’s really cool! It’s right in the centre of Liverpool and right next to the massive and brightly coloured Chinatown arch, the entrance to the oldest Chinatown in Europe. The Main Stage is a lovely big room on the upstairs, Stage 2 and 3 are in the basement, and the exhibition/chillout area is on the ground floor by the entrance. We’re planning to have conference wifi too, supplied by one of our sponsors, The Linux Emporium.

After spending longer than planned roaming The Black-e and trying to imagine it filled with people, we walked 5 minutes down the way to Studio 2, the bar for Saturday night. Studio 2 is the “studio where Coldplay, Barry Manilow, Take That, Spice Girls & Diana Ross recorded” but is now converted into a rather unique-looking bar with food. The building is still a proper recording studio though and, in Studio 2, the padded doors remain, as does the glass window between rooms, and separate recording booths. The bar will be available from 6pm until 2am and the chef will stay on in the early part of the evening so that we can buy food there.

And finally, there’s Liverpool itself. I’ve had various slightly doubtful enquiries about whether it’s worth going to Liverpool (especially if it’s quite a way to travel). I’ve been to Liverpool a few times in my life and I think it’s a really cool city nowadays.

As the 2008 City of Culture, Liverpool has been much regenerated over the past few years and is a really interesting place to be. Lots to see as a visitor, like the big wheel down by the docks, Albert Docks themselves, the Merseyside Maritime Museum, food at the old Bluecoat School…

…and not forgetting the rather random SuperLambBanana, an “unusual artwork [that] was created to warn of the dangers of genetically modified food, whilst being appropriate to the city of Liverpool due to the port’s rich history in the trade of lambs and the import of bananas”,  and the 125 mini SLBs that have been sponsored by local (and not-so-local) businesses and are mostly located around the city just waiting to be found–including near the OggCamp10 venue:

And of course there’s loads of good food (including good Chinese restaurants right by the venue), lots of shopping down the road, and, if today’s anything to go by, lots of sunshine too.

p.s. Thanks to Dan Lynch for the first photo, and to my Mum for the last three.

On Ada Lovelace Day, today, anyone and everyone is encouraged to blog, podcast, videocast, tweet about the achievements of a woman in technology and science.

Laura Czajkowski

I met Laura Czajkowski last September when part of the Ubuntu UK Podcast team shipped off to Dublin to attend her OssBarCamp conference, have a weekend of geekery, and an evening of BBQ and cocktails. Since then, I’ve seen Laura working passionately to help kickstart the Ubuntu Women Project and I’m aware that she is also on the Ubuntu NGO project which looks at how to make it as easy as possible for charities, not-for-profits, and other NGOs to benefit from Ubuntu and Open Source Software.

After I tweeted a few weeks back that I was working on OggCamp10 planning stuff, she replied, offering her help. I wasn’t sure how serious she was but as we had a load of large tasks that needed doing around that time, I figured it was worth asking. Within a week, she was a fully signed-up member of the OggCamp planning team (ie she gets all the emails and can edit the wiki), despite having her own conference to organise as well. OMG Ubuntu published a great interview with her today.

Ana Nelson

Another ace woman I met in Dublin that weekend was Ana Nelson, who Laura had finally convinced to present about her documentation automation work. I swear (as a former technical writer), the stuff she develops on should be used by corporations everywhere to maintain their vast documentation libraries and to save their skillful writers from spending hours manually updating screenshots and code snippets. Her talk at OssBarCamp was fascinating and understated – she sat on a chair, speaking her way round a printed, illustrated mindmap, punctuating it all with physical props like wooden toys and knitting needles. Her tweets are no less insightful, witty, and slightly off-beat.

So they’re just two of the women in the Open Source world (in particular, the Irish Open Source world) who’ve inspired me recently. Go check out their blogs to find out more.

This week, I decided to install Rational Software Architect so that I could try out (again) the User Interface Generator which comes with IBM InfoSphere Master Data Management Server–and other products too, I believe. You can find out more about what user modelling is and how you can use the UIG in RSA (lovin’ the IBM TLAs yet? ) in this series of articles on developerWorks. The rest of this post is not about the UIG but about how to install and configure Rational Software Architect for WebSphere, which is relevant to anyone wanting to do this, regardless of whether they’re wanting to use the UIG.

So I wanted to install Rational Software Architect (RSA; an Eclipse-based piece of software) on to Ubuntu, which is what I run on my work machine, a Thinkpad T61p. Not only that, but I wanted to install RSA for WebSphere, which includes WebSphere Application Server Test Environment (WAS). This meant that I was installing not one but two pieces of software that are not officially supported for Ubuntu Karmic (or indeed for Ubuntu/Debian as far as I know). But as the Linux binaries are .bin files rather than .rpm, life should be easy.

And indeed installing it is. It’s when you want to create a WAS profile that the fun starts. And that’s where it had all fallen apart for me when I tried much the same exercise this time last year. That time, I gave up.

This time, I tweeted my predicament, knowing there were people who might know the answer. Unfortunately, the person I thought might know the answer had failed in much the same way as me only 6 months ago and was now relegated to using Windows. Still, others came back to me, including Gavin Willingham, who I’d not met before but who works possibly 10 minutes walk from my desk, and Jay Limburn, who I’ve known for a year through Twitter and internal instant messaging but, though he also works max 10 minutes walk from my desk, never met in person until yesterday (he’s shorter and blonder in real life).

So, if you’re trying to install RSA for WebSphere 7.5.4 with WAS Test Environment 7.0 (other versions probably work the same way), I’ll end the suspense and start here:

Running the installer

1. Download the many parts of RSA for WebSPhere 7.5.4 and WAS Test Environment 7.0 with licence/activation bits and pieces. (NB this isn’t free software; you have to buy it from IBM so I’m assuming you’ve got that far by now.)
2. Extract all the zip files. If you do a right-click > ‘Extract All’ on the zip file in Ubuntu, the extraction tool doesn’t like to overwrite directories of the same name, so you end up with directories called ‘RSA4WS’, ‘RSA4WS (2)’, ‘RSA4WS (3)’, and so on when actually, you want the contents of each of those directories to be in the same place. So move the directories around so that you have just 3 directories:
   • RSA4WS (contains 7 directories called ‘disk1′, ‘disk2′, ‘disk3′, etc)
   • RSA4WS_SETUP (don’t do anything with the contents of this one)
   • WAS70 (contains 4 directories called ‘disk1′, ‘disk2′, etc)
3. In the RSA4WS_SETUP directory, as sudo, run launchpad.sh to start the installation process.
4. Follow the installer through but when it asks you for a user name and password to create a WAS profile, select that you will create a profile later and that you don’t want to create one now. The installation should run cleanly (if you let it try to create a profile, it will fail part-way through the installation).

You should now have a nice installation of RSA with WAS on your Ubuntu box. Next, you need to create a WAS profile so that you can use the in-built WAS server for development and testing (or in my case, to run the user interface generator).

Creating a WAS profile in RSA

There are a few things that prevent this just happening (some are generic Linux things and some are specific to Ubuntu):

• On Ubuntu, /bin/sh uses dash, not bash, but WAS scripts seem to use bash specifically, so the profile creation scripts fail.
• Something extra that I have no understanding of is required in the eclipse.ini file (which is key in starting the Eclipse-based RSA environment).
• The default location in WAS’s profile creation wizards is in the /opt part of the main file system which you typically won’t have write-access to as a normal user.

So here’s what you need to do (at least, this is what I did and hopefully will work for you to to get a running WAS server in RSA):

1. Change Ubuntu’s /bin/sh to use bash instead of dash.
   In a terminal (sorry it’s the command line but you’re changing some system settings here that you would very very rarely have to do normally, or just if WAS didn’t specify bash specifically), run the following command and select the bash option as the default for /bin/sh:

   sudo dpkg-reconfigure dash

   (As pointed out by @oldmanuk (Dom Evans), this is the proper way to reconfigure where /bin/sh points to (though I used Gavin’s method). )

   After you’ve created your WAS profile and everything’s up and running nicely, run the command again to change back to using dash. The benefit of using dash is speedier boot time, which is lost if you leave the setting as bash (see https://wiki.ubuntu.com/DashAsBinSh – thanks Dom).

   Now you’ve sorted out the bash/dash problem. One down; two to go.

2. Check that you have a version of xulrunner installed (I have no idea what xulrunner is for but, looking in Synaptic Package Manager, my Ubuntu installation included xulrunner-1.9l.1-gnome-support, but not the xulrunner package itself, which seems to be fine for RSA purposes).
3. In your RSA installation, find the eclipse.ini file. I installed RSA to the default location so mine was in /opt/IBM/SDP. In a terminal change to that directory:
   

   cd /opt/IBM/SDP

4. Open the eclipse.ini file in a text editor, such as gedit:

   sudo gedit eclipse.ini

5. Add to the end of the file the following line:

   -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner

   (From an Ubuntu forum post.)

   Now you’ve sorted out the ‘xulrunner’ problem and you can actually start RSA. Two down; one to go.

6. Start RSA from the Applications menu: Applications > IBM Software Delivery Platform > IBM Rational Software Architect for WebSphere 7.5.4.

7. RSA should suggest a directory in your home directory in which to put the RSA workspace. That’s fine; I just accepted the suggested location.

8. When RSA has opened (NB, my Welcome view doesn’t load – I don’t think that’s a problem), give it a moment to think, then it’ll pop up a wizard to create a WAS profile.

9. In the profile wizard, clear the option about security unless you know what you’re doing with WAS security and have a need to use it in a development environment.

10. You’ll also notice that there’s a warning about the currently selected location for creating the profile. This is the third problem I listed above. The default location shown is for creating the profile in the installation directory of RSA. Change the location to a directory in your home directory. For instance, I told it to use /home/laura/IBM/profiles.

11. When the wizard has created the profile (which will take a few moments – you can see the activity in the bottom-right of the RSA window), the default server for the profile is listed in the Servers view on the right-hand-side of the RSA window.
    The server is listed as ‘stopped’.

12. Right-click the server then click Profile. This opens a dialog box about the profile; I just accepted the defaults then it failed to start the server (the error said it had failed to start within 300 seconds). But when I repeated this step, the server started.

And that’s as far as I’ve got but it’s further than ever before. If I come across any more gotchas, or take some screenshots, I’ll update this post.

Yes, it is a pain to have to do all this but remember that WAS isn’t supported (as far as I know) on Ubuntu Karmic. If you want it easier, install it on something that is supported. If you want it on Ubuntu, I hope this post (and the others I cribbed information from) helps.

What’s happening in the video…

The red/orange lights flash faster when the electricity usage in my house increase. The green/blue lights flash faster when the electricity usage in my Mum’s house increases (though in the video, the usage stays at a constant level so the lights don’t speed up).

Initially, the lights are flashing at the default reading of 1 kW. Then as the electricity usage levels vary, the red/orange lights start to flash out of sync with the green/blue lights. After a short time, though, I switch the kettle on (you can just about hear it in the background!) and you can see the red/orange lights start to flash a lot more quickly (as the kettle takes about 3 kW on top of whatever the current reading is). The lights slow down again as the kettle switches off.

How does it work?

In my house I have a Current Cost monitor, which reads the live power usage of the house and publishes it (using IBM messaging protocol MQTT) to a server on the Internet. An application on my laptop (to which my Arduino – small circuit board with a processor on it – is connected) subscribes to the readings in real time and passes the information to the Arduino. The Arduino does some calculations to convert the readings to speed of flashing so that the higher the reading, the faster the lights flash. The Arduino uses that speed calculation to control the relay switches connected to the Arduino, which in turn control the power to the lights – when the relay allows power to the lights, the lights come on; when the relay cuts the power to the lights, the lights go off, and so on.

This slideshow on Slideshare shows the overall connections between all the parts, and some pretty pictures:

OggCamp10 is an unconference, which means that the schedule will be finalised on the day. So if you come along, you can not only have a say in that schedule but you can offer to be part of that schedule.

What to expect…

OggCamp10 isn’t just about software. You can offer to talk about anything at all. And if people want to hear your talk, you’ll be able to give it. Even if your talk isn’t on the schedule, you can still meet up with like-minded people and discuss the things that are important and interesting to you.

At last year’s OggCamp, we had talks on how to hook your house up to Twitter (or Identica!), politics and geeks, online privacy and security, engaging young people in open source, how to explain programming to your grandmother, just what is Pokebook(!), and what your pig says about you (yes, really).

You can see the final schedule from OggCamp 2009, plus photos and Twitter/Identica feeds from the weekend, on the OggCamp 2009 website.

OggCamp is jointly organised by the Ubuntu-UK Podcast and Linux Outlaws podcast teams. OggCamp 2009 was a one-day event in Wolverhampton, UK and about 120 people turned up – which was fantastic! OggCamp10 will be a bigger and better two-day event in Liverpool, UK at The Black-e community arts centre.

Audio trailer…please play

Our resident Liverpudlian, Dan, has done this brilliant audio trailer for OggCamp10 (MP3 or OGG). Have a listen! If you produce your own podcast, we’d be eternally grateful if you’d play it for your listeners – thanks!

Sponsorship opportunity…

And finally, if you are interested in sponsoring OggCamp10 by contributing towards the cost of the venue hire, or by providing prizes for the event, or if you have any cool novel ways to support us, please email me: uupc@lauracowen.co.uk. Thanks.

And then they agreed to do another last ever LugRadio Live – in October 2009. And it really is the last ever this time. It was, as usual, a brilliant event with some great talks (including Matthew Paul Thomas (@mpt) on reporting usability bugs in Ubuntu, and Gervase Markam on his first computer program) and the premiere of Tony’s Don’t Listen Alone documentary about LugRadio; all followed by a highly amusing geek kareoke in the basement of the Connaught Hotel in the evening.

It was, however, unlike previous LugRadio Lives, a one-day event. So the Ubuntu-UK Podcast and the Linux Outlaws podcast teams joined forces to put on a second one-day event, OggCamp, on the Sunday.

Venue

Because we had absolutely no idea, at the start, how many people might be interested in coming, Tony did some hunting around for venues but came to the conclusion that the official LRL hotel, the Connaught, would be best. And it would be free. That way, LRL attendees could stick around in Wolverhampton for a few hours more and nurse their hangovers in company.

I just found an email Tony sent to the OggCamp gang back in July:

In the interests of making it easy to organise…, I was thinking that some sort of unconference…would be best. We’d need to agree (and fund) a venue with ‘net access and set up some sort of website, but that should be about it. And a pithy title, we’d need a pithy title.

And that’s where it started.

Tony booked the venue, three conference rooms in the Connaught, on the collective understanding that we may never see that money again but also the hope that enough people would stick around after LRL that we’d have a respectable number of people turn up out of curiosity.

Money

As I say, the OggCamp team of seven people (Tony, Ciemon, Popey, Daviey, and me from UUPC, and Fab and Dan from LO) agreed that the venue cost would be shared between us and we accepted that we may never recoup it. But if we could recoup the costs, then we would. Also (and moreover), we wanted the day to be a little less spartan than just three conference rooms in a hotel. So we contacted people who we thought might be interested in sponsoring OggCamp, hoping that we might be able to get someone to pay for things like free soft drinks or tea/coffee for attendees throughout the day. And souvenir mugs to put the tea in.

In the end, we couldn’t provide hot drinks but the venue were fine about us bringing loads of soft drinks. Andy Smith from Bitfolk offered to sponsor the drinks. And then a couple of our sponsors said they could lend us enough digital projectors between them that we could have one in each room plus one for a TwitterFall display. It was starting to look like this could turn into something.

Over the following weeks, we got an incredible response from people and companies interested in sponsoring this brand new event. (The full list of sponsors is on the website.) By the time we got to LRL/OggCamp weekend, we had gained enough sponsorship money to cover all the costs we had incurred apart from the venue hire itself. This included things like the free drinks and stationery (little things like a cash tin and bucket for voluntary donations if they were made, and marker pens, paper, and sticky notes for the schedule sign-up grid).

We had also all agreed that we’d really really like to have the OggCamp mugs. So when we knew what sponsorship money we had, Dan found a company who could print Fab’s design on to mugs and deliver them to Popey’s in time for OggCamp weekend. We worked out that if we sold some of the mugs, we could make back the last bit of non-venue money and, if we sold a lot, we could start to make a dent in the venue hire. At any rate, we could give free mugs to the people who volunteered to help out on the day as crew, and we could each have one as a souvenir whatever happened.

Several of our sponsors had given us material prizes, like a couple of Viglen MPC-Ls (mini, low-powered computers), some Ubuntu laptop bags and hoodies, and an Arduino Mega. We hit on a great idea that would distribute the prizes in an interesting way and might help us pay for the venue: we’d have a raffle.

I’m not sure whether an Open Source event has ever taken the village fete approach to fundraising before but it seemed the perfect solution for us. So into our stationery stash went a book of 1000 raffle tickets.

Website

Meanwhile, Fab was getting us all sorted in the digital world. He speedily knocked up an OggCamp website and a very cool logo, as well as some digital badges for us all and others to strategically place in blog posts to publicise the event. Somewhere along the way we’d had a vote on names and OggCamp came out on top – it fitted the ‘pithy title’ requirement, and it chimed nicely with the fact that the two podcasts focus on the open source world and both release a .ogg (open standard) format of their episodes (the ‘camp’ part nods to the unconference/barcamp style of scheduling we were planning to adopt).

Very early on, before anyone could back out, Fab also registered an @oggcamp account on both Twitter and Identica so that we could start tweeting and denting about it.

Research

Next, Tony, Daviey, and I figured we could do with finding out a bit more about how this unconference/barcamp lark works in practice. So we used it as an excuse to nip over to Dublin to attend Laura Czajkowski’s one-day OssBarCamp. Although Laura hadn’t gone for the full unscheduled unconference event, it gave us a good idea of what you can achieve in terms of a community event on a reasonably small budget and lots of enthusiasm and community spirit.

Meanwhile, Tony was also joining regular LRL planning calls because, as in previous years, he was in charge of the AV crew for that event (sound, videoing talks, making sure speakers’ laptops work). So he was building on his insight into how the seasoned LRL organisers did things. Also, we’d all attended LRL several times, and most of us had crewed for LRL at least once. So we had that experience in hand at least.

Unfortunately, the one thing we really couldn’t research, because of the lack of time and the distance from Hampshire to Wolverhampton, was the venue itself. Tony had had to base the booking on disjointed email discussions with the hotel and printed room dimensions. All we knew was that what would become Room 1 was on the fourth floor (fifth floor if you’re in the U.S.) and the two smaller Rooms 2 & 3 were on the first floor (second floor). That separation made us slightly nervous but the hotel assured us that there was a lift right by the rooms so we envisaged people being able to nip up and down between sessions without too much trouble.

Marketing

As I’ve mentioned already, Fab got us Twitter and Identica accounts early on, as well as the OggCamp website so that we could post details about the venue and plans as we got them. We also set up a Facebook event page, which turned out really useful, if only by giving us a sense of the order of magnitude we should expect in terms of numbers (though even Facebook underestimated in the end).

We also recorded a cheesy but fun trailer to play on the podcasts to advertise OggCamp. One late night after a UUPC recording at Popey’s house, we each recorded a script that the Dan had written. Dan then produced the trailer that features in each of the episodes of UUPC and LO in the last few weeks up to OggCamp weekend.

Probably (at a guess) the most effective marketing was by the lovely LugRadio guys themselves who gave us a place on the LRL Weekend page of their website. We certainly got a few emails at the end of September from disappointed LRL fans who couldn’t get tickets for that event and wanted to let us know either that they couldn’t come to OggCamp because they hadn’t got tickets for LRL or that they would come to OggCamp despite not having tickets for LRL and could we guarantee them entry after travelling so far? We did also get emails, tweets, and dents from people who were planning to come to both events or even just for OggCamp anyway. Which was really encouraging.

We’d been pimping the event on each of the podcasts from the time we had confirmed the venue, and both podcasts had had positive feedback from listeners about the event. On the whole, we’d estimated that between the two podcasts (in particular the Linux Outlaws podcast which, like LugRadio, has an active online community based around the podcast – although UUPC has a large listener base, it was hard to know how much of our fairly diverse listenership would make the trip to Wolverhampton), we could probably rustle up at least 50 people.

By the end of September, more than 60 people had signed up to the Facebook event page to say that they would attend. Althought that’s no guarantee at all, it did suggest that we’d get a good attendance. LRL by this time, though, had given out more than 200 tickets. So we knew there’d be maybe 200 geeks in Wolverhampton on the morning of OggCamp, and while we weren’t expecting them all to stay on for OggCamp by any means, there was the possibility that they might! Our maximum capacity was 170. And we knew there were people who were coming only to OggCamp on the Sunday.

LRL at least knew that they were oversubscribed and were able to say ‘no ticket, no entry’. We of course had no idea how many might turn up and wouldn’t know until the morning itself. We did start to get a little nervous at this point about having too many people turn up instead of too few. Which is kindof a nice situation to be in but also not.

In saner moments, though, we figured we could possibly get about 100 people. Which would be a very nice, and very satisfying, number. Even more so if they each bought a mug so that we would break even and so that we wouldn’t have stacks of OggCamp mugs left over to store indefinitely in someone’s house.

And finally, our most impressive marketing came courtesy of Linux Format magazine who kindly ran a free full-page ad for OggCamp. Unbeknownst to us, they also featured us in their Community News column on the opposite page from the advert. Which was all very cool and exciting.

The final week

Aside from Tony (who’d been organising AV stuff for LRL in tandem and was, therefore, very conscious of the LRL/OggCamp weekend moving ever closer), this was when it things got really busy. All the big things (apart from when Daviey’s new baby would make an already overdue appearance) were fine (Dan had AV sorted, Tony had the venue, Fab’s design work was all done, the mugs had turned up in time and were now stacked next to the trays of soft drinks cans at Popey’s, the UUPC team all had new t-shirts and they’d arrived at Ciemon’s in plenty of time) but there were still a few things left to sort out.

So that week, most of my evenings were spent re-learning how to use Scribus and creating, with Popey over IRC and email, a set of direction signs (reversible arrow design idea ‘acquired’ from FOSDEM), signs to warn people that they may be photographed and/or recorded and not to hurt themselves while at OggCamp. As we’d not seen the venue layout, we had no idea how many we’d need so Ciemon and I just printed *a lot*. Ciemon also knocked up some cool CREW badges so that the voluntary crew members would be identifiable.

Fab came over to the UK early to do a live recording of Linux Outlaws with Dan (they’ve only met a few times in person; the first time was only last year at LugRadio Live).

And then it was just a case of packing and hoping that we hadn’t missed anything really important.

Eightbar (as in the IBM logo which is known as the ‘eight-bar logo‘) is a community of people in and around IBM Hursley who are into cool, techie or creative things, either in work, out of work, or both.

The thing about large corporations is that people forget that most of the most amazing things that happen in those corporations come down to individual people just getting on and doing them. It’s easy to think (from inside and outside) that employees are ‘just a cog’ and everything is decided from on-high and nothing can be done without getting it approved in triplicate.

In fact, while a corporation’s culture can play an important part in encouraging and supporting good ideas, it’s the individuals who try them that make the difference. Whether that’s coming up with a better way to do something in your ‘day-job’, or writing a cool app in your evenings which subsequently gets so many downloads it gets incorporated into a real product (several people I know spring to mind immediately), or you just do something like running Linux as your desktop when hardly anyone else is and then helping others do the same.

That kind of innovation and adventure just doesn’t happen because someone in a suit on high tells you to do it. It comes because you think it’s a good idea and decide to give it a go.

The motivation behind eightbar was the realisation that there are loads of cool things happening around IBM Hursley that no one ever finds out about. So 4 years ago the eightbar blog was started.

Until today, I’d never contributed to it because I was too intimidated – but as one of many people around Hursley who attends conferences and unconferences, maintains (mostly) a blog, twitters, and likes to talk to other people who are into cool and interesting stuff, I figured I should make the effort (and the lovely @andypiper hinted very unsubtley that I should too).

So I did.

From the user’s perspective (who the software is written for, after all), they don’t want to know that the error was not expected by the people who wrote the code. The user wants to know that the software (especially when it’s important to their job/finances/life) is in control and knows *exactly* what’s going to happen when you press a certain button. The user has to be able to trust the software and trust that the developer(s) of that software knew what they were doing when they wrote it.

So it gets difficult for the developer/designer when they have to make a call that potentially risks breaking that trust. For instance, supposing you (as a developer) were to provide a new feature that is really beneficial to the target user but there is a small risk that something will go wrong in a big way for that user if they try to use that feature. As developer, what do you do?

Typically, I’d predict, you would make the feature optional so that you aren’t forcing the user to use a feature that could potentially (however unlikely) cause them serious problems. If the user does try to use the feature, you provide scary warnings of what could occur in certain circumstances. Hopefully, that will put them off unless they really know what they’re doing.

Okay, that’s the developer’s perspective. And it’s entirely understandable and even laudable that the developer is doing what they can to keep the user safe.

So, switch now to the user’s perspective. The target user is computer literate but had no knowledge of the development of this feature or who developed it. This user could benefit greatly from this new feature but when they attempt to use it, they get a scary warning message which, as intended, makes them think twice about whether to use the feature or not.

Now what does the user decide? Granted, risk is all about weighing up the costs and benefits, and to one person the relative benefit will outweigh the possible cost. To make a decision, however, a person needs as much information as they can possibly get. In this case, the only (and therefore critical) information is provided by the developer; that is, how informative and/or scary the warning message is.

If the developer provides a lot of information that makes the feature look useful, the user might just choose to use it. But if the developer makes the warning message as scary as possible, the user will probably opt not to use it.

The developer wants users to use the new feature because they’ve made the effort to develop it and it really could benefit many users. The developer, however, doesn’t (understandably) want the responsibility of trashing someone else’s laptop in some way. So the result is that the developer pushes that responsibility off on to the user, when in fact the developer has far more information available to help them make that decision than the user has.

If you’re the user, though, how are you supposed to make that call?

For example…

Computer Janitor is a utility that was introduced in Ubuntu Intrepid (I think) so that you could run it to clean up old kernels that are no longer needed, and other bits and pieces of packages that are no longer used. When I first tried to use it, I raised this bug, which, it turned out, had this duplicate.

Essentially, CJ could potentially remove packages that you might need. So when you try to use it tries to scare you into deciding whether you really really want to risk it. I raised the bug because the scary words don’t actually help you decide – in that, if you aren’t easily scared by such things, the scary message only determines how scared you are – not how well-informed you are to make a decision…and isn’t going to help when you break your computer.

What would maybe be more helpful is if CJ used a stricter set of criteria when selecting which files to remove. In this case, CJ might leave on your system  some files or packages that could be removed, instead of the reverse where it might incorrectly remove files or packages you need. The former is surely the preferably outcome for the majority of users (who would rather have a few unneeded files on their machine than a broken machine).

It would also be possible then, for the minority of users who really really know what they’re doing, to selectively delete the files that probably can be removed but CJ isn’t certain about. In this case, users are only presented with a decision to make if they actually seek it out but the majority of users are still able to benefit from the safer (if slightly less effective) behaviour. In fact, it would be better overall if CJ ran automatically during an Ubuntu upgrade so that the user really doesn’t have to care about it (unless they really really want to).

This is not intended as a dig at Computer Janitor as I think it’s a useful feature in general and I’m kindof surprised that this kind of clean-up wasn’t being done already whenever you do an upgrade of Ubuntu. Also, I think the bugs I’ve linked to above have caused a bit of a headache for the developers.

This issue of forcing users to make ill-informed decisions is a very common occurrence throughout software development and is certainly not specific to Ubuntu; it’s just that Ubuntu is a public development effort and provides examples that are relatively easy to explain. So please don’t be offended if you are part of the development teams for either Computer Janitor or Ubuntu!

So, if you, as developer/designer, find that you’re having to give scary messages to make a user *really* decide if they want to continue, consider stepping back from it, thinking about the possible decisions the user could make and what the consequences of those decisions are. Even talk to some of your target users and find out what decisions they’d make. Just because you can successfully scare them off doesn’t make it a successful feature – if the feature is potentially useful to the user, they should be able to safely use it (no matter what level of fear you instill in them). Then look at the bigger picture, think about it in a different way, and see if the decision can be made for the user, or the decision can even be removed altogether.

I’m sure that it’s not as easy as it might sound. And it’s not always easy to recognise situations like this. I’m hoping, though, that, having thought this through while writing this post, I’ll actually remember it in future the next time a similar issue occurs for me.

That’s on Saturday 24th October.

On Sunday 25th October (that’s the very next day!), you can roll out of bed and into OggCamp (if you’re staying at the LRL official hotel, the Connaught),.

OggCamp is brought to you by a joint collaboration of the Ubuntu UK Podcast and Linux Outlaws teams.

So come and join us for the last ever LugRadio Live followed by lots of barcamp fun!

OggCamp will happen in Wolverhampton on Sunday 25th October.

Why Wolverhampton? Well that’s where LugRadio Live 2009 (@lugradio) will happen too. On Saturday 24th October. See what we did?

So, the Ubuntu-UK Podcast (@uupc) and Linux Outlaws (@linuxoutlaws) podcast teams will be at LRL on the Saturday (and probably the Friday night as well) so we figured we may as well stick around on the Sunday too and organise an unconference where you can drop in to nurse your hangovers, see everyone again, and see some more talks, demos, or whatever.

As it’s an unconference, we won’t publish a full schedule beforehand (if you have an interesting presentation, just turn up on the day and if enough people are interested, you can give it) but both podcasts are likely to record some material during the day (one with swearing and one without ).

I will post more information as we know it. For instance, we should be able to announce the venue any day now…