Open source gov

Last week, the Cabinet Office published a new action plan for government and open source, to level the playing field when it comes to procuring software.

So we consider that the time is now right to build on our record of fairness and achievement and to take further positive action to ensure that Open Source products are fully and fairly considered throughout government IT; to ensure that we specify our requirements and publish our data in terms of Open Standards; and that we seek the same degree of flexibility in our commercial relationships with proprietary software suppliers as are inherent in the open source world.

Excellent stuff. There is a Netvibes dashboard set up to help monitor what is being said online, some of which is a little cynical and critical. I tend to prefer to be relentlessly positive.

Anyway, the situation with open source is a little similar to that of social web stuff, in that knowledge about it, and its possibilities, are somewhat limited. We need open source digital mentors!

Alternatively, we just need a wiki.

OpenSourceGov

OpenSourceGov is a simple MediaWiki site which aims to collect together all the information a civil servant might ever want to know about open source and the options it makes available. Hopefully it will soon be able to answer questions like:

  • Which licence should a government open source project be published under>
  • What is the best open source content management system to use for which purpose?
  • Where are the suppliers of open source solutions?

As well as many others.

Please do visit the wiki, and make use of the (currently limited) information on there. Even better, register for an account and add or edit some stuff you know about and share it with everyone else!

Wikia release social network feature

You can now make your MediaWiki running wiki have social networking features, too, as reported by Wikia head honcho Jimmy Wales:

Today at Wikia we have released our social networking features for MediaWiki under the GNU GPL 2.0. The best place to see this running live is at Halopedia, our Halo site.

I am excited about all the stuff going on in this space. With google’s open social initiative, our work in social search and social networking for mediawiki, I think the whole wiki/free culture space is about to get a whole lot more interesting.

Cool. Will have to track down where I can get this from and have a play. Might be useful for GovHack?

Edit: I can’t find it anywhere.  Help?

Wikis – which is best?

Well, it’s a question. Wikis are funny things, and building communities around them can be quite tricky (although advice like this helps). More than any other types of website, wikis demand community interaction, indeed, they are nothing without it.

There are a number of different ways a wiki system can be operated. One is by using a hosted platform, where you register your wiki at a site, and they host it for you. Unless you want to spend some money, the chances are that you will have to put up with having adverts on your wiki, and you’ll be limited in how you can customise it.

On the other hand, you could register a domain (i.e. www.yourwiki.com) and install a wiki yourself. This makes you responsible for maintenance, support etc, but also means you can completely customise the wiki for your own purposes, whether in terms of style or functionality.

So, which should you choose? As so often is the case, the answer is something along the lines of ‘it depends’. However, to help you decide, here’s a number of points to consider when working out what you want to do.

1. Have you a clue about coding?

If the answer to this is ‘no’, then please get a hosted service. You don’t need to be a skilled coder, able to generate reams of perfect PHP at will, to get a wiki up and running, but it helps if you know a little bit about these things. Otherwise, you are likely to get irritated very quickly, and that’s no good at all.

Wikispaces

2. Do your users know what they’re doing?

If your intended user base are wiki working wonks who like nothing more than to collaboratively edit websites, then you are fine with either the hosted or self-hosted option. However, if the concept of wikis is new to your users, the hosted option might be the better one. Why? Well, they tend to be easier to use. Take Wikispaces, for example, which provides an easy to use wysiwyg editor for all page edits. This is much easier than using traditional wiki markup, which many of the self-hosted options rely on, which involves putting any number of ***asterisks*** or [[square brackets]] around words.

Mediawiki-logo-01

3. Will you need heavy customisation?

If your wiki will be a collection of basic web pages, with lots of text and maybe the odd image or embedded video, then most hosted wiki options will suit you just fine. However, if you want to have different methods of entering or presenting information available – for example by using a specific form for a certain type of information – then you will probably need a self hosted wiki which you can customise to your heart’s content (though remember point 1, above).

Stikipad

4. Traffic

Is this going to be the wiki of the century? Are the numbers of visitors to your wiki going to eclipse even those of Wikipedia? Probably not, but if you are planning on hosting your own wiki, do bear in mind that you are likely to be responsible for paying for bandwidth, especially if your site starts to gobble a lot of it up. Generally speaking, if you have a hosted wiki, this will be the provider’s problem, not yours. This is also true about uploaded content – if you will have lots of videos on your wiki, do bear in mind that you will have to pay for storage on a self hosted wiki. With all hosted ones, you should get a certain amount of free storage.

PBWiki

5. Instant networks

How about attracting people to use your wiki? One of the major problems a lot of platforms suffer from is the fact that they require users to have yet another account with yet another password to remember. This will be the case with any self hosted option, unless you are very clever (see point 1 again). However, if you put a wiki on a hosted network of wikis, then there is a good chance that some of your users will already be using that network, and will therefore already have an account there. Wikispaces is a good example of this.

PMwiki

6. Integration

The look and feel can be an important point for many sites – what’s the point of having a stylish theme for your website if when people click to visit your wiki it looks totally different? Some hosted wiki solutions will let you pay to edit the CSS (Cascading Style Sheets – a way of setting the design elements of your website) of the site, which will allow you quite a bit of room to customise the look of your wiki. But to retheme the guts of the wiki, you’ll really need to have a self-hosted one, where the source code as well as the CSS can be altered to suit your every whim.

WetPaint

So, there’s plenty to be thinking about. My basic rule would be to go for a hosted solution unless there are really good reasons not to, and my personal favourite platform for this is Wikispaces. However, if you really need to go for hosting a wiki yourself, then the best in terms of features and usability for me is MediaWiki, the system which powers Wikipedia.

Below I set out some of the options available. If yoy know of ones I have missed, let me know in the comments and I will update the list.

Hosted Wikis

Self-Hosted Wikis