Opened 10 years ago
Last modified 9 years ago
#11845 new enhancement
(More) nagging/warning for empty changeset comment or source — at Initial Version
| Reported by: | anonymous | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | tested |
| Keywords: | changeset, comment, source, warning | Cc: | Klumbumbus, bastiK, Don-vip |
Description
Please add (more) nagging when a changeset is to be uploaded without a comment or source attribute.
IMHO it is detrimental to OSM to have such changesets; one simple example (I am sure there are better ones): a changeset introducing lots of address data,
no source given - has the address data been copied from a map which is considered a fallback/secondary source only and should thus be checked doing a
survey or has the data actually been collected during a survey? Similarly, empty changeset comments are obviously not helpful for deciding if a changeset
should be checked for quality assurance etc.
I'm aware of the fact that JOSM is aimed at advanced users which should probably know better and actually do provide changeset comment and source, but I still see lots of changesets with one or both of them missing (and also no source attribute on objects).
The nagging/warning dialog should probably explain that providing a meaningful comment and source is important for OSM and collaboration with other contributors (and contain a "Hide in future" checkbox).
If there already is such a dialog, it should probably be worded more strongly to really discourage leaving comment/source empty.
A more radical approach would be to refuse uploading if comment or source is missing (just like some version control systems abort comitting if no commit message is specified).
