Downing Street behind open source push


Computer Weekly’s public sector IT blog reports from Monday’s ‘Open Source Integrator Forum’, described bluntly as:

a dressing down in which the big 12 systems integrators, who supply 80 per cent of all government IT, were told firmly that they were preventing the government from carrying out its policy and had better change their ways.

The Home Office’s Tariq Rashid, described as ‘helping the Cabinet Office unearth the reasons why systems integrators have ignored the government’s open source policy’, told CW ‘there had been more pressure from Number 10 over open source than there had been from the Cabinet Office’. (A statement backed up by Sirius IT, who were also in attendance.)
Slides from the event name Qamar Yunus (ex Identity & Passport Service) as the ‘Government Open Source Lead’, and refer to a Government Open Source Advisory Panel – although I’ve seen no membership list for the latter.
CW has also published the government’s draft Assessment Model for open source, and list of ‘approved’ open-source software – although the latter in particular is very draft indeed. Take this entry on ‘web’ as an example:

To be honest, it’s slightly depressing that the best example they could quote for Drupal or Joomla or WordPress (note: small ‘p’) was the White House – with a question mark, for some reason – since our own head of government blazed the trail for use of open source well before; and indeed, Cabinet Office themselves recently shifted over to Drupal. That’s before we get on to the countless examples of each one elsewhere in HMG and on its fringes. You’d almost think they never read my blog.
But thankfully, there’s a direct quote from Tariq Rashid:

If the Cabinet Office starts producing an assessment model to separate good software from bad software, looking at things like support, how established is it, is there good governance around development, these sorts of things. That would enable customers to say, ‘We want to use WordPress and according to this model it’s not going to fail’.

When Chris Chant spoke at UKGovCamp, my question to him was: we’d heard various commitments to make greater use of open source over 3-4 years; what was going to be different this time? Well, to his team’s great credit, this is something we haven’t had before – in effect, an ‘app store’ of recommended open source applications. To anyone who knows the territory, it’s embarrassingly basic – but what matters is the Cabinet Office logo which will go on the front cover.
To be completely frank, though, there’s a major concern for me in all this: the prospect of big ugly consultancies deciding to sell open source into government, in precisely the same way they’ve sold proprietary-based solutions beforehand. If we’re seeing open source as a way of not paying expensive software licenses – then yes, on one level, it is. But there’s so much more to it than that.
Open source, fundamentally, is about the people. And it’s not just geeks in their back bedrooms these days: it’s about serious, commercial, profitable businesses – but businesses with a very different mindset to the conventional IT consultancy. Agile, innovative, collaborative, JFDI, call it what you will: I don’t often see examples of this approach among the major SIs.
Have a look, for example, at the speaker lists at the BCS Open Source Specialist Group‘s two meetings on the subject: one earlier this week, one next week. Atos Origin, IBM, Hewlett Packard, Fujitsu. Can we expect behemoths like these to offer the kind of response – and frankly, the total price tag – that you’d get from a small operation (yes, like Puffbox, but other suppliers are available) with roots already deep in open source? I’m afraid my own recent experience says not.
This is the right thing to be doing. I’m afraid I remain to be convinced that these are the right people to be doing it.

WordPress v3.1: another step forward

