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

Possible license issue (AGPL vs. GPL) #55

Open
hroncok opened this issue Oct 31, 2017 · 7 comments
Open

Possible license issue (AGPL vs. GPL) #55

hroncok opened this issue Oct 31, 2017 · 7 comments

Comments

@hroncok
Copy link

hroncok commented Oct 31, 2017

Hi there.

PrusaControl is an alternative user interface for Slic3r Prusa Edition

Slic3r is licensed with AGPLv3. I'm not sure whether this alternative user interface isn't by design also licensed as AGPLv3, but this repo says GPLv3. Ask you lawyers if needed.

@bubnikv
Copy link

bubnikv commented Nov 1, 2017 via email

@tibor-vavra
Copy link
Collaborator

Hi,

I agree with Vojtech. Slic3r PE is placed in folder PrusaControl/tools/Slic3r-Lite in binary form and PrusaControl call his command line interface. Repository of Slic3r PE is https://github.com/prusa3d/Slic3r

Tibor

@hroncok
Copy link
Author

hroncok commented Nov 1, 2017

If you agree, why did you close?

@tibor-vavra
Copy link
Collaborator

Im little hot-blooded for this topic :-)))

As I uderstand in section 13 both license AGPLv3 and GPLv3 are compatible for combined work:

Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License.

@tibor-vavra tibor-vavra reopened this Nov 1, 2017
@hroncok
Copy link
Author

hroncok commented Nov 1, 2017

As I understand it: Combining AGPLv3 with GPLv3 is possible, but the result is de facto AGPLv3.

@hroncok
Copy link
Author

hroncok commented Nov 19, 2017

Any news on this topic?

@hroncok
Copy link
Author

hroncok commented Dec 10, 2017

Please either tell me your lawyers don't think this is the case or change the license. Ignoring a possible license violation for such a long time bothers me.

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

3 participants