-
Notifications
You must be signed in to change notification settings - Fork 3
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
www.rifugi.lombardia.it #51
Comments
Thanks for noting this! I tried to fix it right now. What about a new version? See https://github.com/openstreetmap/tile-attribution/blob/668778e6d514813317dd97ab810c594a8d667f09/CONTRIBUTING.md Do you plan to submit such request as described there? |
I did not and do not plan to do this: "You have contacted the website/app owner or representative using the Love Letter model/template (https://osmfoundation.org/wiki/Licence/Attribution_Reminder_Templates) more than a week ago and no proper attribution has been added." I will not do it in this case or any other I will encounter in the future. Does it mean that I can not use this (github) tool to manage cases of (suspected) violations for reporting? |
Yes. In such case it is better to add such entry to https://wiki.openstreetmap.org/w/index.php?title=Insufficient_attribution and note they use OSMF tile server. I actively monitor this page (see its history) and reported some here in this repository. If you do not want it either - please add them to thread at official OSM forums about missing attributions. |
Unless someone else will pick this case up? I guess that single issue with waiting for contact using specific template is fine? Lets see is there interest in processing it (strictly speaking I am interested but I have limited time, lets see when I will manage it) |
Just to be clear, I plan to contact the violator, but not using the "love letter approach", as I consider it a failure to enforce the attribution requirement efficiently, and do so at a scale (as history can attest). You might be aware of my recent post to the osm-legal forum, where I outlined an alternative approach, which I intend to follow. Regardless, I consider it important to have a common attribution violation tracking database for all types of violations, not only cases where the violator uses the osm tiles. Currently we have this Github-based and the Wiki-based general databases I am aware of and (I suspect) a number of regional ones like the one the Slovak community has been using for example. Ideally we would have just one, to avoid duplicating of cases resolution efforts. |
I would expect https://wiki.openstreetmap.org/w/index.php?title=Insufficient_attribution to be the central one. (Wiki editing can be a barrier, but demanding account at Microsoft managed service is also far from ideal, gitlab has atrocious interface etc - though ideas for better central repository are welcome)
It is not intended to replace or duplicate https://wiki.openstreetmap.org/w/index.php?title=Insufficient_attribution listing - it is intended only for cases qualifying for immediate termination of access to OSMF tile servers.
I agree. I have spend quite a lot of time to improve situation in this area (and this repository is one of effects - and to be clear many others also spend a lot of effort here, for start @grischard and @Firefishy ). But situation here is far far far from ideal. Or even OK one. (in my opinion)
I have seen the title in my mailing list inbox, I have not seen its contents yet. |
either way, in this case you need to manually enable "OpenStreetMap" button, right? So main thing missing is mention of ODBL (and suppressing Google logo). Either way it is not blatant and completely missing attribution |
yes on all counts. However, it still takes our time to deal with the issue, which from my point of view warrants a compensation to us (which is the core point of the proposal I announced in the legal-talk forum). |
Closing as stale, letter never sent |
https://www.rifugi.lombardia.it/sondrio/val-masino/rifugio-gianetti.html
steps to reproduce
Note: The Contributing guidelines are not very helpful.
The text was updated successfully, but these errors were encountered: