@bdon @openstreetmap Support doesn't have to be monetary :) Currently there isn't _any_ form of support, but a degree of opposition to anything. It takes a certain frame of mind to participate in OSM, especially in Europe.
Top-level
@bdon @openstreetmap Support doesn't have to be monetary :) Currently there isn't _any_ form of support, but a degree of opposition to anything. It takes a certain frame of mind to participate in OSM, especially in Europe. 9 comments
@bdon @openstreetmap Looks like the question is allocation of resources! Corporations focus on preparing the data to deliver to their customers. Perfectly fine, that's what we're here for: mapping for people. It's developers we're competing after. OSM doesn't have good monitoring / validation tools, hence the downstream distributions. If wikipedia didn't filter lies, won't be there a commercial extract too? Corps have more resources, they get a better deal. OSMF doesn't, mappers get nothing. @zverik @bdon @openstreetmap This is not really similar to Linux at all then. Mapping and make data doesn't require the mapper to be a developer. Developers are needed for infrastructure. You also need expertise in design, and people with product vision who can lead and rally a team. It's hard for mappers to be developers, designers, product owners, all in one person. Many OSMers don't care about usability. Or if somebody actually sees their work. Many like me mostly use Google Maps and Waze. @cbed @bdon @openstreetmap I'll answer to each tweet :) So, this is indeed unlike Linux, but a bit like Wikipedia. They have got millions of editors, but very few developers — some volunteer, some they had to hire, because people rarely align to tasks. Another example is HOT. They are primarily mappers and community builders, but they have to hire developers to make their operations effective. An opposite example is the TomTom OSM team. They struggle with what tools other people made. @zverik @bdon @openstreetmap I am curious if you can expand more on the state of mind. I might have the state of mind, or I might be a pretty active mapper in Europe (for a significant part of 2016-2023 part time to full time) who went under the radar Swiss community is quite exception in my opinion though, and may be different than others, I really enjoy their mailing list @cbed @bdon @openstreetmap Well, in Estonia where I map (and in both other Baltic countries), there are 1-2 people who are mapping a lot, and also checking every other changeset for mistakes. And sometimes attacking in comments even smallest changes. I can see good intentions underneath, but also it's like the worst school possible, where you get punished for slight mistakes, but get no feedback on anything else. @zverik @bdon @openstreetmap Ah I see what you mean! What do you think are good positive Feedbacks? If we were Waze community, you would get badges but that's not much. In another world it's some crypto or cash, but that's not really what OSMers want (well I would accept $1/changeset of course). What are some ideas on more recognition? And is this also moving toward Gamification? @cbed @bdon @openstreetmap At SotM 2013 I proposed a "like" ("good job") button for changesets :) Small, but impactful thing. There could also be notifications like "XXX improved your shop" (but I see how it can hurt), more visible regional statistics, awards, (geo-)chat... Many things, games and wikimedia can provide inspiration. Definitely not monetary or physical incentives! @zverik @bdon @openstreetmap Yes! We thogihtt about this for Mapillary. We allowed commenting photos previously, like OSM in changesets. And we discussed a human feedback loop. Like Google Local Guides: how your data is used. Rob Atkinson at OGC has good idea on Provenance also, seeing how data is applied by who and where, as a way to know it's potential purpose too. I'd love Organic Maps to share the most viewed tiles or click count of POIs as a start. |
@zverik @openstreetmap the malaise over OSM is the alienation of mapping labor - all the productization and thus value extraction happens outside of OSM proper.
So commercial downstreams keep their “distributions” of the kernel proprietary with the minimum possible collaboration inside the OSM bubble.
Mappers are turned off by potential exploitation so become suspicious of anything other than mapping for mapping's sake. A vicious cycle!