[Imports] Making the current guidelines/code of conduct about imports/automated|mechanical edits clearer and merged

[sly (sylvain letuffe)]

Hi X in a private message,
> Sylvain,
> 
>          I'm not technical, but my biggest problem with imports is
> not policy. 
(...)

> the reason is the how-to part of the wiki is so badly written that's
> it's impossible to get to the point of asking members of the Data
> Group what they think about the data that one has.
(...)

> The wiki says something abotu starting a
> web page for each import, but doesn't say even how to do that.

Don't take it personally, I'm just taking this as an example :
If you are not technical, if you don't know how to create a wiki page, if you 
can't tell if your data is good to import or not and if you have a "big" 
dataset.
Then, most likely, you won't be able to revert you import in case something 
goes wrong, you might do things in a somewhat "not so good way" and then the 
policy is for you to read first and we should clarify it so you understand 
that :
you shouldn't import.

First reason is because the DWG isn't there to help people import, and we are 
not here to back up people in case of problems. We exist to prevent problems, 
and to revert problematic imports as quickly as possible because it gets even 
worse when people start touching existing badly imported data.

What you could do however, because it might be perfectly fine or even good for 
a not technical contributor to import, is to find people to back you up, with 
the technical knowledge to document, to create wiki pages, to help in case of 
problems, to give you the good guidelines and to discuss with you the quality 
of your dataset.

Your local community members are the best candidates for that, and if you 
don't have a local community... well... create one ;-)


-- 
sly (sylvain letuffe)