[OSM-talk] How to teach novices about optimal changeset size?

[Rory McCann]

On 17/01/18 15:13, Michał Brzozowski wrote:
> Certainly not:
> - one changeset per building, repeated 20 times

Couldn't this be done with the "upload" vs "new changeset" feature of
the OSM API? A technical solution. Multiple uploads in a single changeset?

Users want to save/upload frequently (because computers), so we'll never
stop them pressing the button often. Maybe iD could keep a changeset
open and an upload rather than open a new changeset? There would have to
be an option to "close current changeset and open a new one" (& close
current changeset), and to word that in a more friendly way for people
who don't know the terminology.

I don't think linking to documentation will solve this issue. Too many
users don't read things like that, no matter how much we'd want them to.

Yes, I know I'm suggesting a software change without offering a patch.