Some software developers participate in this forum to varying degrees, and some even prefer feedback to go here instead of their own issue trackers. But it’s a bit of a fire hose, covering so much ground with a significant level of noise and drama. The discussions here take time away from actually developing software, so I know a lot of developers who don’t bother. If anything is important enough to require their attention, someone will come to them, the thinking goes.
There are other venues for coordination. Some developers have gravitated towards OSMUS Slack over the years, treating it as their sole real-time communication channel, so there’s some organic interaction among them. I’d imagine the other big national communities have seen something similar in their corners. Those who have the means will congregate a few times a year at conferences, as mentioned. OSMF and OSMUS convene working groups to provide a space for more frequent coordination, though this capability is underutilized. Technically there’s still a dev mailing list intended for discussion among software developers and announcements geared to them. But all of the discussion since December 2024 has been about shutting down the list for inactivity.
The relationship between mappers and developers has had ups and downs. At times it feels like an adversarial relationship, due to small things, like a knee-jerk admonition to avoid “mapping for the renderer” solely because a renderer or router motivates someone to ask. Conversely, for a developer, it can be tempting to add some behavior because it’s technically straightforward, while they lack the experience, patience, or social capital to shepherd their idea through a community consultation process. That’s especially true these days, when “anyone can be their own developer” with an LLM coding agent.
OSM doesn’t exist in a vacuum. Various fields like geography/GIS, natural sciences, and cartography all know us, even if they think of us as a read-only static dataset. There’s a ripe opportunity for us to improve the relationship just by showing up in their spaces, online and at conferences. I can’t tell you how often people in these fields tell me that they’ve never met a real-life OSM mapper before and have no idea how our “company” manages to do it all.
(As OSMF’s Core Software Development Facilitator, a big part of my job is to bridge these divides, get people talking to resolve misunderstandings and miscommunication. Most of it is behind the scenes and isn’t a replacement for mappers and developers coordinating directly among themselves. Formally, my job is limited to a definition of “core software”, for some definition thereof, but regardless I’m always happy to help connect the dots as long as I’m around. So if you do see something falling through the cracks, please don’t hesitate to reach out. The worst case scenario is that I have to pull in someone else who’s in a better position to help.)