[OSM-newbies] Do, then document, or ask first?

[Randy]

Alan Mintz wrote:

>For several months, I've been doing a lot of mapping on OSM in southern
>California.
>
>In general, when there is not a direct answer for something in the wiki,
>I've tried to come up with one from logic and similar documented
>situations, tagged that way, and then added it to my list of issues, which
>has grown to several dozen now, instead of bombarding the mailing list with
>questions.
>
>What do I do now? Do I edit the wiki to reflect what I've done, and maybe
>send a list of links to the list so people can review/comment/object, or
>should I send the issues one by one to the mailing list and then fix if
>necessary and document afterwards, or some other method?

I forgot to mention. Even if I felt like it was an "ask first, then tag," 
I would most likely tag one or two isolated areas as examples, using my 
proposed approach, as long as it wouldn't be disruptive to an existing 
scheme. Then you have a concrete example to help folks understand your 
situation, and it will be easy to undo the changes if a better method 
exists. So, if there is any complexity to the change, it's best to make it 
a separate change set, so it can be easily backed out.

-- 
Randy