You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a recent post the OSM community site about the quality of notes, AngocA requested that creators of notes include a hashtag. This was in response to issues like #103 or just knowing who to report note bugs. Including a source hashtag should make it much easier to reslove since user will know who to report them to. I propose that our hashtag be "OnOSM.org-YYYY/MM/DD" so there is no confusion with output from our forks and since this site doesn't use semvar versioning. That way we know when the note was created and be able to determine whether a particular issue has been resolved and when.
Notes created by this site can already be found by searching for "onosm.org submitted note". For example, here is an RSS feed for notes generated by onosm:
It will be great to have the version (Like StreetComplete) and something not replicable with forks. I don't know if part of the URL of the page could be included in a way that forks will have a different value, and we can identify the notes created from OnOSM from notes created in any of its forks.
In a recent post the OSM community site about the quality of notes, AngocA requested that creators of notes include a hashtag. This was in response to issues like #103 or just knowing who to report note bugs. Including a source hashtag should make it much easier to reslove since user will know who to report them to. I propose that our hashtag be "OnOSM.org-YYYY/MM/DD" so there is no confusion with output from our forks and since this site doesn't use semvar versioning. That way we know when the note was created and be able to determine whether a particular issue has been resolved and when.
https://community.openstreetmap.org/t/osm-notes-should-include-the-application-name-including-notes-from-osm-website/9064
The text was updated successfully, but these errors were encountered: