organicmaps / organicmaps/website

Clarify the Libre license of website contents :)

Open
#184 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
36
Forks
44
Avg merge
6h 50m
Merged PRs (30d)
4

Description

I'm trying to publish more OrganicMaps screenshots on Wikimedia Commons but I'm not 100% sure about the license of our screenshots. Example:

https://commons.wikimedia.org/wiki/File:Organic-map--screenshot--dark.jpg

Maybe we clarify this license from the official website itself :) At the moment this is "somehow implicit" from the repository that says Apache 2.0 (but maybe that should cover just source code, not contents?).

For example, maybe in the website we can put a small phrase like this one:

OrganicMaps CC BY-SA example

<p xmlns:cc="http://creativecommons.org/ns#" xmlns:dct="http://purl.org/dc/terms/"><span property="dct:title">OrganicMaps</span> is licensed under <a href="http://creativecommons.org/licenses/by-sa/4.0/?ref=chooser-v1" target="_blank" rel="license noopener noreferrer" style="display:inline-block;">CC BY-SA 4.0<img style="height:22px!important;margin-left:3px;vertical-align:text-bottom;" src="https://mirrors.creativecommons.org/presskit/icons/cc.svg?ref=chooser-v1"><img style="height:22px!important;margin-left:3px;vertical-align:text-bottom;" src="https://mirrors.creativecommons.org/presskit/icons/by.svg?ref=chooser-v1"><img style="height:22px!important;margin-left:3px;vertical-align:text-bottom;" src="https://mirrors.creativecommons.org/presskit/icons/sa.svg?ref=chooser-v1"></a></p> 

Or something like that :) I generated that from here:

https://chooser-beta.creativecommons.org/

Thanks for any opinion :)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the website source and the repository's current Apache 2.0 licensing information, then determine which license applies to website contents and screenshots. Done means the intended license is agreed and an explicit notice is added to the official website.

Written by the indexing model from the issue text.

Assessment

Domain
content, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.