Category Archives: open source

Searching The Vancouver Public Library Catalog using Amazon

A few months ago I posted about a number of civic applications I’d love to see. These are computer, iphone, blackberry applications or websites that leverage data and information shared by the government that would help make life in Vancouver a little nicer.

Recently I was interviewed on CBC’s spark about some of these ideas that have come to fruition because of the hard work and civic mindedness of some local hackers. Mostly, I’ve talked about Vantrash (which sends emails or tweets to remind people of their upcoming garbage day), but during the interviewed I also mentioned that Steve Tannock created a script that allows you to search the Vancouver Public Library (VPL) Catalog from the Amazon website.

Firstly – why would you want you want to use Amazon to search the VPL? Two reasons: First, it is WAY easier to find books on the Amazon site then the library site, so you can leverage Amazon’s search engine to find books (or book recommendations) at the VPL. Second, it’s a great way to keep the book budget in check!

To use the Amazon website to search the VPL catalog you need to follow these instructions:

1. You need to be using the Firefox web browser. You can download and install it for free here. It’s my favourite browser and if you use it, I’m sure it will become yours too.

2. You will need to install the greasemonkey add-on for Firefox. This is really easy to do as well! After you’ve installed Firefox, simply go here and click on install.

3. Finally, you need to download the VPL-Amazon search script from Steve Tannock’s blog here.

4. While you are at Steve’s blog, write something nice – maybe a thank you note!

5. Go to the Amazon website and search for a book. Under the book title will be a small piece of text letting you know if the VPL has the book in its catalog! (See example picture below) Update: I’m hearing from some users that the script works on the Amazon.ca site but not the Amazon.com site.

I hope this is helpful! And happy searching.

Also, for those who are more technically inclined feel free to improve on the script – fix any bugs (I’m not sure there are any) or make it better!

Amazon shot

Emergent Systems in Government: Let's put the horse before the cart

Yesterday Paul McDowall, Knowledge Management Advisor at the Government’s School of the Public Service and chairperson of the Interdepartmental Knowledge Management Forum, wrote the following comment in response to a blog post from several months ago entitled “How GCPEDIA will save the public service.”

I’ve posted his comment – feel free to read it or skip it and go straight to my analysis below. In summary, what makes McDowall’s comments interesting isn’t just the argument (or its reactionary nature) but the underlying perspective/assumptions that drives it. It serves as a wonderful example of the tension between how the traditional hierarchical nature of the public service and some evolving emergent models that challenging this approach.

So first, McDowall:

Will GCPEDIA save the public service, or capture all the tacit knowledge that will walk out the door? No, of course not! To suggest otherwise is, frankly, naive hyperbole.

As great and as promising as GCPEDIA and other Web 2.0 tools are, tools will never save the public service. People are the public service and only people have the capacity to save the public service, and it will take a whole lot more to improve the weak areas of the public service than a tool. Things like leadership play a pretty important role in organizational effectiveness. There are many good Organizational Excellence models (I have researched this area) and they all include people and leadership as two elements, but funny enough, tools aren’t included. Why? Because it is not so much a tool issue as it is a craftsman issue.

With respect to your comment about tacit knowledge and social capital (not the same things by the way), I think it may be helfpul to brush up on what tacit knowledge is, and what Knowledge Management is.

It is unquestionably true that the public service continues to face a potential impact from demographic changes that are both extremely significant and yet unquantified. It is also unquestionably true that most public service organizations haven’t truly understood or addressed these potential impacts, to say nothing of the potential of improving their effectiness right NOW from better Knowledge Management (productivity, innovation, etc).

These issues need to be addressed by public service leaders in an intelligent and thoughtful manner. Tools can and certainly should help but only when wielded by craftsmen and women. For too long vendors have made grandiose and unrealizable promises about their ‘solutions’. I thought we had learned our lessons from all that experience.
Let’s not get the cart before the horse, shall we?

Paul McDowall
Knowledge Management Advisor and chairperson of the Interdepartmental Knowledge Management Forum

McDowall’s main concern appears to be that GCPEDIA doesn’t have a clear purpose and, more importantly, doesn’t serve a specific leadership objective. (If you are wondering how I gleaned that from the above, well, I cheated, I called McDowall to ask him more about his comment since the nature of his concern wasn’t clear to me). For those used to an era where IT projects were planned out from the beginning, everything was figured out in advance, and the needs of the leadership were the paramount priority, GCPEDIA would be disconcerting. Indeed, the very idea of unleashing people willy-nilly on a system would be an anathema. In short, when McDowall says, don’t put the horse before the cart, what he’s saying is, “you’ve rolled out a tool, and you don’t even know what you are going to use it for!”

This would appear to be rational concern. Except, many of the rules that underlay this type of thinking are disappearing. Indeed, had this type of thinking been adhered to, the web would not have developed.

First, The economics have changed. There was a time when IT projects necessarily costed tens of millions of dollars.  But GCPEDIA was built on a (free) open source platform using a handful of internal FTEs (making McDowell’s comments about vendors even more confusing). Indeed GCPEDIA has cost the public service virtually nothing to create. One invests in planning so as to avoid expensive or ineffective deployments. But if the costs of deployment are virtually zero and failure really isn’t that traumatic then… why waste time and years planning? Release, test, and adapt (or kill the project).

Second, with projects like this become cheap to deploy another important shift takes place. Users – not their bosses or a distant IT overlord – decide a) if they want to participate and b) co-develop and decide what is useful. This has powerful implications. It means that you had better serve a real (not perceived or mandated) need, and that, if successful, you’d better be prepared to evolve quickly. This, interestingly, is how that usefully little tool called the World Wide Web evolved. Read the original proposal to create the World Wide Web. IT departments of the world didn’t all collectively and suddenly decide that people should be made to use the web. No! It grew organically responding to demand. In addition, there is very little in it that talks about how we use the web today, users of the web (us!) have helped it evolve so that it serves us more effectively.

This is probably the biggest disconnect between McDowell and myself. He believes GCPEDIA is problematic (or at least won’t do the things I think it will do) because it doesn’t serve the leadership. I think it will work because it does something much better, it serves actual users – public servants (and thus, contrary to his argument, is very much about people). This includes, critically, capturing tacit knowledge and converting it into formal – HTML encoded – knowledge that helps build social capital (I do, actually, know the difference between the two).

Indeed, the last thing we need is a more leadership oriented public service, what we need is an employee centric public service. One that enables those who are actually doing the work to communicate, collaborate and work, more effectively. In this regard, I think GCPEDIA is demonstrating that it is effective (although it is still is very early days) with logarithmic growth, 8000+ users and 200 more signing up every week (all with virtually no promotional budget). Clearly some public servants are finding it to be at worst interesting, and at best, deeply enabling.

Misunderstanding and understanding the Open Data Hype

On Wednesday Gartner’s Andrea Dimaio wrote an interesting blog post entitled Open Data and Application Contests: Government 2.0 at the Peak of Inflated Expectations which Peter Smith nicely linked to the Gartner’s Hype Cycle graph from Wikipedia. I want to break his post down into three components. Two – the bad and the good, I’m going to talk about today – the third, which I’ll tackle on Monday involves some mapping and fun.

The Bad

As someone whose been thinking about and working on Open Data and Gov 2.0 for several years now three things struck me as problematic about Andrea’s post. Firstly, he misunderstands the point of open data. While many people – self-included- talk about how it can empower citizens, citizens will not be its primary beneficiary. The biggest user of open data portals is going to be government employees. Indeed, Tim Wilson reminded me the other day of our conversation with Jason Birch, the thought leader who made much of Nanaimo’s geo-data public, where he talked about how he wasn’t actually tasked with sharing data publicly – he was tasked with making the data available to other Nanaimo city employees. Sharing it with citizens was a (relatively) cost free addition. These projects aren’t about serving some techo-literati, it is about getting a city to first and foremost talk to itself – having it talk to its citizens is an important (and democracy expanding) benefit.

Second, was this unfortunate anecdote:

Yesterday I was discussing with a British client over lunch and he told me how the publication of data may lead to requests for more data (through the Freedom of Information Act), in a never-ending cycle of information gathering which is likely to cost a lot to both government and taxpayers. Another client observed (as I said in a previous post) that there is no way people will be able to tell to what extent a mash up on an application actually uses official, trusted government data.

Could government become swamped with data requests? Who knows, but in theory… it shouldn’t. Making data available should reduce the amount of time public servants spend responding to requests by diverting requests to open data portals. But let’s say Andrea’s concerns are valid and that, as a result of open data, citizens become more actively concerned and interested in how government works and thus Freedom of Information Act requests increase. The horror… citizens are interested in government! Citizens want to know how decisions are made! Remind me again… why is this a problem?

