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

License #126

Open
druppy opened this issue Feb 14, 2024 · 4 comments
Open

License #126

druppy opened this issue Feb 14, 2024 · 4 comments
Assignees

Comments

@druppy
Copy link

druppy commented Feb 14, 2024

I have tried to understand what kind of license BlueR has, and I am a little confused.

The LICENSE file seems to contain 3 licenses, where the last one seems like GPL 2, but in crates.io BlueR are licensed as BSD-2-Clause.

What license are relevant where ?

@surban
Copy link
Collaborator

surban commented Feb 15, 2024

All code is licensed under the BSD-2-Clause.

Doc-comments have been partially copied and adapted from https://github.com/bluez/bluez/tree/master/doc which is in a GPL-2 / LGPL-2 licensed repository.

@druppy
Copy link
Author

druppy commented Feb 15, 2024

All code is licensed under the BSD-2-Clause.

Doc-comments have been partially copied and adapted from https://github.com/bluez/bluez/tree/master/doc which is in a GPL-2 / LGPL-2 licensed repository.

Thanks, for the clarification !

Is the bluez licensing relevant if bluer is using it via dbus, or should the license be replaces with a pure BSD-2-Clause as you (and crates.io) stats ?

@surban
Copy link
Collaborator

surban commented Feb 15, 2024

It's not about D-Bus usage. It's about the doc-comments that have been copied and adapted from the BlueZ D-Bus documentation. Since I am now lawyer, I cannot tell you about the legal implications.

If you want to be on the safe side and help to improve the situation, you could submit a PR that rewords the doc-comments.

@surban surban self-assigned this Feb 15, 2024
@druppy
Copy link
Author

druppy commented Feb 18, 2024

It's not about D-Bus usage. It's about the doc-comments that have been copied and adapted from the BlueZ D-Bus documentation. Since I am now lawyer, I cannot tell you about the legal implications.

If you want to be on the safe side and help to improve the situation, you could submit a PR that rewords the doc-comments.

Thanks, sounds like a good idea when I understand this license thing a bit better :-)

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