It’s taken quite a while to get WordPress version 3.1 out the door; and at first glance, you’d be forgiven for wondering quite why. You’ll run the upgrade process, then struggle to find what exactly has changed. In fact, there are a few significant – or more accurately, potentially significant – enhancements in this release; but a lot of the changes are fairly superficial or ‘nice-to-have’s.
First thing you’ll notice is the new Admin Bar along the top edge of the screen, when you’re logged in – giving instant access to the admin dashboard, an ‘edit this page’ button (where applicable), and so on. In fact, as Puffbox clients will testify, I’ve been coding something similar into all my design work for years… but I’m happy to admit, theirs is better than mine. If you haven’t had the benefit of such a feature before, you’ll soon grow to love it.
Then there’s Post Formats, which have caused some confusion among the developer community. These allow you to classify different types of post – for example: ‘status’, ‘image’, ‘gallery’, ‘quote’ – which can then be presented slightly differently by your theme. It’s really just a standardised taxonomy, meaning – in theory, and in the future – you can switch between themes, and maintain the differentiated presentation. But you’ll only be given the option to choose a Format if your theme explicitly enables it, and few do at this point.
The feature with the greatest potential is multi-taxonomy queries – which, to borrow Simon Wheatley’s example from UKGovCamp, would allow you to find all pictures of cats (being a type of animal) wearing hats (being a type of clothing). This has been possible to a certain extent for some time, by hacking URLs, but now it’s official – and done properly.
In simple terms, this lets you run WordPress more like a database than a blog – you might be a car dealer listing cars for sale, with drop-down menus to let people search by manufacturer, fuel type, size of engine, colour, number of doors, number of seats, etc etc – or any combination thereof.
But to make use of this functionality, you’ll need to be a serious developer: no plugin is going to be able to lay this on a plate for you. So it’s continuing the trend I observed at v3.0’s release:

But the addition of that extra power, underneath the surface, effectively creates a new higher echelon of ‘WordPress guy’. It becomes a platform on which you can do some very serious development, if you know what you’re doing. Graphic designers calling themselves WordPress experts might want to re-evaluate.

There are a few things to look out for, particularly if you’re running a multi-site setup: there’s now a whole new ‘network admin’ view, replacing the ‘Super Admin’ menu box from 3.0 – you’ll find it by clicking the ‘Network Admin’ link in the top right corner. It’s definitely prettier and slicker once you’re into it; but I bet it’s going to confuse a lot of Super Admin users initially.
There’s a new behaviour to adding links within your own site: you’re now presented with an ajax-powered search facility, meaning (in theory) an end to copying-and-pasting URLs from another browser tab. Quite nice I suppose, but it still just results in a hard-coded URL within the text: no DOIs or anything.
And it’s good to see further refinement of custom post types and taxonomies. For example, prior to v3.1, there was no built-in way to present an archive list of custom post types – a curious omission, but it’s resolved now, and should encourage more developers to make use of this functionality.
But as you’ll see from the detailed list of changes at wordpress.org, most of the changes fall under the heading of general housekeeping: a cosmetic tweak here, an update to an included software package there.
Matt Mullenweg declares this release ‘more of a CMS than ever before’ – and of course, he’s right. We’re definitely edging further and further into ‘proper’ CMS territory; but, I think, still clinging on to the ‘I just want to write something’ mentality from WordPress’s early days as a humble blogging platform.
It’s another step forward. Not perhaps the great leap forward that v3.0 represented, but that’s absolutely fine. The best just keeps getting a little better.

Another Cabinet Office WP consultation


Has somebody at the Cabinet Office just discovered WordPress, or something? I see they’ve also just launched a WP-based site to consult on the proposed Public Data Corporation. This time, the site is running in the most vanilla, out-of-the-box configuration imaginable – using the TwentyTen theme, and without even tinkering with the sidebar widgets (albeit with the addition of Disqus for comments). It’s hosted at MediaTemple… despite the fact that the Office has its own hosting capability at Amazon, as demonstrated by today’s Public Bill Stage pilot.

Can Cabinet Office's WordPress-based commentable bills make a difference?


The Protection of Freedoms Bill, published last week, has become the first piece of proposed legislation to go through a ‘public reading stage‘, as promised in the Coalition Agreement. The No10 website says it’s ‘the first step towards meeting the Coalition’s commitment to introduce a public reading stage for all Bills, allowing the Government to test the technology and ensure the system works well.’ And the technology in question is WordPress.
It’s a fairly straightforward presentation, using a custom WordPress theme bearing the catchy name ‘Cabinet Office Commentable Document (non-core)’, produced by the Cabinet Office’s in-house digital team – in double-quick time, so I’m hearing. The government branding is very understated indeed, with only an HM Government logo, in the bottom right corner. It looks like it’s all based on pages, as opposed to posts, with a jQuery-based expand/collapse menu (which I suspect has been hard-coded) in the left margin. It’s sitting on the same Amazon account as the main Cabinet Office site.
Can it work as an idea? I’m not convinced. The commenting technology’s certainly up to it, as we’ve proven time and again. But legislation isn’t exactly written to be read; you don’t have to dig too deeply into the site to find unintelligible passages, with every other sentence cross-referencing another subsection of another chapter of another Act… and no hyperlinking (even though all the source material should presumably be available in legislation.gov.uk). I just can’t imagine how an ordinary member of the public could be expected to make sense of it.
A starting point would be a ‘diff’ tool, similar to a programmer’s code editor – showing the ‘before’ and ‘after’, with changes highlighted. If you’ve never seen one, they look something like this:

One example: the open source tool, Meld

… instantly allowing you to see where text has been added and/or changed, and how. Wikipedia offers something similar: if you click on ‘View history’ for any page, you’re able to compare various past versions of the page, and see the changes highlighted (albeit in a less-than-friendly fashion). And indeed, back in 2007 MySociety proposed a diff tool (of sorts) as part of their Free Our Bills campaign.
Without this, I can’t imagine many ordinary people going to the trouble of decoding what’s actually being proposed… meaning I can’t see it doing anything to widen participation, if that’s the intention. So whilst it’ll be useful as a pilot exercise, I fear it’ll only prove the difference between green/white papers, which are text documents intended to be read; and bills, which just aren’t.

White House contributing back to open source projects

Just over a year ago, I noted how the French government had contributed code back to the open source community, enhancing the Thunderbird email client for military purposes. I failed to not(ic)e that a few months later, the White House had done likewise – contributing a number of new modules for Drupal, based on development work done for its own Drupal-based site. And this week, they’ve announced the release of a few more modules:

Today’s code release constitutes a few modules we developed for ourselves, as well as a recognition of our sponsoring the development of modules widely used in the Drupal community, which improve the administration of our site in a variety of ways… We also recognize that there are really good projects already embedded in the Drupal community and reached out to help support their development.

In other words: not only are they recognising that off-the-shelf open source code is good enough for deployment at the highest conceivable levels… not only are they recognising the opportunity to build on top of it, to suit their own requirements… but they’re also getting actively involved with existing projects, in this case Open Atrium:

Prior to launching its internal site on Open Atrium, the White House helped strengthen the platform’s core by investing in key modules … Investment like this increases efficiencies gained by government agencies utilizing a common platform like Open Atrium … It’s really exciting that the White House team is so committed to giving back to open source communities with code contributions and smart investments like this.

It’s amusing to see the deliberate, repeated use of the word ‘investment’ in the piece: clearly, it’s in the interests of the product’s backers to do so, but I don’t think it’s an unfair choice of words. It’s public money being spent for greater long-term benefit.
I don’t have a problem with open source being initially ‘sold’ into government on the £0.00 pricetag: and in the case of WordPress at least, and probably also Drupal, that argument was won some time ago. We’re now entering the second phase, as departments realise that it can be customised to suit their specific needs: we’re moving from ‘can it do this?’ to ‘can it be made to do this?’. But the campaign won’t be complete until we’re going full-circle, contributing back to the projects we’re using.

Tories' new packaged website service


I see the Conservatives have followed in the footsteps of both Labour and the LibDems, in offering a ‘website in a box’ service to local constituencies. Known as Bluetreenot to be confused with website developers bluetree.co.uk* – it’s based on Drupal (plus multi-site management add-on Aegir) and was developed by the UK’s self-proclaimed Drupal specialists, ComputerMinds. It promises ‘state-of-the-art technology … at a cost well below market rate’ – although there’s no (publicly visible) indication of precisely what that cost is.
It’s taking a little while to find its feet, judging by the first few examples I’ve come across – including WitneyConservatives.com, the constituency of one David Cameron. But the basic structure is obvious: about, events, news, people. Everything’s on brand, naturally, with promo boxes for the (national) party’s Twitter and Facebook accounts; and there’s a nice little arrangement, presumably RSS-based, to pull national news in from conservatives.com. The design is clear, if a little lacking in warmth.
It’s a reasonable idea, but they need to be careful not to fall into the same traps as the Labour and LibDem party offerings: both of which have had widespread takeup, driven primarily by rock-bottom pricing, without winning the hearts and minds of party members and activists. Remember this tirade against Labour’s retained agency, Tangent? And I’m told there’s disappointment among LibDems at Prater Raines’s last relaunch, although it hasn’t seeped into the public domain.
In case you’re wondering, the Tories’ last grand Drupal project, myconservatives.com, has been displaying an ‘under construction’ message for at least the past few weeks.
* I did get in touch with bluetree.co.uk to ask if they were aware of this; but didn’t get a reply in time to include it here.

