Skip to content
This repository has been archived by the owner on Jul 19, 2021. It is now read-only.

GPLv3 license consistent with GPLv3 code already in #2

Merged
merged 1 commit into from Sep 22, 2016
Merged

GPLv3 license consistent with GPLv3 code already in #2

merged 1 commit into from Sep 22, 2016

Conversation

ghost
Copy link

@ghost ghost commented Sep 20, 2016

Note that at minimum osgeo_importer/models.py and osgeo_importer_prj/settings.py are already marked GPLv3.

Other licenses included (MIT, ISC, "OSI Approved: SOME LICENSE") should all be GPL-compatible; but I am not a lawyer, so that is only my lay understanding. I welcome corrections. I don't have the ability at present to verify chain of custody for all contributions to this repo. I also don't have any qualified opinion on the implications of using GPLv3 django apps in a Django project, or what it would take to mark this as a different license. So this should probably get some sort of legal review before we use django-osgeo-importer for anything.

@ghost
Copy link
Author

ghost commented Sep 21, 2016

GNU's doc describes compatibility of licenses that I am aware of possibly applying to this project: https://www.gnu.org/licenses/license-list.html

@ghost
Copy link
Author

ghost commented Sep 21, 2016

Sara mentioned that the package.json lists its license as ISC, and that's true. But I'm not sure how the GPL status of the Python side affects this or not. Also, the entirety of that package.json with only a couple edits is just copy-pasted from some other repo (see package.json for which).

edit: it's at https://github.com/lorem--ipsum/smashing-article/blob/master/package.json

@sarasafavi sarasafavi merged commit dc2ee40 into planetfederal:master Sep 22, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant