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

Question about your licence model #88

Closed
uazo opened this issue Dec 15, 2023 · 4 comments
Closed

Question about your licence model #88

uazo opened this issue Dec 15, 2023 · 4 comments

Comments

@uazo
Copy link

uazo commented Dec 15, 2023

currently in your repo I have not found the type of licence of your project.
is it possible to know which licence you will be using?
thank you for your reply

@John-LittleBearLabs
Copy link
Collaborator

3 weeks! My gosh, I'm sorry I didn't see this sooner.

That's an excellent question. From my perspective, it's whatever the client wants. I'll ask in our meeting tomorrow.

Since we'd like to land code in Chromium eventually, certainly we'll choose a license acceptable to that project.

@John-LittleBearLabs
Copy link
Collaborator

@uazo - do you have a strong preference? I can pass along your input.

@uazo
Copy link
Author

uazo commented Jan 4, 2024

3 weeks! My gosh, I'm sorry I didn't see this sooner.

don't worry, no problem.

Since we'd like to land code in Chromium eventually, certainly we'll choose a license acceptable to that project.

is what I thought, but I was looking for confirmation.
If it's acceptable for chromium, that's fine with me too.

do you have a strong preference? I can pass along your input

no, none of course, at least now!
My question was for the purpose of understanding whether it was not worth it to check your code because of the incompatible license with my project.

@John-LittleBearLabs
Copy link
Collaborator

So yes, we're willing to go with a Chromium license. This article is also very applicable:

https://protocol.ai/blog/announcing-the-permissive-license-stack/

So we may be willing to dual- or triple-license.

I'm going to leave this issue open until we get a LICENSE file in the repo.

John-LittleBearLabs added a commit that referenced this issue Mar 28, 2024
Library dual licensed.
component's googled
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