DECC launches staff blogs on WordPress


Congratulations to the Department of Energy and Climate Change on the launch of their new staff blogs platform; and particular congratulations for choosing the right software to power them. 🙂
Like other Whitehall blogging initiatives such as those at DFID and FCO (both of whom already have their own group blogs on climate change – here and here respectively), the DECC site sets out to give readers an insight on staff’s day-to-day activity. Four bloggers kick things off: one Minister, Conservative Gregory Barker; and three (relatively senior) staff members.
On a technical level, it’s not dissimilar to the work I did for DFID, in that although the four contributors’ entries are presented as independent, stand-alone blogs, they’re actually just multiple users writing into a single group blog.
The work has been done by DECC’s existing digital agency, the Swansea-based S8080. Like their main corporate site, it’s running on a Microsoft IIS server, which may explain the lack of ‘pretty permalinks’ (although it doesn’t have to be like that). There are a few rough edges, and I hope they won’t mind me saying, they’ve done a few things in not very WordPress-y ways: entirely understandable, since they’re primarily a Microsoft-based company. But hey, it’s early days, and I’m sure it’ll all be ironed out soon enough.
It’s quite a brave initiative on one level: you only have to look at the number of comments typically received by climate-sceptic Telegraph writer James Delingpole – always in the hundreds per post, and often well into the thousands! – to see what they could be letting themselves in for. There’s no explicit comment policy showing on the blog: I only hope they’ve given some thought to how they’ll handle the more confrontational comments they’re likely to receive. DFID’s is a great example to follow, if they need one.
I know both FCO and DFID feel they’ve got a lot out of their blogging platforms: and I sincerely hope DECC have a similarly positive experience. But it may be a bumpy ride.

The £585 favicon: explanation and justification

The Guardian’s Charles Arthur followed up yesterday’s story about the Information Commissioner’s Office paying £585 for a favicon, and has managed to secure something of an explanation of how it reached such a price.

Though the creation process is quite simple, confirming that it has been done correctly is not: what’s been generated has to be created against a set of “functional specifications” laid out in the contract for the job – colours, sizes, a long array of confirmations quite separate from the task of making the actual item.
That bumps up the time taken to between two and three “billable hours” for the designer, who works at Reading Room based in Soho – one of the UK’s biggest web agencies, with turnover of £12m and 170 staff whose time is charged at £600 per eight-hour day, significantly lower than many in the business.
But the favicon can’t now simply be sent to the ICO site ready for uploading. First the company has to get approval from Capita, which has the contract to manage the site, and which may make its own comments about what it thinks, and at the very least has to check that it’s the correct size; and then from Eduserve, which hosts the site and has to check it can in theory be uploaded; and from the Central Office of Information, which manages the ICO contract with Reading Room.
All in all, getting everyone involved to approve the favicon that has been created means the time taken balloons to a total of nearly seven billable hours – which means Reading Room, as a commercial outfit, charges about £500; add VAT at the rate prevailing in 2010 and you reach £585.

I’m not entirely convinced by the calculation: I wonder just how long that ‘array of confirmations’ could have been for a favicon; I wonder precisely what input Capita, Eduserv and COI could each have had; and I wonder if the £600-a-day designer was actually the member of a 170-strong company spending 4-5 hours on the phone, valiantly trying to push it live. But that’s beside the point: if £585 is commensurate with the effort Reading Room went to, then they should invoice it. There’s no argument there.
The wider point here is that it simply shouldn’t have to cost that – as, indeed, Reading Room’s Margaret Manning seems to accept:

