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

Licensing problem #68

Open
atitan opened this issue May 19, 2017 · 5 comments
Open

Licensing problem #68

atitan opened this issue May 19, 2017 · 5 comments

Comments

@atitan
Copy link

atitan commented May 19, 2017

Hi there,

pHash is released under GPL 3.0, which restricts programs using it should have same license as well.
I think phashion's current license is a mistake.

http://phash.org/licensing/

@eregon
Copy link

eregon commented Mar 24, 2019

This seems a serious issue, @westonplatter could you reply to this?

@westonplatter
Copy link
Owner

@eregon I hear you. Overloaded at the moment. Licensing questions are not my forte, so any help is appreciated.

@mperham any input on this?

@mperham
Copy link
Collaborator

mperham commented Mar 25, 2019

I have no input. IANAL and don't want to make any incorrect statements on this subject.

@westonplatter
Copy link
Owner

@atitan circling back on this. I'm also not a lawyer and therefore have no advice to give on the subject.

@eregon
Copy link

eregon commented Mar 6, 2023

http://phash.org/licensing/ is very clear, there is no need for lawyer interpretation here, this gem must use GPL3:

pHash is open source software released under the GNU General Public License (GPL) version 3. This means that if you use pHash in your application, it must also be released under the GPLv3. If you wish to distribute a commercial application without including source code, you must obtain a commercial license.

Also https://github.com/aetilius/pHash/blob/master/COPYING
From GitHub's description of GPL3:

Permissions of this strong copyleft license are conditioned on making available complete source code of licensed works and modifications, which include larger works using a licensed work, under the same license. Copyright and license notices must be preserved. Contributors provide an express grant of patent rights.

There is the https://en.wikipedia.org/wiki/GPL_linking_exception but it doesn't seem used by pHash here.

So https://github.com/westonplatter/phashion/blob/master/LICENSE should be changed to the same as https://github.com/aetilius/pHash/blob/master/COPYING
And https://github.com/westonplatter/phashion/blob/master/phashion.gemspec should use s.license = "GPL-3.0".

This might require getting the permission of past contributors though, to relicense from MIT to GPL3.
To be on the safe side I would suggest to ask them, like it was done e.g. in ruby/strscan#25 (comment)

Not doing anything is almost certainly an infringement of pHash's license.

ryoga-chan added a commit to ryoga-chan/phashion that referenced this issue Nov 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants