Microsoft’s new ClearType fonts for Vista are great. The fonts include Constantia, Corbel, Calibri, Cambria, Candara and Consolas.

Getting them installed in Ubuntu is a breeze, thanks to a script I found.
To install the Vista ClearType fonts in Ubuntu, you need to install cabextract first. Cabextract is a utility found in the universe repository, so before you run the following command, make sure you have universe enabled in your repository list. Once this is done, install cabextract using:
$sudo apt-get install cabextract

Then, once that is done, use this script to install the Vista fonts. Create a file called “vista-fonts-installer.sh” in your home (~) directory.
Then open up a text editor and copy and paste the script into that file.
Do a chmod a+x ~/vista-fonts-installer.sh to make the file/script executable.
Then run the script using:
$ ~/vista-fonts-installer.sh

The script downloads the Powerpoint Viewer installer from microsoft.com, and then extracts the Vista cleartype fonts using cabextract. These fonts are then installed in the ~/.fonts directory.

Please remember that the ClearType Vista fonts are not free as in they are not GPL-ed or made available under a re-distributable license. Since you are downloading the fonts from the MS website, and since you might already have a Windows XP/Vista license, this is not a crime, but consider yourself warned against the perils of supporting closed systems

Update::

1. Looks like the use of these fonts are restricted to only Microsoft Windows/Vista operating systems according to the terms of the license. I am sorry, but you’ll be installing them at your own risk.
2. Also, please make sure you use the bash shell, or change the first line of the code to #!/bin/bash
3. In retrospect, this was a bad post – I think we’re better off not using stuff folks don’t want us to use – let’s use the better, freer, easier to install fonts.

So Jorge Castro is now a Canonical employee!

Jorge, I for one, would love to see your mug again on Planet Ubuntu. I would love to see whiprush.org up and about again.

Jorge’s disappearance from the interwebs was followed by pleas for his return, about 9 months ago (you can find his last post here if you really want to). I used to love reading what Jorge had to say. It’s good to have him back in the Ubuntu world, now if only we could have his blog back too Welcome back, Jorge!

I was in love with Acer laptops. I bought my first one, an Acer Travelmate 290 LMi in my second year of grad school. I did pay ~ $1200 for it, but it was awesome, right until the moment there were errors with the hard disk controllers about 3 years later. When I sold it for parts on ebay, it still retained more than 3 hours worth of charge in it’s battery. The finish and the quality of parts spoke loud and clear. I liked the simple looks, the ruggedness, and above all, the dependability.

So when I had to find a replacement, and was short on time and money, I settled for another Acer. An Acer Aspire 5003 LMi. Piece of junk. The plastic looks cheap. The “Aluminum” next to the keyboard is poorly spray painted plastic. The area next to the touchpad, and the left-click button have lost all their paint due to repeated use, and then look white. All within a year. For the last few days, occasionally, I would open up the laptop, and the display wouldn’t work properly. Loud cracks can be heard at the hinges when I open it up. I’d usually fix the display problem by opening the lid to an angle where the display worked. Today it failed completely. No matter what I did, I couldn’t get the display to display anything coherent. The quality of the parts, and the “casing”, is terrible. I admit, this was a cheap laptop, but it had what I needed at a minimum. I am not someone who buys the cheapest thing around. I buy computers with exactly the minimum I need. This one has a Broadcom wireless card, but I thought I could live with that for a bit. I don’t need a separate video card – I never play games. I do need a large screen, and a DVD-burner – well, you get the point. I would have gladly paid $250 more to Acer for the same laptop with better quality.

Personally, I have vouched for Acer laptops, and have directly influenced my friends into buying at least 3-4 Acers. Now I feel like an idiot. I have to try something new. I don’t like how ThinkPads are designed with the recessed screen and clunky looks and all. The Sony Vaios I have known through friends and others have all been terrible – each of them making the trip back to Sony at least once. That leave the glitzy HPs and the Dells. I’d rather have a MacBook or the Pro, which looks infinitely cooler. Wish I had the money for a new MacBookPro. It has way more features and power than I need, though. Anyways, I feel much better having written this – may those that I recommended Acers to find it in them to forgive me!

Ans: A guy in a pic….

Trivial, I know, and not too original either, since I got it from LiveJournal, but I couldn’t resist posting this

I read the impressive growth and traffic details for WordPress.com at Matt’s Blog. WordPress has always been very dear to me, and it makes me happy to note that the WordPress team grows from strength to strength, without compromising on values, and while keeping things open, almost entirely so.

However, the stat freak in me got another tool, and the results are surprising!

I did not have any clue that the number of 45-65 year olds that visit my site are above the average numbers for the internet by around 25-45%. Also, most of my visitors are as poor as I am, with an income of less than $30K a year. That is surprising when you realize that college graduates outnumber any other kind of visitor, based on education. Finally, the male-female disparity is not too high – I get 25% less female visitors, and 25% more male visitors than the average site. Here’s my quantcast report.

Now, like me, you must be thinking, what about ubuntu.com?
Maybe Canonical should sign up for the quantcast setup like WordPress.com and then we could start fixing the problem where, right now, my blog seems to get more visitors than ubuntu.com. Clearly, quantcast is orders-of-magnitude off with the numbers. Let’s hope the percentages are right when it comes to the demographics. If they are, then then, again, Ubuntu seems to attract a middle-aged, may I say “mature” crowd. Ubuntu.com attracts more Asian, Hispanics and “Others” than the average website out there. Also, “linux drivers” seems to be leading the charge of visitors to Ubuntu.com. It would be good to put something related to drivers – perhaps an article with links peppered throughout to the various compatibility resources and hardware profiling tools somewhere on the front page of help.ubuntu.com which seems to be quite a popular destination. Of course, if I had a say in how Ubuntu’s websites worked, I would first ensure that the help pages show up where they belong on Google searches. Somehow, I can’t seem to end up at the Ubuntu help wiki after a web search. I suspect the wiki software’s intricacies, and the “https://” (now why does a help wiki have to be served over https?), are partly responsible for that issue. You get the idea that shipit must be doing something right, since it seems to be quite a popular destination. Also, OpenSuse, FreeSpire and Damn Small Linux seem to the other Linux distributions that are popular among those that visit the Ubuntu website. Scanning the quantcast results might help lots of folks involved with planning, developing and marketing Ubuntu – whether it is deciding what/who to focus on, or finding out how meta-plans are working out.

I was looking for a replacement for SecureCRT in Ubuntu. Something that would let me save all my SSH connections and make it possible to open a connection with the least effort.

As is often the case, I found something better than SecureCRT – a panel applet for GNOME that gives me a drop-down list of SSH connections. SSHMenu is cool, way too cool.


Above, you can see my list of ssh accounts in all their glory. A connection is just a click away.

When you set up the connections, you can specify the geometry – ie, where on your desktop you want the gnome-terminal window to pop up, as well as a “profile” for the gnome-terminal instance – very handy if you want to have different color schemes for different ssh accounts to be able to distinguish between them better.

What’s even better is, in the “Hostname (etc)” field, you can prepend ssh options to the hostname. The figure below shows my port forwarding setup for IRC at school, since I can’t chat using port 6667 at school.

There’s a Debian/Ubuntu repository for SSHMenu, and of course, nothing stops you from downloading the .deb packages and installing them if you don’t wish to add another repository to you list of repositories. I wonder how long before SSHMenu finds itself into the Ubuntu repositories

Once you get SSHMenu installed, you can add it to your panel by right-clicking on your GNOME panel, and selecting “Add to Panel”. SSHMenu should be listed as “SSH Menu Applet” under the “Utilities” section. Then all you have to do is use the tool to add accounts that pops-up when you install the applet, or add the accounts later by clicking on the “SSH” in your panel. However, this still doesn’t take us to “one-click” login, since you will be prompted for your password by the server you are trying to connect to.

To make the connections truly one-click (or two-click), you might want to setup password-less logins using ssh-keygen and ssh-copy-id. A quick overview of that process follows:
On your local computer, type:
$ssh-keygen -t rsa
When prompted for a password, you may want to enter none. If you enter a password there, you will have to enter it everytime you try to use the “passwordless” login, which kind of defeats the purpose.

Enter a password here. Then when you try to connect to the accounts using SSHMenu, you will asked for the password only once, the very first time. (Thanks to Grant, SSHMenu’s author for the explanation in the comments).