“A lot of government contracts involve outsourcing the IT, which sounds like a great idea in many cases. But if you look at the hoops you have to go through … it can make the amount of time needed by outside organisations just go up and up to get anything done.”
She thinks there is a culture within government which doesn’t try to reduce spending. Instead, she suggests, there is a culture of fear that something will go wrong whenever something is put on the web, which leads to a belt-and-braces approach that in turn pushes up costs and times above what any commercial organisation would spend.
But she’s also perplexed by the choices the government has made. “What commercial entity has Capita running its IT?” she asks rhetorically.

Fair points. And it leaves me wondering… what about those other links in the chain? How much did they bill for their contributions to the process, whatever they were? If Reading Room’s designer is spending 4-5 hours making phone calls, presumably Capita / Eduserv / COI will also be charging for answering the calls? Should we maybe double the £585 figure?
It boils down to this. Process is an insurance policy. Like any insurance policy, you pay a premium. You decide what level of premium you’re prepared to pay, for what cover, and what level of excess. And if you aren’t happy with the cover or service you receive, you go elsewhere next time.
If you bring in an insurance broker, you pay him or her a fee – on the understanding that he or she knows the market better than you, and will act on your behalf to ensure you get the best deal. If that doesn’t happen, you get yourself a new broker, or you do it yourself.
Update: which, actually, makes this tweet from yesterday (which I’d missed at the time) all the more interesting:
[blackbirdpie url=”https://twitter.com/ICOnews/status/33217532274028544″]

Er… how much for a favicon?


Chins collectively hit the floor this afternoon, as word got round that the Information Commissioner’s Office had paid £585 for the creation of a single 32×32 ‘favicon’ graphic. Oh, and to be fair to them, adding a line to their pages’ HTML header referencing it.
Mark Bowen used WhatDoTheyKnow to follow up a reference he’d spotted in a document published by the ICO, which doesn’t exactly leave any room for doubt:

There it is, in black and white

His enquiry revealed that the work was done by Reading Room, commissioned through COI. In their defence, ICO say:

The work needed to put the favicon live was complicated by an old environment (which has since been updated) that caused issues and extended the time taken to carry out the work… Whilst there is no recorded information which would [explain the difference between the old environment and the new one that caused the extended time needed] I can confirm that that the old website development environment was upgraded from one server to two.

… which, on the face of it, wouldn’t seem to have caused any direct ‘issue’ when it came to sticking a graphic in a given folder.
But we shouldn’t rush to any rash judgments here. Yes, favicons shouldn’t normally take more than 5 minutes (as Mark notes) to produce. And yes, adding a standard line of HTML to reference it should be basic copy-and-paste… if it’s even necessary, which it usually isn’t. But we don’t know the full facts. Yet. The ball’s in your court, RR.
[blackbirdpie url=”http://twitter.com/simond/status/33191046527586304″]
Continues…

WordPress at Dept of Health

Just a brief post to highlight Stephen Hale’s write-up about WordPress usage at the Department of Health, answering the question I posed in a tweet last week:

Just how many WordPress based sites is @hmshale running over at @dhgovuk?

… to which the answer is, one or two more than I had spotted.
It’s all Steph Gray‘s handiwork, commissioned through Steria, with a child theme of the default Twenty Ten. I’m sure Steph would agree that it isn’t pushing the technology’s boundaries too hard; but it doesn’t need to. Stephen’s team’s needs have been met, allowing them to spin off high-quality subsites, quickly and efficiently, when requirements land on his desk – and indeed, Stephen observes: ‘I think the theme will exceed our expectations for it.’ I look forward to Steph’s write-up of the work; it’s highly unusual for him not to have posted something by now.
There’s a very interesting sign-off to the piece, too:

I don’t need to tell you that using a straightforward publishing tool like WordPress is fairly pleasing. Having dipped a toe in, it’s tempting to go a bit further than we originally planned.

Whatever could he mean? 😉