If you run a Facebook page or group for a local community, you might like to add a FixMyStreet feed. This will publish recent reports, made within the geographic area that you define, as posts on your Facebook page, like this:
Adding a FixMyStreet feed to your Facebook page is not difficult, but you do need to be an administrator for the page you want it on.
Also, it is a multi-step procedure. In other words, you might like to fetch yourself a cup of tea before following along with the instructions below.
Here’s what to do:
1. Visit FixMyStreet.com and locate the area you want a feed for
Does your Facebook page deal with a particular city or town, or an area within that town?
You’ll probably want to publish the FixMyStreet reports that are made within that area. The wider the area you choose, the more reports you will be publishing, so think carefully about what your followers will actually want to see on your Facebook stream.
Once you’ve decided, locate that area on FixMyStreet by putting a postcode or place name into the box on the homepage. It doesn’t need to be precise; you just need to locate any spot within the area that you want to cover.
You’ll be taken to a page showing all recent reports for the surrounding area.
Don’t worry if this isn’t the exact area that you want your feed to cover, so long as you’re at a point within that area – we’re going to refine that in the next step.
You can click and drag the map or zoom in and out if you’re not quite within the area that you want to be.
2. Create your feed
At the very foot of the FixMyStreet page, below the list of reports on the left, you’ll see a little icon marked “get updates”. Click on this.
You now have the choice of several options. You can get a feed for:
– All problems reported within 2km, 5km, 10km or 20km, or within a population of roughly 200,000 people
– All problems reported to your local council
– All problems reported within the ward of your council
Choose which option most closely matches the area that your Facebook page deals with, and click the green button marked ‘Give me an RSS feed’.
3. Grab the URL
Your feed page will look something like this:
It’s basically just the data from FixMyStreet, with none of the site’s styling or functionality around it. This is what we need Facebook to grab and publish on your page.
You will need the URL (web address) of this page in a short while – just keep it open while you go through the next steps.
4. Log into Facebook
You don’t need to be logged in as the page that you want the feed on; it’s fine just to be logged in as yourself, the administrator of that page.
5. Connect an RSS app to your Facebook page In order to publish FixMyStreet reports, you’ll be using what’s called an RSS feed – a stream of data that can be picked up and published anywhere else. In this case, the data stream is found on what you saw in step 3: the ‘bare bones’ FixMyStreet page; and the target for publication is your Facebook page.
Facebook itself does not provide a way to publish RSS feeds, so we’re going to use a third-party app. The one we’ve identified is called RSS Graffiti and you can find it here.
RSS Graffiti have created a video to demonstrate the following steps (and I’ve also explained them in writing below, with specific instructions for using FixMyStreet as a source):
Install this app by clicking ‘OK’ on each of the three permissions pop-ups.
6. Set up your feed
Click on ‘Create publishing plan’. Give your plan a name – ‘FixMyStreet’ is the obvious one in this case.
Every publishing plan needs a source (where the data is coming from) and a target (where it will be published).
Your source is that web address we found on FixMyStreet earlier. Click on ‘new source’ and enter it into the URL box. You’ll need to take out the http://www portion of the web address, so that it just starts with ‘fixmystreet.com‘ – so for example, mine might be fixmystreet.com/rss/reports/Brighton+and+Hove.
Click ‘add source’ and wait. I found that this stage sometimes times out, but succeeds eventually if you try again.
Now you can set up your feed however you like it – or just leave the defaults in place. Don’t worry too much, though, because you can come back and tweak all the settings at any time.
This interface allows you to pick a title for your feed, and add a message to every item it publishes: probably a good idea, because it helps give context to these posts that are going to appear in your Facebook stream.
FixMyStreet reports are often written in the first person, so if they appear without a title or explanation, they may look as if they are posts from you yourself – take a look at the example at the top of this post and you’ll see what I mean.
While you are in this interface, you may wish to set a maximum number for how many posts can be made at once.
In the area I chose, we only get about one report a fortnight, so the quantity isn’t really a concern – but if you are covering a large geographical area, consider placing a cap on the number.
Note that your feed will not start publishing out until the next report is made on FixMyStreet, unless you select a start date that is in the past – you can do this on the ‘advanced’ tab.
Save your settings. Now it’s time to set the target – the page that your feed will be published on.
Click ‘new target’ and choose ‘Facebook’.
You’ll then be given a list of all your Facebook pages. These will include your own personal page, and any page that you have admin rights for.
There are some formatting options – I just went for the default – and then click ‘save changes’.
Just one final step: you need to click the ‘OFF’ button to change it to ‘ON’, and set your feed running. You can return to this page at anytime to set it back to ‘OFF’ if you so desire.
RSS Graffiti say that it can take up to 30 minutes for your feed to start publishing onto your page – in my experiments, I found that it was actually quite a bit longer than this, but when I returned the next day, it had started working.
Do let us know in the comments below if you go ahead and install this functionality – plus any tips you might have.
By the way, you can use this method to publish any RSS feed to your Facebook page, so you could also publish anything from blog posts to YouTube videos, so long as you can find the RSS source, which is usually signaled by that little orange icon:
What impact do mySociety sites actually have? We could lose a lot of sleep over this important question – or we could do something concrete, like conducting academic research to nail the answers down for once and for all.
As slumber enthusiasts, we went for the research option – and, to help us with this commitment we’ve recently taken on a new Head of Research, Rebecca Rumbul. Watch this space as she probes more deeply into whether our tools are making a difference, both in the UK and abroad.
Even before Rebecca came on board, though, we had set a couple of research projects in motion. One of those was in partnership with the University of Manchester, funded by the ESRC, which sought to understand what impact our core UK sites (FixMyStreet, WriteToThem, TheyWorkForYou and WhatDoTheyKnow) have on their users, and specifically on their level of political engagement.
Gateways to participation
It’s perhaps worth mentioning that, while our sites appear, on the face of it, to be nothing more than a handy set of tools for the general citizen, they were built with another purpose in mind. Simply put, each site aims to show people how easy it is to participate in democracy, to contact the people who make decisions on our behalf, and to make changes at the local and national levels.
Like any other online endeavour, we measure user numbers and transaction completions and time spent on site – all of that stuff. But one of the metrics we pay most attention to is whether users say they are contacting their council, their MP or a public body for the first time. Keeping track of this number ensures that we’re doing something to open democratic avenues up to people that haven’t used them before.
But there are plenty more questions we can ask about the impact we’re having. The University of Manchester study looked into one of them, by attempting to track whether there was a measurable change in people’s political activity and engagement after they’ve used one of our sites. On Monday, researchers Rachel Gibson, Marta Cantijoch and Silvia Galandini presented their findings to an attentive audience at King’s College London.
The project has taken a multi-pronged approach, asking our users to complete questionnaires, participate in online discussions, or keep a 12-week diary about political and community engagement (thanks very much to you, if you were one of the participants in this!). The result was a bunch of both qualitative and quantitative data which we’ll be able to come back to and slice multiple ways in the future – Gibson says that they haven’t as yet managed to analyse all of the free text diaries yet, for example.
In itself this study was interesting, because not much research has previously been conducted into the impact of digital civic tools – and yet, as we know from our own international activities, people (not least ourselves) are launching sites all over the world based on the premise that they work.
Some top-level conclusions
The research will be published in full at a future date, and it’s too complex to cover all of it within the confines of a short blog post, but here are just a few of the takeaway findings:
- A small but quantifiable uplift in ‘civic participation’ was noticed in the period after people had used our sites. This could include anything from working with others in the local community to make improvements, to volunteering for a charity.
- No change was found in the level of political influence or understanding that people judged themselves to have. This was a surprise to the researchers, who had thought that users would feel more empowered and knowledgeable after contacting those in power, or checking up on their parliamentary activity.
- As with our research back in 2011, the ‘average’ user of mySociety sites was found to be white, above middle-aged, and educated to at least degree level. Clearly this is a userbase which we desperately need to expand, and we’ll be looking carefully – with more research and some concentrated outreach efforts – at how we can do that.
- Users tended to identify themselves as people who already had an interest in politics. Again, here is an area in which we can improve. Of course, we’re happy to serve such users, but we also want to be accessible to those who have less of a baseline interest.
- Many users spoke of community action as bringing great satisfaction. In some cases, that was getting together in real life to make improvements, but others saw something as simple as reporting graffiti on FixMyStreet as an action that improved the local area for everyone.
Thanks to the University of Manchester researchers for these insights and for presenting them so engagingly. We’ll update when the full research is available.
Residents of East Sussex County Council and Hart District Council can now report potholes, broken street lights, and other local issues, simply and speedily. The two local authorities are the latest to integrate FixMyStreet onto their own websites.
Whether reports – and subsequent updates – are made on the councils’ websites, or within their boundaries on FixMyStreet.com, they will be published on both the council site and FixMyStreet.
FixMyStreet is a proven aid to channel shift, moving report-making online, to save time and money for both residents and councils. Hart and East Sussex’s adoption of the software is just one strand of their ‘digital by default’ approach to transactional services.
If you’re from a council, and would like to find out more about FixMyStreet for Councils, everything you need to know is here.Image: Dominic Alves (CC)
We’re pleased to announce new moderation features for clients of FixMyStreet for Councils.
This new functionality enables nominated members of staff to edit user reports from within the FixMyStreet front end.
It’s quick and easy, and allows you to react immediately to unwanted content on your site. Read on to find out more.
What’s wrong with this report?
So what is wrong with the report in the screenshot above?
If you run a site on the FixMyStreet platform, you’ll be familiar with this kind of report, and the chances are that you’ll already be twitching to edit it.
User-generated content is wonderful in many ways – but it can also present problems on a public-facing site. Let’s look at a few of the potential issues in the report above:
- The user has included his phone number in the report description, and now it’s available for anyone to see.
- The user’s name is also public. While this is the default option on FixMyStreet, users often get in touch to say that they meant to make their report anonymously (an option on FixMyStreet, but one which the user can only access at the point of submission).
- There’s an inappropriate photo. This one is a statue of Carl Jung, which obviously has nothing to do with the report. But even relevant photos can be problematic: imagine if it was a graphic depiction of a dead animal, or some rude graffiti.
- Profanity: in the example above, we’ll imagine that “pesky” is a mild profanity, but experience tells us that users don’t always hold back on their language.
There are other common problems too, not represented in this report. Users sometimes post potentially libellous information: naming someone they suspect of flytipping, for example, or giving an address where they believe planning permission has been flouted.
In the run-up to local election, councils have to be particularly sensitive to any content that might be construed as political – commonly they wish to remove any mention of any candidate.
Moderation in all things
So we’ll shortly be introducing the ability for client moderation of sites. Councils or other bodies who run FixMyStreet will be able to nominate trusted users and give them the ability to edit problematic reports from within the report page.
When logged in, these users will see a “moderate” button on every report – this feature will not be available to any user unless explicitly authorised.
As you can see, this panel provides the ability to:
- Hide the report completely
- Hide the name of the poster
- Hide or show a photo (if one was originally provided)
- Edit the title and body of the report.
For some reports, it might be necessary to make a number of edits, and finally submit the changes:
The moderator can also add a reason for the changes, so it’s recorded if a colleague needs to know the history of the report in the future.
This functionality gives a lot of power to admins to remove inappropriate information – but the user took the time to submit their report, and it’s only fair to let them know it’s been changed. So the system sends them an automatic email, as below:
Finally, the system automatically updates the report to show that it has been moderated. As well as a timestamp, it signals where any information has been removed in the title or body of the report.
Updates can be just as problematic as reports, so the same functionality will apply to them.
We’d welcome feedback on this mechanism, so please let us know if you think we’ve missed any features.
Note: These screenshots are from our work in progress and do not yet display the slick design that we habitually apply right at the end of the build process. Please regard them as preview shots only!
So we wanted to build an app for FixMyStreet. Easy: we just had to make a cut-down version of the website, right?
Hmm, not quite.
Now he explains a little more about what informed the decisions he made during the apps’ development.
Moving the map, not the pin
When you use the desktop version of FixMyStreet, the first thing it asks for is your location, and there’s a good reason for that. It’s such a good reason that it needed to apply to the app as well.
On the desktop site we ask you to input your postcode or street name. With a mobile app, it’s much more likely that you’ll be reporting a problem that’s right in front of you, so we can usually skip that step and show you a map of your current location.
However, while the accuracy of geolocation technology is pretty good, it’s not perfect, so we wanted to let users fine-tune the location.
On the website you click on the map to drop a pin where the problem is, but we’ve found this isn’t the best solution on a small screen. Fingers are big and the end of a pin is small so it can take several clicks to correctly position the pin.
We quickly realised that having a central static crosshair, and moving the map to the location was a much easier and more accurate way to set a location.
Sending reports made offline
As we explained in the previous post, one of the benefits of the apps over the mobile site is that you can make reports even if you have no phone coverage. The app stores all the details until you get back within range and you’re ready to send it off.
One decision we made, which might seem initially puzzling, is that these offline reports don’t automatically get sent off to the council once you’re back within range of a phone or wifi signal.
There are two linked reasons for this, and they’re both related to the fact that FixMyStreet lets you report a problem even if you don’t know who to send it to.
Simply, before we can work out who to send the report to, we need to know exactly where you are – and that you are within FixMyStreet’s area of coverage (ie, within the UK).
Your location also dictates the categories that we show you. Each council has its own categories, and in areas covered by two tiers of government, each council will deal with different types of report. So for example, your county council might deal with potholes, while your district council handles dog fouling.
Once you’re back online we can check that the location is one we can accept a report about, and then fetch the list of categories for you to pick from.
In effect, this delay is also a second chance for you to check your report before you send it off, although that was never the reason for the decision!
The constant map
We initially designed it with the map only appearing when you needed it, but having the map underlying the reporting process provides a nice bit of continuity with the website, and seemed to make the app cohere better too. So, while there’s no particular reason for it to be there, we made the decision to keep things uniform.
If anything else about the app has got you wondering, do feel free to leave a comment below!
In this post, we want to explain a bit more about why we spent time and effort on making them, when normally we advocate for mobile websites.
Plus, for our technical audience, we’ll explain some of the tools we used in the build.
The why bit
When we redesigned FixMyStreet last year, one of the goals was to provide a first class experience for people using the website on their mobile phone browsers. We’re pretty happy with the result.
We’re also believers in only building an app if it offers you something a mobile website can’t. There are lots of reasons for that: for a start, apps have to be installed, adding a hurdle at which people may just give up. They’re time-consuming to build, and you probably can’t cater for every type of phone out there.
Given that, why did we spend time on making a mobile app? Well, firstly, potholes aren’t always in places with a good mobile signal, so we wanted to provide a way to start reporting problems offline and then complete them later.
Secondly, when you’re on the move you often get interrupted, so you might well start reporting a problem and then become distracted. When that happens, reports in browsers may get lost, so we wanted an app that would save it as you went along, and allow you to come back to it later.
And the how bit (with added technical details, for the interested)
Having decided to build an app the next question is how to build it. The main decision is whether to use the native tools for each phone operating system, or to use one of the various toolkits that allow you to re-use code across multiple operating systems.
We quickly decided on using Phonegap, a cross platform toolkit, for several reasons: we’d already used Phonegap successfully in the past to build an app for Channel 4’s Great British Property Scandal (that won an award, so clearly something went right) and for Züri Wie Neu in Zurich, so it was an easy decision to use it again.
We decided to focus on apps for Android and iOS, as these are the two most popular operating systems. Even with this limitation, there is a lot of variety in the size and capability of devices that could be running the app – think iPads and tablets – but we decided to focus primarily on providing a good experience for people using phone-sized devices. This decision was partly informed by the resources we have at hand, but the main decider was that we mostly expect the app to be used on phones.
There was one big challenge: the functionality that allows you to take photos in-app. We just couldn’t get it to work with older versions of Android – and it’s still not really adequate. We just hope most people are updating their operating systems! Later versions of Android (and iOS) were considerably less frustrating, and perhaps an earlier decision to focus on these first would have led to a shorter development process.
On balance though? We’d still advocate a mobile-optimised browser site almost every time. But sometimes circumstances dictate – like they did for FixMyStreet – that you really need an app.
We’d give you the same advice, too, if you asked us. And we’d happily build you an app, or a mobile-friendly site, whichever was more suitable.
They’ve been available for a little while, but we didn’t make a big fuss when they went live.
We often like to release our new products quietly. This gives us a chance to pick up on any problems and fix them before they go to a wider audience.
But now the apps are ready for more general use. So go for it!
A bit of background
We first released an iPhone FixMyStreet app back in 2008, which now seems reasonably fast off the blocks – the iPhone was only available in the UK from late 2007.
That app was followed by an Android one and, thanks to our volunteers, a Nokia app too.
Last year, we launched a new design for the main FixMyStreet website. Based as it is on ‘responsive design’ (where the site resizes itself according to the device it’s being viewed on), the site works elegantly within your mobile browser, so we were not too troubled by the fact that our apps had begun to date. People could simply go to www.FixMyStreet.com on their mobiles.
We removed those early apps from the Apple and Android marketplaces until we could allocate our resources to creating something better.
As you’ll know if you’ve accessed FixMyStreet from your phone’s browser, the website works just fine for most circumstances. But there are some times when only an app will do – our Developer Struan will explain more about that in a later post. He’ll also be looking at some of the design decisions we made.
So, what new features can you expect when you download the FixMyStreet app?
- Make reports even when you have no phone coverage Sometimes you’ll want to make a report even when you’re out of phone range. Your report will be saved in-app until you can send it off.
- Retains unfinished reports Close the app, lose power on your phone, get distracted and start something else.. none of it matters – your report will still be saved.
- Allows photographs Take a snap with your phone and attach it – or use an image you already have in your photo roll (you can add photos on the main website too, of course).
- Smooth, new design The look and feel is now in line with the main FixMyStreet website.
A note about Android
At the moment, the FixMyStreet app is only available for Android 4.1 onwards. Here’s why.
Developing for Apple devices is simpler than for Android, because there are only a handful of devices an app will be viewed on – the various iPhone versions, the iPads, and iPod Touch. Android, on the other hand, is used over a massively diverse range of phones, all with different capabilities.
For a small organisation like mySociety, it is hard to test the app across every single Android device, so we’ve taken the approach of releasing the app for the latest version.
We’ve had particular issues with photographs in earlier versions of Android – again, Struan will write more about this in a subsequent post – but we are still working on it. And don’t forget, as mentioned above, you can always access www.fixmystreet.com on your mobile browser for a totally optimised experience on any smart phone.
Shout-out to the testers
We want to give a massive “thank you” to all the people who helped us test the new app – your feedback has been so helpful at every stage of the build, and has informed the design decisions we’ve made.
This month we released a new version of FixMyStreet. Amongst the new features, fixes, and thingamajigs were some small improvements added by two volunteers, Andrew and Andy.
Even though these are not core pieces of functionality — in fact, precisely because they are not — we want to draw your attention to why they were included, and why this is a Very Good Thing. And perhaps, if you’re a coder who wants to put something into an Open Source project but hasn’t quite found a way in, Andrew and Andy’s work will nudge you into becoming a contributor too.
One of the axioms of Open Source is that, because anyone can read the source code, in theory anyone can contribute to it. In practice, though, it’s not really as simple as that. Both ends of the “anyone can contribute” idea require effort:
- Before contributing to a project of any complexity (as we hope you want to do), there’s often a lot to learn, or figure out, before any work can even begin;
- Before accepting contributions to such a project (keen as we are to do so), there’s an overhead of testing, checking, and managing the incoming code.
The ugly real world
The basic issue here is that software is complex — no matter how well-written, tested and documented program code is, if the problem it’s solving is in the real world, it’s not going to be simple.
This is especially true of anything used by the public, because often you can only make things seem simple at the front (such as a clean web interface or “user journey”) by working hard behind the scenes with data structures and processes that handle the underlying complexity. It’s inevitably true of any projects which have been developed over time — programmers like to use the term “legacy code” to describe anything that wasn’t written then way they’d choose to write it now.
Often the problems that software is solving are not quite as obvious as they first appear. At mySociety we’ve got a wealth of experience and actual usage data that ultimately changes the way we build, and develop, our platforms. We understand the fields we work in well (technically, the nerds like to call these the “problem domain”), whether it’s governmental practice or civic user behaviour, and that’s often knowledge that’s not encapsulated anywhere in the program code.
Furthermore, any established platform must protect against the risk that new changes break old behaviour — something that regression testing is designed to catch. This is especially important on platforms like FixMyStreet or Alaveteli where the software is already running in multiple installations.
This is why we have a team of full-time, experienced, and (thanks to our rigorous recruitment process) talented programmers who can invest the time and effort to be familiar with all these things when they set to work coding.
But this builds up to an impediment: sensitivity to any of these issues is enough to make anyone think twice about simply forking our code and starting to hack on it for us.
How it sometimes works
In practice, then, how does anything get contributed? How come it doesn’t all get written by our own coders?
The answer is, of course, we do work with major contributors outside our own team (have a look at the activity on our github repos to see them) — but it always requires a period of support and on-line discussion both before and during the process. There’s also the business of testing, and sometimes politely pushing back on, pull requests (which is how code contributions are submitted). But the fact of the matter is that this is only possible for people who are willing to spend time familiarising themselves with the specific code, technologies, and practices that we’re using on that project. These tend to be hard-code devs, and — here’s the point — they’re always experienced Open-Sourcers: this will never be the first time they’ve worked on such a project.
Which is where the little features come in.
The joy of small
We noticed this problem — that contributing code to our projects is simply not easy for us or for contributors. Importantly, it’s not just us: it’s Open Source everywhere. But we can’t simply dismiss the opportunity for contribution. We want to encourage coders to do this, because we believe that Open Source is intrinsically a good thing.
We do two things to make it easier to contribute:
- We identify small features that a coder can approach without a full understanding of the code and the problem domain;
- We help people (like you!) get started by opening up a laptop at our weekly meetups.
The first of these seems obvious now: when we add issues (an idea for a new feature, or maybe a bugfix) to our github repos, if we think they’re candidates for manageable, isolated work, we tag them with the label: Suitable for volunteers (like this).
Often these turn out to be “nice-to-haves” that one of our full-time devs can’t be pulled off more pressing problems to add just now. (Case in point: Andrew added a date-picker to the FixMyStreet admin stats page, and three of our own staff had stumbled upon and applauded the difference it had made within a week of it going live).
It means it’s much easier for you to get involved, because often it’s a little, isolated piece of code. And it’s much more manageable for us, because the change you’ll be submitting is also isolated.
So if you’re looking for something to tackle, pick one of those issues, and let us know (just to check nobody else has baggsied it already). Fork the repo, cut the code, write the tests, submit a pull request!
But wait — if that last paragraph made you gulp, here’s the second thing we do: meetups. Of course, this is less helpful if you can’t make it to London on Wednesdays, but the concept is sound. Put simply, if there is a barrier to entry to diving in, and if one-on-one time with a dev, and some pizza, is what it takes to overcome that, it’s time well spent for you to come and see us.
Not 100% confident with git? Not sure when
db/schema.sqlgets used or how we like to handle migrations? No problem: we’re happy to guide you.
If this has struck a chord with you — you’d love to be an Open Source contributor one day, and you think mySociety projects make the world a better place — perhaps you should take a poke in our repos, or come along to a meetup. Start small, but do start.
Oh, and Andrew and Andy — thanks guys
Photo by Matt Katzenberger (CC)
We’re good friends with the people at Mozilla. Every Wednesday, they welcome us into their London Moz space for our weekly meet-ups. They are champions of empowering possibilities of the web through Open Source software (a world we’re part of too). And they’re all so smart and lovely. So of course we’d been looking forward to this year’s Mozilla Festival for some time.
We had a table at the “Science Fair” on Friday night, where we literally had buckets of sweets (OK, they were little plastic buckets). Tom, our director, and Dave, from our international team, talked about mySociety’s work with anyone who came close. Perhaps people were drawn in by those sweets, or the FixMyStreet demo on the monitor, or even the (new!) stickers we had to give away… but regardless of the lure, we think they all learned a little bit more about how our platforms help empower people’s civic lives: from something as simple as reporting a flickering streetlight, to holding a public authority to account, to monitoring a whole parliament. (That’s FixMyStreet, Alaveteli, and Pombola, if you were wondering).
The Mozilla Festival’s venue was, once again, London’s astonishing Ravensbourne, right next to the O2 Millenium Dome. The setting magnifies the wonder of the event. Those big round windows make it feel like being in a spaceship made of Swiss cheese. The place is so open, and so vertical, that the activity and enthusiasm doesn’t just spread out, it spreads up. There is making and teaching, learning and sharing, going on across nine floors, and it’s easy to drift up and down from one themed space to another.
We met old friends. We got to hang out some more with our Chilean brothers-in-code from Ciudadano Inteligente, and the excellent Gaba from Uruguay’s DATA, together with the good people from the OKFN. We made lots of new friends too. And all this didn’t just happen at the sessions. A lot of serendipitous encounters took place by the Alchemy coffee stations. Or on the stairs (khun Toy and khun Hui — hi!). Or in the Alphabet City party venue, afterwards.
So a big “thank you” to that Fiery Fox, and an enthusiastic high five (yes, there was an unLondonlike amount of enthusiasm on show — possibly because quite a few of the attendees were over from the USA — which it is impossible not to be caught up by) to all the people we met at the event. Dave grinned his way through a wonderful Scratch tutorial from Code Club, met a whole array of cool people, got answers to some nerdy coding questions, and learnt about the awesome Hive learning networks… and lots more things besides. That already describes a great weekend. But beyond that, we hope we might see a few new mySociety-powered sites spring up elsewhere in the world due to sparks that were sparked at mozfest last weekend.
We hope that’s a question that is hard to answer, since FixMyStreet was built for everyone – or rather, anyone who wants to report a street problem to their council. Computer whizz or internet newbie, one-off reporter or serial council communicator, FixMyStreet is for you.
All the same, we wanted to chat to someone who uses FixMyStreet regularly, to find out more about how they see the site, and whether it makes a difference. So…
Meet Steve, from Exeter.
Steve’s been using FixMyStreet almost since it launched, in March 2007:
I’m not sure how I heard about it – it’s lost in the mists of time, but it was pretty soon after it went public. I see from your archives that I first reported a problem in July 2007, but I’m sure I knew about it before then.
As a board member for Schoolforge I was always searching for UK open source projects for education, and that’s probably where I came across it initially.
FixMyStreet can be used to report any street problems to the council – it’s most commonly used for potholes, broken streetlights, fly tipping, etc. But every user has their own concerns. What does Steve tend to report?
It’s usually road-related, as I used to push /walk the kids to school when they were young, and I cycle around a lot.
So potholes, traffic lights not responding to bikes, broken street lights, bad signage, low hanging vegetation… I think I reported a crop of Japanese knotweed once.
You did! Here it is. And have the issues been fixed?
Many have, according to your archive. I reckon that using FixMyStreet helped raise the priority, but you never know – and that’s fine. I like to think that reports come to attention of the relevant people more quickly when you put them online where everyone can see them.
Also, when you see an issue in the neighbourhood, it’s easy to assume that someone else has reported it, but as it’s so easy to ping off a report with FixMyStreet, there’s no excuse not to play your part as a citizen.
I appreciate that there’s no need to find the relevant council department, website, or whatever. Just point your browser at FixMyStreet, type in a location, click on the map and type in the problem. Sorted.
Plus if others have used it to report the same issue, you’ll see straight away.
Steve’s noticed an improvement in the way that councils interact with FixMyStreet reports.
I can’t vouch for how fast they get fixed, but at least I usually get an email response from the council to acknowledge receipt.
These have improved over the years too, indicating that the council have sorted their processes to better incorporate FixMyStreet reports.
Does Steve ever browse FixMyStreet to see what has been reported in his local area? Or subscribe to email alerts?
Very rarely, but it is interesting to see what’s been going on. When you report a problem, the process shows you issues that have already been reported in the same area, so you don’t need to browse first as a separate step.
And some final thoughts…
It’s well thought out and easy to use. I especially appreciate that I don’t have to create an account as a first step to reporting a problem: more sites should use a lazy login like this. FixMyStreet has slowly improved over the years; the most noticeable thing is the improved maps.
Also, it’s open source and that is important for such civic software. I don’t know if you get much open development with others contributing, but I do suspect that others use the code.
Yep, they sure do. FixMyStreet Platform is the place to look for that activity, where there’s also a link to our mailing list. The most significant contributions come from people in other countries who are setting up their own version – FixMyStreet in Norway, for example.
Thanks very much to Steve for telling us about how he uses FixMyStreet.
This post is part of a mini-series, in which we’ll be chatting to people who regularly use mySociety’s websites.