Thanks very much, Dear Team. That's great news.
I did see your intention to change licences in some other issue discussions, but great to hear from you directly.
I found conflict licencing agreements.
At ABP Framework root, https://github.com/abpframework/abp/blob/dev/LICENSE.md, it says GNU LESSER GENERAL PUBLIC LICENSE.
But at https://docs.abp.io/en/abp/latest/Modules/Identity, it says "The source code of this module can be accessed here. The source code is licensed with MIT, so you can freely use and customize it."
Can I confirm which licence is used? It is important for us to decide whether we go down the source code approach.
Thanks. As ABP Framework (not ABP Commercial) is on LGPL licence. If we make any changes to Volo.Identity module, should we publish the modification to somewhere public?
Of course, we do not want to make any ABP Commercial source code public, and we need to make sure we protect our own source code, while still satisfying ABP Framework LGPL licence.
Thanks, got it.
Would you have any suggestion on how to implement this in ABP Commercial, based on your experience in ASPNET ZERO?