Just look at the difficulties governments have in practically taxing companies based on profit and/or wealth in a fair fashion - it would be naive to expect the OSM community with no legislative powers whatsoever to do any better.

Or look how well enforcing the attribution requirements is going.

And it is very simple and clear and quite easy to both fulfill and verify!

I don’t know how that would affect the work estimate.

It would require writing StreetComplete from scratch, though research put into quest and some interface ideas could be reused.

So I would expect it to be vastly increased, though maybe some minimum viable prototype could be done faster.

If going that route then likely making new editing set in MapComplete would be the best way to achieve this. And improve MapComplete rather than starting a brand new project.

Shouldn’t you be paid for your edits too? Let’s start sending these firms a collective invoice for our work and use the received funds to benefit the OSM ecosystem.

I am not fan of large corporations but this is quite silly idea.

Paying someone for doing $THING does not mean that you are supposed or obligated to pay anyone doing the same or very similar thing.

And getting invoice for work you have not requested, from person you have not hired is fundamental misunderstanding of how invoices/jobs/etc work.

Entities using OSM data are obligated to attribute it etc - but they are not obligated to pay mappers.

“listing cases where wikipedia:lang tag can be automatically removed” - obviously, only with agreement of a local community

Should this just be a mechanical edit? Or should we have a worldwide campaign of community members checking each and every one?

If local community wants - it could be possible to switch to wikipedia where there is no conflict between wikipedia/wikipedia:lang/wikidata tags and investigate manually remaining cases

Dear all, please, use wikidata, not wikipedia

Both have its place. wikidata can be useful in case of badly made move of page (without leaving redirect).

wikipedia is human readable unlike wikidata tag and definitely should be present.

wikipedia:lang tags are not needed, wikipedia tag is sufficient

I have some code for automatic cleanup that was used in Poland to get rid of such duplicated tags.

Why? it was making harder to maintain links - fixing it required sometimes changing several tags instead of one, it was confusing newbies, it was blocking other tags. In some silly cases people added several links in various languages.

In Ukraine I suspect that this could be done to avoid fights which wikipedia language should be linked.

And wikipedia tags should be kept as wikidata is an alphanumeric soup not readable for human, to distinguish likely correct tag from vandalism one needs to visit Wikidata or make an API call.

Also, I suspect that https://matkoniecz.github.io/OSM-wikipedia-tag-validator-reports/ may be interesting for people caring about such tagging.

And https://matkoniecz.github.io/OSM-wikipedia-tag-validator-reports/%D0%A3%D0%BA%D1%80%D0%B0%D1%97%D0%BD%D0%B0%20(Ukraine)%20-%20obvious.html#wikipedia%20tag%20in%20an%20outdated%20form%20for%20removal listing cases where wikipedia:lang tag can be automatically removed

It is simpler to update single wikidata tag, not multiple tags with unclear (undocumented) preference between each other.

Which part is supposedly undocumented?

Based on google translate:

wikipedia:lang tags are not needed, wikipedia tag is sufficient

I have some code for automatic cleanup that was used in Poland to get rid if such tags.

In Ukraine I suspect that this could be done to avoid fights which wikipedia language should be linked.

And wikipedia tags should be kept as wikidata is an alphanumeric soup not readable for human, to distinguish likely correct tag from vandalism one needs to visit Wikidata or make an API call.

Also, I suspect that https://matkoniecz.github.io/OSM-wikipedia-tag-validator-reports/ may be interesting

And https://matkoniecz.github.io/OSM-wikipedia-tag-validator-reports/%D0%A3%D0%BA%D1%80%D0%B0%D1%97%D0%BD%D0%B0%20(Ukraine)%20-%20obvious.html#wikipedia%20tag%20in%20an%20outdated%20form%20for%20removal listing cases where wikipedia:lang tag can be automatically removed

Note that name is for the common name, not for the official name.

In some cases name and official_name tags will have different values.

I’m glad the 100 Millionth Edit wasn’t somebody’s boring automated thing.

I worried that it may be vandalism or paid editor. The most ironic edit would be DWG revert bot :)

I overestimated how many people would be going for it.

The same for me. I was 200 changesets early (stack of StreetComplete edits made on survey today, with autosaving disabled).

We need support to do that, can we ask you to do it for us

Definitely! In such case you can also go to https://github.com/osmlab/osm-community-index/issues and press “new issue” button (green, toward right).

And follow instructions that will appear.

It still requires English and Github account, but no programming-related knowledge is needed.

(note: if issue is already reported and waits for someone then it makes no sense to report it again)

Thanks for that guide, I linked it at osm.wiki/OSM_Community_Index

OpenStreetMap better and not worry about pushing a FOSS mindset.

Note that in many cases even more FOSS mindset would make OSM better.

ID, the “official” OSM editor, recommends that users collaborate on Slack.

To be more specific - iD is using https://github.com/osmlab/osm-community-index data where for given area primary communication channels are mentioned.

Order can be specified.

For example in Poland https://forum.openstreetmap.org/viewforum.php?id=23 is listed as a primary place.

If primary channel of a community is not Slack then it can be easily changed, but if people actually use Slack primarily then it is more complex.

It was not intended as “and therefore nothing should be done”.

I was rather expanding on “It seems that this is mostly due to a lack of alternatives.”, as I think that there are some reasons for that.

On topic of Gitlab - https://josm.openstreetmap.de/ticket/16857 tracking JOSM attempt to switch to it may be useful.

GitHub is restored in Iran after US gov permits sanctions exemption ( https://developer-tech.com/news/2021/jan/08/github-restored-iran-us-gov-permits-sanctions-exemption/ ).

Thanks for this overview!

Currently, most OSM(F)-related software is being hosted on github.com, and this has a high lock-in potential, it is not FOSS and far away from OSMF having any control over it. It seems that this is mostly due to a lack of alternatives.

I think that “lack of alternatives” is not the primary reason.

It seems to me that reason us that it is highly popular and nearly everyone is there so I have no need to juggle different logins and keep creating accounts.

Network effect is ugly and frustrating but it exists, I would consider it as primary reason - not lack of alternatives.

has a high lock-in potential

Is it so bad? Repository itself is not a problem, Github Wikis are in general unused, issue tracker can be easily exported to GitLab (and I regularly do it as a backup).

Maybe if you setup some elaborate CI? Or is it referring to network effect?

And for other GitHub reasons:

• I really like GitHub interface (that was my primary reason for selecting it rather than its alternatives long time ago)
• I hate overloaded GitLab interface, nothing is where I expect it (it is not just that I am used to GitHub, I liked GitHub from the very beginning)

Thought it may be just me.

exclude contributors from certain countries

Which countries are still affected?

BTW, it may be worth adding some of that to osm.wiki/Tag:highway%3Drest_area

Or at least link to Australian guidelines section in see also

There is no explicit way to say that camping is not allowed in rest areas - just as there isn’t a way to tag that camping isn’t allowed in police stations or the opera house.

Still, it may be worth inventing. Typical opera will not have camping as part of it, explicit “no camping allowed” signs are unusual there.

Have you tried to make global analysis (total length of tagged sidewalk worldwide) using each method?

Still would be affected by some distortions, but would be better than taginfo raw usage count.