[Tagging] Changing proposal process rules - RFC
tomasstraupis at gmail.com
Wed Jan 6 10:19:49 UTC 2021
Idea for consideration:
Proposal/voting for tagging could have different requirements
depending on usage/impact.
* proposal to change/deprecate very prominent schema (say highway=*
tag) should have very high requirements and should generally
discourage ANY change without serious benefits (technical/coding
advantage is not a sufficient benefit). Doing any change requires a
lot of work and participation of a large/experienced part of OSM
* proposal to change/deprecate/introduce niche schema (say colour of a
bench) could have very low requirements. Decisions can be made by a
few or even one person (if nobody else is interested).
usage/impact could be calculated by:
* quantity - number of objects tagged
* domain - general (f.e. roads, water, landuse, addresses) or specific
(f.e. cayaking, archaeology)
This would reduce noise (proposal stream is filled with irrelevant
stuff many people are not interested in) and thus would potenetially
increase participation in important issues.
More information about the Tagging