License change?

[vorburger]

Hello @ustc-zzzz 👋

This is a cool library.

I was just looking into building (something like) this for a project, and thought perhaps I could use this.

However, then I noticed that you chose to use the LGPL license. Unfortunately that means that I cannot use it in a particular context where that license isn't possible.

I don't suppose you would consider changing it to a more permissive license instead? Such as e.g. Apache ASL or MIT ?

Just thought I'd at least ask!

[ustc-zzzz]

Sorry for the things in my real life recently which made me not have enough time to reply.

I may wonder the circumstance where you will use this library, since LGPL-3.0 allows you to either dynamically link to your project (by declaration in the classpath or some classloading technique) or statically link to your project (we often call it "shading" or "repackaging") even if it is a proprietary software. In most cases LGPL-3.0 would not bring any legal trouble.