It seems like you can trivially get around the intended rules of the MPL 2.0 by simply putting your changes in a separate file… and then you don’t have to share 99% of your modifications?
MPL 2.0, what modifications do you have to make available?
opensource.stackexchange.comLet's say I have a project foo that's licensed as MPL 2.0.
// work.go
package foo
func work(a, b int) int {
return a+b
}
Alice is a consumer of my library. She comes up with a different way to ...
You must log in or register to comment.