[josm-dev] Please invest some time into documentation - especially confilict resolution

[Dirk Stöcker]

On Sun, 4 Oct 2009, Apollinaris Schoell wrote:

> But as said before this is NOT a task for the developers. It's not even a
> Josm  problem.
> My problem in the last months was that the development was too fast to even
> catch up with the idea how things work. With a couple of bugs impossible.
> The only solution was to create trac tickets and Karl fixed them all. thanks
> for that.
> Still have some conflict problems from time to time. Not sure if this is a
> Josm problem or more a sync problem when server connections are interrupted
> and josm doesn't receive the response from the server.

Well, normal users (the ones we talk about) should not see this 
development except with the tested steps. So pace is a bit slower for 
them.

Probably all of us agree that conflict resolution in JOSM is not yet the 
best, but this part of JOSM is very young and must mature a bit. 
Documenting it as it is now will be a bit wasted time, as I expect many 
changes here especially when some of the more active users come up with 
useful improvement suggestions.

Comparing current situation where users have a little bit strange dialogs 
to the situation before where the whole changed dataset needed to be 
dropped in case of most conflicts is really a big improvement I think :-)

Making Trac tickets is usually very valuable (except the ones telling 
"there is an error, find out which one"), as this helps to know there are 
errors. Many users believe that troubles they have must be widely known 
(which is total nonsense usually - I even had a situation where I found 
discussions in the net half a year later where users told about a "known" 
bug in one of my programs, but nobody bothered to tell me about it).

So please continue to make bug reports (and don't get discouraged when 
some of them are closed as WONTFIX or WORKSFORME :-)

Ciao
-- 
http://www.dstoecker.eu/ (PGP key available)