If connection goes down while uploading, shouldn't fail - should queue and retry

We could use javascript auto-location to provide a list of local issues rather than just postcode.

Would be useful to have an automated 'watch list' for those skating close to the being-banned edge, etc.

Quite often the photos of new problems on the homepage are rotated the wrong way. Would be nice to either sort this automatically, or if that's not possible, have some trivial way of righting them.

After updating an report from a list of pages near a place, or whatever, it would be nice to have some kind of link back to where you were before giving the update.

So that we can give specific prompts (e.g., if street lighting is picked then it could ask the user to find the light number) rather than generic hints.

Related to this: add in categories for reports which we DON'T want (e.g. noise, ASB, speeding, bins, etc.) and filter the user elsewhere if they are selected.

When browsing reports near a postcode, it would be good to be able to zoom out a bit.

Single hosted service that can be translated into any language, that allows arbitrary areas to be included, and which has federated moderation (i.e certain parts of the world are looked after by different admins)

After submitting a report to FMS from my iPhone, I get an email with a link; clicking that link takes me to a page where I see a map, the photo I took, and some boxes to fill in.

If I click the map to modify the location, the page reloads and there's no photo on the reloaded page.

Make the android (and probably iPhone) app handle the entire process of reporting an issue without having to wait for an email and then follow a link to the website.

(this probably requires having some kind of login - for the android app accepting a Google login would probably do, since almost anyone using an android phone will have a Google account).

1. Don't register a GPS handler on startup, only when you're about to use it
2. Once the GPS handler has got a fix, save it into session data with system time - then onResume, check whether there's already a recent fix

Once a user has reported three or more problems, their account changes status from 'newbie' to 'regular user'.

A moderator looks via an admin interface for locations where two or more people have reported at least three problems within a km of each other.

In situations where they have they write to the near neighbours and suggest they might like to set up a Facebook group, or other similar small group. Where this happens FMS records this fact publicly.

According to one user:

""I've found the automatically generated text description of the location of the problem (based on pin location on the map) is sometimes not very helpful to the council, especially in situations like a large junction where several roads meet. Seeing the text that is going to be sent to the council gives you the chance to add in a better description of the location.

(Poor text descriptions has been the cause of several items not being resolved by the council except after extra chasing from myself.)"

When a user tells us via survey that their problem has not been fixed, we could check to see if their problem was reported within an area where we supply epetitions. If it was, we could encourage them to make a petition to help solve their problem.

Allowing people to update a report by replying to an email might be a bit tricky, given out of office responses etc., but at the least it should have a unique link if the alert is to the problem reporter, letting them write an update without then having to confirm their email - or in fact if the alert is to anyone, that could still work.

Needs rewording, as some find it unclear whether they need to tick/untick.

For example, water leaks to water companies (share data with OFWAT?), housing associations, national parks, the Highways Agency (without having to ask the user if a road is Highways Agency or not).

• Green boxes, etc.
• Abandoned supermarket trolleys.
• TfL, Bear Scotland, etc.
• Crossrail (who emailed in Jan 2011 to ask to be added, sending contact details)
• Apparently Scotland only have one water board (Scottish Water) so this might be an easy one to start with. List of water companies websites http://www.water.org.uk/home/resources-and-links/links/water-operators
• OpenReach (poles)

If someone reports an issue, includes a photo, but makes a mistake in the form, the site should remember the photo and not make them upload it again.

Currently, they just say "New local problems on FixMyStreet" or similar - it should change depending upon the contents of the feed somehow (though the feed just has a point, not the postcode the user might have signed up with, hmm)

Though might be implemented by better varnish default.

Introduce an easy to use, prominent channel to allow users of FixMyStreet to directly and privately communicate with the authors of problems.

This means adding a facility for users to have accounts, and for them to login the system before making new reports. A few regular users have been saying the site is difficult to use without this.

Logins would include Google, Facebook and mySociety's own authentication. The current problem creation process for new users would remain completely unchanged, though, with login being made available through a standard 'Top Right Hand Corner' option in the menu bar. When you are logged in as a user, you both get to create problems without email confirmation, as well as having a central place to see all your problems, their status reports, and any status updates from people other than you.

Most users with logins will create them on the page that comes up after a user has confirmed their email address through an email loop, at the end of the problem reporting process.

Users will have an option to make their personal pages public, for sharing information about what they have been doing.

We must conversion track relative effectiveness of putting account creation before and after confirmation email loop.

The game that we built at the Christmas hack day isn't really finished. ( URL http://fmsgame.mysociety.org ). In particular:

• It needs to only return older/old problems; it is currently returning the newest around a location - need API for looking up reports, even if it's an API of RSS feeds.
• All the text needs improving, and perhaps the URL.
• We should have users chase down problems that have been marked fixed by councils, to check if they are marking things as fixed that are not actually fixed.

When you finish reporting a problem, the site checks to see if there is an a problem of unknown status within, say, 750m of the postcode you originally put in.

If there is, it says:

"Do you fancy a walk? Right now? If so, you could help us by walking to X to and telling us what's going on."

Useful for those browsing the 'All Reports' page or getting email updates

Features that could/should be implemented include offline reporting (working when not online/storing reports for submission/review), a shinier UI, a map showing other people's problems, the ability to leave updates on problems, and integration with user accounts. Also perhaps the ability to choose photos that have already been taken.

As a first step, the apps should be updated to match the new mobile design, though offline reporting/user account remembering are certainly things to be considered.

Bump http://www.fixmystreet.com/posters/ link to the front page with a massive "Like FixMyStreet? Tell your friends about it" message.

Problematic on some handsets, apparently

Many phones now come with the ability to take geotagged photographs with the built in camera.

This would mean adding a new homepage option to FixMyStreet that said "Upload your geotagged photo here". When a user used this option it would skip the phase where they stick the pin in the map, and just ask them for the other fields required to make for a complete report.

Again, take a look at the emails we send - can we reword these to promote the fact that we can post problems directly into their databases if they'll let us?

Take a look at the wording of the emails we send them.

Things like "planned", "investigating", "Not fixing due to beyond our control" on top of just open/fixed.

It turns out that some councils have databases of, and unique identifiers for, all their public street lights. This is the most common form of problem report on FixMyStreet, and so it could help get more of these more successfully resolved if we could import the data for councils that provide it, and then modify the user interface to help people identify exactly where their problem is.

I don't care if Matthew doesn't like the idea. I've never understood why we don't - councils ignore problems far too easily.