Roadmap

OSMCha 2018 Roadmap

Goals

• Make compare functions a more community owned resource, and open to processors outside the mapbox infrastructure. Support organizations and individuals to utilize and contribute a growing set of compare functions.
• Improve the prediction of harmful edits, and enhance interface to focus on harmful (or not) edits. This way, the users can dedicate their time to the changesets that need more attention.
• Support community requests to improve OSMCha. Engage the OpenStreetMap community to use OSMCha and review the changes made in the map.

Actions

• Be responsive to community requests and make the project more community driven
  • Created the discussion list
  • Created some compare functions suggested by the community
  • Worked on some features suggested by the community
• Backend improvements
  • Refactor the Feature model to reduce the amount of data stored in the database, that way we can register a large number of Features (https://github.com/willemarcel/osmcha-django/issues/134) - (doing...)
  • Clean up the Suspicion Reasons, merging some of them (done!) or indicating the ones that are inactive (https://github.com/willemarcel/osmcha-django/issues/136)
  • Keep the backend updated with the new versions of Django and its dependencies (https://github.com/willemarcel/osmcha-django/issues/137) (done!)
• Frontend improvements
  • Improve the interface of OSMCha, adding some new features and making it easier to use
    • Allow to filter changesets by admin area or drawing a polygon (https://github.com/mapbox/osmcha-frontend/issues/208 and https://github.com/mapbox/osmcha-frontend/issues/133) - done!
    • Fix bug in layer toggle (https://github.com/mapbox/osmcha-frontend/issues/250) - done!
    • Remove automatic comments and allow the users to post comments on a changeset from inside OSMCha (https://github.com/mapbox/osmcha-frontend/issues/248) - done!
    • Allow users to whitelist other users (https://github.com/mapbox/osmcha-frontend/issues/127)
    • Improve user changesets filter page (https://github.com/mapbox/osmcha-frontend/issues/178)
    • Visualize filter results in a map (show bbox of all changesets found on a filter) (https://github.com/mapbox/osmcha-frontend/issues/165)
    • Make more clear if a changeset is not in our database (https://github.com/mapbox/osmcha-frontend/issues/155)
    • Show name of filters instead of its ids (https://github.com/mapbox/osmcha-frontend/issues/204)
    • Add support for other languages in the frontend (https://github.com/mapbox/osmcha-frontend/issues/251)
    • Create interface to show statistics about the filters results and Areas of Interest (https://github.com/mapbox/osmcha-frontend/issues/200)
• Analyse the Suspicion Reasons and create a suspicion rate, in order to make it possible the prioritization of changesets (https://github.com/willemarcel/osmcha-django/issues/140)
• Allow other QA tools to add Suspicion Reasons to changesets (https://github.com/willemarcel/osmcha-django/issues/139)
  • Set policy on how to get access to this feature (doing at https://github.com/mapbox/osmcha-collab/issues/19)
  • Create documentation
• Make it possible to push a changeset review from other QA tools
• Review osm-compare functions:
  • Improve the precision and reduce the number of false positive results - done!
  • Remove the functions that are not very useful to the community - done!
  • Improve documentation of functions
• Allow the community to create osm-compare functions to monitor the types of features they are interested on.
  • Improve documentation about how to create new functions
  • Set policy on which kinds of functions will be accepted
  • Change backend to allow changesets to receive suspicion reasons that just flag changes, but that don’t make the changeset suspect (https://github.com/willemarcel/osmcha-django/issues/138)