Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App creates the misleading impression that it is "official" #224

Closed
simonpoole opened this issue Jan 4, 2024 · 7 comments · Fixed by #233
Closed

App creates the misleading impression that it is "official" #224

simonpoole opened this issue Jan 4, 2024 · 7 comments · Fixed by #233

Comments

@simonpoole
Copy link

The project should at least include a prominent disclaimer and other measures when using the OSM trademarks, particularly as it now contains marketing for commercial entities.

See https://osmfoundation.org/wiki/Trademark_Policy and https://osmfoundation.org/wiki/Trademark_Policy_FAQ

@kudlav
Copy link
Contributor

kudlav commented Jan 19, 2024

Hi, I've read those articles.

I suggest to reword A universal OpenStreetMap app to An universal app for OpenStreetMap (there is typo anyway).

The license is always visible, and there is already a big disclaimer in About this app (or when visiting the first time) so there is no violation:

All map data is from OpenStreetMap, a map created by milions of contributors — similar to Wikipedia. You can find Edit button on each map feature.

(typo in milions)

OSM is a community project. Your term "official" can be quite offensive to me or zbycz, maintainers, members of the official Czechia organization of the OSM Foundation.

@thegrasshopper104
Copy link

I think it's not done with malicious intent, and a simple redesign of the sidebar could solve it,
if this was true: All map data is from OpenStreetMap"
But OSMapp seems to use Maptiler Planet, so not all map data is from Openstreetmap. This will need more explanation to avoid possible osm notes for errors in Maptiler data.

@zbycz
Copy link
Owner

zbycz commented Feb 10, 2024

Hi @simonpoole, thank you for the heads up. It didn't really occur to me that this could be an issue. I would like to make everything in agreement as best as possible.

To clarify – OsmAPP aims to be an open-source community project serving the community, and bringing value back to OpenStreetMap. The only reason I use a commercial provider is that there is no other option for world wide vector tiles. I don't do any marketing, I only comply with their terms of use. If you choose a different map layer, the logo disappears. (btw, their layer almost got to the main OSM site as well. Once they prepare a layer without wikipedia, I will be more than glad to switch 🙂)

I just deployed live these changes (PR #233). If this is not good enough, please reopen this issue.

  1. I added a disclaimer from the Trademark page on the project homepage

    OpenStreetMap and OSM are a trademark of the OpenStreetMap Foundation. This project is not endorsed by or affiliated with the OpenStreetMap Foundation.

  2. As suggested by @kudlav, I changed the subtitle to "A universal app for OpenStreetMap".
  3. As suggested by @thegrasshopper104, I added info about wikidata content. I didn't even know about that when I wrote it 😅
  4. I added an issue for more informative layer switcher: Better layer switcher #232

Also @simonpoole,
do you think it is a good idea to ask OSM Foundation for permission about the domain+name? eg. like OsmAnd? :) The app currently has ~200 hits/day, so I am not sure if it is significant enough to bother the Foundation.

@simonpoole
Copy link
Author

I would suggest contacting the OSMF.

It is less an issue of the current situation than one of what happens when you no longer have control of the assets in question, in such cases it is in all of our interests that they fall to the OSMF and can't be monetized or misused in other forms.

@zbycz
Copy link
Owner

zbycz commented Feb 10, 2024

I see! Very good point. Thanks for the clarification, i will contact the foundation 👍

@thegrasshopper104
Copy link

Hi @simonpoole, thank you for the heads up. It didn't really occur to me that this could be an issue. I would like to make everything in agreement as best as possible.

To clarify – OsmAPP aims to be an open-source community project serving the community, and bringing value back to OpenStreetMap. The only reason I use a commercial provider is that there is no other option for world wide vector tiles. I don't do any marketing, I only comply with their terms of use. If you choose a different map layer, the logo disappears. (btw, their layer almost got to the main OSM site as well. Once they prepare a layer without wikipedia, I will be more than glad to switch 🙂)

I just deployed live these changes (PR #233). If this is not good enough, please reopen this issue.

  1. I added a disclaimer from the Trademark page on the project homepage

    OpenStreetMap and OSM are a trademark of the OpenStreetMap Foundation. This project is not endorsed by or affiliated with the OpenStreetMap Foundation.

  2. As suggested by @kudlav, I changed the subtitle to "A universal app for OpenStreetMap".
  3. As suggested by @thegrasshopper104, I added info about wikidata content. I didn't even know about that when I wrote it 😅
  4. I added an issue for more informative layer switcher: Better layer switcher #232

Also @simonpoole, do you think it is a good idea to ask OSM Foundation for permission about the domain+name? eg. like OsmAnd? :) The app currently has ~200 hits/day, so I am not sure if it is significant enough to bother the Foundation.

Those are great steps.
I didn't explain it well, but I meant that Maptiler has building footprints (and other landuse iirc) that isn't on OpenStreetMap.

@govvin
Copy link

govvin commented Oct 27, 2024

For reference, the link to the minutes of the OpenStreetMap Foundation board meeting discussing the trademark license re OsmAPP

https://osmfoundation.org/wiki/Licensing_Working_Group/Minutes/2024-09-09#OsmAPP

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants