We are using ABP Commercial Identity Pro module, but we intend to modify Volo.Identity module, https://github.com/abpframework/abp/tree/dev/modules/identity, in our own private application. We plan to include Volo.Identity module as source code in our code, make quite a bit changes. ABP framework is on LGPL licence. In the guide, https://github.com/abpframework/abp/blob/dev/docs/en/Customizing-Application-Modules-Guide.md, it mentioned to include source code option.
Are we allowed to include source code of ABP Framework module and modify? What's our obligations?
6 إجابة (إجابات)
-
0
As noted in the source code section, you are welcome to simply include the code and make changes freely. We ask only that you do not share the commercial source code with public developers - internal is fine.
-
0
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.
-
0
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.
-
0
ABP Framework
-
0
Hello Richard, I see you have closed this ticket but I would like to add that we discussed your case internally and it is safe for you to make modifications to the code as you wish, without the need to publish the changes publically. We intend to change these module licenses to MIT in the future anyway. So please take this post as written consent that you may do so. Thanks
-
0
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.