Once your RSA key-pair is generated, you need to add the public key to your server’s ~/.ssh/authorized_keys file. You can do this very easily by typing (on your local computer):
$ssh-copy-id ~/.ssh/id_rsa.pub username@example.com
This will copy your public key for the just-generated RSA keypair to the example.com ssh account, where your username is “username”.
Of course, for this passwordless login to work, the server needs to accept this method of authentication. There’s an old article at the Debian Administration blog that describes the process in a little more detail, and countless others have written about this, so you won’t have trouble finding info.

This thought just struck me: the GNOME “save file” icon is still an image of a floppy (or it is at least in Gnumeric). How many people still remember what a floppy looks like?

Should the save icon be replaced by something else (a picture of a cd/usb drive)? Or should floppy discs be “icon”ized forever?
Somehow, all these days, the above thought never occurred to me. That icon with a floppy drive in it meant “Save” and to be honest, I have failed to think “floppy” when I have seen the icon before.

Jem Matzan thinks we technical writers treat you as stupid drooling idiots.

Do I? I can honestly say I don’t. I write for the competent computer user who has switched to Ubuntu. Anything that 90-95% of the people who formerly used Windows or Macs, and are competent enough to help others won’t be published here. Guaranteed. I can say that since I have a target audience of one – myself before I knew what I wrote here. I write so that, some day in the future, when I search for a solution to a problem, I get the pleasure that only a goojà vu (google + déjà vu ) can provide – finding something you wrote as the result of a Google search is priceless.

There are some authors of blogs that write tutorials and guides that cover all and sundry. The installation of some software that should be pretty straightforward to install, and so on, ad nauseum. I understand that the pleasure of earning a check through Google’s adsense can be great, and I wish these authors good luck. There are also the book equivalent of these sites that really do treat Ubuntu users as dunces.

But Jem, what’s the problem with any of that? The world needed a “Linux for Dummies” – something that is inanely simple to install, setup, use and maintain – and that is exactly what Ubuntu is. Power users don’t need to fear it since it does not take away anything in doing that. So there you are – a Linux-based OS that is simple enough for the stupid and as (if not more) flexible and powerful than the best OSes out there. It’s not like there aren’t books out there that don’t address the intricacies of subjects that are technically complex. The wiki and the Official Ubuntu Book, not to mention all the documentation and books out there for Debian all address the power users’ documentation needs.

I was happy to read that article, especially the parallels drawn with how Mac users were once perceived the way the author perceives Ubuntu users now. I was happy because it is a sign that we are moving in the right direction – towards a “Linux for Human Beings” (regardless of IQ).

You guys must remember Jessamyn, the librarian who posted a video about installing Ubuntu at, where else, the library.

Well, by some strange coincidence, which cannot be explained rationally, I ran into her again on the tubes. I followed the user profile link at this comment on Ask MetaFilter to end up at her profile page.

Of the billions of unknown users of the internet, we are two.

What are the chances?, I ask you!! The mind blows.

In other news, there is no news – I’m on the slow track to the Ph.D.

I woke up on Thursday with a left arm more painful than a 100 episodes of Wheel of Fortune. I had almost pulled an all-nighter the night before to finish reviewing/correcting a paper. I went to the doctor, fearing the worst. My left wrist was aching, and no change of position or angle would suppress the hurt.

The doctor said I had tenosynovitis – which is a member of the much talked-about Repetitive Strain Injuries. He advised me against using the laptop on my lap – this keep my hands all hunched up together. He also advised a couple of days of rest. So needless to say, I haven’t typed much over the weekend, though I wanted to write a short guide on implementing a Getting Things Done workflow in Linux. I had set things up for GTD the past week, and the search for tools that work on Linux was frustrating, to say the least. I finally had to narrow it down to an online tool that seems very capable of the task. I have been itching to write the article and yet have resisted.

Monday brought me back to work, and I thought I should look at options to reduce the risk of recurrence of the pain. For two reasons – the pain was real bad, and the doctor said that repeated occurrences of RSI would lead to the much-dreaded Carpal Tunnel Syndrome and perhaps permanent numbness of the digits in my hands.

GNOME is very advanced when it comes to providing methods to save your hands.

There is the Typing Break in GNOME’s keyboard preferences dialog (System -> Preferences -> Keyboard). Here’s a snapshot:

It is easy enough to ask you computer to lock up every once in an hour or so for 5 minutes to enforce a break.

But for those of us who are not satisfied with a fly swatter to swat flies, there is workrave, with the little sheep for a mascot.

You can install workrave using:
$sudo apt-get install workrave

Once installed, you can add it to your panel as an applet by right-clicking on a panel and adding the applet:
.

Once on the panel, you get to right click on the panel applet and set preferences:

There’s a whole lot to choose from – you can choose to have micro-breaks of less than minute every 10 minutes, say. You can also enforce a longer break every hour or so. A break of 5 minutes every hour seems normal. You can also choose whether to be able to postpone the break when you get the warning of an impending break or not. A break can be either just a disabled keyboard, or a locked screen too, just so you don’t use your mouse to sneak a peek at you mail, or visitor stats

Workrave also has a neat feature where you can exercise your fingers, wrist, neck and arms during the break – there is an on-screen display of how to do the exercise and a virtual character does it with you. Marcel has written about workrave in detail and even has some more screenshots – including one of the dudette who does the exercises with you.

In addition to the forced typing breaks, I am thinking this would be a good time to switch to the Dvorak keyboard layout. The initial learning phase where typing gets really slow is what’s holding me back. Maybe that is one thing to filed under “someday/maybe” in my GTD system.

Hey guys,

as you may have noticed, updates to this blog are few and far between. Sadly, I’ve found it harder and harder to find Xubuntu-related material to blog about. I imagine it’s because I’ve shifted more towards GNOME and Openbox. That being said, I felt that was no reason to go months without blogging. To make up for it, I’ve decided to start a more general-purpose Linux blog:

http://toodumbforgentoo.wordpress.com/

Unlike this blog, this one won’t be tied to any certain niche. It’ll basically run on the basis of posting whatever I like whenever I like. That being said, I won’t be abandoning this blog altogether. My blog partner Vincent will still be around to make posts, and I’ll probably pop in and blog from time to time.

It’s been a great 2 years with this blog, but now I feel it’s time to move on to something more.

A while ago, there was a little disagreement in the Xubuntu developer community. Since it did not look like the dispute was going to be resolved on the developer mailinglist, an online meeting was held led by Canonical’s Ubuntu Community Manager Jono Bacon.

That meeting led to several decisions, the most important one being that Cody Somerville was appointed as Xubuntu’s project leader and assigned to create a strategy for Xubuntu, so that everybody knows where Xubuntu stands and what its goals are.

Well, Cody set to the task and, after gathering feedback at the Ubuntu Developer Summit, came up with the first draft of what is to be the Xubuntu Strategy Document.

This being a first draft, everybody is invited to send feedback to Cody’s email address cody-somerville@ubuntu.com.

My first impression was that Cody did a great job on this one: Xubuntu has a bright future ahead under his lead

Xubuntu 8.04 comes shipped with PulseAudio, a new sound management system. For the most part, your commonly used programs should work with this new program. For some, however, Audacity may quit being able to play and record sound. (For those who don’t know, Audacity is a sound editor; which means not being able to play and record sound renders it pretty useless!)

This how-to is extremely easy and short, but it helps me work with one of my favourite programs. In short: uninstall jackd.

1) Go to Xfce Menu > Accessories > Terminal, and enter in the following:

sudo apt-get remove jackd

Reopen up Audacity. Hopefully, it should start working again as it should. If not, you may have to quit the jackd program. Go back to the terminal and enter the following:

killall jackd

Now Audacity should be working just as it did before. Good luck!

