I looked for similar issues and apparently it was already discussed, considered back and forth and modified in iD. https://github.com/openstreetmap/iD/issues/703 https://github.com/openstreetmap/iD/issues/1598 https://github.com/openstreetmap/iD/issues/2251#issuecomment-180469055
I don't know the effect of this recent modification https://github.com/openstreetmap/iD/commit/437893ebb8b31e033e6544f0cc343725c4d6a0fd but it might change a bit the behaviour of iD with open changesets. -- althio On 17 January 2018 at 22:26, Dave F <[email protected]> wrote: > This a purely an iD problem. It should be down to their core programmers to > sort it out. > We should be encouraging users, especially newbies, to save frequently. > Potlatch does this without the problem of numerous changesets. > > DaveF > > > On 17/01/2018 13:26, Michał Brzozowski wrote: > > Many new users have a habit of e.g. sending one or few objects per > changeset, resulting in a dozen or even more changesets per day. Obviously > this makes them PITA to review quickly in Achavi or whatever tool you use. > > This habit is probably caused by non-knowledge of how auto-save works in iD > (which makes the work reasonably secure), as well as just not knowing better > thus forming their own judgement. > > How should we teach about optimal changeset size? This is quite tricky - how > we would define it? > > Can the iD nudge users towards better practice? (Linking to Good changeset > comments wiki page would be useful as well) > > Michał > > > _______________________________________________ > talk mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/talk > > > > _______________________________________________ > talk mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/talk > _______________________________________________ talk mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk
