[OSM-talk] Automated edits code of conduct
Christoph Hormann
chris_hormann at gmx.de
Tue Jul 12 07:53:40 UTC 2016
On Tuesday 12 July 2016, tuxayo wrote:
> > Remember OSM is largely a do-ocracy - those who put work into
> > developing the rules have a significant influence on their content.
> > This does not make them illegitimate.
>
> The questions is how legitimate are they. To know if we can enforce
> them strictly.
Legitimacy in an open community like OSM is a difficult question which
in the framework of a do-ocracy is solved in a relatively practical
way. But as said the rules are no laws.
I would suggest to look at things more in terms of consistency - OSM is
all about local knowledge and mappers mapping their day-to-day
environment. It is inconsistent with this aim to allow others to mess
around in this local mapping through automated edits without looking at
individual features one by one.
> > Both participating in creating and improving the rules as well as
> > working on the DWG making sure mappers comply with the rules are
> > open to everyone.
>
> Is joining the DWG necessary to enforce these rules/guidelines?
No, as also said elsewhere every mapper can - if he/she sees edits that
are for example factually incorrect or violate the rules of automated
edits, imports etc. revert those changes, but of course after
contacting the mappers in question and maybe asking them to fix it
themselves and of course only if your knowledge of the area in question
is sufficient to make such assessment.
This happens more often than you probably think but ultimately it also
does not work in many cases because not every mapper is willing or
capable to do this.
And - since you always talk about enforcing rules - this is generally
not about enforcement, this is about maintaining a friendly and
consistent environment for normal mappers.
--
Christoph Hormann
http://www.imagico.de/
More information about the talk
mailing list