(Credit goes to http://ubuntuforums.org/showpost.php?p=4812244&postcount=5.)

Xubuntu 8.04 Hardy Heron was released today! You can view the release notes here. While I haven’t upgraded yet, this page shows that Xubuntu has received a lot of the same fixes as Ubuntu. Links to ISOs to download are available, but to save some wear and tear on the servers, it is strongly recommended that you use BitTorrent. My partner blog will tell you how. It’s very exciting indeed! Happy Xubuntuing.

Brian J. Tarricone posted the following message to the Xfce mailinglist:

As some of you already know, I’m in the process of applying to Google’s
Summer of Code as a mentoring organisation. Xfce applied in 2006, but
wasn’t accepted. I don’t really know why, but hopefully this year we
can do a bit better. To that end, I’ve created a few pages on our wiki,
and people have been working on them for the past couple weeks:

http://wiki.xfce.org/gsoc-2008-ideas
http://wiki.xfce.org/gsoc-2008-mentors
http://wiki.xfce.org/gsoc-2008-students

Now, we won’t know if we’ve been accepted into the program until March
17th. However, I’d like to generate some interest for our participation
in the program; in particular, I’d like to get some names on that
’students’ wiki page.

So, if you don’t mind, if you have a blog, or some other means of
publishing to a group of people (via means other than spam, of course),
could you please do a little advertising for us? Just point out that
we’re applying to the program, we’re looking for student participants,
and give a link to our wiki page (the main ‘ideas’ page).

Thanks!

He also posted the following on his blog:

While we haven’t been accepted into the program yet, we (Xfce) are applying to participate in the 2008 Google Summer of Code as a mentoring organisation. Please see our wiki page for more information, and add your name to the students list if you’d like to work on one of the projects. Feel free to add to the project ideas list as well.

If you’d like to act as a mentor, you still have a few more days before I submit the application. Add your name to the mentors list and email me to let me know.

The message is simple: if you’re a student that likes Xfce and would like to earn some money improving it over the summer, be sure to add your name to the list so Google can see there are students willing to participate, hopefully being a reason for approving Xfce.

If you own a personal website, a blog, or happen to know a student passionate about Xfce: spread the word! This is an excellent opportunity to improve upon our favourite desktop environment, so make sure Xfce can grab it!

Ubuntu Brainstorm is a new site that allows you to vote for improvements, features, ideas and fixes for Ubuntu. It is made in order to bridge the communication gap from the developers and users. From the article posted at The Fridge:

An idea on brainstorm can easily be linked to a Launchpad blueprint as well as to a bug or a forum discussion thread. In this way we expect to bridge the locations where ideas are often submitted now, as forum posts or bug reports, with the blueprint format they should be expressed in to be implemented.

Here are the current ideas for Xubuntu: http://brainstorm.ubuntu.com/search?keywords=Xubuntu&ordering=mostvotes

Do you have an idea that you’ve been itching to share with the developers, but didn’t know how? Now’s your chance to post it at the Brainstorm!

One of the best scripts for GNOME’s file manager Nautilus is audio-convert. audio-convert is a program that lets you convert mp3s to oggs, wavs, and vice versa. For me, it’s one of the main reasons I use Nautilus. Now, though, I can also use it with Thunar too. Here’s how:

1) If you haven’t already, install audio-convert. To do so, open up a terminal (Xfce Menu > Accessories > Terminal) and run the following:

sudo apt-get install nautilus-script-audio-convert

2) Next, open up the Thunar file manager and go to Edit > Configure custom actions…. Click the Add (plus) sign and put in the following:

a) Under the Basic tab:

Name: audio-convert
Command: /usr/share/nautilus-scripts/ConvertAudioFile %f

b) Under the Appearance Conditions tab:

Put a checkmark next to Audio files. Click Ok and exit out of the actions manager.

Now you can right click any audio file and go to audio-convert. audio-convert will do the work from there. Enjoy!

Rahul Sundaram has announced the release of a new Fedora spin with – you guessed it – Xfce!

Hello Friends,

I am pleased to announce the immediate release of a brand new and sparkling, Fedora 8 Xfce Spin. Fedora Xfce Spin is a bootable Fedora Live CD image available for x86 and x86_64 architecture. It can be optionally installed to hard disk or converted into boot USB images and is ideal for Xfce fans and for users running Fedora on relatively low resource systems. As a additional bonus, this release rolls in updates for Fedora 8 released till yesterday (2008/02/12).

Xfce is a lightweight desktop environment available in Fedora. Designed for productivity, it loads and executes applications fast, while conserving system resources. More information at http://xfce.org

Nicu has posted some screenshots, and it looks as if this spin-off is really focusing on being light-weight and minimalistic. Some Xubuntu users might want to give this a try – being based on Fedora might prevent the speed decrease Xubuntu has by being based on Ubuntu.

In any case, seeing another big distribution providing an Xfce version is always good news, so it will be interesting to read some reviews. Have you tried it? If so, how did you like it?

Windows is not really friendly towards other operating systems – when you installed it while another operating system is already installed, it will replace the bootloader with its own, without including any reference to that other operating system – preventing you from booting it. This is why it is often recommended to install Xubuntu after Windows. Sometimes, however, installed Windows afterwards is unavoidable. Restoring Xubuntu’s bootloader (GRUB) can be a pain.

Luckily, David Mooney comes to the rescue: in a post to the xubuntu-users mailinglist, he explains how to restore GRUB:

If for some odd reason you missed having the Windows operating system and you decided to install it on another partition, you will notice your GRUB is missing afterwords. This usually happens and is a huge headache for those trying to get their GRUB back. Here’s what you need to do to get it back:

Put your bootable Ubuntu/Xubuntu install disk in the CD drive and run it. Instead of installing anything, click on the menu to open the terminal application.

In terminal mode, type the following:

sudo grub
find /boot/grub/stage1
root (x,y)
setup (x)
quit
sudo shutdown "now" -r

The resulting “find” command will display something like (hd0,1). In this example, you would then type root (hd0,1) and then setup (hd0) in the above area. These numbers might be different; that’s why I included the “find” command so that folks who might have their Ubuntu partitions located either in front or behind their Windows installation or on a completely separate internal/external hard drive so that you will get the appropriate/correct setup numbers.

Ok, now you got your GRUB-on, but what about that darn GRUB menu? It’s not displaying what you want it to display? Well, let just see here…

Upon reboot, select “Recovery Mode”, usuaully the second option down on the GRUB menu. This will allow you to boot into the root. Once you’re in the terminal mode, type:

editor /boot/grub/menu.lst

Well, the rest is pretty much self explanatory. There should be enough comments in the menu.lst to direct you to what you can and cannot do to your GRUB menu.lst.

I usually put the Windows option at the top of the menu so that others (none-Linux users) who use my computer can find it easily if they have to do a reboot. Your Windows installation will have a different root than your Ubuntu/Xubuntu, but it’s usually automatically placed by GRUB once it’s set up again (like the above). I also recommend removing the timeout option as this is sometimes annoying. Have fun!

-David

P.S.- If you have a question, I’ll be happy to answer to the best of my ability.

Thanks David!

I for one got tired of having to type lame -b 128 etc, etc. into the terminal each time I wanted to change the quality of an mp3. Sure, there’s http://www.media-convert.com/ , but that lags our internet. So I whipped up this script. It has an installation guide for both Thunar and Nautilus and for me it works great.

Read the guide here: http://ubuntuforums.org/showthread.php?t=653006

Background: building on the best practice of cadence

The practice of regular releases, and now time-based releases, is becoming widespread within the free software community. From the kernel, to GNOME and KDE, to X, and distributions like Ubuntu, Fedora, the idea of a regular, predictable cycle is now better understood and widely embraced. Many smarter folks than me have articulated the benefits of such a cadence: energising the whole community, REALLY releasing early and often, shaking out good and bad code, rapid course correction.

There has been some experimentation with different cycles. I’m involved in projects that have 1 month, 3 month and 6 month cycles, for different reasons. They all work well.

..but addressing the needs of the longer term

But there are also weaknesses to the six-month cycle:

• It’s hard to communicate to your users that you have made some definitive, significant change,
• It’s hard to know what to support for how long, you obviously can’t support every release indefinitely.

I think there is growing insight into this, on both sides of the original “cadence” debate.

A tale of two philosophies, perhaps with a unifying theory

A few years back, at AKademy in Glasgow, I was in the middle of a great discussion about six month cycles. I was a passionate advocate of the six month cycle, and interested in the arguments against it. The strongest one was the challenge of making “big bold moves”.

“You just can’t do some things in six months” was the common refrain. “You need to be able to take a longer view, and you need a plan for the big change.” There was a lot of criticism of GNOME for having “stagnated” due to the inability to make tough choices inside a six month cycle (and with perpetual backward compatibility guarantees). Such discussions often become ideological, with folks on one side saying “you can evolve anything incrementally” and others saying “you need to make a clean break”.

At the time of course, KDE was gearing up for KDE 4.0, a significant and bold move indeed. And GNOME was quite happily making its regular releases. When the KDE release arrived, it was beautiful, but it had real issues. Somewhat predictably, the regular-release crowd said “see, we told you, BIG releases don’t work”. But since then KDE has knuckled down with regular, well managed, incremental improvements, and KDE is looking fantastic. Suddenly, the big bold move comes into focus, and the benefits become clear. Well done KDE

On the other side of the fence, GNOME is now more aware of the limitations of indefinite regular releases. I’m very excited by the zest and spirit with which the “user experience MATTERS” campaign is being taken up in Gnome, there’s a real desire to deliver breakthrough changes. This kicked off at the excellent Gnome usability summit last year, which I enjoyed and which quite a few of the Canonical usability and design folks participated in, and the fruits of that are shaping up in things like the new Activities shell.

But it’s become clear that a change like this represents a definitive break with the past, and might take more than a single six month release to achieve. And most important of all, that this is an opportunity to make other, significant, distinctive changes. A break with the past. A big bold move. And so there’s been a series of conversations about how to “do a 3.0″, in effect, how to break with the tradition of incremental change, in order to make this vision possible.

It strikes me that both projects are converging on a common set of ideas:

• Rapid, predictable releases are super for keeping energy high and code evolving cleanly and efficiently, they keep people out of a deathmarch scenario, they tighten things up and they allow for a shakeout of good and bad ideas in a coordinated, managed fashion.

• Big releases are energising too. They are motivational, they make people feel like it’s possible to change anything, they release a lot of creative energy and generate a lot of healthy discussion. But they can be a bit messy, things can break on the way, and that’s a healthy thing.

Anecdotally, there are other interesting stories that feed into this.

Recently, the Python community decided that Python 3.0 will be a shorter cycle than the usual Python release. The 3.0 release is serving to shake out the ideas and code for 3.x, but it won’t be heavily adopted itself so it doesn’t really make sense to put a lot of effort into maintaining it - get it out there, have a short cycle, and then invest in quality for the next cycle because 3.x will be much more heavily used than 3.0. This reminds me a lot of KDE 4.0.

So, I’m interesting in gathering opinions, challenges, ideas, commitments, hypotheses etc about the idea of meta-cycles and how we could organise ourselves to make the most of this. I suspect that we can define a best practice, which includes regular releases for continuous improvement on a predictable schedule, and ALSO defines a good practice for how MAJOR releases fit into that cadence, in a well structured and manageable fashion. I think we can draw on the experiences in both GNOME and KDE, and other projects, to shape that thinking.

This is important for distributions, too

The major distributions tend to have big releases, as well as more frequent releases. RHEL has Fedora, Ubuntu makes LTS releases, Debian takes cadence to its logical continuous integration extreme with Sid and Testing :-).

When we did Ubuntu 6.06 LTS we said we’d do another LTS in “2 to 3 years”. When we did 8.04 LTS we said that the benefits of predictability for LTS’s are such that it would be good to say in advance when the next LTS would be. I said I would like that to be 10.04 LTS, a major cycle of 2 years, unless the opportunity came up to coordinate major releases with one or two other major distributions - Debian, Suse or Red Hat.

I’ve spoken with folks at Novell, and it doesn’t look like there’s an opportunity to coordinate for the moment. In conversations with Steve McIntyre, the current Debian Project Leader, we’ve identified an interesting opportunity to collaborate. Debian is aiming for an 18 month cycle, which would put their next release around October 2010, which would be the same time as the Ubuntu 10.10 release. Potentially, then, we could defer the Ubuntu LTS till 10.10, coordinating and collaborating with the Debian project for a release with very similar choices of core infrastructure. That would make sharing patches a lot easier, a benefit both ways. Since there will be a lot of folks from Ubuntu at Debconf, and hopefully a number of Debian developers at UDS in Barcelona in May, we will have good opportunities to examine this opportunity in detail. If there is goodwill, excitement and broad commitment to such an idea from Debian, I would be willing to promote the idea of deferring the LTS from 10.04 to 10.10 LTS.

Questions and options

So, what would the “best practices” of a meta-cycle be? What sorts of things should be considered in planning for these meta-cycles? What problems do they cause, and how are those best addressed? How do short term (3 month, 6 month) cycles fit into a broader meta-cycle? Asking these questions across multiple communities will help test the ideas and generate better ones.

What’s a good name for such a meta-cycle? Meta-cycle seems…. very meta.

Is it true that the “first release of the major cycle” (KDE 4.0, Python 3.0) is best done as a short cycle that does not get long term attention? Are there counter-examples, or better examples, of this?

Which release in the major cycle is best for long term support? Is it the last of the releases before major new changes begin (Python 2.6? GNOME 2.28?) or is it the result of a couple of quick iterations on the X.0 release (KDE 4.2? GNOME 3.2?) Does it matter? I do believe that it’s worthwhile for upstreams to support an occasional release for a longer time than usual, because that’s what large organisations want.

Is a whole-year cycle beneficial? For example, is 2.5 years a good idea? Personally, I think not. I think conferences and holidays tend to happen at the same time of the year every year and it’s much, much easier to think in terms of whole number of year cycles. But in informal conversations about this, some people have said 18 months, others have said 30 months (2.5 years) might suit them. I think they’re craaaazy, what do you think?

If it’s 2 years or 3 years, which is better for you? Hardware guys tend to say “2 years!” to get the benefit of new hardware, sooner. Software guys say “3 years!” so that they have less change to deal with. Personally, I am in the 2 years camp, but I think it’s more important to be aligned with the pulse of the community, and if GNOME / KDE / Kernel wanted 3 years, I’d be happy to go with it.

How do the meta-cycles of different projects come together? Does it make sense to have low-level, hardware-related things on a different cycle to high-level, user visible things? Or does it make more sense to have a rhythm of life that’s shared from the top to the bottom of the stack?

Would it make more sense to stagger long term releases based on how they depend on one another, like GCC then X then OpenOffice? Or would it make more sense to have them all follow the same meta-cycle, so that we get big breakage across the stack at times, and big stability across the stack at others?

Are any projects out there already doing this?

Is there any established theory or practice for this?

A cross-community conversation

If you’ve read this far, thank you! Please do comment, and if you are interested then please do take up these questions in the communities that you care about, and bring the results of those discussions back here as comments. I’m pretty sure that we can take the art of software to a whole new level if we take advantage of the fact that we are NOT proprietary, and this is one of the key ways we can do it.

Notify-OSD handles both application notifications and keyboard special keys like brightness and volume

MPT has posted an overview of the conceptual framework for “attention management” at https://wiki.ubuntu.com/NotificationDesignGuidelines, which puts ephemeral notification into context as just one of several distinct tools that applications can use when they don’t have the focus but need to make users aware of something. That’s a draft, and when it’s at 1.0 we’ll move it to a new site which will host design patterns on Canonical.com.

There is also a detailed specification for our implementation of the notification display agent, notify-osd, which can be found at https://wiki.ubuntu.com/NotifyOSD and which defines not only the expected behaviour of notify-osd but also all of the consequential updates we need to make across the packages in main an universe to ensure that those applications use notification and other techniques consistently.

There are at least 35 apps that need tweaking, and there may well be others! If you find an app that isn’t using notifications elegantly, please add it to the notification design guidelines page, and if you file a bug on the package, please tag it “notifications” so we can track these issues in a single consistent way.

Together with notify-osd, we’ve uploaded a new panel indicator which is used to provide a way to respond to messaging events, such as email and IRC pings. If someone IM’s you, then you should see an ephemeral notification, and the messaging indicator will give you a way to respond immediately. Same for email. Pidgin and Evolution are the primary focuses of the work, over time we’ll broaden that to the full complement of IM and email apps in the archive - patches welcome

There will be rough patches. Apps which don’t comply with the FreeDesktop.org spec and send actions on notifications even when the display agent says it does not support them, will have their notifications translated into alerts. That’s the primary focus of the effort now, the find and fix those apps. Also, we know there are several cases where a persistent response framework is required. The messaging indicator gets most of them, we will have additional persistent tools in place for Karmic in October.

