On Tue, Aug 5, 2025 at 6:49 AM Serhat Sevki Dincer <jfcga...@gmail.com> wrote:
> - MPL is a file based license, covering only files released under it. Unlike > GPL, it does not “spread” to other files in a project that uses MPL libraries. > > - Users of MPL libraries (who do not own copyright on those libraries) must > disclose their changes “only” on those MPL libraries IF they want to modify > AND distribute those MPL licensed files in some form (like source code or an > executable). > > - If you don’t modify an MPL library source you don’t have to do anything, > you can use it in anything including your closed source commercial software. > Many commercial software regularly use MPL licensed libraries. > > I think it is a great and flexible library license, it ensures > fixes/improvements on the library only to be contributed back to the library. > That’s why I chose it for almost all of my open source work. TIL how much better MPL is than I thought before. Thanks for posting! -j -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/CAA40n-XPtTkrQm3WWQrqf%3DjkQAZb%2Bzm30rpiPOnZSyEZUANffw%40mail.gmail.com.
