Aramis was the high tech automated subway developed in Paris in the 1980s. After its sudden demise an investigation was requested into the reasons of this failure. Bruno Latour. While writing about Aramis's demise Latour describes ANT (Actor-Network Theory). In this book he argues that Aramis failed not because any particular Actor killed it but because it was not sustained through negotiation and adaptation to a changing social situation.

See http://www.bruno-latour.fr/node/106

I guess I'll be able to write the same about this project in a few years time.... and HS2... etc.......

I've played with this a few times, never used it in anger though.

http://www.mayan-edms.com/

I might take up your challenge on going paperless too and give Mayan a go.

There is an arms race between companies like Nebula and Eucalyptus, backed by VCs, as to who can stay in the game long enough to be the defacto clound management environment for companies who want an open alternative to VMWare/Microsoft but need on-premise or have a specific use-case so can't choose EWS or Google.

Eucalyptus, for all the partner-with-amazon, are loosing market share and shedding staff.
Nebula are still struggling to get a viable product out of the door.

(I know senior people in both companies)

Who will win? Who cares! Because as its 'open' at least when the VCs behind Euca/Neubla shut up shop (or they are bought by HP/IBM) and go home customer will still have the code, and in the example of Nebula also own a box in the mid rack as a cloud controller.

ICO issues guidance about private emails, reminding the public sector that the Freedom of Information Act covers private emails if they are used for business matters.

"Christopher Graham, the information commissioner, said: "It should not come as a surprise to public authorities to have the clarification that information held in private email accounts can be subject to freedom of information law if it relates to official business."

Not really a device thing... but related none the less.

I work for a large confectionary manufacture who have one of the best password policies I've come across in the 7 years of my IT career.

8x90. It's simple. Eight characters with forced policies on every system to change them every 90 days. Splash screens at startup give advice on choosing stronger passwords. We advise choosing a six letter word, breaking it in half and inserting a two digit number.

e.g. let01ter

Simple and effective.

Of course, without running a cracker over the password lists I guess we'll never know if the policy actually works!