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

Licence #49

Open
Phaestion opened this issue Sep 8, 2016 · 3 comments
Open

Licence #49

Phaestion opened this issue Sep 8, 2016 · 3 comments

Comments

@Phaestion
Copy link

Hi there

Would it be possible to licence the core component as Apache or MIT?

Regards

@perlundq
Copy link
Owner

perlundq commented Sep 8, 2016

Hi Steyn, I have investigated this earlier (https://lists.samba.org/archive/rsync/2016-January/030489.html), but since this is based on reading the code for rsync (which is GPL 3), I believe I am bound by that license.

@Phaestion
Copy link
Author

Hi there

That is unfortunate. We plan on using Yajsync on Android, so there is a bit of modification to be done. A GPL licence does however have the effect that we cannot use Yajsync in our (closed source) project.

What we can however do is to create a separate app (something like a service) which accepts IPC messages from any other app. This app will of course be GPL then.

Regards

@perlundq
Copy link
Owner

perlundq commented Sep 9, 2016

OK, yes I am aware of the issue with having the library part GPL:ed. But it will stay GPL (unless I actually get some trustworthy legal advice that says it is OK to choose another one)

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