Now that the ISS has the capacity for a larger full-time crew, the seats are more likely to be devoted to long-duration ISS crew rotation than short-term ISS visits, whether visits by professional EU / US astronauts or folks flying privately. I’ve no doubt that there are economics attached to the Russian seats that are similar for both cases - the EU and US have to pay for the lift just like us ordinary folks.

There are a couple of interesting twists to the story.

One is that, when the Shuttle is retired, the Russians will have the only manned access to orbital flight in the ISS partnership. Russia and China will be the only nations with manned orbital capabilities, and the US huffishly refuses to welcome China into the ISS club. Expect the price of a seat to rise substantially while that’s the case.

Another is the EU’s plan to evolve their autonomous cargo vessel (ATV) into a manned capability, something that’s perfectly feasible and quite sensible IMO.

And the third twist is that the Russians have long been open to commercial offers for a long-duration flight (six month ISS crew rotation). That woudl require substantially more training (12-18 months minimum depending on who you ask) but would certainly include the Soyuz lift to get there and back.

See the mockup as a Flash movie.

There are some fairly bold (read: controversial) ideas that we’d like to explore with, so the opportunity to discuss them with a broader cross-section of the community was fantastic. There were several rough edges and traps that I think we’ll avoid in the first round as a result, thanks to everyone who participated. Some of the things we work on in these teams are done directly with partners for their devices, so they don’t see this level of discussion before they ship, but it’s wonderful when we do get the opportunity to do so.

Some of these ideas are unproven, they boil down to matters of opinion, but since our commitment to them is based on a desire to learn more I think of them as constructive experiments. Experiments are just that - experiments. They may succeed and they may fail. We should judge them carefully, after we have data. We are putting new ideas into the free desktop without ego. We know those ideas could be better or worse than similar work being done in other communities, and we want to gather real user feedback to help find the best mix for everyone. The best ideas, and the best code, will ultimately form part of the digital free software commons and be shared by GNOME, KDE and every distribution. So, for those folks who were upset that we might ship something other than a GNOME or KDE default, I would ask for your patience and support - we want to contribute new ideas and new code, and that means having some delta which can be used as a basis for discussions about the future direction of upstream. In the past, we’ve had a few such delta’s in Ubuntu. Some, like the current panel layout, were widely embraced. Others, like the infamous “Ubuntu spacial mode”, were not. C’est la vie, and we all benefit from the evolution.

Experiments are also not something we should do lightly. The Ubuntu desktop is something I take very personally; I feel personally responsible for the productivity and happiness of every Ubuntu user, so when we bring new ideas and code to the desktop I believe we should do everything we can to make sure of success first time round. We should not inflict bad ideas on our users just because we’re curious or arrogant or stubborn or proud. Despite being occasionally curious, arrogant, stubborn and proud

So, what are we proposing?

First, we are focusing some attention on desktop notifications in this cycle, as part of a broader interest in the “space between applications”.

I think Canonical and Ubuntu can best help the cause of free software by focusing on the cracks between the major components of the desktop. In other words, while there are already great upstreams for individual applications in the free software desktop (Novell for Evolution, Sun for OpenOffice, Mozilla for Firefox, Red Hat for NetworkManager), we think there is a lot of productive and useful work to be done in the gaps between them. Notifications are things that many apps do, and if we can contribute new ideas there then we are helping improve the user experience of all of those applications. That’s a nice force multiplier - we’re hopefully doing work that makes the work of every other community even more valuable.

Nevertheless, expect bumps ahead. Ideas we are exploring may / will / do conflict with assumptions that are present today in various applications. We can address the relevant code in packages in main, but I’m more focused on addressing the potential social disruption that conflict can create, and that’s more a matter of conversation than code.

Notifications are interesting, subtle and complex. There are lots of different approaches on lots of different platforms. There are lots of different use cases. We’re trying to simplify and eliminate complexity, while still making it possible to meet the use cases we know about.

There has been good work in the freedesktop.org community on notifications, and even a spec that is *almost* at 1.0 in that community, with existing open source implementations. Our proposal is based on that specification, but it deprecates several capabilities and features in it. We will likely be compatible with the current API’s for sending notifications, but likely will not display all the notifications that might be sent, if they require features that we deprecate. If this experiment goes well, we would hope to help move that FD.o specification to 1.0, with or without our amendments.

The key proposals we are making are that:

• There should be no actions on notifications.
• Notifications should not be displayed synchronously, but may be queued. Our implementation of the notification display daemon will display only one notification at a time, others may do it differently.

That’s pretty much it. There are some subtleties and variations, but these are the key changes we are proposing, and which we will explore in a netbook device with a partner, as well as in the general Ubuntu 9.04 release, schedule gods being willing.

This work will show up as a new notification display agent, not as a fork or patch to the existing GNOME notification daemon. We don’t think the client API - libnotify - needs to be changed for this experiment, though we may not display notifications sent through that API that use capabilities we are suggesting be deprecated. We will try to ensure that packages in main are appropriately tuned, and hope MOTU will identify and update key packages in universe accordingly.

Why a completely new notification display agent? We are designing it to be built with Qt on KDE, and Gtk on GNOME. The idea is to have as much code in common as we can, but still take advantage of the appropriate text display framework on Ubuntu and Kubuntu. We hope to deliver both simultaneously, and have discussed this with both Ubuntu and Kubuntu community members. At the moment, there is some disagreement about the status of the FD.o specification between GNOME and KDE, and we hope our efforts will help build a bridge there. In Ubuntu 9.04, we would likely continue to package and publish the existing notification daemon in addition, to offer both options for users that have a particular preference. In general, where we invest in experimental new work, we plan to continue to offer a standard GNOME or KDE component / package set in the archive so that people can enjoy that experience too.

The most controversial part of the proposal is the idea that notifications should not have actions associated with them. In other words, no buttons, sliders, links, or even a dismissal [x]. When a notification pops up, you won’t be able to click on it, you won’t be able to make it go away, you won’t be able to follow it to another window, or to a web page. Are you loving this freedom? Hmmm? Madness, on the face of it, but there is method in this madness.

Our hypothesis is that the existence of ANY action creates a weighty obligation to act, or to THINK ABOUT ACTING. That make notifications turn from play into work. That makes them heavy responsibilities. That makes them an interruption, not a notification. And interruptions are a bag of hurt when you have things to do.

So, we have a three-prong line of attack.

1. We want to make notifications truly ephemeral. They are there, and then they are gone, and that’s life. If you are at your desktop when a notification comes by, you will sense it, and if you want you can LOOK at it, and it will be beautiful and clear and easy to parse. If you want to ignore it, you can safely do that and it will always go away without you having to dismiss it. If you miss it, that’s OK. Notifications are only for things which you can safely ignore or miss out on. If you went out for coffee and a notification flew by, you are no worse off. They don’t pile up like email, there is no journal of the ones you missed, you can’t scroll back and see them again, and therefor you are under no obligation to do so - they can’t become work while you are already busy with something else. They are gone like a mystery girl on the bus you didn’t get on, and they enrich your life in exactly the same way!
2. We think there should be persistent panel indicators for things which you really need to know about, even if you missed the notification because you urgently wanted that coffee. So we are making a list of those things, and plan to implement them.
3. Everything else should be dealt with by having a window call for attention, while staying in the background, unless it’s critical in which case that window could come to the foreground.

Since this is clearly the work of several releases, we may have glitches and inconsistencies along the way at interim checkpoints. I hope not, but it’s not unlikely, especially in the first iteration. Also, these ideas may turn out to be poor, and we should be ready to adjust our course based on feedback once we have an implementation in the wild.

We had a superb UXD and DEE (user experience design team, and desktop experience engineering team) sprint in San Francisco the week before UDS. Thanks to everyone who took part, especially those who came in from other teams. This notifications work may just be the tip of the iceberg, but it’s a very cool tip

One or more of our early-access OEM partners (companies that we work with on new desktop features) will likely ship this feature as part of a netbook product during the 9.04 cycle. At that point, we would also drop the code into a PPA for testing with a wider set of applications. There are active discussions about updating the freedesktop.org specification based on this work. I think we should be cautious, and gather real user testing feedback and hard data, but if it goes well then we would propose simplifying the spec accordingly, and submit our notification display agent to FreeDesktop.org. Long term collaboration around the code would take place on Launchpad.

