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: Choice of License #33

Closed
christophwille opened this issue Aug 28, 2023 · 6 comments
Closed

Question: Choice of License #33

christophwille opened this issue Aug 28, 2023 · 6 comments

Comments

@christophwille
Copy link

I know I am broaching a potential touchy subject - but I am always curious when libraries choose GPL (and in this special case: what if a BFF isn't only forwarding, but actually also doing something "else").

@appie2go
Copy link
Collaborator

Hi Cristoph,

I see your point and I am open to change the license. I have two concerns which I would like the license to cover:

  • Given this is a security-related product, and this is an open source product, I don't want any liability
  • There are many vendors out there who are selling this kind of software. I want this software to be available for anyone, for free, and I don't want people to sell improved versions of our software that contain critical security improvements without sharing those with the community.

Would would be an appropriate license in that case?

@christophwille
Copy link
Author

christophwille commented Aug 28, 2023

If you want to stay in the realm of OSS licenses, maybe https://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License might be a good fit. However, that would not preclude someone using it in a hosted commercial product or building a library on top of it. This is where you'd have to leave the realm of approved OSS licenses, and eg go for something like https://www.linkedin.com/pulse/why-terraform-license-change-good-news-everyone-except-mike-hodgkins/ (I wouldn't comment on the "good news" part though, this was the first article that came up for me).

@appie2go
Copy link
Collaborator

It seems that LGPL makes sense in this case. I'm quite busy working on other features at the moment. Would you mind making a pull-request?

@christophwille
Copy link
Author

To be legally safe, please look at icsharpcode/SharpZipLib#103 (comment) and the thread following. Basically, you need the ok of every past contributor to change the license. (the various "I certify..." replies give you an idea how easy that actually is).

@appie2go
Copy link
Collaborator

That's not a problem. But we're having a meeting soon anyways. Because, as you may have noticed, none of us are legal experts, @yuriburger is deepdiving into the implications of everything to get it right in one go. More on that next week.

Anyways, we're addressing the issue of people having to open source their implementations in one of the next versions.

Stay tuned

@appie2go
Copy link
Collaborator

appie2go commented Sep 6, 2023

License has been changed to LGPL

Thanks Christoph, for your feedback!

Cheers,

@appie2go appie2go closed this as completed Sep 6, 2023
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