[openstreetmap/openstreetmap-website] Improvement: changeset feedback message template, customized per editor (#1424)

BushmanK notifications at github.com
Thu Feb 2 20:04:09 UTC 2017


There is a very useful improvement in #1401, however, as far as I understand it, it is unable to solve a case of Maps.me users (a growing fraction of OSM contributors with a questionable input quality). There are several observations, telling us that Maps.me users very rarely respond to changeset comments. Often, they do not seem to be completely aware of OSM, they don't even know that they are registered users of it.

Examining this use case, it is easy to notice, that they receiving a feedback on their edits made in Maps.me from a completely unknown party - some private person, a member of the different project (OSM). There is nothing that connects Maps.me (or any other particular editor or application) to OSM in that letter. So, it is easy to get confused and to ignore this odd message. 

I understand, that it might sound like Maps.me developers should be taking care of it by implementing a notification system in this app. However, this case could be the first but not the last one. So, having a personalized template could be a solution for these future potential cases.

By "personalized template" I mean a template, that could address a user depending on editor he used for making a particular changeset. That might include a custom greeting, like "Dear _whatever editor_ user, ..."; custom documentation links, addressing some common editor-specific issues; custom warning messages,  related to a specific version of an editor (like if we know that a certain version of JOSM has a bug that does something really bad).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/1424
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20170202/ae4b60c9/attachment.html>


More information about the rails-dev mailing list