In the design discussions, we spent a lot of time working on a new approach to “dialog boxes, wizards and workflows”, trying to solve a thorny problem in user interaction: how do you make it easy to do something complex? There are lots of cases in Launchpad where you need to get lots of ducks in a row before you can do something. For example, you might need to make sure there is a team with specific people in it before you subscribe that team to a bug. Or you might need to create a new milestone while triaging and scheduling work on bugs in your project.

Currently, that means jumping all around Launchpad in a way that assumes you know exactly how those pieces work. You need to go to one place to register a team, and a completely different place to setup a milestone. That means that lots of people don’t use capabilities in Launchpad, because they need to understand the whole system before they can get something small done. Every time someone bumps their head on that, we fail! And that’s the problem we set out to solve.

We came up with a nifty approach, which we call morphing dialogs, that ensures the user always has the minimum number of choices to make, and still allows for complex variations on a process in a way that feels quite natural for users.

The key ideas behind morphing dialogs are:

• Only show one primary decision at a time, and make it obvious what that is. Sometimes, there are several directions you could take in order to get something done, but there is usually a single normal path for users to follow, and we always want users to be able to do the easy things easily.
• Give users a sense of how far they are in the process, but don’t be too dogmatic about that, since getting one thing done often involves stepping off to the side to take care of preliminary business and those detours can also require several steps.

Here’s an example movie, which shows a person linking a blueprint to a bug. They need to search for the right blueprint, which they can do across a couple of projects simultaneously. In this mockup, they add GNOME to the list of projects that they look for the blueprint in, and when they can’t find it, they go to register a new blueprint for what they want. In the end he decides to go back and pick one from the search results. None of this involved a page load, and the round trips to the server are much cheaper than loading full pages, since we can just get what we need in highly optimized way.

You can see a couple of the key ideas coming through in the movie.

Note the “progress bar” - the green line - is not particular large or obtrusive. It’s also not obviously a progress bar, until one has done a few multi-step processes. Note also that you can have detours; you can step off to one side to get something done, like register a team or register a new blueprint, and those detours get their own progress indicator which is separate from the main one.

We had a major sprint recently that brought the whole Launchpad team together for two weeks while we did a deep dive into JavaScript and AJAX. We picked YUI 3, the next version of Yahoo’s UI toolkit for the web, as a foundational layer for this AJAX effort, and we wanted to bring everyone up to speed on the processes for designing, building and testing web client apps. It was a lot of fun.

In particular, we wanted to unify the web service API’s that we already publish with this AJAX work, so that it would be easy to write web browser code that could talk to the exact same API’s we publish for developers who are integrating with Launchpad. That’s now possible, which means that any API we use for AJAX work will also be available to developers writing their own tools to access Launchpad directly through the web services.

Thanks to the awesomeness of YUI 3, the team is now hard at work turning those ideas into reality. Given that YUI 3 is right on the cutting edge (some would say bleeding edge!) we’re focusing on pieces that don’t depend on complex widgets - those will only start to fall into place next year as YUI 3 emerges from development.

Over the next couple of months you will see pieces of this puzzle land in successive Launchpad monthly releases (or daily, if you’re on edge.launchpad.net and a beta tester). Initially, the AJAX bling will just enable inline editing. In six to nine months, the more complex pieces should have land. And by then Launchpad’s web front-end will also be open source.

I certainly hope not.

I think a world without regulated capitalism would be a bleak one indeed. I had the great privilege to spend a year living in Russia in 2001/2002, and the visible evidence of the destruction wrought by central planning was still very much present. We are all ultimately human, with human failings, whether we work for a state planning agency or a private company, and those failings have consequences either way. To think that moving all private enterprise into state hands will somehow create a panacea of efficiency and sustainability is to ignore the stark lessons of the 20th century.

The leaders and decision makers in a centrally-planned economy are just as fallible as those in a capitalist one - they would probably be the same people! But state enterprises lack the forces of evolution that apply in a capitalist economy - state enterprises are rarely if ever allowed to fail. And hence bad ideas are perpetuated indefinitely, and an economy becomes dysfunctional to the point of systemic collapse. It is the fact that private enterprises fail which keeps industries vibrant. The tension between the imperative to innovate and the consequences of failure drives capitalist economies to evolve quickly. Despite all of the nasty consequences that we have seen, and those we have yet to see, of capitalism gone wrong, I am still firmly of the view that society must tap into its capitalist strengths if it wants to move forward.

But I chose my words carefully when I said “regulated capitalism”. I used to be a fan of Adam Smith’s invisible hand, and great admirer of Ayn Rand’s vision. Now, I feel differently. Left to it’s own devices, the market will tend to reinforce the position of those who were successful in the past, at the exclusion of those who might create future successes. We see evidence of this all the time. The heavyweights that define an industry tend to do everything in their power to prevent innovation from changing the rules that enrich them.

A classic example of that is the RIAA’s behaviour - in the name of “saving the music industry” they have spent the past ten years desperately trying to keep it in the analog era to save their members, with DRM and morally unjustifiable special-interest lobbying around copyright rules that affect the whole of society.

Similarly, patent rules tend to evolve to suit the companies that hold many patents, rather than the people who might generate the NEXT set of innovative ideas. Of course, the lobbying is dressed up in language that describes it as being “in the interests of innovation”, but at heart it is really aimed at preserving the privileged position of the incumbent.

In South Africa, the incumbent monopoly telco, which was a state enterprise until it was partially privatized in 1996, has systematically delayed, interfered, challenged and obstructed the natural process of deregulation and the creation of a healthy competitive sector. Private interests act in their own interest, by definition, so powerful private interests tend to drive the system in ways that make THEM healthier rather than ways that make society healthier.

Left to their own devices, private companies will tend to gobble one another up, and create monopolies. Those monopolies will then undermine every potential new entrant, using whatever tactics they can dream up, from FUD to lobbying to thuggery.

So, I’m a fan of regulated capitalism.

We need regulation to ensure that society’s broader needs, like environmental sustainability, are met while private companies pursue their profits. We also need regulation to ensure that those who manage national and international infrastructure, whether it’s railways or power stations or financial systems, don’t cook the books in a way that lets them declare fat profits and fatter bonuses while driving those systems into crisis.

But effective regulation is not the same as state management and supervision. I would much rather have private companies managing power stations competitively, than state agencies doing so as part of a complacent government monopoly.

Good regulation is very hard. Over the years I’ve interacted with a few different regulatory authorities, and I sympathise with the problems they encounter.

First, to be an effective regulator, you need superb talent. And for that you need to pay - talent follows the money and the lights, whether we like it or not, so to design a system on other assumptions is to design it for failure. My ideal regulator is an insightful genius working for the common good, but since I’m never likely to meet that person, a practical goal is to encourage regulators to be small but very well funded, with key salaries and performance measures that are just behind the industries they are supposed to regulate. Regulators must be able to be fired - no sense in offering someone a private sector salary and public sector accountability. Unfortunately, most regulators end up going the other way, hiring more and more people of average competence, that they become both expensive and ineffective.

Second, a great regulator needs to be independent. You’re the guy who tells people to stop doing what will hurt society; it’s very hard to do that to your friends. A regulatory job is a lonely job, which is why you hear so many stories of regulators being wined and dined by the industries they regulate only to make sure they don’t look too hard in the back room. A great regulator needs to know a lot about an industry, but be independent of that industry. Again, my ideal is someone who has made a good living in a sector, knows it backwards, can justify their high price, but wants to make a contribution to society.

Third, a great regulator needs to have teeth and muscle. It has been very frustrating for me to watch the South African telecomms regulator get tied up in court by Telkom, and stymied by government department inadequacy. Regulators need to be able to drive things forward, they need to be able to change the way companies behave, and they cannot rely on moral suasion to do so.

And fourth, a regulator has to make very tough decisions about innovation, which amount to venture capital decisions - to make them well, you have to be able to tell the future. For example, when an industry changes, as all industries change, how should the rules evolve? When a new need for society is identified, like the need to address climate change early and systemically, how should the rules evolve? Regulators need to move forward as fast as the industries they regulate, and they need to make decisions about things we don’t yet understand. And even when you regulate, you may not be able to stop an impending crisis. It’s very easy to criticize Greenspan for his light touch regulation on hedge funds and derivatives today, but it’s not at all clear to me that regulation would have made a difference, I think it would simply have moved the shadow global financial system offshore.

