-
Notifications
You must be signed in to change notification settings - Fork 1
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
Comments
Comment by PeterParslow 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. |
Comment by KoalaGeo My mistake the readme states CC-BY-4.0, so changed licence file to this not OGL |
Comment by PeterParslow Good catch - but should it be just the URL or is there good reason to copy the text? |
Comment by KoalaGeo 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 |
Comment by PeterParslow 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? |
Comment by PeterParslow Here's an OGC example: https://github.com/opengeospatial/ets-omxml20/blob/master/LICENSE.txt |
Comment by KoalaGeo The text is pulled from a template from a site GitHub curates https://choosealicense.com/ 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/ |
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
The text was updated successfully, but these errors were encountered: