[josm-dev] Commit message not empty

[Ulf Lamping]

Frederik Ramm schrieb:
>> Making the GUI complicated and adding a Help button to explain the 
>> complications is, well, not the best idea for improved user 
>> friendliness IMHO.
> 
> A text field where you have to enter text is not a complicated element. 

I perfectly agree, that there's no need to explain that you can enter 
text into a text field - but that's not the "complicated point".

> Not the field needs explaining, we need to explain why we want users to 
> fill the field with text.

If I understand correctly what you mean, you're currently focussing on: 
"there are people that do not want to enter stuff, maybe because they 
are too lazy - but it would help us OSMers a lot if they do it right".


What we really (also) need to explain is: *what* we want users to enter 
into this field! It's not enough to convince people to do something, 
it's also essential to enable them to actually do it!

I'm thinking more of users thoughts like: "Oh, I have to enter a comment 
here. But what do they expect here?!? Maybe the source of my mapping 
data? Or do I need to mention the area involved? Is there any format 
that I have to follow here?" and so on.

For someone new to OSM it can be a real relief to simply hit enter in 
this situation, instead of spending a none trivial amount of time to 
find out what to enter here.

> This is not a complication of the user 
> interface, but a complication of the process how one can contribute to OSM.
> 
> Whether or not entering a commit comment is mandatory - the complexity 
> remains, and the need to explain to the user why we want him to enter one.

Well, no, having a label like:

"Comment (leave empty if unsure):"

would easily remove the complexity for the first time users ...

Regards, ULFL