So regulation is extremely difficult, but also very much worth investing in if you are trying to run a healthy, vibrant, capitalist society.

Coming back to the original suggestion that sparked this blog - I’m sure we will see a lot of failed capitalists in the future. Hell, I might join their ranks, I wouldn’t be the first ;-). But that doesn’t spell the end of capitalism, only the opportunity to start again - smarter.

Here is a screenshot of the work itself in action:

New FUSA applet allows you to mange your presence setting, as well as switch to a guest or other user, and logout

In one of the first user experience sessions, we looked in more detail at the way people “stop working”. We thought it interesting to try and group those actions together in a way which would feel natural to users.

We have already done some work in Ubuntu around this - for a long time we have had a button in the top-right corner of the panel which brought up a system modal dialog that gave you the usual “end your session” options of logout, restart, shutdown, hibernate, suspend and switch user. That patch was always a bit controversial and had not been accepted upstream, so we looked at ways to solve the problem differently.

We decided to use the top-right location, because it’s one of the key places in the screen that’s quick and easy to get to (you can throw your mouse into a corner of the screen very easily and accurately) and because there was a strong precedent in the old Ubuntu logout button.

One key insight was that we wanted to make “switching user” less an exercise in guesswork and more direct - we wanted to let people switch directly to the specific user they were interested in rather than have an intermediate step where they login as that other user. So we started with the Fast User Switcher applet, or FUSA, as a base fr the design. Another key idea that emerged was that we wanted to integrate the “presence setting” into the same menu, because “going offline” or “I’m busy” are similar state-of-mind-and-work decisions to “log me off the system” or “shut down”.

Menu order
We discussed at length the right order for the menu items. On the one hand, putting the “other users” at the top of the menu would mean that all the user names - yours and the ones you can switch to - would appear “in the same place” at the top of the menu. On the other, we strongly felt that things that would be used more casually and more easily should be at the top. In the end we settled on putting the presence management options at the top (Available, Away, Busy, Offline). Right next to those (in the same set) we put the “Lock screen” option, because it feels like a presence setting more than a session management setting - you are saying “Away” more than anything else.

Ted did a lot of work to make the presence menu elements work with both Pidgin and Empathy because there was some uncertainty as to which would be used by default in the release. Since it all uses dbus, it should be straightforward to make it work with KDE IM clients too.

We then put the user switching options - including the Guest Session which is a cool new feature in Intrepid that as been widely blogged (check out the YouTube demo) and which uses AppArmor to enforce security.

And finally, the session termination options - log out, suspend, hibernate, restart and shutdown are at the bottom of the menu, because you’re only ever likely to use them once in a session, by definition!

Styling
The design of the menu is deliberately clean. We use very simple colours and shapes for the presence indicators, and replicate those colours and shapes in the actual GNOME panel so that you can see at a glance what your current presence setting is. Ted had to jump through some hoops, I think, to get the presence icons in the menu to line up with the current-presence-status indicator in the panel applet, but it worked out quite nicely. There’s some additional work to tighten up the layout which didn’t make it in time for the release but which might come in as a stable release update (SRU) or in Jaunty.

We decided not to put icons into the menu for each of the different statuses. Our design ethic is to aim for cleaner, less cluttered layouts with fewer icons and better choice of text. A couple of people have said that the menu looks “sparse” or “bare” but I think it sets the right direction and we’ll be continuing with this approach as we touch other parts of the system.

Upstream
This work was discussed at UDS in Prague with a number of members of the GNOME community. I was also very glad to see that there’s a lot of support for a tighter, simpler panel at the GNOME hackfest, an idea that we’ve championed. The FUSA applet itself is going through a bit of a transformation upstream as it’s been merged into the new GDM codebase and the old code - on which our work is based - is more or less EOL’d. But we’ll figure out how to update this work for Jaunty and hopefully it will be easier to get it upstreamed at that point.

In Jaunty, we’ll likely do some more work on the GNOME panel, building on the GNOME user experience discussions. There was a lot of discussion about locking down the panel more tightly, which we may pursue.

Integration into Ubuntu
We realised rather late in the Ubuntu cycle that we hadn’t thought much about packaging. The Ubuntu team had kindly offered to help package and integrate the applet but we definitely learned the value of getting the packaging done earlier rather than later. We had the applet in a PPA for testing between developers fairly early, but we underestimated the difference between that and actual integration into the release.

The Ubuntu team rallied to the cause and helped to smooth the upgrade process for new users, so that we can try to get everyone onto the same footing when they start out with Intrepid whether as a new install or an upgrade. There are some challenges there, because the panel is so customisable, and we had to think hard about how we could ensure there was a consistent experience for something as important as logging out or shutting down while at the same time trying not to stomp on the preferences of folks who have customised their panels. Similarly, we were concerned that people who run different versions of Ubuntu, or different distributions entirely, with the same home directory, would have problems if those other OS’s didn’t have the same version of FUSA - we weren’t really able to address that satisfactorily.

We also realised (DOH!) that we hadn’t thought all the way through the process of integration, because we hadn’t figured out what to do with the old System menu options. It turned out that those were in a state of flux, with the Ubuntu folks having to choose between the current GNOME default which everyone said would change, the patches for the likely NEXT GNOME approach, and the old Ubuntu approach. Ted whipped up some patches to make the GNOME panel more dynamic with its menus, so that we could remove the System menu logout options when people have the same menu in the FUSA applet, but that landed too late for inclusion into Intrepid final.

All in all, I think it’s a neat piece of work and hope other distro’s find it useful too. It’s just a teaser of the work we plan to do around the desktop experience. I’m looking forward to seeing everyone at UDS Jaunty in Mountain View in December, when we can talk about the next round! Thanks and well done to Ted, Martin, Scott, Sebastien and everyone else who helped to make this a reality.

Well done to Team Ubuntu (thousands of people across Ubuntu, Debian and upstreams) who make the magic in 8.10 possible. Happy Release Day everyone!

Though there wasn’t a lot of hacking, there was a LOT of discussion, and we covered a lot of ground. There were at least 7 Canonical folks there, so it was a bit of a mini-sprint and a nice opportunity to meet the team at the same time. We had great participation from a number of organisations and free spirits, there’s a widespread desire to see GNOME stay on the forefront of usability.

Neil Patel of Canonical did a few mockups to try and capture the spirit of what was discussed, but I think the most interesting piece wasn’t really possible to capture in a screenshot because it’s abstract and conceptual - file and content management. There’s a revolution coming as we throw out the old “files and folders” metaphor and leap to something new, and it would be phenomenal if free software were leading the way.

I was struck by the number of different ways this meme cropped up. We had superb presentations of “real life support problems” from a large-scale user of desktop Linux, and a persistent theme was “where the hell did that file just go?” People save an attachment they receive in email, and an hour later have no idea where to find it. They import a picture into F-spot and then have no idea how to attach it to an email. They download a PDF from the web, then want to read it offline and can’t remember where they put it. Someone else pointed out that most people find it easier to find something on the Internet - through Google - than they do on their hard drives.

The Codethink guys also showed off some prototype experience work with Wizbit, which is a single-file version control system that draws on both Git and Bazaar for ideas about how you do efficient, transparent versioning of a file for online and offline editing.

We need to rearchitect the experience of “working with your content”, and we need to do it in a way that will work with the web and shared content as easily as it does locally.

My biggest concern on this front is that it be done in a way that every desktop environment can embrace. We need a consistent experience across GNOME, KDE, OpenOffice and Firefox so that content can flow from app to app in a seamless fashion and the user’s expectations can be met no matter which app or environment they happen to use. If someone sends a file to me over Empathy, and I want to open it in Amarok, then I shouldn’t have to work with two completely different mental models of content storage. Similarly, if I’ve downloaded something from the web with Firefox, and want to edit it in OpenOffice, I shouldn’t have to be super-aware or super-smart to be able to connect the apps to the content.

So, IMO this is work that should be championed in a forum like FreeDesktop.org, where it can rise above some of the existing rivalries of desktop linux. There’s a good tradition of practical collaboration in that forum, and this is a great candidate for similar treatment.

At the end of the day, bling is less transformational than a fundamental shift in content management. Kudos to the folks who are driving this!

Update: thanks mjg59 for pointing out my thinko. The Collabora guys do great stuff, but Codethink does Wizbit.

The term “credit crunch” is very misleading for the current crisis. It suggests that the problem is merely one of confidence, that calm will return if liquidity is introduced to the system.

My view, though, is that the real issue is one of solvency. This is the systemic bankruptcy of 2008.

Mortgages are just the beginning.
At real rates of interest, with real expectations of a reasonable rate of return, many of the deals which have been done since 2003 just do not make economic sense. Thus far, the spotlight has been on one piece of that problem - bad mortgage loans - but I think we’ll see the problem areas expanding rapidly to include a lot of the private equity deals which were done on the basis of free money between 2003-2007. I remember a fatuous statement by some private equity genius that “everybody’s rushing to do the first $100bn deal”. Well, the chickens are coming home to roost. Expect a steady flood of announcements of setbacks, restructurings and bankruptcies as companies that were bought with borrowed money turn out to be unable to service their debt.

Lower interest rates will ease the symptoms only.
Dramatic easing of interest rates will help to slow down the pace at which we have to deal with the bankruptcies, but they won’t change the cold reality of the situation, and they run the very real risk of making things worse by encouraging another round of speculation based on free money. We are once again in a situation where the US discount rate is effectively a negative real rate of interest, as a gift to the banks, but staying there for any length of time puts us back into a state of addiction.

Interventions must target bank equity and leverage, not liquidity.
The latest move from the UK to buy equity stakes is the best response yet, I think. It dramatically improves the capitalisation of those institutions, it keeps the upside of that move in taxpayers hands (they are taking the pain and funding the bailout, it seems right to preserve the upside for them) and it dilutes the existing shareholders who allowed their institutions to become insolvent. Personally, I’d be inclined to do more than dilute those shareholders.

I don’t see the current $700bn deal making a real difference to US banks. I would expect the US to announce a deal similar to the UK deal soon, but the numbers would have to be larger. Scarily large. Much better for the US to make that move, than to wait for Asian and Middle-eastern sovereign wealth funds to step into the breach.

Depositors in regulated banks should be protected by the governments that run the regulators. Shareholders not so much. Bondholders… maybe.
I think the Irish and other countries who have guaranteed the deposits of individual users have done the right thing. Governments setup regulatory authorities, and banks advertise that they are regulated. The people who appoint those regulators need to stand by the approach they take - they should offer a guarantee that they will stand by their product, and when it fails, they will stand by the people who trusted in them. Depositors at banks in the UK really should not have to worry that the bank might fail - such a failure should at most affect the interest rate they receive, not the safety of their capital. Shareholders in those banks, however, should be very worried indeed. There’s an interesting question about bondholders and institutional depositors. By one argument they are sophisticated investors and should be responsible for their bonds. By another argument, they are the very people who can cause massive shifts in funds from bank paper to T-bills, and hence worth keeping pacified. I would lump them in with individual depositors too.

Executive compensation should be structured not fixed.
There has been a lot of discussion about limiting executive compensation. That’s just an invitation for armies of consultants and lawyers and accountants to work around whatever compensation limits are put in place. And frankly, I’m hard-pressed to understand how politicians, who constantly vote themselves bigger salaries and expense accounts, are qualified to set bank executive salaries. They effectively WERE in charge of Fannie and Freddie executive compensation, and that wasn’t a stellar success.

What I would say, however, is that financial institution earnings should only be recognised over a seven year period, and bonuses based on those earnings should be held in escrow until that seven year period is up. Imagine if we could now tap into the bonuses of investment bank employees over the past seven years in order to shore up the balance sheets of those banks. That would include the bonuses paid to Mr Fuld, Mr Greenberg, and Mr Greenspan. Anybody care to run the numbers? I think it would be material.

I’m nervous.
The big question I’m asking is which sidelines don’t have landmines? My team and I are fortunate to have stepped out of many markets before the current flood of fear. We stepped right into a few problems, but in large part dodged the cannonballs. So far so good. But what does it mean to have cash in the bank, when banks themselves are failing? What does it mean to hold dollars, when the dollar is being debased in a way that would feel familiar to the Reserve Bank of Zimbabwe? These are very dangerous times, and nobody should think otherwise.]]> http://www.markshuttleworth.com/archives/220 http://feedproxy.google.com/~r/XubuntuBlogroll/~3/p8OnnATN9JI/162 Canonical is building a design and user experience team, with engineering resources for upstream development to turn their ideas into code. http://www.markshuttleworth.com/?p=162 Wed, 10 Sep 2008 08:29:06 -0700 When you present yourself on the web, you have 15 seconds to make an impression, so aspiring champions of the web 2.0 industry have converged on a good recipe for success:

1. Make your site visually appealing,
2. Do something different and do it very, very well,
3. Call users to action and give them an immediate, rewarding experience.

We need the same urgency, immediacy and elegance as part of the free software desktop experience, and that’s is an area where Canonical will, I hope, make a significant contribution. We are hiring designers, user experience champions and interaction design visionaries and challenging them to lead not only Canonical’s distinctive projects but also to participate in GNOME, KDE and other upstream efforts to improve FLOSS usability.

Fortunately, we won’t be working in a vacuum. This is an idea that is already being widely explored. It’s great to see that communities like GNOME and KDE have embraced user experience as a powerful driver of evolution in their platforms. Partly because of the web-2.0 phenomenon and the iPhone, there’s a widely held desire to see FLOSS leap forward in usability and design. We want to participate and help drive that forward.

There’s also recognition for the scale of the challenge that faces us. When I laid out the goal of “delivering a user experience that can compete with Apple in two years” at OSCON, I had many questions afterwards about how on earth we could achieve that. “Everyone scratches their own itch, how can you possibly make the UI consistent?” was a common theme. And it’s true - the free software desktop is often patchy and inconsistent. But I see the lack of consistency as both a weakness (GNOME, OpenOffice and Firefox all have different UI toolkits, and it’s very difficult to make them seamless) and as a strength - people are free to innovate, and the results are world-leading. Our challenge is to get the best of both of those worlds.

I don’t have answers to all of those questions. I do, however, have a deep belief in the power of the free software process to solve seemingly intractable problems, especially in the long tail. If we articulate a comprehensive design ethic, a next-generation HIG, we can harness the wisdom of crowds to find corner cases and inconsistencies across a much broader portfolio of applications than one person or company could do alone. That’s why it’s so important to me that Canonical’s design and user experience team also participate in upstream projects across the board.

In Ubuntu we have in general considered upstream to be “our ROCK”, by which we mean that we want upstream to be happy with the way we express their ideas and their work. More than happy - we want upstream to be delighted! We focus most of our effort on integration. Our competitors turn that into “Canonical doesn’t contribute” but it’s more accurate to say we measure our contribution in the effectiveness with which we get the latest stable work of upstream, with security maintenance, to the widest possible audience for testing and love. To my mind, that’s a huge contribution.

Increasingly, though, Canonical is in a position to drive real change in the software that is part of Ubuntu. If we just showed up with pictures and prototypes and asked people to shape their projects differently, I can’t imagine that being well received! So we are also hiring a team who will work on X, OpenGL, Gtk, Qt, GNOME and KDE, with a view to doing some of the heavy lifting required to turn those desktop experience ideas into reality. Those teams will publish their Bzr branches in Launchpad and of course submit their work upstream, and participate in upstream sprints and events. Some of the folks we have hired into those positions are familiar contributors in the FLOSS world, others will be developers with relevant technical expertise from other industries.

One strong meme we want to preserve is the idea that Ubuntu, the platform team, is still primarily focused on integration and distribution. We will keep that team and the upstream work distinct to minimise the conflict of interest inherent in choosing the patches and the changes and the applications that actually ship each six months as part of an Ubuntu release.

Of course, there’s a risk to participation, because you can’t easily participate without expressing opinions, visions, desires, goals, and those can clash with other participants. It’s hard to drive change, even when people agree that change is needed. I hope we can find ways to explore and experiment with new ideas without blocking on consensus across diverse and distributed teams. We have to play to our strengths, which include the ability to diverge for experimental purposes to see what really works before we commit everyone to a course of action. It will be a challenge, but I think it’s achievable.

All of this has me tapdancing to work in the mornings, because we’re sketching out really interesting ideas for user interaction in Launchpad and in the desktop. The team has come together very nicely, and I’m thoroughly enjoying the processes, brainstorming and prototyping. I can’t wait to see those ideas landing in production!