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

Need to be GPLv3 #172

Open
Sebanisu opened this issue May 25, 2020 · 1 comment
Open

Need to be GPLv3 #172

Sebanisu opened this issue May 25, 2020 · 1 comment

Comments

@Sebanisu
Copy link
Collaborator

Sebanisu commented May 25, 2020

We use code ported from other projects that use GPLv3. And that license requires all code used by new projects to be GPLv3 or newer.


SebanisuToday at 8:57 AM
if i leave the GPL v3 comment infront of a function is that enough to use the function in my code? or does my entire project need to be gpl v3?

quantumpencilToday at 9:02 AM
If you call the function by via either static/dynamic linking in your own code, that makes your entire project GPLv3 legally (not just that function). If you communicate with a running instance of a GPLv3 application via IPC or something but don't link (i.e, you have an output only dependency, no shared code/data structures between the projects) then your project isn't legally GPL3

SebanisuToday at 9:04 AM
So I need to change all my lisance.txt to gpl v3. i guess. and technically openviii is gpl v3 too because we have code ported from dieling. and all of dieling is gplv3.

quantumpencilToday at 9:05 AM
yep
NEW
[9:06 AM]
license is very infectious

@Albeoris
Copy link
Collaborator

Albeoris commented Aug 6, 2020

Better to get rid of the Deling's code in the repository so that this infection doesn't spread. :)

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

2 participants