The real problem here isn’t access to data, it’s that the Freedom of Information Act process is itself broken. If open data creates a further demand for more transparent government and pushes us to foster better mechanisms for sharing government information, this is a good consequence. As for concerns that people might misrepresent public data, well a) people can already do this and we haven’t had a rash of bad applications, but even if they tried… people will stop using their service pretty quick.

Finally, another nice thing about public data is that it tends to get very clean, very quickly. My concern isn’t that government data will be misrepresented… I’m concerned that government data is already wrong and isn’t being verified. Knowing that someone might actually look at a data set is one of the most powerful incentives for organization to improve its collection. (Something Clay Shirky noted in a talk he made the other day at a Bioinformatics conference I’m at).

(There is of course, one group who may not see these a good consequences as it will change how they work: British public servant like Andrea’s client’s who raised the objections… but then they pay Gartner’s bills, not you.)

The Good

The end of Andrea Dimiao’s piece is where we find common ground. I agree that the Apps for Democracy competitions run the risk of limiting the definition of “the public” to citizen coders.  We want broader participation – particularly once more complex data sets like budgets, procurement and crime data are released – from academics, citizens groups and NGOs. Here in Vancouver we’ve talked about focusing any Apps competition on the themes of homelessness, housing and the environment, since these have been the dominant concerns of citizens in recent years.

More importantly, I agree (and love) Dimiao’s concept of employee-centric government. Indeed, my chapter for Tim O’Reilly’s upcoming book on Open Government makes a parallel argument, that namely we should stop trying to teach an analogue government to talk to a digital public and instead focus on making government digital (ie. getting it “open,” networked and using web 2.0 internally) first.

And perhaps most importantly, I agree that government 2.0 risks being over-hyped. I still believe in the potential, but know that getting there is going to be a painful process (mind the gap!). Government 2.0 advocates should expect lots of resistance and adoption problems ahead – but then change is painful.

How bloggers can keep the internet healthy

I’m continuously trying to brainstorming ways that Mozilla can find the next million mozillians and figure out activities they can do. I think I’ve stumbled on to a new one but would need some help to make it happen.

As some of you may know, as part of Mozilla Service Week Mozillians around the world donated their time and helped perform numerous Internet Health Checks. The goal here is to help people migrate off of Internet Explorer 6 (which is vulnerable to attacks and therefor makes the web less safe).

In my case, I’d already helped move pretty much anyone I know who uses IE 6 to something newer and better. What I need is a way to help prod people I don’t know.

What I thought might be interesting is if someone could build a blogger & wordpress plugin. This plug would ascertain what browser a visitor to your blog is using and… if they are using IE6… then the blog widget would let the reader know that the author of the blog strongly encourages them to upgrade to IE8, Firefox, Safari or really anything newer and safer. With this (hopefully relatively simple plug-in) Mozilla can engage the blogging community, enable people to help advocate for a safer internet and, most importantly, encourage still more IE6 users to move to something newer and safer.

Yes, it isn’t the be all and end all, but its another small idea that allows another group of people to contribute is an easy, but tangible and important way. That said, if this widget can’t be created, or if there is something easier/better that can be done, please, send me an email or comment below!

More ways to make open data sexy: 5 Municipal Apps I'd love to see (what are yours?)

One of the big goals of the open data project is to get many citizens interested in different ways the data can be used. Many citizens lack the skills to code up an application and creating a website is intimidating, but they may have ideas that could improve the city or be useful to many citizens.

In the hopes of spurring more interest in the open data and getting those not tradition involved, well… involved, I’ve created an “Ideas for the Taking” page on the Vancouver Open Data wiki. I’ve seeded the page with some of the ideas I promised I would share at the Open Data Hackathon last week . Some use open data, others don’t. Mostly however, I hop they spurn others to think of what is possible and what interests them. (PS. If you are a reader and the wiki is too confusing, just email me your idea and I’ll add it to the wiki with (or without, if you prefer) you’re name attached.

So here are some ideas I’ve brainstormed:

1. Stolen Bike Tracker

Vancouver’s cycling community is huge, sadly however, the city is plagued by a serious problem: stolen bicycles. There is no solution to this problem but I think a well crafted app could help minimize the nuisance. I can imagine an app or website in which you take a photo of your bike and upload it along with some identifying information(like the serial number) to a website. The picture stays hidden, however, if your bike gets tragically stolen you load up the apps and press the “my bike was stolen button.” This marks the physical place where your bike was stolen and activates your bike photo and marks it as stolen. Now cyclists, bike shop owners and the police can check bikes to see if they are stolen before buying them (or return them to their owner if they are recovered). In addition, a street map of bike theft would also be created. This could be particularly relevant since I suspect a great deal of bike theft is not reported. Finally, for those worried about privacy, I could imagine the app using a Craigslist style contact system that would preserve the anonymity of the original owner.

2. A Downtown East Side Landlord wiki

There are a few data sets that might allow for someone to create a geo-wiki of the DTES. I think it would be interesting to have a wiki that – on a building by building level – outlined who owned which residential buildings, what they charged in rent, a list of the room amenities and comments about the property’s management. It might also be interesting to enable photos to be posted so people can show the living conditions. Such a wiki might give the public (and prospective renters) a window into the deplorable conditions and poor practices of the worst offenders. It might also help City Staff deploy resources for investigating code violations and other questionable practices.

3. Everyblock+

Obviously, I think an Everyblock app for Vancouver would be great. The one new layer I’d love to see added to it is a charity button. With this button you would see what charities are operating on the block/area you are standing on. This is harder to imagine realizing, but cooler still would be a button that would allow you to then donate to that charity.

4. Burrard Bridge Trial Website

While not located on the Open Data Portal, the city has been releasing weekly data sets on vehicle, pedestrian and cycle trip across the Burrard Bridge Trial on the Burrard Trial blog. The data is not particularly well organized (you’d have to scrape it and its only granular to the 24hr time block – so no hour by hour data sets) but it is a start. I’d be fascinating to have a site that does a deeper analysis of the data and maybe shows it in a more interesting format. Maybe a discussion on carbon emissions reduced… still more interesting would be an analysis of bicycle accidents at present versus before the trial (data that is, sadly, not obviously available).

5. City Services vs. Land Value Mashup

It would be interesting to see what impact city services have on land values. I’m not sure if land value data is available (anyone know?) but mashing it up against the location of parks, community centres, schools, firehalls, and other city amenities would be interesting. While potentially interesting to prospective home owners (maybe a real estate agency should develop – or pay to develop – this app) I think it might also be of interest to the electorate and politicians.

One last one: A Library-Amazon Greasemonkey script

A Library-Amazon Greasemonkey search script allows a user to see if a book being displayed on an Amazon.ca website is available in the Vancouver Public Library. This has two benefits. First, it is WAY easier to find books on the Amazon site then the library site, so you can leverage Amazon’s search engine to find books (or book recommendations) at the VPL. Second, it’s a great way to keep the book budget in check!

The Vancouver Public Library has said that it will share access to its database that would allow such an app to work. I believe I have the email address for the relevant person somewhere on my computer who can make this happen. (I can get the contact info for the right person if someone nudges me.) Better still the necessary Greasemonkey script is already available (scripts exist for Palo  Alto, Seattle and Ottawa), it would be great if someone tweaked the script so it worked with the VPL.

Of course, I’m hoping that others are already hatching plans about how they’d like to use the city’s data to create something they feel passionate about. And remember, if there is an app you’d like to create but the data set isn’t available – take the Open Data survey to let your voice be heard! If any of these ideas interest you, go for it. If I can help in any way, let me know, I’m keen to contribute.

Garbage Collection now IS sexy: Introducing VanTrash

garbage-can_rgbA few months ago some of you will remember I blogged about How Open Data even makes Garbage collection sexier, easier and cheaper. I suggested that, with open data, coders could digitize the city’s garbage collection schedule and city maps and enable citizens to download it into their calendar or even set up a recurring email reminder.

The post went fairly viral being picked up places like here and here. As a result, two weeks later Luke Closs and Kevin Jones, two Vancouver based coders with a strong sense of fun and civic duty emailed me and said they’d actually scrapped the data and had created an alpha version of the site. I offered my (meagre) skills to help move the application forward and we began working on it.

Today, I’m pleased to say that VanTrash has been launched. If you live in Vancouver (or don’t) please do take a look at the website.

Our goal with VanTrash is twofold. First: we want a great service that leverages public data to helpmake our fellow citizens’ lives a little better or easier. Second: we’d like to sign up 3000 or more users.

Since there are about 260,000 households in Vancouver (although many have private contracted garbage pick up) 3000 users would represent between 1-2% of all households for whom the city collects their garbage. There are not that many services that citizens opt in for that get this market penetration – especially services created for virtually nothing. The more users we get, the stronger the message we send to government’s everywhere that government is a platform and that we need to let citizens built on top of it. More importantly, we demonstrate that great, and useful, things can be done for cheap, a lesson citizens and governments need to constantly relearn.

So if you live in Vancouver, and you think there service would be helpful to you (or perhaps to a forgetful or absent minded friend, family member or neighbour) please sign up or spread the word.

Vancouver's Open Data Portal: Use it, or Lose it.

As some of you saw yesterday via Twitter, Vancouver has launched a beta version of its open data portal. This is a major milestone for Vancouver on several levels. It is a testament to our politicians, who had the vision and foresight to embrace this idea. It is a tribute to the city’s staff who have worked unbelievably hard to make this project come alive so quickly. It is a triumph for those of us who advocate and have been working with the city to move us towards open government and government as platform. Finally, it represents an enormous opportunity for coders and citizens alike, and it is to this group that I’d like to address this blog post.

The Data Portal represents an opportunity for citizens, especially citizen coders, to help create a City that Thinks Like the Web: a city that enables citizens to create and access collective knowledge and information to create new services, suggest new ideas, and identify critical bugs in the infrastructure and services, among other a million other possibilities.

But the open data is only the part of the puzzle. Yes, our data is now beginning to be set free. But we have to use it.

If not, we’ll risk losing it.

I wish I could say that the city will share data no matter what and that political support will continue forever. But the fact is, municipal resources are limited. While the potential of open data is enormous, we need more than potential; we need some wins. More importantly, we need an active and engaged community working to make Vancouver better, more efficient, and more interesting because of our open data. We need to show politicians and public servants in Vancouver, but also in Edmonton, Calgary, Ottawa, Toronto, Montreal, Nanaimo, Moncton and other places across the country that citizens want access to data, and that if we get it, we will help their city (or province, or country) come alive in new and inventive ways.

Back in June, shortly after City Council passed Open3 (the nickname for the Open Motion), I gave this presentation to both City staff and at Open Web Vancouver. In it I described how “the bargain” Clay Shirky says exists on every successful web 2.0 site also exists in cities that want to think like the web.

In our case the bargain is simple: On one side, the city agrees to share as much data as it possibly can, in open formats, as quickly as it can. On the other side, the community – and in particular citizen coders – must make that data come alive in applications, websites and analysis. The city has taken the first step in fulfilling its side of the bargain. (And yes, we need to keep adding more data; there is work to be done.) Now it is time to activate the other half of the bargain. If we don’t, we put the deal at risk.

So what can you do?

First, you can code up an app, or find ways to help those who are. Indeed, there is going to be a Hackathon tomorrow evening at the Vancouver Archives to do just this. A number of projects are already underway that you can join – or start one yourself! I will be there myself, and I encourage you to swing by too.

Second, if you’d like to build an application, but the dataset you need is currently not available, then complete the city’s Open Data priority survey!

Third, come add ideas, resources and projects to the Vancouver Open Data Wiki.

I’m enormously excited to see what evolves next. As many of you know, I’ve been advising the Mayor’s Office on open data and open government for several months now – and through my work with them and with city staff, I’ve been deeply impressed by the energy and commitment that I’ve seen. As far as I know, only three major cities have created data portals such as this, and to do this in three months is incredible. Over the next few days I’m going to share some more thoughts on what the Open Data portal means for Vancouver. If you get a chance I hope you’ll send me your thoughts as well, or post some to your own blog if you have one.

Many eyes make all bugs shallow – especially when the eyes get smarter

[Please bear with me for the next 24 hours – I’m moving to a new hosting company, and there may be some glitches here and there to work out. Thanks.]

My friend Diederik has been writing a number of cool posts over at his blog Network-labs.org. For example he has an awesome jetpack plugin that predicts the likelihood a bug will get fixed and a plugin that allows users to rate how badly a bug is being flamed (to spot counterproductive behaviours).

But he recently published a very cool post that uses data from Mozilla bug submissions over the past decade to demonstrate that bug submitters become more proficient over time. However, there are outliers who are a “drag” on the system. More importantly, I believe his data can be interpreted in another way. That, with some minor investment (particularly some simpler vetting screens prior to reaching bugzilla) bug submitters could learn faster.

For example, a landing screen that asks you if you’ve ever submitted a bug before might take newbies to a different page where the bugzilla process is explained in greater detail, the fact that this is not a support site is outlined, and some models of good “submissions” are shared (along with some words of encouragement). By segmenting newbies we might ease the work burden on those who have to vet the bugs.

I think this also has implications for cities and 311 systems (systems that essentially allow citizens to report problems – or bugs – with city infrastructure or services). There will inevitably be people who become heavy users of 311 – the goal is not to get frustrated with them, but to move them up a learning curve of submitting helpful and useful information as quickly as possible. Ignoring them will not work. Strategies for engagement, including understanding what is motivating them and why they continue to use the system in an ineffective way, could help save the city resources and help foster a larger army of citizens who use their spare social capital to make the city a better and more resilient space.

SXSWi Panel: Fostering Collaborative Open Source Communities

Yesterday I saw this academic journal article and was reminded about how an individuals behaviour can negatively impact and groups productivity. In his article “Overlooked but not untouched: How incivility reduces onlookers’ performance on routine and creative tasks.” in the Organizational Behavior and Human Decision Processes (109: 29-44) Amir Erez describes how even just witnessing rudeness resulted in diminished creativity, increased one’s own negative behaviour, damaged productivity and short term memory.

This is a perfect example of why I believe we need open source communities to foster collaborative cultures that nudge people to engage in positive and constructive ways.

In pursuit of talking about this more, I’ve put together a presentation proposal for SXSWi in which I’d like to build on my FSOSS presentation (which has logged over 15000 views since going up on SlideShare.net two years ago) on how the skills and tools from the field of negotiation and collaboration can help improve community management and productivity in open source communities. If this sounds at all interesting to you, I’m hoping that you’ll consider going to the SXSWi Panel Picker website and voting for this panel.

Since FSOSS 2008 I’ve done more research and work in the area and so have more examples to share out of the open source space. In addition, I’ve been working with Diederik Van Liere at the University of Toronto’s business school trying to get data around how behaviour impacts a open source community’s effectiveness.

Title:

Fostering Collaborative Open Source Communities

Description:

Community management is a core competency of open source. So what skills, tools and culture can facilitate and enable collaboration? Drawing from negotiation theory David shares what open source project participants can do to foster sustainable and effective collaborative communities where conflict is productive and not soul-sucking or time consuming.

Questions Answered:

  1. What skills does an open source project leader need
  2. How to a minimize destructive conversations?
  3. How can I encourage participation in my open source project?
  4. How do enable members of my open source community to work together better?
  5. What is negotiation theory?
  6. Someone is being a troll in my discussion group. What do I do?
  7. How can I attract more users to my open source project?
  8. How can I make my open project contributors more effective?
  9. I don’t like arguing with people, what should I do?
  10. I think I may be abrasive, what should do?

Category:

Community / Online Community, Open Source, Self-Help /Self-Improvement, User Experience

How to Engage Citizens on a Municipal Website…

Sometimes, it’s nice to be small, the City of Nanaimo has been pushing the envelop on open data and open government for a number of years now.

Recently, I was directed to their new Council Agendas and Minutes webpage. I recommend you check it out.

Here’s why.

At first blush the site seems normal. There is the standard video of the council meeting (queue cheesy local cable access public service announcement), but them meeting minutes underneath are actually broken down by the second and by clicking on them you can jump straight to that moment in the meeting.

As anyone who’s ever attended a City Council meeting (or the legislature, or parliament) knows, the 80/20 rule is basically always in effect. About 80% of the time the proceedings are either dead boring and about 20% (often much less) of the time the proceedings are exciting, or more importantly, pertinent to you. One challenge with getting citizens engaged on the local level is that they often encounter a noise to signal problem. The ratio of “noise” (issues a given citizen doesn’t care about) drowns out the “signal” (the relatively fewer issues they do care about).

The City of Nanaimo’s website helps address this problem. It enables citizens to find what matters to them without having to watch or scroll through a long and dry council meeting. Better still, they are given a number of options by which to share that relevant moment with friends, neighbours, allies or colleagues via twitter, facebook, delicious or any other number of social media tools.

One might be wondering: can my city afford such a wizbang setup?

Excellent question.

Given Nanaimo’s modest size (it has 78,692 citizens) suggests they have a modest IT budget. So I asked Chris McLuckie, a City of Nanaimo public servant who worked on the project. He informed me that the system was built in-house by him and another city staff member, it uses off-the-shelf hardware and software and so cost under $2000 and it took 2 week to code up.

2 weeks?

No million dollar contract? No 8 month timeline? No expensive new software?

No. Instead, if you’re smart, you might find a couple of local creative citizen-hackers to put something together in no time at all.

You know what’s more, because Chris and the City of Nanaimo want to help more cities learn how to think like the web, I bet if the IT director from any city (or legislative body) asked nicely, they would just give them the code.

So how Open is your city? And if not, do they have $2000 lying around to change that?