stefan-hdt

Generally, if you do not change components under copyleft licenses (e.g. GPL-2.0) you do not have to provide the (changed) source code. But using your component "CleanRL" together with dependencies...

Yes, you are fine licensing CleanRL unter MIT. This gives anyone who wants to use your software a lot of flexibility - if that is what you intend to achieve....

Thanks for your reply. And sorry for mispelling your last name. :-) I'll do better next time. Just to give you some background information of me: I am a lawyer...

@cowtowncoder I understand that using the unmodified license template is very convenient for programmers. And, of course, putting copyright and license information in each source code file becomes a problem...

There might be limitations in using the program. That depends whether you can fulfill the license conditions of the LGPL-3.0-or-later. If so, it does not affect the program itself. But...

Thanks a lot.

It is not clear whether the GPL-2.0 is incompatible with the Apache-2.0. Both the Free Software Foundation (FSF) and the Apache Software Foundation (ASF) have different opinions on this matter....

Same problem here. I am looking for a license text with copyright information.