[openstreetmap/openstreetmap-website] Link to openplaques (#2405)

eehpcm notifications at github.com
Mon May 4 15:43:17 UTC 2020


@gravitystorm 

> No they aren't. 

It wasn't apparent, but I actually agree with you that slippery slope arguments are (usually) a bad idea.  Like the implicit, distributed slippery slope argument that went "Wikipedia links -> openplaques links -> War and Peace."

> this is an issue tracker, not a debating forum.

This is not a debating forum but feature requests count as issues (or so I thought).  If feature requests are dismissed for what the requester feels are poorly-considered reasons, should the requester stay silent?

Turning openplaques:id into a link would permit the deprecation of inscription=* being used with plaques that are suitable candidates for openplaques (not all are).  Which seems to be a reason why those who think inscriptions ought not to be in the database would support making openplaques:id a link rather than fight it. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/2405#issuecomment-623541452
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20200504/7d1e3c14/attachment.htm>


More information about the rails-dev mailing list