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

Create LICENSE.md #6

Open
archaeogeek opened this issue Mar 8, 2021 · 7 comments
Open

Create LICENSE.md #6

archaeogeek opened this issue Mar 8, 2021 · 7 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@archaeogeek
Copy link
Member

Issue by KoalaGeo
Tue Jan 12 15:06:35 2021
Originally opened as AGIuk/Schematron#5


Contains OGL licence text


KoalaGeo included the following code: https://github.com/AGIuk/Schematron/pull/5/commits

@archaeogeek
Copy link
Member Author

Comment by PeterParslow
Tue Jan 12 15:48:25 2021


Should the licence simply be 'by reference' to the OGL at http://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/

I'm not sure it's good to copy their text into here.

@archaeogeek
Copy link
Member Author

Comment by KoalaGeo
Tue Jan 12 16:01:32 2021


My mistake the readme states CC-BY-4.0, so changed licence file to this not OGL

@archaeogeek
Copy link
Member Author

Comment by PeterParslow
Tue Jan 12 16:08:08 2021


Good catch - but should it be just the URL or is there good reason to copy the text?

@archaeogeek
Copy link
Member Author

Comment by KoalaGeo
Tue Jan 12 20:21:16 2021


That's how GitHub expects you to do it either when you initalise a repo or add a license later, you add all the text to the LICENCE file, GitHub then "reads" this and adds the license buttons to the repo with links.

See my branch in the "About" on the left it says what license the repo is - https://github.com/KoalaGeo/Schematron

Docs on adding a license - https://docs.github.com/en/free-pro-team@latest/github/building-a-strong-community/adding-a-license-to-a-repository

@archaeogeek
Copy link
Member Author

Comment by PeterParslow
Wed Jan 13 08:04:04 2021


Well, that's frankly bizarre of GitHub, so I've asked about it: https://github.community/t/gtihub-approach-to-licence-why-copy-text/155217

CC-BY's preferred way of being cited is by reference, that's why they provide the persistent versioned dereferenceable URIs. See e.g. https://creativecommons.org/choose/results-one?license_code=by&jurisdiction=&version=2.0&lang=en

So, should we adopt GitHub's preferred approach, or CCs?

@archaeogeek
Copy link
Member Author

Comment by PeterParslow
Wed Jan 13 08:28:49 2021


Here's an OGC example: https://github.com/opengeospatial/ets-omxml20/blob/master/LICENSE.txt

@archaeogeek
Copy link
Member Author

Comment by KoalaGeo
Wed Jan 13 13:39:16 2021


The text is pulled from a template from a site GitHub curates https://choosealicense.com/
CC-BT-4.0 - https://choosealicense.com/licenses/cc-by-4.0/
This links to https://spdx.org/licenses/CC-BY-4.0.html
And from there to the actual licence https://creativecommons.org/licenses/by/4.0/legalcode

For end users, using GitHub's preferred approach makes things clearer , it also integrates with their API https://github.blog/2015-03-09-open-source-license-usage-on-github-com/

@PeterParslow PeterParslow added documentation Improvements or additions to documentation enhancement New feature or request labels Mar 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants