search

little-bear-labs / ipfs-chromium

19 stars 1 forks source link

Question about your licence model #88

Closed uazo closed 4 months ago

uazo commented 9 months ago

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 commented 8 months ago

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 commented 8 months ago

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

uazo commented 8 months ago

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 commented 8 months ago

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.